User development, A new message was posted in the thread "jBPM 4.3 - Multiple values (types) in JBPM4_VARIABLE for single entry.": http://community.jboss.org/message/523563#523563 Author : Martin Porter Profile : http://community.jboss.org/people/jedizippy Message: -------------------------------------------------------------- The main process is just a sequence of calls to the sub-process with continue="async". The subprocess calls a <custom> task first and then goes to a decision to evaluate the status of the custom. Then moves to a <custom> which implements ExternalActivityBehaviour and does a waitForSignal(). There is some retry handling and a timer on the ExternalActvitvityBehaviour node in case no response comes back which goes to a <task>. Thats about it. Its pretty simple stuff.   For each sub-process we pass in 3 parameters and we find that one of these parameters (String orderId) is being written into a value that also contains a Long which is created in the ExternalActvitvityBehaviour node using execution.setVariable(). So it looks like somehow the process inbound parameters are getting mixed up with ones created manually in the java code.   I read something that in 4.3 process parameters are automatically persisted now but we dont use that feature. We explicitly call setVariable() when we need to store something. The code is quite simple so it looks definitely like a bug. Problem is that its hard to reproduce.   As for the unique id generation issue we are seeing it seems to be related to JTA/Transactions so maybe when something gets rolled back this triggers the problem. Will see how it goes in next days if we see it again or not.   Sadly we can get any info on the JTA confiuration for 4.3 as no one seems to know which .cf.xml to use. The one detailed in the docs wont work on any other app server than JBoss and I still can get an answer on if jbpm.tx.jta.cfg.xml should be used or not (see previous post on transactions).   REgards Martin -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523563#523563