What is the default conversation timeout in WELD?

[rsoika]

Hi,

I have a CDI bean which uses a conversation scope. In some situations I see the following exception in the server log:

2016-09-21 11:58:45,506 ERROR [io.undertow.request] (default task-4) UT005023: Exception handling request to /imixs-office/pages/workitems/workitem.jsf: javax.servlet.ServletException: /pa
ges/workitems/workitem.xhtml @30,74 src="/pages/workitems/forms/#{workflowController.editor}.xhtml" WELD-000321: No conversation found to restore for id 6
        at javax.faces.webapp.FacesServlet.service(FacesServlet.java:671)
        at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86)

My question is: how long is the default timeout. Should I set the timeout manually or can I use a configuration param?

===
Ralph

[tremes]

Hi Ralph,

Please check Weld 2.4.0.Final - CDI Reference Implementation  and especially Weld 2.4.0.Final - CDI Reference Implementation

[rsoika]

Thanks for your response. I thought that the timeout is coupled to the web session timeout. So thanks you for your hint.

I now placed the file 'weld.properties' into /WEB-INF/classes/

Is this the right place? Because all other files (e.g. jboss-web.xml) are located directly under /WEB-INF/

[tremes]

Yes WEB-INF/classes/ is the right place.

[rsoika]

I now use the following code to synchronize my conversation timeout with the current httpSession timeout

conversation.setTimeout(((HttpServletRequest)FacesContext.getCurrentInstance().getExternalContext().
getRequest()).getSession().getMaxInactiveInterval()*1000);

[dhladky]

I am trying to configure the timeout globally as well. I created WEB-INF/classes/weld.properties file and added

org.jboss.weld.conversation.timeout=1200000

I get:

14:54:30,695 WARN  [org.jboss.weld.Configuration] (MSC service thread 1-4) WELD-001904: Unsupported configuration key found and ignored: org.jboss.weld.conversation.timeout

I use EAP 7. Any idea what I might be doing wrong? Thank you.

[tremes]

This configuration key has been added to Weld 2.3.4.Final - see [WELD-2113] Conversations - allow to configure defaultTimeout and concurrentAccessTimeout - JBoss Issue Tracker So if you are using the older Weld version then you will likely see this warning.