Red Hat Bugzilla – Bug 845229
Many warnings occur when deploying BRMS 5.3.0 .war files on EAP 6.0
Last modified: 2016-09-20 01:08:29 EDT
Created attachment 601928 [details]
server.log with many class-path reference warnings
Many warnings occur when deploying BRMS 5.3.0 .war files on EAP 6.0. It's because the application server complains about that many classpath entries do not point to a valid jar for a Class-Path reference. See the attached server.log file.
This issue happens on jbpm console, designer but also guvnor. This issue will probably need to be split up.
It's caused because some of our dependencies (such as derby) have a META-INF/Manifest.MF file with a "Class-Path" entry.
End-user jars (such as drools-planner-examples and drools-examples) are allowed to use a "Class-Path" entry, but non-end users jars (which are used as dependencies) should NOT use that.
I don't see a direct way to fix it, except for trying to get rid of those "bad" dependencies if possible.
On the guvnor side: derby comes in through jackrabbit-core.
[INFO] | +- org.drools:guvnor-repository-connector-jackrabbit:jar:5.3.4-SNAPSHOT:runtime
[INFO] | | \- org.apache.jackrabbit:jackrabbit-core:jar:2.2.8:runtimee
[INFO] | | \- org.apache.derby:derby:jar:10.5.3.0_1:runtime
Guvnor suffers from this on the jars derby, itext and jaxb-impl. Unless we're willing to rerelease those jars (which is not realistic and not maintainable), we can't do much about it.
So the only options I see are:
- Wait till those jar stop using the "Class-Path" entry and upgrade
- A) Ignore the warnings
- B) Figure out a way to hide the warnings (with a JBoss AS switch or by logging config).
With regards to human-task and console-server, I've removed as many possible extraneous jars (that were mostly used for hibernate 3 and thus not used any more) from the EAP 6 wars. Any other warning messages with regards to these 2 wars are unavoidable until BRMS/SOA moves to EAP 6.
Geoffrey and Tihomir will have to speak for their respective projects (Guvnor, Designer) themselves.
Setting to new, since I'm not actively working on this issue and also because it also partially falls under Geoffrey's and Tihomir's purview/responsibilities.
Added jira's for Designer and Guvnor issues.
Marco Rietveld <email@example.com> updated the status of jira JBPM-3821 to Resolved
Marco Rietveld <firstname.lastname@example.org> made a comment on jira JBPM-3821
Designer is being rewritten.
Marco Rietveld <email@example.com> updated the status of jira GUVNOR-1955 to Resolved
Marco Rietveld <firstname.lastname@example.org> made a comment on jira GUVNOR-1955
Guvnor is being rewritten.
Marco Rietveld <email@example.com> updated the status of jira GUVNOR-1955 to Reopened
Jiri, I would like to close this bug. Is there a satisfactory solution that you could suggest here? None of the current warnings are due to jbpm components, as far as I know (warnings are generated by either designer or guvnor, not jbpm components).
this Bugzilla is deprecated as it targets already released BRMS 5.3.x. So closing it as Verified. If there will be similar issues in jBPM 6, new Bugzilla will be opened.