Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion "Re: workItemByteArray null when persisting WorkItemInfo" To view the discussion, visit: https://community.jboss.org/message/773623#773623 -------------------------------------------------------------- could you provide bit more details? Is this a human task or a custom work item? Would be great if you could provide test case that illustrates this. So far I have not seen this at all but it is very important Cheers -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/773623#773623] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion "Re: workItemByteArray null when persisting WorkItemInfo" To view the discussion, visit: https://community.jboss.org/message/774784#774784 -------------------------------------------------------------- Just tried with two data bases (H2 and postgresql) and default HumanTask work item handler and workiteminfo table has properly set byte array, so can't really see any problem with that and in fact there was no change in that area. If you could provide some test cases that illustrates it it would make it easier to look into that but without being able to reproduce it can't help much here. HTH -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/774784#774784] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Timothy Charman [https://community.jboss.org/people/tcharman] created the discussion "Re: workItemByteArray null when persisting WorkItemInfo" To view the discussion, visit: https://community.jboss.org/message/774868#774868 -------------------------------------------------------------- Hi Maciej The latest is now that the WorkItemInfo is actually being written with the byte array, and deleted a few log lines later, so we don't think that is the real issue.  We are now seeing this: 16:51:17,738 DEBUG [org.hibernate.engine.jdbc.internal.LogicalConnectionImpl] (NioProcessor-7) Aggressively releasing JDBC connection 16:51:17,739 DEBUG [org.hibernate.engine.jdbc.internal.LogicalConnectionImpl] (NioProcessor-7) Releasing JDBC connection 16:51:17,739 DEBUG [org.hibernate.engine.jdbc.internal.LogicalConnectionImpl] (NioProcessor-7) Released JDBC connection 16:51:17,739 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] (NioProcessor-7) Looking for a JTA transaction to join 16:51:17,739 WARN  [org.hibernate.ejb.AbstractEntityManagerImpl] (NioProcessor-7) HHH000326: Cannot join transaction: do not override hibernate.transaction.factory_class We have this in persistence.xml:       <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup" /> Our datasource uses the standard MySQL driver, not the XA driver... could that be the problem? Thanks -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/774868#774868] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Timothy Charman [https://community.jboss.org/people/tcharman] created the discussion "Re: workItemByteArray null when persisting WorkItemInfo" To view the discussion, visit: https://community.jboss.org/message/775278#775278 -------------------------------------------------------------- Yes, we are on AS7 and Hibernate 4.  We followed Marco's recommendations and that seems to remove a bunch of error messages, but now we're running into a couple of oddities when debugging why it still won't work. Our task handler is meant to be a long running process, which enters a wait state after calling externally.  I believe that the WorkItemInfo table is written prior to hitting the wait state, and on hitting the wait state the bytearray with the work item's state is persisted with an update statement. Either we see this: - The WorkItemInfo record is written, the byte array is not written, and on completing the task handler the JPAWorkItemManager reads state out of memory, hits the signalEvent and hangs on synchronisation. - The WorkItemInfo record is written, the byte array is written, but on completing the task the WorkItemInfo record is already deleted, cannot be retrieved from memory or from DB, and so the process fails. We continue to debug. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775278#775278] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Namjun Park [https://community.jboss.org/people/pnj1917] created the discussion "Re: workItemByteArray null when persisting WorkItemInfo" To view the discussion, visit: https://community.jboss.org/message/775316#775316 -------------------------------------------------------------- Hi Maciej, I'm Namjun who work with Tim and Khetha. What we found was that when we remove the timer task(10min) from our workflow it works fine and workItemByteArray gets updated properly. Originally, we have a timer task just right after begining(start event) in our jBPM workflow. Do you have any idea if there is any relation between timer task and storing workItemByteArray? Namjun -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775316#775316] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]