I was in a similar situation last week. But my case might be a litlle different
from yours because I'm running mine in CMT. Anyway, I had noticed in your code
you issued a commit only and did not use a commit and close the transaction as
ff:
| JbpmSession s = JbpmSessionFactory.getInstance().openJbpmSession();
| try {
| s.beginTransaction();
| s.getGraphSession().saveProcessInstance( p );
| s.getSession().flush(); //might be optional
| s.commitTransactionAndClose(); //commit and close
| }
| catch( Exception e) {
| s.rollbackTransactionAndClose();
| }
|
If you had done this already then disregard this suggestion. I am quite a
newbie to hibernate and had to go to their site for more info. If its a
persistence problem then its clearly about hibernate. A couple of info though
that might be useful for you - when debugging in the server, set the
hibernate.show_sql=true in jbpm.hibernate.properties so you can see the sql
statements, at least I found that very useful. Use one JbpmSession per
thread/request but the JbpmSessionFactory/configurations must be loaded only
once. BTW, what database are you using?
Elmo
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913526#3913526
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913526
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
