jBPM Processus Designer failed to initialize on Websphere 8.5.5

[blang...@gmail.com]

Hello guys,

We're currently deploying a clustered persistent jbpm-console (6.4.1-SNAPSHOT-WAS8-Final) into Websphere 8.5.5 with an Oracle database.
Everything works correctly except when we want to launch the jBPM Web design from the authoring module, the initialization of process designer stay stuck at "jBPM Web Design loading. Please Wait...".

We have investigated the reason and found in the logs that the Bpmn2Package failed during his initialization :

00001687 ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper service Uncaught service() exception thrown by servlet UUIDBasedRepositoryServlet: java.lang.NoClassDefFoundError: org.eclipse.bpmn2.Bpmn2Package (initialization failure)
at java.lang.J9VMInternals.initializationAlreadyFailed(J9VMInternals.java:84)
at org.jbpm.designer.web.profile.impl.JbpmProfileImpl.getDefinitions(JbpmProfileImpl.java:313)
at org.jbpm.designer.web.profile.impl.JbpmProfileImpl$2.parseModel(JbpmProfileImpl.java:270)
at org.jbpm.designer.web.repository.impl.UUIDBasedJbpmRepository.load(UUIDBasedJbpmRepository.java:66)
at org.jbpm.designer.web.server.UUIDBasedRepositoryServlet.doGet(UUIDBasedRepositoryServlet.java:116)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1232)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:781)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:480)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97)
at org.uberfire.ext.security.server.SecurityIntegrationFilter.doFilter(SecurityIntegrationFilter.java:61)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3928)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1007)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)
Caused by: java.lang.NoSuchMethodError: org/eclipse/dd/dc/impl/DcPackageImpl.addEOperation(Lorg/eclipse/emf/ecore/EClass;Lorg/eclipse/emf/ecore/EClassifier;Ljava/lang/String;IIZZ)Lorg/eclipse/emf/ecore/EOperation;
at org.eclipse.dd.dc.impl.DcPackageImpl.initializePackageContents(DcPackageImpl.java:519)
at org.eclipse.dd.dc.impl.DcPackageImpl.initGen(DcPackageImpl.java:153)
at org.eclipse.dd.dc.impl.DcPackageImpl.init(DcPackageImpl.java:105)
at org.eclipse.dd.dc.DcPackage.<clinit>(DcPackage.java:68)
at org.eclipse.dd.di.impl.DiPackageImpl.initGen(DiPackageImpl.java:202)
at org.eclipse.dd.di.impl.DiPackageImpl.init(DiPackageImpl.java:162)
at org.eclipse.dd.di.DiPackage.<clinit>(DiPackage.java:68)
at org.eclipse.bpmn2.di.impl.BpmnDiPackageImpl.initGen(BpmnDiPackageImpl.java:178)
at org.eclipse.bpmn2.di.impl.BpmnDiPackageImpl.init(BpmnDiPackageImpl.java:143)
at org.eclipse.bpmn2.di.BpmnDiPackage.<clinit>(BpmnDiPackage.java:71)
at org.eclipse.bpmn2.impl.Bpmn2PackageImpl.initGen(Bpmn2PackageImpl.java:1156)
at org.eclipse.bpmn2.impl.Bpmn2PackageImpl.init(Bpmn2PackageImpl.java:1122)
at org.eclipse.bpmn2.Bpmn2Package.<clinit>(Bpmn2Package.java:69)
... 34 more

We have first think about an issue linked to the 6.4.1-Final and tried to launch this version on a Wildfly AS, but on Wildfly the Process Designer is initialized correctly.
Also method addEOperation() is correctly defined in DcPackageImpl, so we believe that the issue should be related to Websphere 8.5.5.

If you have already encountered this kind of issue, we'll be very happy to read your comments on how you have fixed it, or if you have an idea for the rootcause (we don't want to influence you, but actually we are investigating if there are know marschalling problems on Webpshere).

Thanks in advance,

Jonathan

[Maciej Swiderski]

it's most likely caused by class loader settings. Make sure your application has changed the classloader from defaults and uses single application class loader and parent last strategy.

See more details about WAS setup here: https://github.com/droolsjbpm/kie-wb-distributions/tree/master/kie-wb/kie-wb-distribution-wars/src/main/assembly/was8

Maciej

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/2c474779-2cc5-40ef-9740-a1922d4dc335%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[blang...@gmail.com]

Hello Maciej,

Many thanks, we have checked the classloader configuration and it was incorrect regarding the specifications in the WAS setup.

Now it's working perfectly !

Thanks a lot !

Regards,

Jonathan