Much if not all of this information is already displayed in the output from
asadmin start-domain --verbose
and it would seem to be a nice improvement to always put that same info
into the server.log at start-up, regardless of the log level setting,
during "non-verbose" launches of the server.
- Tim
Lloyd Chambers wrote:
> Anissa,
>
> I don't know the answers here, but I like the idea. Tell the user:
> - JDK version
> - 32 bit or 64 bit
> - key settings like maximum memory
>
> I think you should file an RFE.
>
> I poked around in the JDK MBeans. You can get the version from the
> java.lang:type=Runtime MBean as getVmVersion();
>
> kmxcmd> get V*
> ---java.lang:type=Runtime---
> VmName=Java HotSpot(TM) Client VM
> VmVendor=Apple Inc.
> VmVersion=1.5.0_16-133
>
> Also useful:
> jmxcmd> get *
> ---java.lang:type=OperatingSystem---
> Arch=i386
> AvailableProcessors=2
> CommittedVirtualMemorySize=1378996224
> FreePhysicalMemorySize=1323405312
> FreeSwapSpaceSize=67108864
> MaxFileDescriptorCount=10240
> Name=Mac OS X
> OpenFileDescriptorCount=0
> ProcessCpuTime=4090000000
> TotalPhysicalMemorySize=4294967296
> TotalSwapSpaceSize=67108864
> Version=10.5.5
>
>
> Lloyd
> ..............................................
> Lloyd Chambers
> lloyd.chambers_at_sun.com
> GlassFish team, LSARC member
>
>
> On Oct 1, 2008, at 6:59 PM, Anissa Lam wrote:
>
>> Hi,
>>
>> I want to see how we can better inform user that they are starting up
>> the server with JRE instead of JDK when they run into errors, such
>> as accessing context sensitive help in the admin console.
>>
>> SEVERE: ApplicationDispatcher[] PWC1231: Servlet.service() for
>> servlet jsp threw exception
>> java.lang.NullPointerException
>> at
>> org.apache.jasper.compiler.Jsr199JavaCompiler.compile(Jsr199JavaCompiler.java:197)
>>
>> at
>> org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:361)
>> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:430)
>> at
>> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:608)
>>
>> at
>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
>>
>> at
>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473)
>> at
>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:366)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
>>
>> When i tried to help resolving the issue #6125 , i can't even tell
>> whether they are running JRE or JDK, or which version of JDK the
>> server is using, just by looking at server.log. Should we add such
>> information in server.log ?
>> In v2, I can at least look at asenv.conf to find out which jdk the
>> server is using, but in v3, i can't do that anymore.
>>
>> I have looked at the QuickStart Guide and quickly looked at
>> Administration Guide, I don't see anywhere that mentions about what
>> JDK version is supported or if JRE is fine to use or what problem
>> user may run into if they use JRE. Should we include this
>> information ? If not in quick start guide, should be available
>> somewhere.
>> Just want to see if you have any idea to help user to resolve issues
>> like this.
>>
>> thanks
>> Anissa
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>