1 Reply Latest reply on Aug 10, 2010 2:32 PM by mhfox

    jBPM 3.2.3 (with Seam 2.2.0) on WebSphere

    mhfox

      Hello,

      I've got a Seam 2.2 app that that has been running on JBoss and I now need to get it running on WebSphere.  I've run across an error now during the deployment of the business process.  When it goes to the database to look for an existing process (which does exist) I get back an odd error as shown below:

       

      java.lang.ClassCastException: org.jbpm.graph.def.ProcessDefinition incompatible with org.jbpm.graph.def.ProcessDefinition
           at org.jbpm.db.GraphSession.findLatestProcessDefinition(GraphSession.java:153)
           at uk.co.iblocks.jbpm.JbpmExtensions$ProcessDescriptor.<init>(JbpmExtensions.java:84)
           at uk.co.iblocks.jbpm.JbpmExtensions.installProcessDefinitions(JbpmExtensions.java:404)
           at uk.co.iblocks.jbpm.JbpmExtensions.startup(JbpmExtensions.java:352)
           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
           at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
           at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
           at java.lang.reflect.Method.invoke(Method.java:600)
           at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
           at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144)
           at org.jboss.seam.Component.callComponentMethod(Component.java:2249)
           at org.jboss.seam.Component.callCreateMethod(Component.java:2172)
           at org.jboss.seam.Component.newInstance(Component.java:2132)
           at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
           at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
           at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:116)
           at org.jboss.seam.init.Initialization.init(Initialization.java:740)
           at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36)
           at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1678)
           at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:371)
           at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:298)
           at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)
           at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
           at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:731)
           at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:616)
           at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376)
           at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668)
           at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1122)
           at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1315)
           at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:619)
           at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:940)
           at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:725)
           at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2046)
           at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:439)
           at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
           at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:382)
           at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$300(CompositionUnitMgrImpl.java:110)
           at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:949)
           at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
           at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)

       

      All I can figure is that it's pulling back a null and trying to cast that, but when I look at the hibernate query defined by GraphSession.findProcessDefinitionByNameAndVersion, everything looks good and there certainly should be data. I'm not seeing any hibernate issues at the DEBUG level in log4j.

       

      Has anyone here ever run into this or something similar before?

      thanks,

      Mike

        • 1. Re: jBPM 3.2.3 (with Seam 2.2.0) on WebSphere
          mhfox

          As usual, I'll look at something all day, and as soon as I post it I find the answer.  I keep forgetting that WebSphere won't allow the WAR access to libraries stored in the EAR.  I had to copy some jars over to the WAR and I got past it.

           

          On to the next issue now!