| Summary: | Error on Processing Image of an started process on the jBPM console | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Jehudi Castro Sierra <jcastro> | ||||||||
| Component: | JBPM - within SOA | Assignee: | Koen Aers <koen.aers> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 4.2 Beta 1 | CC: | mvecera | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 4.2 CR3 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-253 | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: |
RHEL5, jboss-soa-p-standalone
|
|||||||||
| Last Closed: | 2008-01-18 18:24:22 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
Attachment: Added: error-jbpm.png Can you try to reproduce this with the latest jbpm-jpdl suite release? i.e. 3.2.2 Can you try to do that and attach the process definition information if this is the case? The version of the jbpm-jpdl suite used by the JBoss SOA Platform - Version 4.2.0.beta1 is 3.2.2 process definition information Attachment: Added: processDefinition.tar.gz 1. Are you sure that all the classes that are referenced in your process definition are on the classpath? More in particular the referenced actions and their dependent classes. 2. Can you attach the log file that was produces by the server. The stacktrace above is probably a result of some other error happening earlier. The server is no complaining about any missing class, so I guess that the classpath is OK. Anyway if there is a problem with the process definition, this is a quickstart (bpm_orchestration1) bug. This is the console output between the deployment of the Process Definition and the exception: 10:58:24,395 INFO [CommandExecutor] Process Definition 'processDefinition2' is deployed. 10:58:24,412 WARN [ActionProcessingPipeline] No reply to address defined for reply message! To: FileEpr [ PortReference < <wsa:Address file:/home/jcastros/Projects/SOA/BETA1/soa-4.2.0/jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/bpm_orchestration1/build/inputdir//>, <wsa:ReferenceProperties jbossesb:inputSuffix : .deployProcessESB/>, <wsa:ReferenceProperties jbossesb:errorDelete : true/>, <wsa:ReferenceProperties jbossesb:errorDir : /home/jcastros/Projects/SOA/BETA1/soa-4.2.0/jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/bpm_orchestration1/build/inputdir//>, <wsa:ReferenceProperties jbossesb:errorSuffix : .esbERROR/>, <wsa:ReferenceProperties jbossesb:postDelete : true/>, <wsa:ReferenceProperties jbossesb:postDir : /home/jcastros/Projects/SOA/BETA1/soa-4.2.0/jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/bpm_orchestration1/build/inputdir//>, <wsa:ReferenceProperties jbossesb:postSuffix : .esbDONE/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/file/> > ] MessageID: 1e68d9f9-0fda-43ce-a658-f81a1d6bd3ba 10:59:13,630 ERROR [Services] problem closing service 'persistence' org.jbpm.JbpmException: setRollbackOnly was invoked while configuration specifies user managed transactions ... Your assumptions are wrong, it is not because the deployment is ok that all the classes are available on the classpath. Please do what I asked for and upload the complete log file. It is impossible to analyze the error otherwise. attaching complete log file Attachment: Added: server.log.tar.gz Ok, the error indicates that you are using a wrong configuration for jbpm. You probably invoke setRollbackOnly somewhere in the code of one of your action handlers while your configuration indicates that you are using user managed transactions. Either update the configuration to use container managed transactions or update your actionhandler code to invoke a rollback on the transaction instead of a setRollbackOnly. Btw, I couldn't find you initial error message (Error getting diagram info: An exception of type "java.lang.NullPointerException" was thrown) in the logfile. Please make sure that you reproduce the same exact behaviour and then post the corresponding log file. In that case bpm_orchestration1 quickstart is broken, should work out of the box. the "java.lang.NullPointerException" appears on the page, as you can see in the attached screen capture, but no in the logs. If this issue is against the Quickstart now then close this issue and open a new one. Link: Added: This issue related SOA-343 I'm closing this JIRA in favor of opening a new JIRA for this quickstart. Link: Added: This issue related SOA-344 Link: Added: This issue related SOA-345 Link: Added: This issue is a dependency of SOA-446 |
Date of First Response: 2008-01-08 10:11:39 project_key: SOA 1. Run the bpm_orchestration1 quickstart 2. Enter to the jBPM console, examine the process, start the process 3. Enter to the Process Image Get the message: Error getting diagram info: An exception of type "java.lang.NullPointerException" was thrown. See logs attached. Console output: 18:41:37,073 ERROR [Services] problem closing service 'persistence' org.jbpm.JbpmException: setRollbackOnly was invoked while configuration specifies user managed transactions at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:206) at org.jbpm.persistence.jta.JtaDbPersistenceService.close(JtaDbPersistenceService.java:34) at org.jbpm.svc.Services.close(Services.java:225) at org.jbpm.JbpmContext.close(JbpmContext.java:139) at org.jbpm.jsf.core.phase.JbpmPhaseListener.closeContext(JbpmPhaseListener.java:94) at org.jbpm.jsf.core.phase.JbpmPhaseListener.afterPhase(JbpmPhaseListener.java:45) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) 18:41:37,074 ERROR [CachedConnectionValve] Application error: Faces Servlet did not complete its transaction