| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| SYSTEM.MANAGED.NDURABLE |
« View previous topic :: View next topic » |
| Author |
Message
|
| calanais |
 Posted: Wed May 14, 2014 6:47 am Post subject: |
 |
|
Apprentice
Joined: 12 Mar 2010
Posts: 32
|
Can you give some detail about the what the subscriber is please?
For example is this an MDB/EJB?
Or is a message listener or synchronous receive defined in a JavaSE application?
This makes a difference because being in a container means the options defined on the createSesion() call don't take effect. eg. you could have an EJB defined as container managed, in which case the app server is handling an XA transaction for you. It might not then be committing the transaction.
For a JavaSE app, the AUTO_ACK and DUPS_OK will handle the commit of the syncpoint for you. DUPS_OK will delay the commit and only do it every 20 messages. |
|
| Back to top |
|
 |
| rajeshso |
| Posted: Thu May 15, 2014 1:03 am Post subject: |
|
|
Novice
Joined: 13 May 2014
Posts: 10
|
Many thanks to fjb, Morag, PeterPotkay, bruce and calanais.
You have helped me solve the problem.
This link you shared helped. The non-transacted Topic Session did the trick.
Thanks again people.  |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu May 15, 2014 4:50 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Now that the immediate emergency is under the control, stop and think if non transacted sessions meet your business requirements.
If these subscribers are consuming the MQ messages over an MQ Client connection, you very much want to use syncpoint when consuming the messages to avoid potential message loss. You'll just need to commit those transactions regularly.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| calanais |
| Posted: Thu May 15, 2014 6:50 am Post subject: |
|
|
Apprentice
Joined: 12 Mar 2010
Posts: 32
|
Thanks for posting the outcome; the createSession(...) call can be confusing. Indeed in JMS2.0 there are two variants for createSession(...). One that doesn't take any parameters - for use in JavaEE containers. The second that only takes one parameter - more sensible as it doesn't mean you confuse the transacted boolean and the auto-ack/client-ack/dups-ok settings.
In summary this is how MQ JMS maps down to the WMQ Syncpoint:
Transacted = Syncpoint for all sends and gets. Session.commit() or Session.rollback() must be called by the application
Client-Acknowledge = Syncpoint for all gets. Session.recover() or Message.acknowledge() must be called by the application
Auto-Acknowledge or Dups-ok = The Syncpoint is handled for gets by the WMQ JMS code. Application needs to do nothing. For Dups-ok, the syncpoint is not committed on every message - only happens every 20 messages. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
