Is there any resolution to this? I just tried to restart a proxy IS and got a very similar error.
AuditLogManager Initialization Exception: com.wm.app.audit.AuditException:[BAA.0002.0000] Wrapped Exception: com.wm.app.repov4.RepositoryException: [BAR.0002.0000] Wrapped Exception: com.wm.util.BasisRuntimeException: [BAC.0001.0034] RuntimeException: unable to create shared cursor: com.wm.data.DataException: [BAF.0002.0000] Wrapped Exception: com.wm.driver.data.fs.FSDataCoderException: [BAF.0002.0000] Wrapped Exception: com.wm.io.codec.CodecException: [BAC.0005.0004] CodecException: Unknown Object Type 28
At the same time the Broker configuration on the IS is vanished and trying to re-define it , i see a single radio button ( Not Configured) , and no way to reconfigure the Broker Connection.
I checked the DB and the connections are OK and running , furthermore there seems to be enough space on the DB.
Can anyone from webMethods please provide some hint?
At the same time the Broker configuration on the IS is vanished
and trying to re-define it , i see a single radio button
The default Broker for Integration Server is configured via the config/dispatch.cnf. If this file has been truncated (dirty shutdown, maybe?) then you can get a default one by deleting it.
Shutdown the Integration Server, backup the Config directory, delete dispatch.cnf, and start Integration Server. You should then be able to re-configure the Broker connection that Integration Server will use for Triggers and publishing.
I am getting this error after I restart the IS from putty :
AuditLogManager Initialization Exception: com.wm.app.audit.AuditException:[BAA.0000.0003] no schema associations for configuration DefaultTxoutFSConfig version 1.
2008-06-15 05:10:33 CEST [ISS.0095.9998C] AuditLogManager Exception: com.wm.app.audit.AuditException: [BAA.0000.0003] no schema associations for configuration DefaultTxoutFSConfig version 1.
com.wm.app.audit.AuditException: [BAA.0000.0003] no schema associations for configuration DefaultTxoutFSConfig version 1.
[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:562)
at com.wm.app.b2b.server.AuditLogManager.init(AuditLogManager.java:548)
at com.wm.app.b2b.server.Server.initAuditLogManager(Server.java:782)
at com.wm.app.b2b.server.Server.run(Server.java:344)
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
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:568)
at com.wm.app.b2b.server.AuditLogManager.init(AuditLogManager.java:548)
at com.wm.app.b2b.server.Server.initAuditLogManager(Server.java:782)
at com.wm.app.b2b.server.Server.run(Server.java:344)
Solution: seems like, the files got corrupted, removed the below files/folder and restarted the Integration Server.
Step1: Deleted all the files from "“IntegrationServer/WMReporsitory4”
Step2: Deleted the folder IntegrationServer/db
Step3: Restarted the Integration Server
1> Before you delete any files/folder under IntegrationServer folder, it is always advised to take a backup
2> I have seen this issue happening in webMethods 7
Not sure if the same is happening in webMethods 8.x and above.
@ Daswanth,
Can you please confirm your webMethods version?