If your Glassfish v2.1 won't start...
If your Glassfish v2.1 won't start and the problem persists, there is probably a problem with your embedded JMS broker. I found in my logfiles the following hint:
[#|2010-01-14T10:27:36.227+0100|SEVERE|sun-appserver9.1|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;_RequestID=e2ff9fe6-ceb2-4436-bc22-5b88ed5dd49b;|RAR6035 : Resource adapter start failed : {0}
javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:476)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:135)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.(ActiveInboundResourceAdapter.java:131)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.(ActiveJmsResourceAdapter.java:247)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:107)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:300)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:445)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:224)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:428)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:442)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:120)
at com.sun.enterprise.server.PEMain.run(PEMain.java:411)
at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:268)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:472)
... 18 more
|#]
The solution is simple: removal of the
glassfish-v2/domains/domain1/imq/instances/imqbroker/lock file and restart the server.
The cause of the problem is frequent change of the ipadress and booting glassfish without network on linux.
Posted at 10:55AM Jan 14, 2010
by Adam Bien in Java / JEE / Architecture |
[my tweets] 
Rss My book: Real World Java EE - Rethinking Best Practices
In addition to the information provided by Adam. If for some reasons the "lock" file is not under the specified directory, you can also remove from the same directory the transaction related files. The files have a 'trans' prefix. In some cases the files are corrupted when Glassfish is not properly shutdown.
Gesendet von Yves do Rego am January 14, 2010 at 11:21 PM CET #