AS startup - JMS service startup failed
After sucessful instalation of AS7 on sparc Solaris 8, I've got error during startup.
[10/Jul/2003:16:42:12] INFO ( 1145): CORE1116: Sun ONE Application Server 7.0.0_01
[10/Jul/2003:16:42:13] INFO ( 1146): CORE3016: daemon is running as super-user
[10/Jul/2003:16:42:18] INFO ( 1146): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.1_01] from [Sun Microsystems Inc.]
[10/Jul/2003:16:42:56] INFO ( 1146): JMS5035: Timed out after 30000 milliseconds while trying to verify if the JMS service startup succeeded.
[10/Jul/2003:16:42:56] INFO ( 1146): JMS5036: More details may be available in the log file for the JMS service broker instance domain1_server1. Please refer to the JMS provider documentation for the exact location of this log file.
[10/Jul/2003:16:42:56] SEVERE ( 1146): JMS5024: JMS service startup failed.
[10/Jul/2003:16:42:56] SEVERE ( 1146): CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:247)
at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
Caused by: com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:231)
... 2 more
Caused by: javax.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:183)
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:136)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:145)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:86)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:47)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:46)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:101)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:501)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:930)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1482)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:403)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:234)
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:733)
at com.iplanet.ias.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:284)
at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:224)
... 2 more
[10/Jul/2003:16:42:56] SEVERE ( 1146): CORE3186: Failed to set configuration
This seems to be the same problem as one described in: http://swforum.sun.com/jive/thread.jsp?forum=68&thread=20049
Double check JMS port assignments - port might already be in use by some other process and should be changed.
Hope this helps...
Similar Messages
-
JMS5024: JMS service startup failed.
I have created a hellowworld.jsp. I deployed the project using server Sun Java Application Server Edition 8.1 and Type exploded. The deploy was successful. When I try to start the sun Java Application Server Edition 8.1, I am receiving a JMS5024: JMS service startup failed SEVERE error. Any help would be appreciated. The error is below:
Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
SEVERE: JMS5024: JMS service startup failed.
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: Feb 21
recursive call into SystemOutandErrhandler
java.lang.RuntimeException: recursivecall
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:189)
at java.io.PrintStream.write(PrintStream.java:260)
at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395)
at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136)
at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146)
at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204)
at java.io.Writer.write(Writer.java:126)
at java.util.logging.StreamHandler.publish(StreamHandler.java:191)
at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:87)
at java.util.logging.Logger.log(Logger.java:424)
at java.util.logging.Logger.doLog(Logger.java:446)
at java.util.logging.Logger.log(Logger.java:469)
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:198)
at java.io.PrintStream.write(PrintStream.java:260)
at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
at java.util.logging.StreamHandler.flush(StreamHandler.java:224)
at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88)
at java.util.logging.Logger.log(Logger.java:424)
at java.util.logging.Logger.doLog(Logger.java:446)
at java.util.logging.Logger.log(Logger.java:469)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:285)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
SEVERE: JMS5024: JMS service startup failed.
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
SEVERE: JMS5024: JMS service startup failed.
Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
SEVERE: JMS5024: JMS service startup failed.
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
SEVERE: JMS5024: JMS service startup failed.
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
... 5 more
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFa
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
... 5 more
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
... 5 more
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
... 5 more
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
... 5 more
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
SEVERE: Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
SEVERE: Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.ja
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
SEVERE: Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
SEVERE: Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
SEVERE: Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
SEVERE: Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)Hi
successful. When I try to start the sun Java
Application Server Edition 8.1, I am receiving a
JMS5024: JMS service startup failed SEVERE error. Any
help would be appreciated. The error is below:Could you share your MQ broker log file [$AS_INSTALL_DIR/domains/domain1/imq/instances/imqbroker/log/log.txt]? Does this error occur after you had installed the jsp app? Was the earlier shutdown a clean shutdown? Could you check and see if there are any jms processes around[ ps -efa | grep
imqbrokerd] ?
>
WARNING: Feb 21, 2005 11:34:38 AM
com.sun.enterprise.server.ss.ASLazyKernel
startASSocketServices
SEVERE: UnknownException during startup. Disable
quick startup by setting system property
com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleExceptionIs AS startup successful if you disable application server lazy startup using the above system property?
--Siva. -
Folks,
I am having problem starting the application server after trying to add the following JVM options
-DproxyHost=<my_host>.<my_domain> -DproxyPort=80
OK, it didn't work, so I decided to remove the above options and back to where it was. Since then, I am unable to start the server. Below is the error log:
[10/Nov/2004:18:12:00] INFO ( 1110): CORE1116: Sun ONE Application Server 7.0.0_03c
[10/Nov/2004:18:12:00] INFO ( 1111): CORE3016: daemon is running as super-user
[10/Nov/2004:18:12:03] INFO ( 1111): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2_04] from [Sun Microsystems Inc.]
[10/Nov/2004:18:12:05] SEVERE ( 1111): JMS5024: JMS service startup failed.
[10/Nov/2004:18:12:05] SEVERE ( 1111): CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: congo.abc.com.au: congo.abc.com.au
at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:247)
at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
Caused by: java.net.UnknownHostException: congo.abc.com.au: congo.abc.com.au
at java.net.InetAddress.getLocalHost(InetAddress.java:1191)
at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:148)
... 2 more
[10/Nov/2004:18:12:05] SEVERE ( 1111): CORE3186: Failed to set configuration
I have tried the followings: change the JMS port, increase time out, increase memory heaps AND nothing work.
Appreciate any help.
VQCheck for lock file blocking JMS service startup in /var/opt/imq/instances/domain1_server1
I found it was causing me problems after rebooting without stopping the app server.
Cheers,
Ed -
Hello All,
Can anyone please, please help me out?!!! I really would appreciate any possible help. I've searched every where seeking a solution and have yet to have found one.
I cannot get appServer8 up and running without a "server startup failed" error. I am running WinDozeXP Pro.
I tried re-installing, seperate bundle and full bundle downloads, checking system/global variables, path/classpath for spaces and quotes, followed all troubleshooting docs, checked the <http-listener> default ports in the domain1/config/domain1.xml
Startup shows: Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Domain domain1 is ready to receive client requests. Additional services are being started in background.
Press any key to continue . . .
Shut down shows: The domain (domain1) isn't running.
CLI157 Could not stop the domain domain1.
Press any key to continue . . .
Server log shows:
[#|2005-06-05T13:28:06.062-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/jdk1.5.0_03\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/jdk1.5.0_03/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\jdk1.5.0_03\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\jdk1.5.0_03\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\System32;C:\apache-ant-1.6.2\bin;C:\apache-ant-1.6.2\bin;C:\apache-ant-1.6.2\bin
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/jdk1.5.0_03/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-06-05T13:28:12.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2005-06-05T13:28:12.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2005-06-05T13:28:12.984-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-06-05T13:28:13.625-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-06-05T13:28:14.234-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2005-06-05T13:28:14.234-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2005-06-05T13:28:15.015-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
[#|2005-06-05T13:28:15.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
[#|2005-06-05T13:28:15.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
[#|2005-06-05T13:28:16.250-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2005-06-05T13:28:19.937-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2005-06-05T13:28:20.312-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\MEjbApp.ear for autodeployment.|#]
[#|2005-06-05T13:28:22.187-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2005-06-05T13:28:22.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-06-05T13:28:22.218-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2005-06-05T13:28:22.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 1375 msec, Total EJB Compiler Module Time: 31 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 31 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-06-05T13:28:22.906-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2005-06-05T13:28:23.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added MEjbApp]|#]
[#|2005-06-05T13:28:23.140-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:23.171-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2005-06-05T13:28:23.328-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 73269464414158848|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]
[#|2005-06-05T13:28:23.859-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2005-06-05T13:28:27.875-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-06-05T13:28:27.875-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2005-06-05T13:28:27.984-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 4438 msec, Total EJB Compiler Module Time: 4016 msec, Portion spent EJB Compiling: 90%
Breakdown of EJBC Module Time: Total Time for EJBC: 4016 msec, CMP Generation: 641 msec (15%), Java Compilation: 3297 msec (82%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-06-05T13:28:28.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2005-06-05T13:28:28.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added __ejb_container_timer_app]|#]
[#|2005-06-05T13:28:28.250-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:28.265-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2005-06-05T13:28:28.406-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 73269464784896000|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2005-06-05T13:28:29.109-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
[#|2005-06-05T13:28:29.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
[#|2005-06-05T13:28:29.281-0700|WARNING|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-06-05T13:28:29.421-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
[#|2005-06-05T13:28:29.453-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
[#|2005-06-05T13:28:29.453-0700|WARNING|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-06-05T13:28:29.484-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
[#|2005-06-05T13:28:29.578-0700|INFO|sun-appserver-pe8.1_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
[#|2005-06-05T13:28:31.046-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:31.062-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:31.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:31.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:31.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:31.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]4 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:101)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.io.IOException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
at com.sun.enterprise.admin.jmx.remote.server.JmxConnectorServerDriver.startConnectorServer(JmxConnectorServerDriver.java:173)
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:93)
... 3 more
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
... 5 more
Caused by: java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
... 9 more
Caused by: java.net.ConnectException: Connection timed out: no further information
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:175)
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 sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
... 14 more
|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2005-06-05T13:28:52.546-0700|WARNING|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:118)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:414)
at com.sun.enterprise.server.PEMain.run(PEMain.java:317)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:52.562-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2005/06/05 13:28:52]|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2005-06-05T13:28:53.015-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
[#|2005-06-05T13:28:53.015-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
Thanks in Advance,
~StacyIs your windoze machine on the network ? Does this machine have a firewall ? Does it have a static IP address or a DHCP ? Can you check if port 8686 is being used by some other process ?
If you have checked all of the above, not really sure what else could be the problem. I have installed AS8.1on a wondoze xp laptop and it's running merrily. -
Sun AppServer 8-Startup failed
Hello All,
Can anyone please, please help me out?!!!
I cannot get appServer8 up and running without a "server startup failed" error. I am running WinDozeXP Pro.
I tried re-installing, seperate bundle and full bundle downloads, checking system/global variables, path/classpath for spaces and quotes, followed all troubleshooting docs, checked the <http-listener> default ports in the domain1/config/domain1.xml
Startup shows: Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Domain domain1 is ready to receive client requests. Additional services are being started in background.
Press any key to continue . . .
Shut down shows: The domain (domain1) isn't running.
CLI157 Could not stop the domain domain1.
Press any key to continue . . .
Server log shows:
[#|2005-06-05T13:28:06.062-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/jdk1.5.0_03\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/jdk1.5.0_03/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\jdk1.5.0_03\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\jdk1.5.0_03\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\System32;C:\apache-ant-1.6.2\bin;C:\apache-ant-1.6.2\bin;C:\apache-ant-1.6.2\bin
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/jdk1.5.0_03/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-06-05T13:28:12.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2005-06-05T13:28:12.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2005-06-05T13:28:12.984-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-06-05T13:28:13.625-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-06-05T13:28:14.234-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2005-06-05T13:28:14.234-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2005-06-05T13:28:15.015-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
[#|2005-06-05T13:28:15.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
[#|2005-06-05T13:28:15.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
[#|2005-06-05T13:28:16.250-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2005-06-05T13:28:19.937-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2005-06-05T13:28:20.312-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\MEjbApp.ear for autodeployment.|#]
[#|2005-06-05T13:28:22.187-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2005-06-05T13:28:22.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-06-05T13:28:22.218-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2005-06-05T13:28:22.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 1375 msec, Total EJB Compiler Module Time: 31 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 31 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-06-05T13:28:22.906-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2005-06-05T13:28:23.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added MEjbApp]|#]
[#|2005-06-05T13:28:23.140-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:23.171-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2005-06-05T13:28:23.328-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 73269464414158848|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]
[#|2005-06-05T13:28:23.859-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2005-06-05T13:28:27.875-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-06-05T13:28:27.875-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2005-06-05T13:28:27.984-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 4438 msec, Total EJB Compiler Module Time: 4016 msec, Portion spent EJB Compiling: 90%
Breakdown of EJBC Module Time: Total Time for EJBC: 4016 msec, CMP Generation: 641 msec (15%), Java Compilation: 3297 msec (82%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-06-05T13:28:28.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2005-06-05T13:28:28.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added __ejb_container_timer_app]|#]
[#|2005-06-05T13:28:28.250-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:28.265-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2005-06-05T13:28:28.406-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 73269464784896000|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2005-06-05T13:28:29.109-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
[#|2005-06-05T13:28:29.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
[#|2005-06-05T13:28:29.281-0700|WARNING|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-06-05T13:28:29.421-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
[#|2005-06-05T13:28:29.453-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
[#|2005-06-05T13:28:29.453-0700|WARNING|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-06-05T13:28:29.484-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
[#|2005-06-05T13:28:29.578-0700|INFO|sun-appserver-pe8.1_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
[#|2005-06-05T13:28:31.046-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:31.062-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:31.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:31.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:31.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:31.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]4 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:101)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.io.IOException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
at com.sun.enterprise.admin.jmx.remote.server.JmxConnectorServerDriver.startConnectorServer(JmxConnectorServerDriver.java:173)
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:93)
... 3 more
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
... 5 more
Caused by: java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
... 9 more
Caused by: java.net.ConnectException: Connection timed out: no further information
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:175)
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 sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
... 14 more
|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2005-06-05T13:28:52.546-0700|WARNING|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:118)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:414)
at com.sun.enterprise.server.PEMain.run(PEMain.java:317)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:52.562-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2005/06/05 13:28:52]|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2005-06-05T13:28:53.015-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
[#|2005-06-05T13:28:53.015-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
Thanks in Advance,
~Stacy[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]4 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]|#]
is the start of your problem, but I expect you've guessed that.. Have you googled for the messages? is host romeo available on that port??? -
OC4J startup failed on AMD64 Fedora Core 5
The installation guide for JDeveloper10131 says:
"Note: <jdev_home>/j2ee/home/application-deployments is not available until you run java -jar oc4j.jar -install"
Running
"java -jar <jdev_home>/j2ee/home/oc4j.jar -install"
results in
"WARNING: System property "java.util.logging.manager" should be the name of a subclass of java.util.logging.LogManager
WARNING: Cannot cleanup application URLStreamHandlers.
OC4J startup failed
oracle.classloader.util.AnnotatedClassFormatError: oracle.j2ee.ws.client.ClientMessageBundle_fi (erroneous identifier)
Invalid class: oracle.j2ee.ws.client.ClientMessageBundle_fi
Loader: oracle.ws.client:10.1.3
Code-Source: /home/dan/lib/jdev10131/webservices/lib/wsclient.jar
Configuration: <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in /home/dan/lib/jdev10131/j2ee/home/oc4j.jar
Dependent class: oracle.classloader.util.XMLConfiguration
Loader: gnu.gcj.runtime.SystemClassLoader@1694307706
Code-Source: /home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar
Configuration: /home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar
at oracle.classloader.PolicyClassLoader.bulkLoadClasses (PolicyClassLoader.java:1538) [home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar, by gnu.gcj.runtime.SystemClassLoader@1694307706]
at oracle.classloader.util.XMLConfiguration.bulkLoadClasses (XMLConfiguration.java:888) [home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar, by gnu.gcj.runtime.SystemClassLoader@1694307706]
at oracle.classloader.util.XMLConfiguration.access$100 (XMLConfiguration.java:41) [home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar, by gnu.gcj.runtime.SystemClassLoader@1694307706]
at oracle.classloader.util.XMLConfiguration$Externals.load (XMLConfiguration.java:872) [home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar, by gnu.gcj.runtime.SystemClassLoader@1694307706]
at oracle.classloader.util.XMLConfiguration.endElement (XMLConfiguration.java:686) [home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar, by gnu.gcj.runtime.SystemClassLoader@1694307706]
at gnu.xml.aelfred2.SAXDriver.endElement (libgcj.so.7) [jre bootstrap, by jre.bootstrap:1.4.2]
at gnu.xml.aelfred2.XmlParser.parseETag (libgcj.so.7) [jre bootstrap, by jre.bootstrap:1.4.2]
at gnu.xml.aelfred2.XmlParser.parseContent (libgcj.so.7) [jre bootstrap, by jre.bootstrap:1.4.2]
at gnu.xml.aelfred2.XmlParser.parseElement (libgcj.so.7) [jre bootstrap, by jre.bootstrap:1.4.2]
at gnu.xml.aelfred2.XmlParser.parseContent (libgcj.so.7) [jre bootstrap, by jre.bootstrap:1.4.2]
at gnu.xml.aelfred2.XmlParser.parseElement (libgcj.so.7) [jre bootstrap, by jre.bootstrap:1.4.2]
at gnu.xml.aelfred2.XmlParser.parseDocument (libgcj.so.7) [jre bootstrap, by jre.bootstrap:1.4.2]
at gnu.xml.aelfred2.XmlParser.doParse (libgcj.so.7) [jre bootstrap, by jre.bootstrap:1.4.2]
at gnu.xml.aelfred2.SAXDriver.parse (libgcj.so.7) [jre bootstrap, by jre.bootstrap:1.4.2]
at gnu.xml.aelfred2.XmlReader.parse (libgcj.so.7) [jre bootstrap, by jre.bootstrap:1.4.2]
at oracle.classloader.util.XMLConfiguration.configureLoaders (XMLConfiguration.java:279) [home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar, by gnu.gcj.runtime.SystemClassLoader@1694307706]
at oracle.classloader.util.InitialLoadersFactory.populateLoaders (InitialLoadersFactory.java:389) [home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar, by gnu.gcj.runtime.SystemClassLoader@1694307706]
at oracle.classloader.util.InitialLoadersFactory.initLoaders (InitialLoadersFactory.java:230) [home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar, by gnu.gcj.runtime.SystemClassLoader@1694307706]
at oracle.classloader.util.InitialLoadersFactory.create (InitialLoadersFactory.java:167) [home/dan/lib/jdev10131/j2ee/home/lib/pcl.jar, by gnu.gcj.runtime.SystemClassLoader@1694307706]
at oracle.oc4j.loader.boot.BootStrap.main (BootStrap.java:26) [home/dan/lib/jdev10131/j2ee/home/oc4j.jar, by gnu.gcj.runtime.SystemClassLoader@1694307706]
at oracle.oc4j.loader.boot.BootStrap (method and line unknown).
at gnu.java.lang.MainThread (method and line unknown)."When I run the example file Start.jsp (with OC4J startup failed, i.e. there is no folder <jdev_home>/j2ee/home/application-deployments) I get the following (and a web page saying:"Error instantiating web-application
Application: login-LOGIN-webapp has been stopped"):
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
/home/dan/lib/jdev10131/jdev/bin/$/home/dan/jdevhome/system/oracle.j2ee.10.1.3.39.84/embedded-oc4j/config>
/usr/local/jdk1.5.0_10/bin/java -server -classpath /home/dan/lib/jdev10131/j2ee/home/oc4j.jar:/home/dan/lib/jdev10131/jdev/lib/jdev-oc4j-embedded.jar -Xverify:none -DcheckForUpdates=adminClientOnly -Xrs -Doracle.application.environment=development -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 -Doc4j.jms.usePersistenceLockFiles=false oracle.oc4j.loader.boot.BootStrap -config /home/dan/lib/jdev10131/jdev/bin/$/home/dan/jdevhome/system/oracle.j2ee.10.1.3.39.84/embedded-oc4j/config/server.xml
[waiting for the server to complete its initialization...]
Jan 18, 2007 12:09:37 PM com.evermind.server.jms.JMSMessages log
INFO: JMSServer[]: OC4J JMS server recovering transactions (commit 0) (rollback 0) (prepared 0).
Jan 18, 2007 12:09:37 PM com.evermind.server.jms.JMSMessages log
INFO: JMSServer[]: OC4J JMS server recovering local transactions Queue[jms/Oc4jJmsExceptionQueue].
07/01/18 12:09:41 SEVERE: ApplicationStateRunning.initConnector Error occurred initializing connectors. Exception is: Exception creating connection pool. Exception: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.mysql.jdbc.Driver
07/01/18 12:09:41 SEVERE: ApplicationStateRunning.initConnector Stack trace: oracle.oc4j.sql.DataSourceException: Exception creating connection pool. Exception: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.mysql.jdbc.Driver
at com.evermind.server.ApplicationStateRunning.initDataSourceConnectionPool(ApplicationStateRunning.java:2072)
at com.evermind.server.ApplicationStateRunning.initDataSourceConnector(ApplicationStateRunning.java:2017)
at com.evermind.server.ApplicationStateRunning.initConnector(ApplicationStateRunning.java:1272)
at com.evermind.server.ApplicationStateRunning.initConnectors(ApplicationStateRunning.java:345)
at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:206)
at com.evermind.server.Application.setConfig(Application.java:413)
at com.evermind.server.Application.setConfig(Application.java:314)
at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1853)
at com.evermind.server.ApplicationServer.initializeDeployedApplications(ApplicationServer.java:1608)
at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:990)
at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.resource.ResourceException: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.mysql.jdbc.Driver
at oracle.oc4j.sql.spi.ResourceAdapterImpl.createDataSourceConnectionPool(ResourceAdapterImpl.java:106)
at oracle.oc4j.sql.DataSourceUtils.getDataSourceConnectionPool(DataSourceUtils.java:326)
at com.evermind.server.ApplicationStateRunning.initDataSourceConnectionPool(ApplicationStateRunning.java:2053)
... 11 more
Caused by: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.mysql.jdbc.Driver
at oracle.oc4j.sql.config.DataSourceConfigUtils.createConnectionFactory(DataSourceConfigUtils.java:284)
at oracle.oc4j.sql.DataSourceConnectionPoolImpl.<init>(DataSourceConnectionPoolImpl.java:108)
at oracle.oc4j.sql.spi.ResourceAdapterImpl.createDataSourceConnectionPool(ResourceAdapterImpl.java:99)
... 13 more
Caused by: oracle.classloader.util.AnnotatedClassNotFoundException:
Missing class: com.mysql.jdbc.Driver
Dependent class: oracle.oc4j.sql.config.DataSourceConfigUtils
Loader: oc4j:10.1.3
Code-Source: /home/dan/lib/jdev10131/j2ee/home/lib/oc4j-internal.jar
Configuration: <code-source> in META-INF/boot.xml in /home/dan/lib/jdev10131/j2ee/home/oc4j.jar
This load was initiated at current-workspace-app.root:0.0.0 using the Class.forName() method.
The missing class is not available from any code-source or loader in the system.
at oracle.classloader.PolicyClassLoader.handleClassNotFound(PolicyClassLoader.java:2078)
at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1679)
at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1635)
at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1620)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at oracle.oc4j.sql.config.DataSourceConfigUtils.createConnectionFactory(DataSourceConfigUtils.java:281)
... 15 more
Jan 18, 2007 12:09:41 PM oracle.j2ee.util.LoggingUtils logAndReturnMessage
WARNING: Exception creating connection pool. Exception: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.mysql.jdbc.Driver
07/01/18 12:09:41 WARNING: Application.setConfig Application: current-workspace-app is in failed state as initialization failed.
java.lang.InstantiationException: Error occurred initializing connectors. Exception is: Exception creating connection pool. Exception: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.mysql.jdbc.Driver
Jan 18, 2007 12:09:41 PM com.evermind.server.ServerMessages warningApplicationInitializationFailed
WARNING: Exception initializing deployed application: current-workspace-app. Application: current-workspace-app is in failed state as initialization failed
Ready message received from Oc4jNotifier.
Embedded OC4J startup time: 18153 ms.
07/01/18 12:09:45 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
Target URL -- http://127.0.0.1:8988/login-LOGIN-context-root/faces/Start.jsp -
Hub startup failed due to licensing failure
Hi all.
I have just installed weblogic 6.0 sp1 on solaris 2.8. the web server starts
up and everything is hunky dory.
furthermore i downloaded collaborate 1.0.1 and installed it. the
installation went fine.
here is my problem. when i execute the startWeblogic.sh script in the hub,
Weblogic reports the following error:
<24-Apr-01 13:49:03 GMT+01:00> <Error> <WLC> <<Hub> ERROR: Hub startup
failed due to licensing failure.>
I get this problem using jdk122 and jdk130.
I cannot seem to find the problem.
Any feedback would be appreciated.
PS. My license.bea file looks as follows:
<?xml version="1.0"?>
<bea-licenses>
<license-group format="1.0" product="WebLogic Collaborate"
release="1.0">
<license
component="Core Server"
expiration="2001-05-24"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
signature="2tDDH3g1qXubdlfsahWRNrR6+tc=0MC0CFCoH/XUHiZuu+yhzpuzv6UFl
kJ44AhUA2/U26g1keq5nNoO00NC2u9ezWeA="
/>
</license-group>
<license-group format="1.0" product="wlpi" release="1.2">
<license
component="WebLogic Process Integrator"
expiration="2001-05-24"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
users="5"
signature="2tDDH3g1qXubdlfsahWRNrR6+tc=0MCwCFEh5H427STpTMX1y25DSmc65
b/MVAhQMNJo1ujoB6DudzF59hL/Tx2vbGQ=="
/>
</license-group>
<license
component="WebLogic"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="OFcm7oSc4jOT5vonluVZpsAHX2g=0MCwCFEmkcBweXEoxtJxzCIarx8i+
XBguAhQvCxM9E/T4HGfbIUfb4+OiNUYsPw=="
/>
<license
component="SSL/Export"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="OgS8PvglCrGr5xglLHeut8tE5vc=0MC0CFQDcxuNftALK3tZYuJw6hI15
GaqrBgIUcTi0vNzwoG1alTX1WXnvcX9EOiM="
/>
<license
component="2PC"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="CcdspC/3P0iELwWsETBWI/hEalw=0MC0CFQCtTlW7enw3kFZ7IU09jaa/
BVle5wIUSSfMk23C19hznredmfr+soEYiX0="
/>
<license
component="In-memory Replication - Servlet"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="c+mtrQ1ZuRiKeiELua/hSxvHqew=0MC4CFQC4qvLRsblTBvC5+IEVrDI1
Tek1YwIVAJ1NYWZE6xPHYyyVdlaXRJbhayCj"
/>
<license
component="In-memory Replication - EJB"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="ZenJ1bPXGf2N/Bq8XugDnDIP8sQ=0MC0CFQC+ayYQFxhpIMug7ZHtZIfS
vg4tlwIUHIYgx30GoxIdmR19cGddWM/mp3E="
/>
<license
component="EJB 1.1"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="XwwhoY5ysJ8h1pjzx23ujxZI9nY=0MC4CFQC2ATLeRv6cStQE1B/gyMUT
R6SRvQIVAMsQmtFC0/J4sF26n+B1zEyDOmv/"
/>
<license
component="EJB 2.0"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
units="5"
signature="ksI9jkE6gL9u8GdVEpZNQtOvjm8=0MCwCFBUir1rQV/FLNdc+4lfdIV1x
+xk5AhQpQwwWMfUd6TbL3UvB0u9DbZponQ=="
/>
<license
component="JMS"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="Z4Q4VngOAJSqSsr1UXC37DTOyVg=0MC0CFQCZtOwzb02hOSR3z9Hp6k86
nl1uFQIUfhy+ODL+Y7B9DkGDS7yT4zQPPpE="
/>
<license
component="Cluster"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="Tkg9CGjEik3MbkFmi6rPsSiO0J0=0MC0CFEAV5hPKLVSgV8YoeCEVu5m7
5ktkAhUA2lBI0PwiMigvK1E/pVS0vqmsy3w="
/>
<license
component="Clustered JMS"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="nEpfLZwWyM4Bo7UZZHE4hQgntMc=0MCwCFBKYtPvqZE18JdGBvU6cZomM
xW1cAhR3moJKg7FHMxvsZphQz5jVCahrfA=="
/>
<license
component="jDriver/MSSQLServer4"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="Dgw2DzDWyBNob6pJunUY1Xoz7c8=0MC0CFQC4PKj8UFoC3J0XuC7pmzRL
TtgP8QIUAhJF5DuvZ10zvf/6mxe0Ti/rG4c="
/>
<license
component="jDriver/Informix4"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="6O/i8fVnKIeVwzz+e0zUMQL5uRU=0MC0CFH+NK7nnRm+Qp+qRXZdeV2yF
6YxdAhUA3vch2xTdmM5Ao+00+IOR5f3jGH0="
/>
<license
component="jDriver/Oracle"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="NtSVpPAloTJqBstOWKVnuh3q0H4=0MC0CFA+2ny24Zdyrb0lsL3duwfEB
9zKMAhUAqDtTbLMN3QfJWUVhJr+NBQU/x/k="
/>
</license-group>
</bea-licenses>Gotta add listeners.ContextListener to your CLASSPATH
in Eclipse.
I don't think that package name is right. You've got
another problem besides your context XML.
%The context XML may not be the problem at all. Such tomcat errors are standard when it was unable to load required classes on startup.
The listeners all being interfaces, it's impossible to say whether it is the standard listeners or custom listener classes (regd in your web.xml) that's not being found on startup.
cheers,
ram. -
Biserver startup failed please help
Hi
while starting biserver the following error appeared in log file and server startup failed
Server start up failed: [nQSError: 46036] Internal Assertion: Condition m_pFile->Read(&*(bytes.begin() + sizeof(int32)), numChars * sizeof(uint16)) == numChars * siz
eof(uint16), file server/objectmodel/Src/SORpArchivePersistStream.cpp, line 349.
i am using custom rpd ( not paint.rpd).
what could be the possible reason for the above error
Thanks
MS
Message was edited by:
user617442it looks like a windows problem... if you google on it, you see the same problem with different services..
Dit you reboot your system etc?? -
Hi All,
I am getting the following error when starting the server:
IBM AIX RISC System/6000 Error: 13: Permission Denied
R3trans: connect check finished with error code 12
ora 27121
DB startup failed
What is to be done?
Plz help me with this.
Regards,
ArchanaHi Archana,
This look like an authorization issue, Check that all the Oracle services are running and the DB is online, check that the listener is running, check authorizations. You can also check dev_ms, dev_disp and dev_w0, for more info about the error.
Hope this help
Juan
Please reward with points if helpful -
'Dataguard remote process startup failed'
Hi
When I try to use the Data Guard to configure my Physical Database ( Which for testing purposes, is planned to have onthe same machind as the Primary) - gives me the error
'Dataguard remote process startup failed'
Please help me.!
Can anyone give me the details of how to create a physical standby from scratch.. considernig the fact that I am new to Oracle... I am donig it as per the documentation, but not able to start the standyby database which is on the same machine using the pfile...
Thanks
RadhikaAre you creating standby database using data guard manager through oracle managment server? If so, have you applied patches or not?
Here is the excerpt from metalink note : 204848.1
====
Data Guard Manager reports "Data Guard remote process startup failed." Error Dialog
Fact
Oracle Enterprise Manager Data Guard Manager 9.2.0.1.0
Symptom
"Data Guard remote process startup failed" error dialog in the Oracle
Enterprise Manager 'Create Configuration' Wizard is displayed when you
attempt to run Data Guard Manager and your environment is not setup
correctly.
Fix
Check and address the following items in the order listed.
1) Ensure the Oracle installations for both the primary and standby Oracle
Homes contain Perl.
On UNIX systems, verify this by looking in each Oracle Home for the
$ORACLE_HOME/Apache/perl/bin/perl file. On NT systems, look for the
file $ORACLE_HOME\apache\perl\5.00503\bin\mswin32-x86\perl.
If this file is present, Perl is installed; and proceed to step 2.
If not, then you must install the Perl that comes with Oracle.
Follow these steps to install Perl on both the primary and standby
Oracle Homes:
a. Run the Oracle Installer and choose the Oracle Home in question.
b. Choose the "Oracle9i Database 9.2.0.1.0" option.
c. Choose "Custom" for the installation type.
d. Under "Oracle Enterprise Manager Products 9.2.0.1.0", choose to
install the "Enterprise Manager Website 9.2.0.1.0" item.
e. Complete the install.
f. Verify that the Perl installation succeeded by checking for the
presence of the above file. If successful, proceed to step 2.
2) Ensure that all Data Guard Manager patches are installed in
the OEM installation.
These following two patches are independent of each other and must both be
installed on all versions of 9.2.0:
Patch Number 3409886 (supercedes Patch 2670975)
Patch Number 2671349
Download these patches from Oracle Support Services Website, Metalink,
http://metalink.oracle.com. Activate the "Patches" button to get the
patches Web page. Enter the Patch number and activate the "Submit"
button. The patches are listed for the Windows and Solaris operating
systems only. However, they are generic patches that will work on
other platforms.
After verifying that each patches are installed, proceed to step 3.
3) Ensure the Oracle Intelligent Agent is running on both the primary and
standby nodes.
The Agent must be running for Data Guard to function. Check it by
running agentctl status on the primary and standby nodes. If it is not
running, start it by running the command agentctl start. After verifying
that it is running on both nodes, proceed to step 4.
4) Ensure that the user specified in the primary and standby node preferred
credentials can successfully run an OEM job.
Data Guard Manager requires that OEM preferred credentials are specified
for both the primary and standby node. Furthermore, these credentials
must specify a user(s) who has read/write permissions in the primary
and standby Oracle Homes, respectively.
Note well: Databases that are on Windows NT/2000 require that the
the user(s) specified in the credentials must be granted
the "Log on as a batch job" privilege.
After checking that preferred node credentials are set correctly on both
nodes, run a test OEM job to verify that jobs are functioning properly.
Do this as follows:
a) Select the Create Job item in the OEM Console Job menu.
b) Give the job a name, select Node as the Target Type, select and
add the primary node as the target.
c) Go to the Tasks tab, select and add "Run OS Command".
d) Go to the Parameters tab and specify a simple OS command such
as ls on UNIX, or dir on NT.
e) Click Submit.
f) Once the job is finished, select the Jobs icon in the OEM Console
tree, select the History tab, and examine the Job output.
If it was successful, jobs are working and you can try the Data
Guard Create Configuration wizard again.
If the job failed, you must troubleshoot this problem and fix it
before continuing with Data Guard Manager.
5) If problems persist, obtain additional information and log a
Support Request (iTAR).
If everything in the previous steps is OK, and Data Guard Manager
continues to fail, additional information is required to diagnose the
problem. The following two items must be obtained and submitted to
Oracle Support Services:
a) OEM client tracing.
The Create Configuration wizard must be run again in trace mode.
This can be done by starting OEM from a command prompt (i.e., not
the Windows NT start menu) as follows:
oemapp trace console
Client tracing messages will appear in the command window from
which this command is run. Data Guard Manager should be started and
the Create Configuration wizard should then be run up to the point
where the error occurs. All tracing messages from Create
Configuration wizard start-up to this point should then be captured
and saved into a file.
b) Data Guard job output
The output from any failed Data Guard jobs must be captured. This
can be done as follows:
1) Select the Jobs icon in the OEM Console tree.
2) Select the History tab.
3) Double-click on the latest "DataGuardCtrlXXXX" job that has a
Failed status.
4) An Edit Job window will pop up; double-click on the Failed line
to obtain the output.
5) Put the output into a file.
If a Data Guard Manager bug is submitted, the tracing output and the
job output will be required.
====
Jaffar -
Hello together.
I have a problem with our Enterprise Portal 6.0 (SPS19).
This morning under System Administration -> Monitoring -> Knowledge Management -> Component Monitor under Services -> scheduler the ThreadPool was red with the status "startup failed".
The status was ok after a restart of the whole Portal.
Please let me know if there is a possibility to Restart the ThreadPool alone without a restart of the whole Portal.
Please let me know what can be the reason for a ThreadPool with red status.
Kind Regards,
MischaRemove the Battery for a couple of minutes, insert and keep the phone on charging for 15-20 minutes. Then switch the phone ON. If problem remains, you need to visit Nokia Care ..or think of buying a new phone ...as the existing phone is running on an OS which is long dead.
-
OC4J startup failed. Not sure how to fix it.
I am starting the oc4j container from eclipse. I was able to start it and debug it, but now I cannot. The only thing that change is that I installed the oracle client. Then I started getting the problems bellow.
I think that change several environment variables. How can I trouble shoot this problem. Thanks
OC4J startup failed
oracle.classloader.util.AnnotatedNoClassDefFoundError:
Missing class: oracle.security.xmlsec.saml2.core.Assertion
Dependent class: oracle.security.xmlsec.wss.saml2.SAML2AssertionToken
Loader: oracle.xml.security:10.1.3
Code-Source: /C:/oc4j/jlib/osdt_wss.jar
Configuration: <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in C:\oc4j\j2ee\home\oc4j.jar
The missing class is not available from any code-source or loader in the system.
at oracle.classloader.PolicyClassLoader.defineClass(PolicyClassLoader.java:2401)
at oracle.classloader.PolicyClassLoader.bulkLoadClasses(PolicyClassLoader.java:1637)
at oracle.classloader.util.XMLConfiguration$Externals.load(XMLConfiguration.java:895)
at oracle.classloader.util.XMLConfiguration.doPostProcessing(XMLConfiguration.java:914)
at oracle.classloader.util.XMLConfiguration.configureLoaders(XMLConfiguration.java:328)
at oracle.classloader.util.InitialLoadersFactory.populateLoaders(InitialLoadersFactory.java:410)
at oracle.classloader.util.InitialLoadersFactory.initLoaders(InitialLoadersFactory.java:235)
at oracle.classloader.util.InitialLoadersFactory.create(InitialLoadersFactory.java:176)
at oracle.oc4j.loader.boot.BootStrap.main(BootStrap.java:31)
Edited by: hh**** on Sep 12, 2012 4:04 PMMikeTheBorg wrote:
OK, I agree it's simpler for simple cases, but how do I do something like this:
JPEGImageEncoder jie = JPEGCodec.createJPEGEncoder(os);
JPEGEncodeParam jep = jie.getDefaultJPEGEncodeParam(bi);
jep.setDensityUnit(JPEGEncodeParam.DENSITY_UNIT_DOTS_INCH);
jep.setXDensity(1200);
jep.setYDensity(1200);
jep.setQuality(1, false);
jie.setJPEGEncodeParam(jep);
jie.encode(bi);
using ImageIO?
"Stupid" Eclipse+Maven refuse to compile this legacy code.It's an Eclipse error, not a Java/compiler error as such. To fix it, I believe you have to check your plug-in configuration -- imported packages here or exported packages there. Try adding "com.sun.image.codec.jpeg" to the imported packages. Something along those lines. Anyway, bottom line: this is not an issue with the code.
Furthermore, lookee here: GIAD -
DB startup failed when restart SAP sys
below was the error message when I restart my SAP sys.
Listener was running.
Oracle environment variables were correct.
Trying to start RD1 database ...
Log file: /home/rd1adm/startdb.log
/usr/sap/RD1/SYS/exe/run/startdb: Terminating with error code 12
DB startup failed
Please assist me regarding this.Log on to Sidadm user .
open a cmd prompt
type Sqlplus /nolog
connect /as sysdba
startup force
provide points
Regards
Balamurugan.P -
10.2.0.4 Agent startup fails "/libjvm.so, because No such file or directory
Hi Team,
10.2.0.4 Agent startup fails with below errors.Customer is having 30 agents in failover on the same system .Issue is happening for his newly installed agents and existing agents also.
When he stop few agents(like 26th agent and 27th agent... ) and he able to start the agent which is failed to start with below error.Issue looks like lack of some resources to start the agent.
oracle@sorapx2:/u00/app/oracle/ [AGENTFSP] emctl status agent
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
sh: 28400 Killed
/usr/lib/hpux32/dld.so: Cannot map text for library</pkg/FSP/u00/app/oracle/product/agent10g/jdk/jre/lib/IA64N/hotspot/libjvm.so>: mmap(0x0, 0xd51870, 0x5, 0x41, 3, 0x0) returns Not enough space.
oracle@sorapx2:/pkg/FSP/u00/app/oracle/product/agent10g/ [AGENTFSP] emctl start agent
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
sh: 20806 Killed
Agent is already running
oracle@sorapx2:/pkg/FSP/u00/app/oracle/product/agent10g/ [AGENTFSP] emctl upload agent
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
sh: 22988 Killed
/usr/lib/hpux32/dld.so: Cannot map text for library</pkg/FSP/u00/app/oracle/product/agent10g/jdk/jre/lib/IA64N/hotspot/libjvm.so>: mmap(0x0, 0xd51870, 0x5, 0x41, 3, 0x0) returns Not enough space.
+ No issues with space:
oracle@sorapx2:/pkg/FSP/u00/app/oracle/product/agent10g/ [AGENTFSP] bdf .
Filesystem kbytes used avail %used Mounted on
/dev/vgfsp1/lvol1 5144576 1973904 3146008 39% /pkg/FSP/u00
Agent also gives below error:
oracle@sorapx2:/u00/app/oracle/emdiag/log/ [AGENTGCP] emctl status agent
Error: failed to load /pkg/GCP/u00/app/oracle/product/agent10g/jdk/jre/lib/IA64N/server/libjvm.so, because No such file or directory
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
sh: 25923 Killed
/usr/lib/hpux32/dld.so: Cannot map text for library</pkg/GCP/u00/app/oracle/product/agent10g/lib32/libclntsh.so.10.1>: mmap(0x0, 0x21cded0, 0x5, 0x41, 3, 0x0) returns Not enough space.
Here emctl agent start command is trying to to load a 32 bit library in stead of the 64 bit.which is causing the issue:
There are a 32 Bit Library and a 64Bit Library available for the agent
oracle@vorakx2:/pkg/HYK/u00/app/oracle/product/agent10g/lib/ [HYK]
file libagtsh.so.1.0
libagtsh.so.1.0: ELF-64 shared object file - IA64
oracle@vorakx2:/pkg/HYK/u00/app/oracle/product/agent10g/lib32/ [HYK]
file libagtsh.so.1.0
libagtsh.so.1.0: ELF-32 shared object file - IA64
set below things properly still same problem.:
export ORACLE_HOME=<path of the agent10g installation>
export PATH=$ORACLE_HOME/bin:$PATH
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
Please suggest me further
+what emctl status agent is loading 32 bit library
+how to resolve the "Not enough space."
Environment Details:
10.2.0.4 OMS
10.2.0.4 Agent
Operating System HP-UX B.11.31 U (64)
SR 3-4636880901
Thanks
NarendraHi Narendra,
I just checked the link and it was ok. So maybe try again?
Copy/past Alain's post:
Hi,
-Buf cache is too high: SAM->kernel-> change dbc_pct_max from 50% to 10%.
-Whith GPM and command "extract" you can find which process consumme too much memory.
-Install lastest Quality Pack.
-With 32 bits processes, you can have problem with memory quadrant restriction. <= you have 64 bit so this is not of use to you
-Check kernel parameter related to max memory used by each process: maxdsiz
-Verify with swapinfo -tam and GPM -> memory.
See doc http://docs.hp.com/en/1218/mem_mgt.html
http://docs.hp.com/en/5580/Misconfigured_Resources.pdf
Alain.
Eric -
Hi
I am using sap business one 8.8. PL 15.Windows 7
I get the following error when i start xl reporter on the Server.SAP Business one is installed only on the server and no client machines are installed.
An error occurred during the process "Report Initialize".Description: (667) MetaInfo.xml not found!(Please contact the administrator to fix the repository connection)
XL Reporter startup failed!
Regards
FarheenTry the below suggested procedure from an SAP Note
1. Find the directory in which you installed the program. This would normally be: C:\Program Files\SAP Manage\SAP Business One\AddOns\XLR\XLReporter.
2. In the Client folder, run the program file ConnectionManager.exe.
3. In the first window that appears, choose one of the following:
Database server administrator password has been changed
Choose this option if the database server password has been changed and you need to change the encrypted password
set in the meta data repository. Since the changes that you make with this option only affect the tables in the meta data
repository, you will only have to perform this operation once on one of the clients.
Database server name and/or administrator password has been changed
Choose this option if you have moved the database(s) to a new server and you need to change the server name and/or
administrator password set in the XL Reporter meta data repository. Since the changes you make with this option affect
both the tables in the XL Reporter meta data repository and the XL Reporter Metainfo.xml file in the installation directory, you
must perform this operation on each client running XL Reporter.
4. Choose Next to continue.
5. Enter the following information:
In the Server field, enter the name of the new server. (This option is only available if you have selected the option, "Database server name and/or administrator password has been changed", in step 3 above.)
In the User field, enter a new user only if the user has changed on the database server. (This option is only availible if you have selected the option, "Database server name and/or administrator password has been changed", in step 3 above.)
In the Password field, enter a valid password.
6. Choose Next to continue. When the process is complete, the Operation Finished window appears.
The status information at the bottom of the window gives you information about the actions performed.
7. Choose Finish to exit.
Maybe you are looking for
-
IPhoto 11 will not open, I tried reloading my ILife but that did not work either. It says the certificate expired Mar 23, 2012
-
I recently upgraded my Macbook Pro to SL OS 10.6.8 and now have pink lines around the desktop borders and some menus. There is also a horrible red colour that appears in the background of photobooth and parts of Safari. The screen saver looks like an
-
Do the new versions of IPad support flash players?
I really like the IPad am in need of another mobile device but many programs require a flash player to view them. Do the new ones or the Mac books support Adobe Flash Players?
-
Hi all, Installing CRS I got the error: PRKC-1073 : Failed to transfer directory "/crs" to any of the given nodes "dwbd02 ". Error on node dwbd02:null Open the log: Log: installActions2010-05-31_04-50-09PM.log ------ INFO: Updating files in Oracle ho
-
I need help with my Itouch Screen. It's running erratic with white line running up and down. Tried restoring and resetting but nothing works. Any ideas? I don't know how this happened. Might have rubbed a smudge off screen while it was on. Woul