Application server stop running

Question

I installed J2EE1.4 bundled with application server8.2, it runs smoothly. However, after I reboot the machine, the application server could not be start. I got error after I issued:
asadmin start-domains domain1. The following error is what I got from server.log:
[#|2006-06-27T16:07:33.420-0400|INFO|sun-appserver-pe8.2|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.|#]
[#|2006-06-27T16:07:33.420-0400|SEVERE|sun-appserver-pe8.2|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.net.ConnectException: Connection refused
     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.net.ConnectException: Connection refused
     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:191)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:116)
     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:291)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:113)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:98)
     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:1949)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:745)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:315)
     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.net.ConnectException: Connection refused
     at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
     at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:525)
     at com.sun.enterprise.server.ss.ASClientSocketImpl.connect(ASClientSocketImpl.java:181)
     at java.net.Socket.connect(Socket.java:507)
     at java.net.Socket.connect(Socket.java:457)
     at java.net.Socket.<init>(Socket.java:365)
     at java.net.Socket.<init>(Socket.java:178)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:171)
     ... 21 more
|#]
I also opened log.txt under: .../domains/domain1/imq/instances/imqbroker/log, the following is the error messages from log.txt:
[27/Jun/2006:16:06:34 EDT] Using built-in file-based persistent store: /home/pzhang/java2/domains/domain1/imq/instances/imqbroker/
[27/Jun/2006:16:06:34 EDT] ERROR [B4032]: Failed to load transaction from store:
java.io.StreamCorruptedException: /home/pzhang/java2/domains/domain1/imq/instances/imqbroker/fs370/txn: Bad file magic number: 0; Expecting: 1431677610
[27/Jun/2006:16:06:34 EDT] ERROR [B3000]: Could not open persistent message store:
com.sun.messaging.jmq.jmsserver.util.BrokerException: Failed to load transaction from store
I did not edit any .xml file yet, any hints will be greatly appreciated.

Answer 1

Hi James,
Thanks for the reply. Yes i will lock all the users before we start with the downtime phase. But there is a problem in application server A1 and A2 that if you check in the dev_evt log, it states that
Thu Jul 10 10:17:44 2014
Trace File of External Event Raiser (Level=2, Append=0)
******* Complete Call: *******
sapevt.exe
SAP_TRIGGER_RDDIMPDP
-t
name=ZP1
pf=O:\usr\sap\ZP1\SYS\profile\DEFAULT.PFL
******* End of Call *******
EventID: SAP_TRIGGER_RDDIMPDP
*** ERROR ***: Cannot determine mshost
and CI dev_evt states that
Fri Jul 18 09:43:13 2014
Trace File of External Event Raiser (Level=0, Append=0)
******* Complete Call: *******
sapevt.exe
SAP_TRIGGER_RDDIMPDP
name=ZP1
******* End of Call *******
EventID: SAP_TRIGGER_RDDIMPDP
SAP message server host: ZP1CI
SAP message server service (new): 3900
SAP message server service (old): sapmsZP1
Event sent to server A1_ZP1_00
So is there any problem with it? or should i stop both A1 and A2 before start in downtime (uptime finished successfully)?
Regards,
Mohit