3 Replies Latest reply on Jul 17, 2007 9:35 AM by Toni Beckman

    Could not destroy component

    Toni Beckman Novice

      Hi,

      have read about the problem with components vanishing before the http sessions ends.

      I have left the sfsb timeout at 30 min, set the http session timeout to 20 and the conversation timeout to 60 min.

      I still get the error "Could not destroy component". Is this because of the conversation timeout of 60 min? I thought that every conversation is being destroyed, when the http session ends?!

      Also I was wondering how to interpretate the sfsb timeout. Will my sfsb be removed, even if its involved in some batch processing for a longer preriod than 30 minutes? For example a database update?

        • 1. Re: Could not destroy component
          Gavin King Master

          You need to make the SFSB timeout longer than your conversation timeout if you have concurrent conversations.

          • 2. Re: Could not destroy component
            Toni Beckman Novice

            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 Beckman Novice

              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)