Win a copy of Spark in Action this week in the Open Source Projects forum!

Dimka Noneen

Greenhorn
+ Follow
since Apr 10, 2010
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 Dimka Noneen

Hi!

There are a lot of projects in our life and they cover lot of topics of it.
And it is curiously enough what are you working on?

My work is to get SPA information from open spaces and consolidate them for people ))

Thanks.
7 years ago
>>yes. if you're using CMT, this is the behaviour the container provides you automatically if you're using the REQUIRED transaction attribute (the default). if some problem results in a system (runtime) exception, the container automatically rollbacks your changes, including putting the message back in the queue.


Thanks, I read MDB spec and cannot understand that the transaction begins from removing a message from queue.
On exception it will be redelivered.

But I have solved this problem - not to try save message in inbox queue ))

Hi!

In general I have MDB which consums messages and call onMessage method. And the problem is that messages
will be deleted when MDB will be called to proceed message. So, it is only one chance to process this
message. I dont want to resend the message again, so setRollbackOnly not a solution.

So the question is - is it possible to delete message from inbox queue only after success processing the message?
Or to put a message back to inbox queue with less priority?

I thing that it is bad solution because of it will cycle and it is hard to controll it.

JBM 1.4

Thanks.