TeamSite 6.5 SP1
Solaris 2.9
We continually are seeing this in production in the eventsubd.log file:
23:17:19.102 ERROR [server-24] - Failed to process message due to out-of-memory error
java.lang.OutOfMemoryError
and we have things like this in the localhost_log.2006-12-13.txt file in iw-home/local/logs/iwui:
2006-12-13 11:14:15 StandardContext[/iw/eventsubsystem]Created InitialContext :: javax.naming.InitialContext@15ec79b
2006-12-13 11:14:17 StandardContext[/iw/eventsubsystem]Looking up topics...
2006-12-13 11:14:17 StandardContext[/iw/eventsubsystem]Creating topic connection
2006-12-13 11:14:17 StandardContext[/iw/eventsubsystem]Creating TeamSite_User topic session: not transacted, auto ack
2006-12-13 11:14:17 StandardContext[/iw/eventsubsystem]Creating TeamSite_System topic session: not transacted, auto ack
2006-12-13 11:14:18 StandardContext[/iw/eventsubsystem]Creating TeamSite_Workflow topic session: not transacted, auto ac
k
2006-12-13 11:14:26 StandardContext[/iw/eventsubsystem]Failed to process message due to out-of-memory error
javax.jms.JMSException: Failed to process message due to out-of-memory error
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)
We were running through mass loads of dcrs. We did the same on our staging box which has less processing power, half the cpus and a quarter of the memory and didn't see this.
Is the event sub system bring us down
