3 Replies Latest reply on Feb 19, 2016 2:43 AM by Martin Kouba

    Conversation time out bug?

    Filipe Amaral Newbie

      Hi Guys

       

      I was setting up a simple web project with a @ConversationScoped bean and after begining a conversation I noticed that, by logging the conversation time out value, it stands incorrect with the actual disposal time period of the bean.

       

      I'm currently using WildFly 10.0.0.Final with JDK8 on Windows.

       

      The ouput of my test:

       

       

      As you can see right after creating the bean, the conversation is started with a default timeout value of 600 seconds. Nevertheless, the bean is destroyed just after 60 seconds, since there was no interaction between client and server in the meantime.

       

      Does my analysis stands correct, or am I missing something?

       

      Best regards,

      --Filipe