Hi Gavin, No don't think so, the timeout was set pretty high. I did set it even higher today:
| <context-param> | <param-name>org.jboss.seam.core.manager.conversationTimeout</param-name> | <param-value>3600000</param-value> | </context-param> | but with no effect. Plus - if the conversation gets timed out the SFSB should be destroyed, right? And the brakepoint in the @Destroy method gets never called before undeploy. cu, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912565#3912565 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912565 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
