Affects Version/s: EJBCA 6.14.1
Fix Version/s: EJBCA 6.15.1
Environment:Wildfly 12 or JBoss EAP 7.1
Issue discovered during:Integration
Sprint:EJBCA Sprint 21 Team Alice
For remote EJB we need the remote EJB client library from the application server.
On Wildfly 12 the library will fail (busy at 100% CPU of one thread) to perform remote EJB invocations if we shadow the org,jboss.logging.Logger in the app-servers library (3.3.x) with the one that we bundle for Hibernate (3.1.x).
The situation also applies with JBoss EAP 7.1.
The quick solution to this is to change the order of library inclusion in our system tests from
A potential side effect that needs to be checked is if tests relying on client side Hibernate are affected (..if any.. or these should perhaps even run with a different class path).
Additionally, the WS Tests are run with
instead of systemtests.classpath and apparently this will still hang the overall systems tests with the same problem as before.