Hi Brian, sorry for a very late reply.
Your suggestion was accurate, we had some Apache Geronimo dependencies lying around, conflicting with WAS'.
Removing those solved this particular issue.
Thank you very much!
Rafael.
------------------------------
Rafael Escudero
------------------------------
Original Message:
Sent: Thu October 31, 2024 01:10 PM
From: Brian S Paskin
Subject: WAS 9.0.5.20 LinkageError with Spring-tx 5.3.31 and com/ibm/websphere/uow/UOWSynchronizationRegistry
I always recommend removing all JEE libraries in the application because they can cause problems in a multi classloader situation. I believe the default is parent last, but you could also make tWAS use a single classloader. Without a trace, I cannot tell you which classes may be causing the issue. Either that or change your code to use JEE and then not have issues in the future when you upgrade to another version of tWAS/Liberty/Other JEE platform.
Brian
------------------------------
Brian S Paskin
Sr. Technology Engineer
IBM Cloud Engineering
------------------------------
Original Message:
Sent: Thu October 31, 2024 12:40 PM
From: Rafael Escudero
Subject: WAS 9.0.5.20 LinkageError with Spring-tx 5.3.31 and com/ibm/websphere/uow/UOWSynchronizationRegistry
Hi Brian.
Thanks for your reply. I however think this is not the case, as the conflict seems to be with a WAS class directly and the Spring class
Namely: com.ibm.websphere.uow.UOWSynchronizationRegistry
and org.springframework.transaction.jta.WebSphereUowTransactionManager
loaded by different ClassLoaders.
Nonetheless I did see other people with LinkageException problems that had conflict with JTA. I excluded that, but didn't have any effect.
Do you know which specific Java EE classes could be conflicting here?
Thanks!
------------------------------
Rafael Escudero
Original Message:
Sent: Thu October 31, 2024 07:37 AM
From: Brian S Paskin
Subject: WAS 9.0.5.20 LinkageError with Spring-tx 5.3.31 and com/ibm/websphere/uow/UOWSynchronizationRegistry
Without seeing a trace, I would expect that your application includes JEE libraries that conflict with those in tWAS. Exclude those libraries and the problem should go away.
Brian
------------------------------
Brian S Paskin
Sr. Technology Engineer
IBM Cloud Engineering