Hello,
We are having some interesting issues with app dynamics java agent. The application is basically a workflow engine developed with JBPM. We have one app database (storing business logic data) but beside that, JBPM has it's own database for storing it's internal state. Also, JBPM utilizes QUARTZ for executing actions at predefined times so quartz has it's third database for storing it's internal state as well. So in total, there are 3 databases (all 3 of them are Postgres 9.4)
JBPM works directly with quartz so it esentially doas read/write operations on JBPM and QUARTZ databases. For the app database, JBPM only does read operations.
Tranasaction management in the app is done via Atomikos which uses XA datasources for JBPM and QUARTZ db (in order to have global transaction benefits) and for the app database we use a simple spring transaction manager with a non XA datasource definition.
Important to mention is that all 3 datasources + the atomikos transaction manager are defined and instantiated by tomcat.
Now, this works fine as it is, however, after enabling the app dynamics javaagent in tomcat, we started to see exceptions at the transaction management level -> "transaction interleaving not implemented"
Caused by: org.postgresql.xa.PGXAException: L'entrelacement des transactions n'est pas implémenté
at org.postgresql.xa.PGXAConnection.start(PGXAConnection.java:217)
at com.atomikos.datasource.xa.XAResourceTransaction.resume(XAResourceTransaction.java:297)
... 115 more
We have been testing this with and without the javaagent and the issue reproduced consistently only after enabling the javaagent.
Do you have any records of transaction interference of the javaagent like the one above? Do you know what might be the cause of this?
Any help on the matter would be greatly appreciated.
Thanks in advance,
Boieriu Alexandru
