Hi,

You can turn on logging for the specific namespace like log:set DEBUG 
org.apache.aries.transaction or
I choose the pax-jdbc-pool-aries because it supported XA transactions, there 
are pools that do not IIRC.

Met vriendelijke groet / Mit freundlichen Grüßen / Kind regards,
Maurice Betzel
Principal Software Engineer
Gaston Schul Group


-----Original Message-----
From: Ephemeris Lappis <[email protected]>
Sent: 02 December 2022 12:24
To: [email protected]
Subject: Transactions and PAX JDBC

 CAUTION: This email originated from outside of Gaston Schul. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


Hello.

I'm testing pax-jdbc-config to configure XA data sources that should be 
available as "wrapped and auto-enlisted" javax.sql.DataSource to be used in 
Camel routes.

The data source is configured using the pax-jdbc-config with a simple CFG file 
setting the pool type (dbcp2) and xa flag.

My tests seem to be OK, both on simple "non transacted" routes with SQL only 
and on "transacted" routes with JMS and SQL operations. From an external point 
of view, the transactions are correct...

Is there any way to monitor the transaction manager to see what it does ?

When I look at the JMX MBeans I can see some information about the
DBCP2 pool, but nothing about underlying (postgresql) connections...

What kind of statistics should I care about to control transactions ?

Thanks for your help.

Regards.
Al onze verrichtingen geschieden op basis van de Algemene voorwaarden der 
Expediteurs van België, gepubliceerd in de bijlage tot het Belgisch Staatsblad 
dd. 24 juni 2005 onder nr. 0090237. De tekst van deze voorwaarden wordt op uw 
verzoek gratis toegezonden.
All our transactions are subject to the General Conditions of the Belgian 
Forwarders Association which have been published under nr. 0090237 in the 
"Bijlage tot het Belgisch Staatsblad" dated June 24th, 2005, and is available 
free of charge upon request.
Toutes nos opérations se font sur base des Conditions Générales des Expéditeurs 
de Belgique. Le texte en a été publié dans l' Annexe au Moniteur Belge du 24 
juin 2005 sous le n° 0090237. Ce texte sera vous envoyé gratuitment sur demande.
Email confidentiality notice:
This email and any files transmitted with it are confidential and intended only 
for the use of the recipient. If you have received this email in error please 
notify its sender.

Reply via email to