This content has been marked as final.
Show 3 replies
-
1. Re: Could not destroy component
gavin.king Jul 5, 2007 1:31 PM (in response to toni)You need to make the SFSB timeout longer than your conversation timeout if you have concurrent conversations.
-
2. Re: Could not destroy component
toni Jul 16, 2007 9:19 AM (in response to toni)Here are the config files. What am I missing? I guess besides the web.xml descriptor timeouts are meassured in ms (you should put this in the docs)?
web.xml<!-- ==================== Default Session Configuration ================= --> <!-- You can set the default session timeout (in minutes) for all newly --> <!-- created sessions by modifying the value below. --> <session-config> <session-timeout>20</session-timeout> </session-config>
standardjboss.xml<max-bean-life>1800</max-bean-life>
components.xml<!-- 120 0 000 ms conversation timeout = 20 minuten --> <component name="org.jboss.seam.core.manager"> <property name="conversationTimeout">1200000</property> </component>
-
3. Re: Could not destroy component
toni Jul 17, 2007 9:35 AM (in response to toni)But I still keep getting this exception:
007-07-17 15:25:54,741 WARN [org.jboss.seam.contexts.Contexts] Could not destroy component: messageSchedulerManager javax.ejb.EJBNoSuchObjectException: Could not find Stateful bean: 5x6n5t5h-ieb81j-f471zzrs-1-f48dvzar-az at org.jboss.ejb3.cache.simple.SimpleStatefulCache.get(SimpleStatefulCache.java:268)