IS not able to come up after restarting from the IS Adming page

[Mayank_Tripathi]

Hi

Recently we have been facing a problem while starting the IS from the IS Administrator page.
The error we see in the logs is as below:

2013-01-31 13:21:09 GMT [ISS.0028.0015I] WmRoot: Shutdown service (wm.server.remote:shutdown)
2013-01-31 13:21:09 GMT [ISS.0134.0001I] JMS subsystem shutdown completed
2013-01-31 13:21:09 GMT [ISS.0098.0022I] Persistent Trigger Output Dispatcher stopped
2013-01-31 13:21:09 GMT [ISS.0098.0022I] Volatile Trigger Output Dispatcher stopped
2013-01-31 13:21:09 GMT [ISS.0025.0033I] Dispatcher shutdown completed
2013-01-31 13:21:17 GMT [ISP.0046.0011I] Disabling HTTP Listener on port 6666
2013-01-31 13:21:19 GMT [CommonLib.MWS.0002W] Should have positive integer specified for com.webMethods.sc.mws.db.cleanup.period. The current value is null
2013-01-31 13:21:19 GMT [CommonLib.MWS.0002W] Should have positive integer specified for com.webMethods.sc.mws.db.max.waittime. The current value is null
2013-01-31 13:21:19 GMT [ISS.0024.0010C] Central User Manager initialization failed with error : null

2013-01-31 13:21:19 GMT [Error.QueueProvider.ueueStoppedE] Message not found for messageKey Error.QueueProvider.QueueStopped

2013-01-31 13:21:19 GMT [WmAuditingSC.queue.2011E] Queue ‘Error Queue’ has not been started
2013-01-31 13:21:19 GMT [WmAuditingSC.logger.3109E] In logger ‘Error Logger’, failed to insert in queue; reason: Queue ‘Error Queue’ has not been started
2013-01-31 13:21:19 GMT [ISS.0095.0010E] AuditLogManager Runtime Exception: >>>BasicData:AuditRecordType=com.wm.app.b2b.server.audit.type.ErrorRecordType,ErrStackTrace=com.webMethods.portal.system.PortalRuntimeException: null
at com.webMethods.portal.system.PortalRuntimeException.(PortalRuntimeException.java:19)
at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:807)
at com.webMethods.sc.mws.MWSLibrary.init(MWSLibrary.java:240)
at com.wm.app.b2b.server.cds.CDSUserManager.initialize(CDSUserManager.java:162)
at com.wm.app.b2b.server.UserManager.jndiInit(UserManager.java:540)
at com.wm.app.b2b.server.ACLGroup$GroupLoader$GroupLoadingTask.run(ACLGroup.java:393)
at java.lang.Thread.run(Thread.java:736),ErrorMessage=null<<< publishing log entry com.wm.app.audit.AuditException: [BAA.0000.0057] Auditing failed. The audit record was written to the failed audit log. com.webMethods.sc.auditing.API.queue.WmAuditQueueException: Queue ‘Error Queue’ has not been started .
com.webMethods.sc.auditing.API.queue.WmAuditQueueException: Queue ‘Error Queue’ has not been started
at com.webMethods.sc.auditing.queue.WmBaseAuditQueue.insert(WmBaseAuditQueue.java:253)
at com.webMethods.sc.auditing.logger.WmAsyncAuditLogger.logRecord(WmAsyncAuditLogger.java:103)
at com.webMethods.sc.auditing.logger.WmBaseAuditLogger.logRecord(WmBaseAuditLogger.java:107)
at com.wm.app.audit.impl.AuditRuntime.publishAudit(AuditRuntime.java:163)
at com.wm.app.audit.impl.AuditRuntime.publishAudit(AuditRuntime.java:156)
at com.wm.app.b2b.server.audit.ErrorAuditLogger.writeLog(ErrorAuditLogger.java:157)
at com.wm.app.b2b.server.AuditLogManager.errorLog(AuditLogManager.java:886)
at com.wm.app.b2b.server.AuditLogManager.errorLog(AuditLogManager.java:880)
at com.wm.app.b2b.server.AuditLogManager.errorLog(AuditLogManager.java:829)
at com.wm.app.b2b.server.AuditLogManager.errorLog(AuditLogManager.java:867)
at com.wm.app.b2b.server.Server.logError(Server.java:1549)
at com.wm.app.b2b.server.cds.CDSUserManager.initialize(CDSUserManager.java:170)
at com.wm.app.b2b.server.UserManager.jndiInit(UserManager.java:540)
at com.wm.app.b2b.server.ACLGroup$GroupLoader$GroupLoadingTask.run(ACLGroup.java:393)
at java.lang.Thread.run(Thread.java:736)
com.wm.app.audit.AuditException: [BAA.0000.0057] Auditing failed. The audit record was written to the failed audit log. com.webMethods.sc.auditing.API.queue.WmAuditQueueException: Queue ‘Error Queue’ has not been started

The Error logger is in “enabled” state in the IS Admin page and have default configurations.

IS version is 8.2 and its running on AIX box.

Can any one suggest what posibbly is going wrong.

Any help is appreciated.

Thanks,
Mayank

[Pankaj_Bhatt]

Hi Mayank,

Can you try to start the IS via command prompt with verbose error message?

You can use following command to do so :

<installation_directory>\Integrationserver\bin\server.bat -debug 9

the above error points to AuditLogManager Runtime Exception, where are you logging the Audit logs?

Some similar threads on this kind of error:
[url]wmusers.com

If using JDBC Pool, verify if it is correct.

Let me know, if you need any further help

[Mayank_Tripathi]

Hi Pankaj

Thanks for the reply

Our IS is running on AIX v6.1 and from the AIX console i am able to restart the server using the server.sh script.

We log all our logs like application, server,failed audit etc. in the logs folder inside the IntegrationServer folder.
/IntegrationServer/logs/

Not sure if this is the location for the AuditLogManager.The error logger and the service logger are pointing to database and they opearte in asynchronous mode, server logger points to the file system and is operating in synchronous mode.

In the jdbc pools, not sure were it can be going wrong since i can test all the connections sucessfully to the database.
Can you please let me know what are the parameters i should be verifying for the JDBC pools being correctly configured.

Not well versed in the jdbc pools section so have to seek some sort of help.

Regards
Mayank