dev@glassfish.java.net

Re: Reminder: Re: REVIEW REQUEST: Troubleshooting Guide

From: Gail Risdal <Gail.Risdal_at_Sun.COM>
Date: Mon, 01 Dec 2008 18:43:06 -0800

Thanks for the followup, Wim.

Gail

Wim Verreycken wrote:

> Hi Gail,
>
> Inline.
>
> -----Original Message-----
> From: Gail.Risdal_at_Sun.COM [mailto:Gail.Risdal_at_Sun.COM]
> Sent: maandag 24 november 2008 21:59
> To: dev_at_glassfish.dev.java.net
> Subject: Re: Reminder: Re: REVIEW REQUEST: Troubleshooting Guide
>
> Hi Wim,
>
> Thanks very much! Your review is very helpful. A few comments inline.
>
> Gail
>
> Wim Verreycken wrote:
>
>
>>Hi gail,
>>
>>Here's the short version already :
>>
>>Page 1 : Enterprise Server -> Glassfish/Sun Java Enterprise Server
>>Page 10 : "Uniform Resource Locator (URL) -> URL will do fine, don't
>>pampetr/insult the reader
>
>
> Good point.
>
>
>>Page 16 : ...and functional "yet" :
>>Don't worry users about backwards compatibility.
>>+ there is limited EJB 3.1 Support ie. If EJB's Session Beans are packaged
>>within the war they will be operational in Prelude V3
>>(you can develop a session bean stateless or statefull, put it under a
>>package within the war, gf 3 Prelude will install them as EJB's
>
>
> Good point. I'll rewrite this content.
> This is not completely correct. I apologize.
> "put it under a package within the war, fg V3 prelude will install them as
> EJB's
>
> The following is copied from v3 Prelude output:
>
> 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or
> message driven bean.
> 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library
> jar.
> 3. If the jar file contains valid EJBs which are annotated with EJB
> component level annotations (@Stateless, @Stateful, @MessageDriven), please
> check server.log to see whether the annotations were processed properly.
>
> note
> I have strong doubts about wheter mesagedriven beans actually work though.
>
>
>>Page 17 : Please refer to chapter about visualVM here
>
>
> You mean refer to 'Troubleshooting Tools' section?
> OK
>
>
>>Page 18 : + permgen size : this is a common error (when a OutOfMemoryError
>
> :
>
>>Perm Genspace is throuwn
>
>
> I'll add this to 'What is Your System Configuration?'
>
>
>>Page 19 : could you explain briefly HOWTO log meesages to windows event
>
> log
>
>>Standard, this is NOT the case
>
>
> Can anyone on the list provide this information?
> I'll look into it
>
>
>>Page 20 : See page 19 : howto use Windows Event log to log errors.
>
>
> I'll add this.
>
>
>>+ ps-ef can proof usefull
>>+ Task manager can be usefull to kill process on windows systems
>
>
> I'll add this to 'Operating System Utilities'.
> OK
>
>
>>Page 22 :
>>Most common use of visual VM
>>Detect memory leaks : refer to visualVM home page
>
>
> Great - I'll add this.
>
>
>>Page 25 : If the specified port number is already taken ...
>>This is not correct. Gf V3 prelude will not attempt to take the next
>>available port.
>
>
> I'll remove this.
>
>
>>Page 26 : Note also : an entry can be made in the systems hosts file,
>>pointing 127.0.0.1 to the localhost. 127.0.0.1 is not proxied.
>
>
> I'll add this to the note.
>
>
>>
>>Page 29 : ~/.asadminprefs : don't know about this in prelude
>>On windows : no command line security by default. This is imo a security
>>breach in v3 predlude
>
>
> Can anyone comment on this?
>
>
>>Page 30 : V3 prelude does not automatically choose next available port on
>>windows
>
>
> I'll remove this.
>
>
>>Page 31 : "After" is the default on V3 prelude, I think
>
>
> I'm not totally clear on this.
> No it is correct. I went over that part to fast. + I checked it against a
> default installation to be sure.
>
>
>>Page 32 : netstat only reports the first instance (at least on windows)
>
>
> I'll change this.
> Thanks.
>
>
>>Page 34 : or you can kill it, refer to page 20
>
>
> I'll add this to 'Cannot Stop Domain Using ...'
> OK
>
>
>>Page 35 : Note that EJB Session Beans can be put in the war, just putting
>>the EJB and it's interpaces in a normal package under the web project/war
>>file
>
>
> Good point. I'll include this.
> Same as p16.
>
>
>>Page 37 : never used gf v3 with eclipse....
>>But netstat -ab can proof usefull here (shows pid)
>
>
> OK. I'll mention this.
>
>
>>Page 38 : instllation errors related to ant :
>>Depricated!
>>For V3 Prelude, one does not need to run ant -f setup.xml anymore
>
>
> I'll remove this.
>
>
>>P49 : no an expert on this, but I think there's a possibility using java
>>keytool?
>
>
> Can anyone provide this information?
>
>
>>In general :
>>
>>2 Common errors are not discussed :
>>- unsafe or unchecked operations :
>>Is it possible this error occurs on deployment when one chooses not to
>>precompile JSP's???
>>In this case :
>>Most common cause : lack of use of generics
>>Refer to JSR 14
>>
>
>
>>- java.lang.OutOfMemoryError : PermGen space :
>>increase perm gen space in server.xml
>
>
> Great - thanks for these suggestions. I'm a little confused about the
> first error - what's the error message (or is that included at the start
> of your text)?
> Well it occurs compiling java files or servlets conainting Collections
> without using generic.
> Fe. Set t = new HashSet();
> Instead of
> Set<User> us=new HashSet<User>();
> I'm curious as what will happen if a collection is specified this way in a
> JSP. Haven't tested yet.
>
>
>>Hope this helps...
>
>
> Oh yes, this helps tremendously - thanks!
>
> wim
>
>>wim
>>-----Original Message-----
>>From: Wim Verreycken [mailto:wim_at_pizzastop.be]
>>Sent: maandag 24 november 2008 20:46
>>To: dev_at_glassfish.dev.java.net
>>Subject: RE: Reminder: Re: REVIEW REQUEST: Troubleshooting Guide
>>
>>Hi Gail, yes I reviewed it, I'll send comments tonight/tomorrow, sorry for
>>the delay.
>>
>>Some questions remain open though, not an expert on all...
>>wim
>>-----Original Message-----
>>From: Gail.Risdal_at_Sun.COM [mailto:Gail.Risdal_at_Sun.COM]
>>Sent: maandag 24 november 2008 19:08
>>To: dev_at_glassfish.dev.java.net; users_at_glassfish.dev.java.net;
>>quality_at_glassfish.dev.java.net; docs_at_glassfish.dev.java.net
>>Subject: Reminder: Re: REVIEW REQUEST: Troubleshooting Guide
>>
>>Hello,
>>
>>Just a reminder that review comments are due close of business today PT.
>>
>>Thanks,
>>Gail
>>
>>Gail Risdal wrote:
>>
>>
>>>Hello,
>>>
>>>The GlassFish v3 Prelude Troubleshooting Guide is now available for
>>>review. Please review the document and provide feedback by close of
>>>business Monday Nov 24th PT (earlier would be even better). I know
>>>that's not much time, but that's the reality of the schedule.
>>>
>>>The document is available from the doc comments wiki:
>>>http://wiki.glassfish.java.net/Wiki.jsp?page=TroubleShootingGuideV3
>>>
>>>Please add your comments to the page or, given the short timeline, send
>>>them directly to me (gail.risdal_at_sun.com) - whatever is easiest for you.
>>>A copyedit will be performed to address editorial and formatting issues
>>>(and there are some), so I'm less concerned about those than I am about
>>>the accuracy of the content. That's the important thing. Some of the
>>>content was carried forward from the GlassFish v2 Troubleshooting Guide,
>>>and some is new.
>>>
>>>Because the document covers so many areas and technologies, providing a
>>>list of mandatory reviewers is not feasible in this case. Please review
>>>the content for your specific area of expertise and ownership.
>>>
>>>Thanks in advance! Your input is important and greatly appreciated.
>>>
>>>Gail
>>>+++++
>>>GlassFish Documentation
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>