Kbase P26200: Error starting Container for SonicMQ 5.0
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/12/2005 |
|
Status: Unverified
FACT(s) (Environment):
SonicMQ 5.x
SYMPTOM(s):
Error starting Container for SonicMQ 5.0
Unable to connect via Management Console
A lock was found on the "Domain1" domain storage.
There is either a Directory Service running already or the previous session was not properly terminated. If you are sure there is no other Directory Service running then you may remove the ./Domain1/data/_MFSystem/lock file and restart this program.
SQL Exception: Failed to start database '/sonic/SonicSoftware/SonicMQ5/SonicMQDB', see the next exception for details.
at db2j.r.h.tp_(Unknown Source)
at db2j.r.h.newCloudscapeSQLException(Unknown Source)
at db2j.r.h.generateCsSQLException(Unknown Source)
at db2j.r.c._eo(Unknown Source)
at db2j.r.c.<init>(Unknown Source)
at db2j.h.c.<init>(Unknown Source)
at db2j.h.b.getNewLocalConnection(Unknown Source)
at db2j.r.n.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:141)
at progress.message.db.JDBCDatabase.newConnection(:1020)
at progress.message.db.JDBCDatabase.start(:278)
at progress.message.broker.BrokerDatabase.<init>(:212)
at progress.message.broker.BrokerDatabase.<init>(:188)
at progress.message.broker.AgentRegistrar.kb_(:859)
at progress.message.broker.AgentRegistrar.stateChanged(:7236)
at progress.message.broker.xe.run(:566)
SQLException(SQLState=XJ040, errorCode=40000): Failed to start database '/sonic/SonicSoftware/SonicMQ5/SonicMQDB', see the next exception for details.
SQLException(SQLState=XSDB8, errorCode=45000): WARNING: Cloudscape (instance [Ljava.lang.Object;@3c5596) is attempting to boot the database {1} even though Cloudscape (instance {2}) may still be active. Only one instance of Cloudscape should boot a database at a time. Severe and non-recoverable corruption can result if 2 instances of Cloudscape boot on the same database at the same time. The db2j.database.forceDatabaseLock=true property has been set, so the database will not boot until the db.lck is no longer present. Normally this file is removed when the first instance of Cloudscape to boot on the database exits, but it may be left behind in some shutdowns. It will be necessary to remove the file by hand in that case. It is important to verify that no other VM is accessing the database before deleting the db.lck file by hand.
ID=Broker1 (severe) SonicMQ Broker start failure
(severe) Failed to start ID=Broker1, trace follows...
java.lang.RuntimeException: Problem with database: [2002] progress.message.db.EDatabaseException: SQL Exception: Failed to start database '/sonic/SonicSoftware/SonicMQ5/SonicMQDB', see the next exception for details.
at progress.message.broker.Broker.init(:537)
at com.sonicsw.mq.components.BrokerComponent.start(:560)
at com.sonicsw.mf.framework.container.AbstractContainer.loadComponent(AbstractContainer.java:1321)
at com.sonicsw.mf.framework.container.AbstractContainer.loadConfiguredComponent(AbstractContainer.java:1147)
at com.sonicsw.mf.framework.container.AbstractContainer.loadConfiguredComponents(AbstractContainer.java:1084)
at com.sonicsw.mf.framework.container.AbstractContainer.bootFramework(AbstractContainer.java:384)
at com.sonicsw.mf.framework.container.AbstractContainer.<init>(AbstractContainer.java:238)
at com.sonicsw.mf.framework.container.AbstractContainer.<init>(AbstractContainer.java:168)
at com.sonicsw.mf.jmx.Container.<init>(Container.java:48)
at java.lang.reflect.Constructor.newInstance(Native Method)
at com.sonicsw.mf.framework.container.ContainerUtil.createContainer(ContainerUtil.java:68)
at com.sonicsw.mf.framework.container.ContainerUtil.createContainer(ContainerUtil.java:33)
at com.sonicsw.mf.Agent.<init>(Agent.java:20)
at com.sonicsw.mf.Agent.main(Agent.java:13)
CAUSE:
db.lck file exist in the database directory
FIX:
Remove the .lck file and restart the container