| Author |
Message
|
| grebstad |
 Posted: Thu May 19, 2005 6:48 am Post subject: MDB stops after 1. message |
 |
|
Newbie
Joined: 16 Nov 2004
Posts: 7
Location: Norway
|
Hi,
after upgrading from WAS 5.1.0.4 to WAS 5.1.1.4 the MDB doesn't pick up all messages if there are more than one message on the queue. When putting one and one it's ok, but with many messages on the queue it stops after picking up the first message. The message listener port seems to be running in the administrative console but it does not pick up messages. In the activity.log for WAS it says: MQJE016: MQ queue manager closed channel immediately during connect Closure reason = 2009.
Thankful for all help
regards,
Dag Rune |
|
| Back to top |
|
 |
| malammik |
| Posted: Thu May 19, 2005 8:53 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu May 19, 2005 5:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Could it be that it is a client connection and the network interruptions are just over the time out interval.
Anyway with an MDB I'd like to have a bindings connection. Too much trouble otherwise.
Enjoy  |
|
| Back to top |
|
|
| grebstad |
| Posted: Fri May 20, 2005 5:42 am Post subject: |
|
|
Newbie
Joined: 16 Nov 2004
Posts: 7
Location: Norway
|
Hi again,
we are using a bindings connection, today we went back to WAS5.1.0.4 and it's working again. I don't know but maybe WAS5.1.1.4 requires a patch for WMQ5.3?
rgds,
Dag Rune |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 20, 2005 6:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| grebstad wrote: |
Hi again,
we are using a bindings connection, today we went back to WAS5.1.0.4 and it's working again. I don't know but maybe WAS5.1.1.4 requires a patch for WMQ5.3? |
You can't be using a bindings connection if you are getting a 2009 error.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| grebstad |
| Posted: Fri May 20, 2005 6:44 am Post subject: |
|
|
Newbie
Joined: 16 Nov 2004
Posts: 7
Location: Norway
|
I went from bindings to client connection when it did not work to see if that helped, so I guess thats the reason for 2009. I'm not able to find back to the reason code when I used the bindings connection and it failed ,since I don't have the old log anymore  Anyway, I'm using binding mode now and it's working with 5.1.0.4.
_________________
Dag Rune Grebstad
Consultant
Bluegarden Technologies AS |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 20, 2005 6:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There are a couple of APARs that are supposedly fixed in CF4 for WAS 5.1 that would produce this problem. But they're supposedly fixed.
It does not, forgive me for saying this, sound like you have actually performed troubleshooting on the issue - just flailed a bit.
This is very likely to be an application issue, where it is not handling a poison message properly (or possibly an MDBListener configuration issue). It is not likely to be an issue with the WAS version.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vennela |
| Posted: Fri May 20, 2005 6:56 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Also, there are tons of JMS bugs that are fixed in CSD08 and CSD09 and there are some hyper fixes too. The readme's of both these CSD's are filled with JMS bugs. |
|
| Back to top |
|
|
| grebstad |
| Posted: Fri May 20, 2005 7:01 am Post subject: |
|
|
Newbie
Joined: 16 Nov 2004
Posts: 7
Location: Norway
|
The only difference is the version of WAS, but I should have been troubleshooting more with the bindings connection.
_________________
Dag Rune Grebstad
Consultant
Bluegarden Technologies AS |
|
| Back to top |
|
|
|
|
