Atomikos Forum
Warnings in Logfiles |
Hello,
although my application works fine, I keep getting the following warnings in the Atomikos console log files:
10-09-27 12:56:24,738 [jmsListener-5] atomikos connection proxy for resource ACPMF_MQSeries_XA_RMI: you are creating a JMS session in non-transacted mode - the resulting JMS work will NOT be part of the JTA transaction!
10-09-28 09:44:45,001 [main] Local heuristic termination of coordinator 10.7.36.72_ACPMService0107600002 with state COMMITTING
I am not sure what the second message means, but the first one is obvious - I am using JMS without XA.
This is fine for my use case - I did not need XA here and so I simply set Spring's sessionTransacted flag to false.
However, the log files produce LOTS of warnings like the ones above, which will impair performance.
So I see 2 possibilities:
1) Either I am wrong to use Atomikos when I do not need XA. However, I think it is quite practical because I have the same setup whether I need XA or not, and I can enable XA later by simply change one property. Furthermore, I can use the JTA API in both cases, which means I do not need to change any code when I later switch to XA...
2) ...Or there should be a possibility to suppress these warning messages. I would have expected that by using slf4j and log4j, the warning would disappear - but while this affects the log4j output, there still is the Atomikos console output which still receives all these warning messages.
although my application works fine, I keep getting the following warnings in the Atomikos console log files:
10-09-27 12:56:24,738 [jmsListener-5] atomikos connection proxy for resource ACPMF_MQSeries_XA_RMI: you are creating a JMS session in non-transacted mode - the resulting JMS work will NOT be part of the JTA transaction!
10-09-28 09:44:45,001 [main] Local heuristic termination of coordinator 10.7.36.72_ACPMService0107600002 with state COMMITTING
I am not sure what the second message means, but the first one is obvious - I am using JMS without XA.
This is fine for my use case - I did not need XA here and so I simply set Spring's sessionTransacted flag to false.
However, the log files produce LOTS of warnings like the ones above, which will impair performance.
So I see 2 possibilities:
1) Either I am wrong to use Atomikos when I do not need XA. However, I think it is quite practical because I have the same setup whether I need XA or not, and I can enable XA later by simply change one property. Furthermore, I can use the JTA API in both cases, which means I do not need to change any code when I later switch to XA...
2) ...Or there should be a possibility to suppress these warning messages. I would have expected that by using slf4j and log4j, the warning would disappear - but while this affects the log4j output, there still is the Atomikos console output which still receives all these warning messages.
Stefan Mader 
Tuesday, September 28, 2010
Tuesday, September 28, 2010
Other recent topics