OpenLiberty / open-liberty

Open Liberty is a highly composable, fast to start, dynamic application server runtime environment
https://openliberty.io
Eclipse Public License 2.0
1.16k stars 599 forks source link

OL wssecurity CXF SAML/SAML.2 FAT with EE8 and Java11 failed with feature conflict #17097

Closed meiaus closed 3 years ago

meiaus commented 3 years ago

Running wsscxf.saml and wsscxf.saml.2 FAT with EE8 wssecurity latest runtime (including April 29 commits) either with Java11 or Java8, the EE8 tests all failed with the same error related to feature conflict.
Below logs are from one of the tests as an example:

- ffdc
- ffdc

------Start of DE processing------ = [5/7/21, 20:11:48:556 PDT] Exception = java.lang.IllegalArgumentException Source = com.ibm.ws.kernel.feature.internal.FeatureManager probeid = reportErrors Stack Dump = java.lang.IllegalArgumentException: Unable to load conflicting versions of features "com.ibm.websphere.appserver.samlWeb2.0.internal.opensaml-2.6" and "com.ibm.websphere.appserver.samlWeb2.0.internal.opensaml-3.4". The feature dependency chains that led to the conflict are: com.ibm.websphere.appserver.samlWeb-2.0 -> io.openliberty.samlWeb2.0.internal.ee-6.0 -> com.ibm.websphere.appserver.samlWeb2.0.internal.opensaml-2.6 and com.ibm.websphere.appserver.wsSecuritySaml1.1-jaxws2.3 -> com.ibm.websphere.appserver.samlWeb2.0.internal.opensaml-3.4 at com.ibm.ws.kernel.feature.internal.FeatureManager.reportErrors(FeatureManager.java:1864) at com.ibm.ws.kernel.feature.internal.FeatureManager.updateFeatures(FeatureManager.java:1390) at com.ibm.ws.kernel.feature.internal.FeatureManager.update(FeatureManager.java:749) at com.ibm.ws.kernel.feature.internal.FeatureManager.processFeatureChanges(FeatureManager.java:863) at com.ibm.ws.kernel.feature.internal.FeatureManager$1.run(FeatureManager.java:649) at com.ibm.ws.threading.internal.ExecutorServiceImpl$RunnableWrapper.run(ExecutorServiceImpl.java:238) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:836)

- ffdc

------Start of DE processing------ = [5/7/21, 20:11:48:578 PDT] Exception = java.lang.IllegalArgumentException Source = com.ibm.ws.kernel.feature.internal.FeatureManager probeid = reportErrors Stack Dump = java.lang.IllegalArgumentException: Unable to load conflicting versions of features "com.ibm.websphere.appserver.wss4j-1.0" and "com.ibm.websphere.appserver.wss4j-2.3". The feature dependency chains that led to the conflict are: com.ibm.websphere.appserver.samlWeb-2.0 -> io.openliberty.samlWeb2.0.internal.ee-6.0 -> com.ibm.websphere.appserver.samlWeb2.0.internal.opensaml-2.6 -> com.ibm.websphere.appserver.wss4j-1.0 and com.ibm.websphere.appserver.wsSecurity1.1-jaxws2.3 -> com.ibm.websphere.appserver.wsSecurity1.1.internal.jaxws-2.3 -> com.ibm.websphere.appserver.wss4j-2.3 at com.ibm.ws.kernel.feature.internal.FeatureManager.reportErrors(FeatureManager.java:1864) at com.ibm.ws.kernel.feature.internal.FeatureManager.updateFeatures(FeatureManager.java:1390) at com.ibm.ws.kernel.feature.internal.FeatureManager.update(FeatureManager.java:749) at com.ibm.ws.kernel.feature.internal.FeatureManager.processFeatureChanges(FeatureManager.java:863) at com.ibm.ws.kernel.feature.internal.FeatureManager$1.run(FeatureManager.java:649) at com.ibm.ws.threading.internal.ExecutorServiceImpl$RunnableWrapper.run(ExecutorServiceImpl.java:238) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:836)

meiaus commented 3 years ago

@arunavemulapalli

jhanders34 commented 3 years ago

Are these runs with the commits in PR #16725? Those changes have not been merged yet. I am still doing review for them and have concerns about the feature file changes.

arunavemulapalli commented 3 years ago

@jhanders34 , Yes. Mei-hsiang is trying to run the updated tests with the commits from the mentioned PR to make progress with the FAT changes. I am going to close this issue and we need to track Mei-hsiang's work with some other mechanism.