Atomikos Forum

Timeout/setRollbackOnly of ACTIVE coordinator !

Hi Guy

As already mentioned in this forum

default82df.html?community.6.2868.2
default82df.html?community.6.2948.1

there is a regression between version 3.7 and 3.8.
The symptom is zillions of

Timeout/setRollbackOnly of ACTIVE coordinator !

messages.

It seems caused by the following code that was added to ActiveStateHandler.java

92,93c91,96
<
<                    printMsg ( "Rollback of timedout ACTIVE coordinator !" );
---
>                      if ( getCoordinator().prefersSingleThreaded2PC() ) {
>                              //cf case 71748
>                              LOGGER.logWarning ( "Timeout/setRollbackOnly of ACTIVE coordinator !" );
>                              getCoordinator().setRollbackOnly();
>                      } else {
>                              LOGGER.logWarning ( "Rollback of timedout ACTIVE coordinator !" );

Compared to 3.7, the call to setRollbackOnly() does not modify the state but only
adds a RollbackParticipant to the Coordinator.
This is then done repeatedly every 150ms as long as the Active state handler runs.
Martin Lichtin Send private email
Thursday, April 25, 2013
 
 
Thanks, this was fixed in the 3.7 and 3.8 branches.
Guy Pardon Send private email
Monday, May 27, 2013
 
 
Will there ever be a 3.8.1 release to fix this?
Benjamin Graf Send private email
Wednesday, July 31, 2013
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics