[JBoss Seam] - Re: Excessive [could not destroy component] 1.1B1 to 1.1CR1
by gavin.king＠jboss.com
Hum, OK I just realized that there *is* a problem (perhaps this is what you have been trying to say all along).
If you have an SFSB sitting in session scope, and you make some requests to the server which do not actually touch that SFSB, then the SFSB will timeout *before* the HttpSession times out. I don't see a really good way to fix this (there is no safe way to "ping" an SFSB AFAIK).
So the only solution is to set the SFSB timeout "much" longer than the HttpSession timeout. Disabling the SFSB timeout altogether will work, and should be reasonably safe to do, since Seam is pretty good about guaranteeing that cleanup occurs at HttpSession timeout.
The other solution is to simply not use SFSBs in this way. Use session-scoped SFSBs only if you know that they will be used on each page, or at the beginning of each conversation, or whatever.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990298#3990298
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990298
18 years
[JBoss jBPM] - org.jbpm.JbpmException: setRollbackOnly was invoked
by meghanai_99
Hello,
I have been struggling to get jBPM running on Tomcat 5.5.17. As it currently stands, the webapp seems to have deployed with all the jars specfieid in 'JBPM3 on Tomcat' thread. When I try to visit index.jsp I get FacesException that it cannot get value for userBean.userSelectItem. I have posted that on the same thread.
Then I copied hsqldb.jar to my jbpm\web-inf\lib and also added log4j.properties to classes folder. Now I get following exception -
org.jbpm.JbpmException: setRollbackOnly was invoked while configuration specifie
s user managed transactions
at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceServi
ce.java:139)
at org.jbpm.svc.Services.close(Services.java:211)
at org.jbpm.JbpmContext.close(JbpmContext.java:139)
at org.jbpm.msg.command.CommandExecutorThread.executeCommand(CommandExec
utorThread.java:139)
at org.jbpm.msg.command.CommandExecutorThread.run(CommandExecutorThread.
java:79)
and it is throwing this exception periodically. so my question is was it right thing to add that jar file? I did not see any hsql specific jar in the lib folder and Tomcat doesn't have any by default like jBoss so I thought of adding one.
Also I don't think I am getting anything by adding log4j.properties. How do I turn on logging from jBPM?
Please let me know what I am doing wrong? :(
I have to get this working by tomorrow :((
Thank you in advance.
- Meghana
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990294#3990294
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990294
18 years