OpenJMS logging to eventssubd.log

Environment:

TeamSite 6.5 SP1
OpenDeploy 6.0.2 (with DD enabled)
Windows 2003 EE

Problem:

We're seeing our 'eventsubd.log' file in the /iw-home/local/logs directory growing at a fairly considerable (and consistent) rate. When we run a tail on this file, a single set of errors seems to be occuring over and over again dealing with OpenJMS. Below are the three error messages that repeat at an interval of roughly half a second. I have no experience with OpenJMS - can anyone shed some light on this one? Is OpenJMS a necessary service? Our deployments (OD & DD) still seem to work properly, although I'm concerned that the perpetual logging to this file may be slowing down OD in general.

Thanks,
Derek

===============================================================
19:38:58.150 ERROR [server-36] - begin failed. Status of transaction is opened
19:38:58.150 ERROR [server-36] - Failed to make message persistent
org.exolab.jms.persistence.PersistenceException: Error in addMessage org.exolab.core.foundation.TransactionInProgressException: status of the tx is opened
at org.exolab.jms.persistence.ObjectAdapter.addMessage(Unknown Source)
at org.exolab.jms.messagemgr.MessageMgr.addPersistentMessage(Unknown Source)
at org.exolab.jms.messagemgr.MessageMgr.add(Unknown Source)
at org.exolab.jms.server.JmsServerSession.sendMessage(Unknown Source)
at org.exolab.jms.server.mipc.IpcJmsSessionConnection.sendMessage(Unknown Source)
at org.exolab.jms.server.mipc.IpcJmsSessionConnection.notify(Unknown Source)
at org.exolab.jms.server.mipc.IpcJmsReceiver.notify(Unknown Source)
at org.exolab.jms.server.mipc.IpcServerChannel.run(Unknown Source)
19:38:58.150 ERROR [server-36] - Failed to process message
javax.jms.JMSException: Failed to make message persistent: org.exolab.jms.persistence.PersistenceException: Error in addMessage org.exolab.core.foundation.TransactionInProgressException: status of the tx is opened
at org.exolab.jms.messagemgr.MessageMgr.addPersistentMessage(Unknown Source)
at org.exolab.jms.messagemgr.MessageMgr.add(Unknown Source)
at org.exolab.jms.server.JmsServerSession.sendMessage(Unknown Source)
at org.exolab.jms.server.mipc.IpcJmsSessionConnection.sendMessage(Unknown Source)
at org.exolab.jms.server.mipc.IpcJmsSessionConnection.notify(Unknown Source)
at org.exolab.jms.server.mipc.IpcJmsReceiver.notify(Unknown Source)
at org.exolab.jms.server.mipc.IpcServerChannel.run(Unknown Source)

Find more posts tagged with

Comments

Bill Klish

We ran into a similar problem on the same platform, without OD or DD involved. I read in some other posts here that there was a bug with something not cleaning up properly. I think it may have been the .db file, but at any rate, it grew to be about 4 GB in size and pretty much brought our server to its knees. We disabled the event subsystem service from starting up and things are working fine ever since. Not sure if the two are related, but we did have a similar problem.

dazzlad

Hi,

I am getting this on TS 6.5 W2K.

Does anyone know what causes and how to resolve without disabling event subsystem??

Thanks.
Darren

Migrateduser

The reason why the eventsubsystem grows at such a large rate is because it is using a flat file database structure that grows really fast. If you want the event subsystem to manage better, you would have to integrate a RDBMS database such as Oracle, MSSQL Server, DB2, or MySQL. Using one of those databases will prevent the log file from growing rapidly.

dazzlad

No I don't think that is the answer.

The file grows from 0 -> 4gb in the space of a few minutes.

I've never seent this before.