Wildfly Session timeout configuration

[jboss234]

I am using Wildfly 10. How to configure session timeout.

I wanted to keep application session alive for 30 minutes.

Thanks,

[pferraro]

Do you mean HttpSession?  Configuration of the timeout for web sessions is standardized by the servlet specification (see section 14.4 discussing the <session-config> element of web.xml):

http://download.oracle.com/otn-pub/jcp/servlet-3_1-fr-eval-spec/servlet-3_1-final.pdf

An application can override the default the timeout per session via HttpSession.setMaxInactiveInterval(...) See section 7.5 of the spec, also:

HttpSession (Java(TM) EE 7 Specification APIs)

[jboss234]

Can it configured through Wildfly configuration files ?

Thanks,

[pferraro]

Yes - via the undertow subsystem.

e.g.

    <subsystem xmlns="urn:jboss:domain:undertow:3.1">
       <!-- ... -->
        <servlet-container name="default" default-session-timeout="30">
            <!-- ... -->
        </servlet-container>
        <!-- ... -->
    </subsystem>

30 (minutes) is already the default value.

[jboss234]

Tried it but didn't work. Am I missing anything.

Thanks,

[pferraro]

Can you be more specific?  What exactly doesn't work?

[jboss234]

Changed default time out to 45 minutes in standalone.xml

<servlet-container name="default" default-session-timeout="45">

Still application is timing out after 2 minutes ? Looks like this change is not making any difference.

Thanks,

[pferraro]

The default session timeout is only applied if the web application does not specify a session timeout.  Are you sure that your web.xml does not already define a <session-timeout/>?

[jboss234]

web.xml does not have <session-timeout> defined.

[jboss234]

My application's web.xml doen't have <session-timeout> defined, I changed <servlet-container name="default" default-session-timeout="45"> in standalone.xml looks like its not making any difference.

Any other configuration changes I need to make ?

Thanks,

[pferraro]

Please file a bug report for the Web/Undertow component at Agile Board - JBoss Issue Tracker

In the meantime, use <session-timeout/> in web.xml.

[swd847]

Why is your session timing out after 2 minutes? The only way that can happen is if you configured this in web.xml, or you have some code that is manually setting the session timeout. The default is 30 minutes.

[skull]

I am using wildfly 10.0.0-Final with domain mode + cluster with ajp + apache 2.4 with mod_cluster 1.3.1.

I have in web.xml :

<distributable />
<session-config>
    <session-timeout>30</session-timeout>
</session-config>

and the session timeout is never fired.

If i test with standalone everything is ok.

[pferraro]

When using distributed web sessions, session expiration notifications will only trigger on one node in the cluster.  Normally, this will happen on the node that created the session, but that can change if the cluster topology changes (i.e. ownership is based on a consistent hash of the session id as well as the membership size).  Might this be the case?

[skull]

Not the case. I just have one node at cluster, and if user do not call logout ("session.invalidate()"), I think that never happen on session timeout 30min.

In wildfly 8.2 its ok, I see this erro after update to wildfly 9.0.2, and now I migrate to wildfly 10 but still the same.