[ http://jira.jboss.com/jira/browse/JBESB-1236?page=all ] Kevin Conner closed JBESB-1236. ------------------------------- Resolution: Rejected This is not part of the project, you need to feed issues back to Burr. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1236?page=comments#action_12384540 ] Burr Sutter commented on JBESB-1236: ------------------------------------ jBPM is a feature of the project and this feature should work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1236?page=comments#action_12384546 ] Burr Sutter commented on JBESB-1236: ------------------------------------ I can reproduce it consistently (pulled from trunk at 8:15 AM EDT, Oct 26). This does require manual testing. And you are correct, this is related to jBPM Hibernate however it is still our issue to chase down since it impacts our users. I've not had much time to dig in, it could be a configuration issue or perhaps something we need to tweak in the actual test case. 08:22:37,812 ERROR [LazyInitializationException] could not initialize proxy - no Session org.hibernate.LazyInitializationException: could not initialize proxy - no Sessi on at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyIn itializer.java:57) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(Abstrac tLazyInitializer.java:111) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyI nitializer.java:150) at org.jbpm.bytes.ByteArray$$EnhancerByCGLIB$$946ef8a5.getBytes(<generat ed>) at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.rever t(SerializableToByteArrayConverter.java:62) at org.jbpm.context.exe.VariableInstance.getValue(VariableInstance.java: 147) at org.jbpm.context.exe.VariableContainer.getVariablesLocally(VariableCo ntainer.java:125) at org.jbpm.context.exe.VariableContainer.getVariables(VariableContainer .java:106) at org.jbpm.context.exe.ContextInstance.getVariables(ContextInstance.jav a:106) at org.jbpm.context.exe.ContextInstance.getVariables(ContextInstance.jav a:95) at org.jboss.soa.esb.services.jbpm.actions.impl.facades.FacadeUtil.jbpmV arsToMessage(FacadeUtil.java:130) at org.jboss.soa.esb.services.jbpm.actions.impl.facades.SignalFacade.pos tFormat(SignalFacade.java:65) at org.jboss.soa.esb.services.jbpm.actions.BpmProcessor.process(BpmProce ssor.java:65) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.process Methods(ActionProcessorMethodInfo.java:102) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcesso r.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process( ActionProcessingPipeline.java:276) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(Messag eAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:675) at java.lang.Thread.run(Thread.java:595) AND perhaps related: org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation targe t exception from processor at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.process Methods(ActionProcessorMethodInfo.java:127) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcesso r.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process( ActionProcessingPipeline.java:276) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(Messag eAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:675) at java.lang.Thread.run(Thread.java:595) Caused by: org.jbpm.JbpmException: couldn't deserialize object at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.rever t(SerializableToByteArrayConverter.java:66) at org.jbpm.context.exe.VariableInstance.getValue(VariableInstance.java: 147) at org.jbpm.context.exe.VariableContainer.getVariablesLocally(VariableCo ntainer.java:125) at org.jbpm.context.exe.VariableContainer.getVariables(VariableContainer .java:106) at org.jbpm.context.exe.ContextInstance.getVariables(ContextInstance.jav a:106) at org.jbpm.context.exe.ContextInstance.getVariables(ContextInstance.jav a:95) at org.jboss.soa.esb.services.jbpm.actions.impl.facades.FacadeUtil.jbpmV arsToMessage(FacadeUtil.java:130) at org.jboss.soa.esb.services.jbpm.actions.impl.facades.SignalFacade.pos tFormat(SignalFacade.java:65) at org.jboss.soa.esb.services.jbpm.actions.BpmProcessor.process(BpmProce ssor.java:65) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.process Methods(ActionProcessorMethodInfo.java:102) ... 6 more Caused by: org.hibernate.LazyInitializationException: could not initialize proxy - no Session at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyIn itializer.java:57) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(Abstrac tLazyInitializer.java:111) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyI nitializer.java:150) at org.jbpm.bytes.ByteArray$$EnhancerByCGLIB$$946ef8a5.getBytes(<generat ed>) at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.rever t(SerializableToByteArrayConverter.java:62) ... 19 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1236?page=comments#action_12384562 ] Kevin Conner commented on JBESB-1236: ------------------------------------- On reading this again it looks like this may not be a classloader issue. The stacktrace shows a deserialisation error but further up it shows an error message from hibernate when deserialising a proxy from the vars. The proxy obviously requires a hibernate session to be active when it is being deserialised. I have sent an email to Tom Baeyens asking for his opinion of our code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1236?page=comments#action_12384594 ] Kevin Conner commented on JBESB-1236: ------------------------------------- This is Tom's reply. "after serialization and deserialization, a process instance is not auto-connectable to hibernate session. serialize the token.getId() or processInstance.getId(). on the other end, load the process instance or token in another JbpmContext block." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1236?page=all ] Kevin Conner updated JBESB-1236: -------------------------------- Fix Version/s: 4.3 (was: 4.2.1) Moving this to a later release, it will be handled with the rest of the jBPM integration issues. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1236?page=all ] Kurt Stam reassigned JBESB-1236: -------------------------------- Assignee: Kurt Stam (was: Kevin Conner) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1236?page=comments#action_12386671 ] Kevin Conner commented on JBESB-1236: ------------------------------------- Fady, this issue came to light in a quickstart which Burr Sutter created. The cause of the error is an attempt by the ESB integration code to deserialise and access jBPM variables without creating a jBPM context. We are currently looking at the ESB/jPBM integration and this issue is one to be addressed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1236?page=comments#action_12386805 ] Kevin Conner commented on JBESB-1236: ------------------------------------- Tom, this is the issue I emailed you about a couple of weeks ago. I included your reply in one of the earlier comments. The error is definitely within the ESB integration layer and is not jBPM. The issue is more basic than transactions though, the integration code attempts to access these variables outside of a jBPM context. The code in question was intended to do what you suggest, return the actual values to the client, but the way in which it is doing this is incorrect. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1236?page=all ] Kurt Stam closed JBESB-1236. ---------------------------- Resolution: Done Fixed, largely by making the interaction asynchronous, but also by using our own CommandServiceImpl, which does not close the session, until closed later 'by hand'. I'll bring this up with TomB, as I think jBPM could do something nicer here so that we don't have to have our own version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira