[jBPM] - jBPM 5.3.0 - Persistence fails a little bit
by nt2005
nt2005 [https://community.jboss.org/people/nt2005] created the discussion
"jBPM 5.3.0 - Persistence fails a little bit"
To view the discussion, visit: https://community.jboss.org/message/744185#744185
--------------------------------------------------------------
Hey Guys,
I upgraded my ear from 5.2.0 to 5.3.0. It seems to work fine but persistence fails. An example what I mean:
I have a global handler who goes in all workitems. In this handler I save text or pictures generated by the workitems.
GuiProcessHandler handler = new GuiProcessHandler();
// add any text example
handler.addText(123124124l, "Hello World");
Map<String, Object> params = new HashMap<String, Object>();
params.put("handler", handler);
// start a new process instance
ksession.startProcess(process_bpmn_id, params); //workitems make changes to the handler
In my BPMN-File the Handler looks like:
<itemDefinition id="_handlerItem" />
And goes into each workitem with:
<task id="_100" name="DoIt" tns:taskName="doIt" >
<ioSpecification>
<dataInput id="_100_handlerInput" name="handler" />
<inputSet>
<dataInputRefs>_100_handlerInput</dataInputRefs>
</inputSet>
</ioSpecification>
<dataInputAssociation>
<sourceRef>handler</sourceRef>
<targetRef>_100_handlerInput</targetRef>
</dataInputAssociation>
</task>
After process is finish. I get all images out of the handler. Brilliant.
But if I reload the session and the process the handler only contains the text "Hello World"
Anyone have an idea? WIth jBPM 5.2 it works well.
I hope you could understood my problem. If not tell me. ;)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/744185#744185]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 5 months
[JBoss Messaging] - Re: XA transaction does not work correctly
by Justin Bertram
Justin Bertram [https://community.jboss.org/people/jbertram] created the discussion
"Re: XA transaction does not work correctly"
To view the discussion, visit: https://community.jboss.org/message/744093#744093
--------------------------------------------------------------
So the question here really isn't related to HornetQ. The question is how JBoss Messaging, acting as a JTA resource manager, behaves when a transaction manager prepares a transaction involving one of its resources. Specifically, if JBoss Messaging will ever terminate the in-doubt transaction on its own (e.g. via a time-out).
To my knowledge, the answer to that question is, "no." The messages added to or removed from the destination will simply stay in the prepared stage. The in-doubt transaction will not be rolled-back or committed automatically by the resource manager (i.e. JBoss Messaging). Ideally you would have recovery configured in the AS instance which was managing the transaction so all this would be resolved without manual intervention. However, if that isn't configured correctly then the jboss.messaging:service=ServerPeer MBean has several operations you can use to resolve the transaction as far as JBoss Messaging is concerned from the JMX Console:
* showPreparedTransactionsAsHTML
* commitPreparedTransaction
* rollbackPreparedTransaction
There is no way to configure JBoss Messaging to terminate the transaction itself.
*Note:* Even if you resolve the transaction in the resource manager, the transaction manager will still have the in-doubt transaction in its log and it will still complain periodically that it can't recover it.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/744093#744093]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 5 months