installation problem : AuditLogManager Initialization Except

Hi,
I was able to install the webmethods 6.0 successfully but I am not able to launch it.
It gives the exception:

Wrapped Exception:com.wm.data.DataException
com.wm.util.BasisRuntimeException
AuditLogManager Initialization Exception
Unable to create shared cursor

etc etc

Does anyone know why is this happening?
Thanks in advance for all and any of your help.

RD

Has this problem been resolved?
I ran into very simmilar problem. I got “AuditLogManager Runtime Exception: java.sql…”

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

We have found a similar error :

[ISS.0095.0004C]AuditLogManager Runtime Rejected Entery>>>… ERRORINFO=Delivery retry attempts exhausted<<<.

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?

thanks in advance.

take the backup of /auidt/data directory and restart the server

The broker_admin.cnf should be backed up and restart the server…thats where your

broker config infor is stored

Hi masoud.salatini,

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.

Regards,
Adrian

Hi,

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.

Hi,

I was getting the same error, below are the logs.

[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

resolved the issue.

Thanks

Yes deleting the files should resolve the issue (always backup the files just in case)

HTH,
RMG

Adding few more points to this

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?

Hi,

even if this is a old post, there are some updates:

This is occuring in 9.5 SP1, too.
At least something similar:


2016-05-09 04:14:28 MEST [MOD.0120.0769E] Error retrieving db type: com.wm.util.BasisSQLException: [BAC.0002.0000] Wrapped Exception: com.wm.app.repov4.RepositoryDeadlockException: [BAR.0002.0000] Wrapped Exception: com.wm.data.DataNoActiveTxnException: [BAC.0004.0018] no active tran
2016-05-09 04:14:28 MEST [MOD.0120.0769E] Error retrieving db type: com.wm.util.BasisSQLException: [BAC.0002.0000] Wrapped Exception: com.wm.app.repov4.RepositoryDeadlockException: [BAR.0002.0000] Wrapped Exception: com.wm.data.DataDeadlockException: [BAC.0004.0008] Deadlock detected
2016-05-09 04:14:28 MEST [MOD.0120.0000I] java.lang.Exception: Error in archiving: com.wm.monitor.common.util.MonitorException: pm.cannotConnectArchiveDatabase
2016-05-09 04:14:28 MEST [MOD.0120.0769E] Error retrieving db type: com.wm.util.BasisSQLException: [BAC.0002.0000] Wrapped Exception: com.wm.app.repov4.RepositoryDeadlockException: [BAR.0002.0000] Wrapped Exception: com.wm.data.DataDeadlockException: [BAC.0004.0008] Deadlock detected
2016-05-09 04:14:28 MEST [MOD.0120.0769E] Error retrieving db type: com.wm.util.BasisSQLException: [BAC.0002.0000] Wrapped Exception: com.wm.app.repov4.RepositoryDeadlockException: [BAR.0002.0000] Wrapped Exception: com.wm.data.DataDeadlockException: [BAC.0004.0008] Deadlock detected
2016-05-09 04:14:28 MEST [MOD.0120.0769E] Error retrieving db type: com.wm.util.BasisSQLException: [BAC.0002.0000] Wrapped Exception: com.wm.app.repov4.RepositoryDeadlockException: [BAR.0002.0000] Wrapped Exception: com.wm.data.DataDeadlockException: [BAC.0004.0008] Deadlock detected
2016-05-09 04:14:28 MEST [MOD.0120.0000I] java.lang.Exception: Error in archiving: com.wm.monitor.common.util.MonitorException: pm.cannotConnectArchiveDatabase

or


2016-05-09 12:53:40 MEST [WmAuditingSC.destination.1122E] Destination 'SessionDBDest' caught unexpected Throwable logging audit event: [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-00001: unique constraint (IS20841.IDX_SESS_MSGID) violated
2016-05-09 12:53:40 MEST [WmAuditingSC.logger.3405E] In logger 'Session Logger', failed to log to destination; reason: Fatal SQLException detected

Regards,
Holger