Java Runtime: 1.6.0_25 Sun Microsystems Inc. C:\Program Files\Java\jdk1.6.0_25\jre
[22/Nov/2013:14:29:08 SGT] IMQ_HOME=D:\GlassFishESBv22\glassfish\imq
[22/Nov/2013:14:29:08 SGT] IMQ_VARHOME=D:\GlassFishESBv22\glassfish\domains\domain1\imq
[22/Nov/2013:14:29:08 SGT]
[22/Nov/2013:14:29:08 SGT] Java Heap Size: max=4019584k, current=4019584k
[22/Nov/2013:14:29:08 SGT] Arguments: -port 7676 -name imqbroker -imqhome D:\GlassFishESBv22\glassfish\imq -varhome D:\GlassFishESBv22\glassfish\domains\domain1\imq -libhome D:\GlassFishESBv22\glassfish\imq\lib -useRmiRegistry -rmiRegistryPort 8686 -save -silent
[22/Nov/2013:14:29:08 SGT] Embedded Broker
[22/Nov/2013:14:29:08 SGT] [B1202]: Broker broker1 is running in HA mode as part of the cluster1 cluster
[22/Nov/2013:14:29:08 SGT] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
[22/Nov/2013:14:29:08 SGT] [B1060]: Loading persistent data...
[22/Nov/2013:14:29:08 SGT] Using plugged-in persistent store:
version=410
brokerid=broker1
database connection url=jdbc:ha-jdbc:Derbyimq
database user=imqdb
[22/Nov/2013:14:29:08 SGT] [B1170]: Auto Creation of plugged-in persistent store is enabled
imq log.txt
However, during the startup of the Glassfish Application Server, the following exception was occured and the Glassfish Application server was unable to start.
According to your ha-jdbc configuration file, the 2 databases in your cluster refer to the same database instance. This is guaranteed to result in lock acquisition failures.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
I am trying to configure Open Message Queue database store to use HA JDBC in Glassfish Server v2.1.
Below is the configuration I have done:
config.properties
ha-jdbc-Derbyimq.xml
imq log.txt
However, during the startup of the Glassfish Application Server, the following exception was occured and the Glassfish Application server was unable to start.
server.log
Please assist me whenever possible. Thank you !
According to your ha-jdbc configuration file, the 2 databases in your cluster refer to the same database instance. This is guaranteed to result in lock acquisition failures.