| Author |
Message
|
| nityak |
 Posted: Thu Aug 21, 2003 10:34 am Post subject: not processing messages in MQ queue sporadically |
 |
|
Newbie
Joined: 23 Nov 2002
Posts: 5
|
Hi all,
I have an MDB listening on a queue. I want messages processed in the sequence they have arrived. I have only one mdb in the pool. After processing a few messages, the MDB stops processing and the messages start getting stacked up in the queue.
I have tried the following
1. Cleared all queues
2. Restarted application. Now messages are properly processed.
3. After some duration, messages are stacked again and processing is not happening.
Can anybody help.
I am using Weblogic 7.0 on solaris 2.8 with MQ5.3.
ThanX
Nitya |
|
| Back to top |
|
 |
| mpuetz |
| Posted: Thu Aug 21, 2003 1:12 pm Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi,
which transport mode are you using (client or bindings mode) and
what type is your connection factory Queue or Topic ?
_________________
Mathias Puetz
IBM/Central WebSphere Services
WebSphere Business Integration Specialist |
|
| Back to top |
|
|
| nityak |
| Posted: Thu Aug 21, 2003 1:26 pm Post subject: |
|
|
Newbie
Joined: 23 Nov 2002
Posts: 5
|
My transport mode is client and connection factory is Queue
ThanX
Nitya |
|
| Back to top |
|
|
| mpuetz |
| Posted: Thu Aug 21, 2003 1:36 pm Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi,
there are two things that come to my mind:
1) You might be suffering from a bug recently detected in MQ 5.3
which causes JMS get operations to break the connection to
the queue manager in some occasions. There is fix to this which I
believe to be included with CSD04.
You may ask IBM support for defects 73848 and 73758 and let
them tell you know whether CSD04 has them included or if otherwise
ask them for an e-fix.
2.) In combination to this, WLS might not handle the CONNECTION_BROKEN exception from the underlying MQ java classes
correctly and does not re-open the JMS session.
The first is definitely an MQ problem, the second is a WLS problem
which has to detect failed sessions/connections and re-open them
accordingly.
_________________
Mathias Puetz
IBM/Central WebSphere Services
WebSphere Business Integration Specialist |
|
| Back to top |
|
|
| nityak |
| Posted: Thu Aug 21, 2003 1:40 pm Post subject: |
|
|
Newbie
Joined: 23 Nov 2002
Posts: 5
|
Hi Mathias,
ThanX so much. That was helpful. Will go out & look for the patches & see if they help.
Rgds
Nitya |
|
| Back to top |
|
|
|
|
