| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Transaction control with remote system |
« View previous topic :: View next topic » |
| Author |
Message
|
| rsashi |
 Posted: Thu Nov 09, 2006 10:42 am Post subject: Transaction control with remote system |
 |
|
Apprentice
Joined: 29 Jan 2004
Posts: 35
|
We have a [b]System A[/b] and [b]System B[/b]. On system A we have [b]MQ Server [/b]and [b]WAS Server [/b]and on system B we have a [b]java helper class[/b]( threaded) and a [b]databas[/b]e. Our design requirement is , we don't like to loose any message at any given time. Our plan of flow is like this,
Message Driven Bean will read a message from a local MQ queue on System A and then calls a remote java helper class which is on System B , once message gets into java helper class, it try's to inject into database. My question is how can we implement above flow with out loosing even single message on any system failure too.
Your response is highly appreciated. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Nov 09, 2006 11:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Why would you possibly reimplement your own database client, when you could use a regular database driver to connect to the database?
In other words, it is an insanity to run the "java helper class" on the database machine.
Particularly in this manner, you can not configure an XA transaction - so it prevents you from doing exactly what you want to do - ensure that you never lose a message.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| malammik |
| Posted: Thu Nov 09, 2006 11:41 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
This is poor design approach. You transaction is going to be as reliable as its weakest element. Calling an external POJO outside of any kind transaction container context breaks any kind of UOW you will potentially loose messages. Your helper class has to execute inside a transactional container which can communicate with MDB container as an XA participant. HOWEVER if all you care about is just lost messages not issues such as lost updates or duplicate inserts, etc have your MDB use bean driven transactions, not container, wait for helper class to ack work and the commit or rollback.
_________________
Mikhail Malamud
http://www.netflexity.com
http://groups.google.com/group/qflex |
|
| 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
|
|
|
|
