Actually the first message being placed on the queue worked. The following messages were queued up.
This is a discussion on Websphere Application Server MDB fails to wake up - Websphere ; Maximum Sessions, everything work perfectly. If I set to 1, MDB fails to wake up when message is placed on init queue. Log is shown below. And the depth of init queue just keeps increasing as MDB thread is dead. ...
Maximum Sessions, everything work perfectly. If I set to 1, MDB fails to wake up when message is placed on init queue. Log is shown below. And the depth of init queue just keeps increasing as MDB thread is dead. Since it worked with 5 max sessions, I really dont know why 1 could fail. The reason I need to change it to 1 max session is that the order of the message processing is critical now. I dont wanna have multiple threads process messages at the same time.
Is there any setting that I am not aware of in WAS to make single MDB thread work? Or is it related to MQ's setting?
Log:
When server got started, we can see on Message method being called:
[8/20/09 9:18:15:099 HST] 31f8cb8a SystemOut O 2009-08-20 09:18:15,099 DEBUG [MessageListenerThreadPool : 0] bean.EllipseEventMDBBean.onMessage:421 : Start - onMessage
Exited on Message method:
[8/20/09 9:18:16:115 HST] 31f8cb8a SystemOut O 2009-08-20 09:18:16,115 DEBUG [MessageListenerThreadPool : 0] bean.EllipseEventMDBBean.onMessage:663 : End - onMessage
After that I dont see anything related to MDB. Messages are just being queued up.
Actually the first message being placed on the queue worked. The following messages were queued up.