Sun Java System Application Server crashes 1

[normm]

Hi all I'm currently working with a:-
Sun Java™ System Application Server Platform Edition 8.2
which for some unknown reason keeps hanging at random intervals.

during normal operation the the program hosted on the application server appears to become unavailable for no apparent reason - the problem is compounded by the unavailability of the admin console as well.

after the application server is stopped and re-started the problem appears to dissapear.

any help greatly appreciated

Normm

 

[timw]

Are you starting it with enough memory for the JVM? Maybe it is running out.

Tim

 

[normm]

Hi tim,

we have left the server on default settings and think that this should be enough. The machine that the system is running on is stupidly fast with 2gb of ram - we are wondering more if this behaviour can be caused by a confict with other programs installed on this machine namely a clarion built app.

port 3700 has been mentioned as a listener port and we are wondering if another program is attempting to use this too and causing the conflict.

 

[timw]

Well, if you want to know what ports are in use by other apps, use a port sniffer. There is a free one for windows at

http://www.nirsoft.net/utils/cports.html

What is the default JVM max heap setting?

Tim

 

[stevexff]

Have you looked at the server logs? Does something happen just prior to the hang-up?

Steve

[small]"Every program can be reduced by one instruction, and every program has at least one bug. Therefore, any program can be reduced to one instruction which doesn't work." (Object:erlDesignPatterns)[/small]

 

[normm]

Thanks for the help guys - is this the information you requested?

JvmHeapSizeDescription: The JVM's memory heap size
Current: 64,618,496 bytes
High Water Mark: 64,618,496 bytes
Low Water Mark: 0 bytes
Upper Bound: 518,979,584 bytes
Lower Bound: 0 bytes

Normm

 

[timw]

So it's got plenty of bytes to play with. Next step is to check that port number you think might be clashing.

Tim

 

[normm]

appserv.exe 2584 TCP 3700 0.0.0.0 0.0.0.0 Listening C:\Sun\AppServer\lib\appserv.exe 11/21/2006 11:01:35 AM LNTGROUP\CoolServer A


that is the only entry for the port in question.

- hope this helps

normm

 

[stevexff]

Don't like to nag, but is there anything useful in the server.log file?

Steve

[small]"Every program can be reduced by one instruction, and every program has at least one bug. Therefore, any program can be reduced to one instruction which doesn't work." (Object:erlDesignPatterns)[/small]

 

[timw]

Oh yes, I forgot, and check the server.log file

Tim

 

[normm]

Sorry for the delays in posting these replies to your requests but Im currently bug hunting on this and other applications.

after looking at the server log file we only have one occurance of a severe error occuring in log file.

This problem appears to have been generated by using the server log viewer i.e.

Unabled to handle pre-compiled JSP '/jsp/LogDetail.jsp'. Expected pre-compiled classname: 'org.apac...


any other ideas.

 

[normm]

Hi again anyone,

we are still having the same problem and this time I may have found something more tangible.

Can anyone give me any further advice on this problem?

[#|2006-11-27T18:23:53.812+0000|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=15;|
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host  has failed. java.io.IOException: Unable to establish loopback connection
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
	at java.sql.DriverManager.getConnection(DriverManager.java:525)
	at java.sql.DriverManager.getConnection(DriverManager.java:193)
	at lib_server.DBProcessor.ConnectToDatabase(DBProcessor.java:112)
	at lib_server.CoolServer.ConnectToDatabase(CoolServer.java:69)
	at CoolCareServer.[URL unfurl="true"]WWWBroker.processRequest(WWWBroker.java:85)[/URL]
	at CoolCareServer.[URL unfurl="true"]WWWBroker.doPost(WWWBroker.java:79)[/URL]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
	at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
	at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
	at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
	at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
	at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
	at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
	at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:189)
	at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doProcess(ProcessorTask.java:604)
	at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:475)
	at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:371)
	at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:264)
	at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:281)
	at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:83)
|#]

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  EXCEPTION_ILLEGAL_INSTRUCTION_2 (0xc000001e) at pc=0x28331768, pid=3700, tid=2420
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# C  0x28331768
#
# An error report file with more information is saved as hs_err_pid3700.log
#
# If you would like to submit a bug report, please visit:
#   [URL unfurl="true"]http://java.sun.com/webapps/bugreport/crash.jsp[/URL]
#
[#|2006-11-28T07:15:14.996+0000|WARNING|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]

hope someone can help.

 

[timw]

Well, on the face of it, it looks like the MS SQL JDBC Driver has blown up. As you can see, it claims not to be able to establish a 'loopback' TCP/IP connection. Maybe this is a configuration issue with the JDBC driver. Perhaps you could write a small stand-alone test class to use this JDBC Driver direct and see if it works outside of the J2EE application server.

Tim

 

[normm]

Thanks timw will get onto it and let you know how things pan out

 

[normm]

Here is another interesting crash

[#|2006-11-28T07:15:30.780+0000|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]

[#|2006-11-28T08:55:59.121+0000|WARNING|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]

the server crashed at 8:30 am which appears to be a period of inactivity according to the server log

 

[timw]

That looks like a 'Warning' rather than an an error. Anyway, it's a tad unreasonable IMO for the app server to expect you to have no spaces on your path in windows, since the path to most installed applications in 'Program Files' contains one by default.

You could always try intalling your app server to a directory path which doesn't contain spaces to check it's startup behaviour in that case.

Tim