This release of JBoss EAP 6 carries a bug that causes EJB3 clients to swallow exceptions unless logging is set to DEBUG.
This issue is expected to be resolved in a future release of the product.
Description of problem:
Customer had great difficulty tracking down the root cause of the EJB client failure. It turned out to be a serialization exception.
The code in EJBInvocationHandler.sendRequestWithPossibleRetries swallows the exception in order to retry other nodes. However, with this serialization exception it was never going to work.
The only way the customer could find the exception is to set DEBUG logging in production, which they find unacceptable.
Is it possible to return these exceptions up the stack to aid in troubleshooting?
Version-Release number of selected component (if applicable):
PR merged: https://issues.jboss.org/browse/EJBCLIENT-106
Shifting to 'MODIFIED'
Verified in EAP 6.3.1.CR1 / ejb client 1.0.26.Final