The counter is managed on the server I presume, so I don't expect it to be
part of the transaction.
What I'm wondering though is why even after a consumer.close(),
session.close(), connection.close() the consumer stays connected to the
server ?
On Thu, Oct 16, 2014 at 8:26 PM, David Jencks <
davi
Maybe the redelivery counter is transactional so if the xa tx rolls back and
redelivery is needed the counter gets reset? this is speculation but might
explain your result.
david jencks
On Oct 16, 2014, at 10:45 AM, Xander Uiterlinden wrote:
> Hi,
>
> I'm trying to implement a JMS consumer
Hi,
I'm trying to implement a JMS consumer that uses XA transactions in order
to create a consumer that consumes the message and does work with the
message in a single transaction.
The code for the consuming worker is as follows:
class Worker implements Runnable {
public void run() {
Active
