Hi,

I am trying to restart the webMethods 8 Integration Server but getting the below exception, the servers were not restarted for past almost 3 months. Have installed in June, 2011.

2012-09-01 17:23:59 MDT [ISS.0096.0001C] JDBCConnectionManager: initialization failed for Xref functional alias, check configuration.
2012-09-01 17:23:59 MDT [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ISInternal functional alias, check configuration.
2012-09-01 17:23:59 MDT [ISS.0025.0024I] JDBC Connection Manager started
2012-09-01 17:24:00 MDT [Error.DBMessageStore.nitializationE] Failed to initialize DB message store.
2012-09-01 17:24:00 MDT [Error.DBMessageStore.nitializationE] Failed to initialize DB message store.
2012-09-01 17:24:00 MDT [Error.DB.onnectionE] Could not obtain a DB connection.
2012-09-01 17:24:00 MDT [WmAuditingSC.queue.2025W] Caught exception detecting orphaned queues: Could not obtain a DB connection
2012-09-01 17:24:00 MDT [Error.DB.onnectionE] Could not obtain a DB connection.
2012-09-01 17:24:00 MDT [WmAuditingSC.main.5011E] Failed to start queue ‘GuaranteedRetryQueue’; reason ‘Failed to start queue ‘GuaranteedRetryQueue’’
2012-09-01 17:24:00 MDT [ISS.0095.9998C] AuditLogManager Exception: com.wm.app.audit.AuditException: [BAA.0002.0000] Wrapped Exception: com.webMethods.sc.auditing.API.WmAuditException: Failed to start queue ‘GuaranteedRetryQueue’; reason ‘Failed to start queue ‘GuaranteedRetryQueue’’
com.webMethods.sc.auditing.API.WmAuditException: Failed to start queue ‘GuaranteedRetryQueue’; reason ‘Failed to start queue ‘GuaranteedRetryQueue’’
at com.webMethods.sc.auditing.WmAuditingImpl.startAuditing(WmAuditingImpl.java:330)
at com.wm.app.b2b.server.AuditLogManager.initAuditingComponent(AuditLogManager.java:536)
at com.wm.app.b2b.server.AuditLogManager.init(AuditLogManager.java:522)
at com.wm.app.b2b.server.Server.initAuditLogManager(Server.java:822)
at com.wm.app.b2b.server.Server.run(Server.java:360)
Caused by: com.webMethods.sc.auditing.API.queue.WmAuditQueueException: Failed to start queue ‘GuaranteedRetryQueue’
at com.webMethods.sc.auditing.queue.WmGuaranteedQueue.start(WmGuaranteedQueue.java:55)
at com.webMethods.sc.auditing.WmAuditingImpl.startAuditing(WmAuditingImpl.java:325)
… 4 more
Caused by: com.webMethods.lwq.LwqException: Could not obtain a DB connection
at com.webMethods.lwq.db.AbstractDBMessageStore.getAutoCommitConnection(AbstractDBMessageStore.java:1452)
at com.webMethods.lwq.db.AbstractDBMessageStore.getNumberOfMessages(AbstractDBMessageStore.java:1394)
at com.webMethods.lwq.db.AbstractDBMessageStore.open(AbstractDBMessageStore.java:1302)
at com.webMethods.lwq.impl.QueueProvider.(QueueProvider.java:60)
at com.webMethods.lwq.impl.AbstractQueueStore.openQueue(AbstractQueueStore.java:282)
at com.webMethods.lwq.impl.AbstractQueueStore.createQueue(AbstractQueueStore.java:243)
at com.webMethods.sc.auditing.queue.WmGuaranteedQueue.start(WmGuaranteedQueue.java:47)
… 5 more
com.wm.app.audit.AuditException: [BAA.0002.0000] Wrapped Exception: com.webMethods.sc.auditing.API.WmAuditException: Failed to start queue ‘GuaranteedRetryQueue’; reason ‘Failed to start queue ‘GuaranteedRetryQueue’’
at com.wm.app.b2b.server.AuditLogManager.initAuditingComponent(AuditLogManager.java:542)
at com.wm.app.b2b.server.AuditLogManager.init(AuditLogManager.java:522)
at com.wm.app.b2b.server.Server.initAuditLogManager(Server.java:822)
at com.wm.app.b2b.server.Server.run(Server.java:360)

2012-09-01 17:24:00 MDT [ISS.0014.0005I] Shutting down server. Shutting Down…

Hi,

It would be worth to check the JDBC pool configurations which is located at “IntegrationServer/config/jdbc”, to make sure that the Xref and ISInternal settings are correct as you expected.

Regards,
Natarajan R

Thanks for the suggestion, however, I later figured out it was a deployment issue, once that was corrected, IS came up fine.

We have wM 8.2 running on DB2 9.7 and are getting this error as well. This happened once before and our DBA restarted DB2 and that seemed to rectify the problem. What is IS doing to cause this? We have the same environment in production and that could pose a serious risk.

2013-05-17 14:44:00 CDT [ISS.0025.0041I] FIPS mode not initialized
2013-05-17 14:44:02 CDT [BAS.0123.0001I] FSData full consistency check is being performed. Db:WmRepository4/RepoV4
2013-05-17 14:44:03 CDT [ISS.0025.0017I] Repository Manager started
2013-05-17 14:44:05 CDT [ISS.0025.0024I] JDBC Connection Manager started
2013-05-17 14:44:06 CDT [Error.DBMessageStore.nitializationE] Failed to initialize DB message store.
2013-05-17 14:44:06 CDT [Error.DBMessageStore.nitializationE] Failed to initialize DB message store.
2013-05-17 14:44:06 CDT [Error.DB.onnectionE] Message not found for messageKey Error.DB.Connection
2013-05-17 14:44:06 CDT [WmAuditingSC.queue.2025W] Caught exception detecting orphaned queues: Failed to start database ‘AUDITINGSC’, see the next exception for details.
2013-05-17 14:44:06 CDT [Error.DB.onnectionE] Message not found for messageKey Error.DB.Connection
2013-05-17 14:44:06 CDT [WmAuditingSC.main.5011E] Failed to start queue ‘GuaranteedRetryQueue’; reason ‘Failed to start queue ‘GuaranteedRetryQueue’’
2013-05-17 14:44:06 CDT [ISS.0095.9998C] AuditLogManager Exception: com.wm.app.audit.AuditException: [BAA.0002.0000] Wrapped Exception: com.webMethods.sc.auditing.API.WmAuditException: Failed to start queue ‘GuaranteedRetryQueue’; reason ‘Failed to start queue ‘GuaranteedRetryQueue’’
com.webMethods.sc.auditing.API.WmAuditException: Failed to start queue ‘GuaranteedRetryQueue’; reason ‘Failed to start queue ‘GuaranteedRetryQueue’’
at com.webMethods.sc.auditing.WmAuditingImpl.startAuditing(WmAuditingImpl.java:330)
at com.wm.app.b2b.server.AuditLogManager.initAuditingComponent(AuditLogManager.java:536)
at com.wm.app.b2b.server.AuditLogManager.init(AuditLogManager.java:522)
at com.wm.app.b2b.server.Server.initAuditLogManager(Server.java:837)
at com.wm.app.b2b.server.Server.run(Server.java:364)
Caused by: com.webMethods.sc.auditing.API.queue.WmAuditQueueException: Failed to start queue ‘GuaranteedRetryQueue’
at com.webMethods.sc.auditing.queue.WmGuaranteedQueue.start(WmGuaranteedQueue.java:55)
at com.webMethods.sc.auditing.WmAuditingImpl.startAuditing(WmAuditingImpl.java:325)
… 4 more
Caused by: com.webMethods.lwq.LwqException: Failed to start database ‘AUDITINGSC’, see the next exception for details.
at com.webMethods.lwq.util.DBPool.createNewConnections(DBPool.java:155)
at com.webMethods.lwq.util.DBPool.(DBPool.java:63)
at com.webMethods.lwq.util.DBPool.getInstance(DBPool.java:108)
at com.webMethods.lwq.db.AbstractDBMessageStore.getAutoCommitConnection(AbstractDBMessageStore.java:1450)
at com.webMethods.lwq.db.AbstractDBMessageStore.getNumberOfMessages(AbstractDBMessageStore.java:1394)
at com.webMethods.lwq.db.AbstractDBMessageStore.open(AbstractDBMessageStore.java:1302)
at com.webMethods.lwq.impl.QueueProvider.(QueueProvider.java:60)
at com.webMethods.lwq.impl.AbstractQueueStore.openQueue(AbstractQueueStore.java:282)
at com.webMethods.lwq.impl.AbstractQueueStore.createQueue(AbstractQueueStore.java:243)
at com.webMethods.sc.auditing.queue.WmGuaranteedQueue.start(WmGuaranteedQueue.java:47)
… 5 more
com.wm.app.audit.AuditException: [BAA.0002.0000] Wrapped Exception: com.webMethods.sc.auditing.API.WmAuditException: Failed to start queue ‘GuaranteedRetryQueue’; reason ‘Failed to start queue ‘GuaranteedRetryQueue’’
at com.wm.app.b2b.server.AuditLogManager.initAuditingComponent(AuditLogManager.java:542)
at com.wm.app.b2b.server.AuditLogManager.init(AuditLogManager.java:522)
at com.wm.app.b2b.server.Server.initAuditLogManager(Server.java:837)
at com.wm.app.b2b.server.Server.run(Server.java:364)

2013-05-17 14:44:06 CDT [ISS.0014.0005I] Shutting down server. Shutting Down…

No, it is not DB2 related. Try this:
Take a copy of IntegrationServer\db then delete IntegrationServer\db* and restart IS

The errors seems to be issue iwth Audit files could be corrupted.

You can try deleting the Audit/data/ files and restart IS should resolve the issue with new Audit files being created.

Any recent changes in your IS environment?

HTH,
RMG

I just had the same problem with Oracle after an unclean/forced shutdown because of an irresponsive JDBC-Connection.

Deleting the db-folder did the trick! Thanks!

Cheers,
Sascha

Thanks a lot Shmuel !!!

It worked me.