Chapter 6. Known issues
See Known Issues for JBoss EAP 7.4 to view the list of known issues for this release.
6.1. Changed behaviors for JBoss EAP 7.4
Setting OPENSHIFT_DNS_PING_SERVICE_NAME
to an empty value results in boot error
Do not set OPENSHIFT_DNS_PING_SERVICE_NAME
to an empty value. A boot error occurs and clustering is disabled.
Unpredictable web session expiration
Previously, JBoss EAP mistakenly recalculated some web session timeouts, and these sessions did not expire as specified in the web application configuration file (such as web.xml
, jboss-web.xml
or jboss-all.xml
). JBoss EAP no longer performs this mistaken calculation, so web sessions now expire as specified in the application configuration.
Memory leaks in distributed JSF applications when caching managed beans in a WebInjectionContainer
JBoss EAP cluster membership changes, such as starting or stopping a server, can cause the events that correspond to a given session to resume on a different cluster member than the one that last handled those events. Specifically, org.jboss.as.web.common.WebInjectionContainer
caches references to all managed beans and their references so that it can call ManagedReference.release
, which causes a memory leak. This issue affects distributed Jakarta Server Faces (JSF) applications that use the JBoss EAP high-availability (HA) server configuration. References to session-scoped beans can persist after the associated HTTP session expires, if a different cluster member handles that expiration. As a workaround, change the distributable-web
subsystem like in the following example:
/subsystem=distributable-web/infinispan-session-management=default/affinity=local:add
Java.lang.NullPointerException error when using ibm-java-1.8 and Bouncy Castle
If you’re directly or indirectly using the Bouncy Castle provider with IBM JDK 1.8 on JBoss EAP, you might get the following error:
Caused by: java.lang.NullPointerException at org.bouncycastle.jcajce.provider.asymmetric.rsa.BCRSAPrivateKey.getAlgorithm(BCRSAPrivateKey.java:79) at com.ibm.crypto.provider.bf.supportsParameter(Unknown Source) at javax.crypto.Cipher.a(Unknown Source) at javax.crypto.Cipher.init(Unknown Source) at javax.crypto.Cipher.init(Unknown Source) at org.bouncycastle.operator.jcajce.JceAsymmetricKeyUnwrapper.generateUnwrappedKey(JceAsymmetricKeyUnwrapper.java:109) at org.bouncycastle.cms.jcajce.JceKeyTransRecipient.extractSecretKey(JceKeyTransRecipient.java:208) at org.bouncycastle.cms.jcajce.JceKeyTransEnvelopedRecipient.getRecipientOperator(JceKeyTransEnvelopedRecipient.java:26) at org.bouncycastle.cms.KeyTransRecipientInformation.getRecipientOperator(KeyTransRecipientInformation.java:48) at org.bouncycastle.cms.RecipientInformation.getContentStream(RecipientInformation.java:169) at org.bouncycastle.cms.RecipientInformation.getContent(RecipientInformation.java:150) at org.jboss.resteasy.security.smime.EnvelopedInputImpl.getEntity(EnvelopedInputImpl.java:168) ... 76 more
To work around this issue, modify your JBoss EAP module.xml
structure similarly to that of the WFLY-14688 diff, which you can access in the Additional resources section.
Additional resources
- For more information about working around this issue, see WFLY-14688 diff.
- For more information about Bouncy Castle cryptography APIs, see bouncycastle.org.
Revised on 2024-02-08 08:04:53 UTC