| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| RFH2s and MDBs |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Wed Dec 14, 2005 12:22 pm Post subject: RFH2s and MDBs |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If a sending .NET app says the usr folder is x bytes long, but in fact it is x + 10 bytes long, how will a WebLogics MDB react to that?
We have an app that is dropping its connection to the QM and reconnecting, and the developers feel that the above scenario is what's causing the parsing to fail, and thus the MDB drops and reconnects. There are no errors on the QM side. Obviously fixing the RFh2 header so the usr folder's lenght matches the NameValueLenght needs to be done, but isn't it extreme for the MDB to fail like that?
They are saying that this is the way the JMS MQ API handles this scenario. True? Anyway around it?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Dec 14, 2005 3:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Well,,, Weblogic not being WAS you would have to know what defaults have been designed into the Weblogic flavor of MDB implementation....
WAS wise the MDB would consider this to be a poison message ?
Enjoy  |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Dec 14, 2005 5:05 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
See lets assume WAS for the sake of arguement. A bad message wouldn't cause the MDB to disconnect and reconnect would it?
If we are dealing with a scenario where the MDB thinks this is a poison message, then would setting the MQ queue's backout attributes let the MDB move the bad message to the backout q and not drop the connection, hopefully the next message in the queue is properly built?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Dec 14, 2005 8:23 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Assuming WAS for sake of argument....
a) no Backout threshold.
Poison message gets delivered MDB retry times. The MDB stops.
b) Backout threshold no BO Queue.
BO >= MDB retry see a)
BO < MDB retry)
Poison message gets moved to the DLQ with DLQH after BO times.
MDB reads next message in Q
c) Backout Threshold and BO Queue
BO >= MDB retry see a)
BO < MDB retry
Poison message gets moved to the BO Q after BO times. No DLQH.
MDB reads next message in Q.
Now depending on type of error DB timeout ? etc it might look like a specific instance of the MDB stopped working and then restarts. The truth behind that view is that the MDB is just waiting for the DB timeout to hit BO retry times. The next message is then read giving the impression that the MDB started working again....
Enjoy |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 15, 2005 4:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
But understand that WebLogic may do this entirely differently.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
