gopinathang ganapathy

Greenhorn
+ Follow
since Nov 22, 2008
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by gopinathang ganapathy

learnt that just before the 2phase commit Transaction manager checks with the resources involved in this transaction. ack is part of whole transaction even if the acknowledgement fails it considered that transaction failed and everything has to rollback.
message can be persisted to avoid message lost [for example jvm crash]. message can persisted to db/file system based on the messaging service configuration. in this case when the message service gets a message it makes sure it persist the message successfully before it sends ack.

hth
Gopi
what is the expected behavior when MDB configured to run in CMT mode and just before Messaging service gets the acknowledgement it died? observed behavior is message is not deleted from the messaging service since the ack not received. when the message service came back again it message was redelivered that caused the duplication. Is this something container to take care such scenarios or application has to handle them.

Thanks for the input!
Gopi
S.o.p(" starting at : "+timestamp);
executeQuery();
S.o.p(" ending at : "+timestamp);