Skip to Main Content

Java EE (Java Enterprise Edition) General Discussion

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Sun ONE AppServer doesn't start anymore, it's doing my head in

843833Jan 7 2005 — edited Jan 18 2005
Hi, can anyone help please,

The AppServer was running nicely a couple of months ago, but recently it just wouldn't start. I've tried everything including:
- multiple restarts
- uninstalling (ensuring registry is cleaned out) and reinstalling
- removing old (ensuring registry is cleaned out) and installing 2005Q1.
- changing ports for the JMS default host (the same thing happens on all ports).
- stopping firewalls on PC.
- monitored port 7676 via Windows PortReporter utility, found that there always seems to be a SYN SENT for the appserv.exe process but never gets to ESTABLISHED state, typically goes to CLOSE WAIT. There's also a java.exe process that runs at startup gets to the LISTENING state and never changes, even after shutdown. I typically have to kill the imqbrokersvc and java processes after the server fails to start.

Here's a section of the port report stats
==============================

(appserv.exe)

PID Port Local IP State Remote IP:Port
1544 TCP 1699 127.0.0.1 LISTENING 0.0.0.0
1544 TCP 1699 127.0.0.1 ESTABLISHED 127.0.0.1:1700
1544 TCP 1701 127.0.0.1 SYN SENT 127.0.0.1:7676
1544 TCP 1702 127.0.0.1 ESTABLISHED 127.0.0.1:1704

(java.exe)

PID Port Local IP State Remote IP:Port
1540 TCP 1713 0.0.0.0 LISTENING 0.0.0.0
1540 TCP 1714 0.0.0.0 LISTENING 0.0.0.0
1540 TCP 7676 0.0.0.0 LISTENING 0.0.0.0

I'm working on a Windows XP SP2 OS, with the McAfee Security Centre suite (firewall, virus shield, privacy).

The problem seems to be related to the JMS service, I'm pulling my hear out boo hoo hoo :-(. Please please please, can somebody help, I'll forever be in your debt :)

Here's the failed message on startup.
===============================
Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Timeout waiting for domain domain1 to go to starting state.
CLI156 Could not start the domain domain1.
Press any key to continue . . .


Here's the interesting section from the domain1 server.log
==============================================

[#|2005-01-07T05:13:55.171+0000|INFO|sun-appserver-pe8.1|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]

[#|2005-01-07T05:13:55.171+0000|INFO|sun-appserver-pe8.1|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory C:\Sun\AppServer\imq\var\instances|#]

[#|2005-01-07T05:13:55.171+0000|INFO|sun-appserver-pe8.1|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]

[#|2005-01-07T05:13:55.171+0000|SEVERE|sun-appserver-pe8.1|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.lang.NumberFormatException: For input string: "<lots of blank spaces>"
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:427)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:54)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.lang.NumberFormatException: For input string: "<lots of blank spaces>"
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:176)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:101)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:54)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:61)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:281)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:613)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1194)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1894)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:712)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:293)
at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:783)
at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:335)
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:396)
... 3 more
Caused by: java.lang.NumberFormatException: For input string: "<lots of blank spaces>"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:468)
at java.lang.Integer.parseInt(Integer.java:518)
at com.sun.messaging.jmq.io.PortMapperTable.read(PortMapperTable.java:238)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:170)
... 21 more

Here's the output in the imq/instances/imqbroker/log
=========================================

Java Runtime: 1.4.2_06 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
[07/Jan/2005:04:27:34 GMT] License: Sun Java(tm) System Message Queue 3.6 Platform Edition
[07/Jan/2005:04:27:34 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[07/Jan/2005:04:27:34 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[07/Jan/2005:04:27:34 GMT] Windows XP 5.1 x86 EDWINLPT (2 cpu) Edwin
[07/Jan/2005:04:27:34 GMT] Java Heap Size: max=194432k, current=16256k
[07/Jan/2005:04:27:34 GMT] Arguments: -name imqbroker -port 7676 -bgnd -silent
[07/Jan/2005:04:27:34 GMT] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
[07/Jan/2005:04:27:34 GMT] [B1060]: Loading persistent data...
[07/Jan/2005:04:27:34 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
[07/Jan/2005:04:27:34 GMT] WARNING [B3164]: The portmapper service got an exception processing a request from client 127.0.0.1. The client may need to attempt the connection again:
java.net.SocketException: socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:408)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:450)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:182)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at com.sun.messaging.jmq.jmsserver.service.PortMapper.run(PortMapper.java:429)
at java.lang.Thread.run(Thread.java:534)
[07/Jan/2005:04:27:34 GMT] [B1136]: Processing stored transactions
[07/Jan/2005:04:27:34 GMT] [B1013]: Auto Creation of Queues is Enabled
[07/Jan/2005:04:27:34 GMT] [B1151]: Loading destination mq.sys.dmq [Queue] with 0 messages
[07/Jan/2005:04:27:34 GMT] [B1152]: Loading of destination mq.sys.dmq [Queue] complete
[07/Jan/2005:04:27:34 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
[07/Jan/2005:04:27:34 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[07/Jan/2005:04:27:34 GMT] [B1039]: Broker "imqbroker@EDWINLPT:7676" ready.
[07/Jan/2005:04:27:36 GMT] WARNING [B3164]: The portmapper service got an exception processing a request from client 127.0.0.1. The client may need to attempt the connection again:
java.net.SocketException: socket closed at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:408)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:450)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:182)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at com.sun.messaging.jmq.jmsserver.service.PortMapper.run(PortMapper.java:429)
at java.lang.Thread.run(Thread.java:534)

Tried to provide as much info as I could, hope it helps. I'm desperate. Thanks, again for any assistance. Cheers.
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Feb 15 2005
Added on Jan 7 2005
9 comments
426 views