Do you have any monitoring tool that keeps pinging some page/url of the application ? Or if the application pages contains some sort of ajax that polls resources, if this is true, then the session will not expire.
Also, check the expiration timeout in web.xml
We've already check our web.xml - it has the standard
Also tried defining default-session-timeout in standalone.xml but issue still occurs. Yes, we have some keep-alive implementation on some of our pages/url but this scenario where I can replicate the issue is just loading our home page which doesn't have any polling mechanism. Please also note that the replication steps doesn't have any issue using jboss eap 6.2. I wonder if there is something related in our apache config during our upgrade from jboss 6.2 to jboss 7.0 that's causing this since in our local (dev) environment which doesn't have the apache layer, we can't replicate the issue using jboss 7.0 and jboss 7.1. We can only replicate this in azure vms. We've also tried using latest versions of undertow libraries but still no luck.
Thank you for your feedback Claudio!
Is this a <distributable/> web application?
Nope. We did not define <distributable/> in our web.xml and we only have one node on our current setup. We have Apache httpd in front. Any leads please? Our initial hope was by using the latest undertow version (1.4.24 and 2.0.5-Final) would resolve this issue as stated in other threads for this the same issue that it was an undertow problem. It feels weird though that there is no enough conversation regarding this if this still a jboss issue so another angle we are leaning is maybe we are just missing some configuration somewhere during our upgrade as it was working fine in jboss 6.2.
Can you activate access log for the undertow server in wildfly configuration ? This way you will see if there are requests on the undertow server and if this is true, the session will keep active.
You can activate it in web console, configuration -> web (undertow) -> server -> view -> hosts -> (selected the host) -> Access Log (tab) -> Add
Or using CLI,
This can be done thru standalone.xml with this definition - <access-log prefix="undertow_access" pattern="%h %l %u %t %r %s %b %T"/>, correct? The session logged a few lines during loading of the page which I assume is fine but nothing else after that. Is this the expected behavior? One thing to note though in the access log is the continuous hazelcast logging to connect to mancenter for our distributed caching (we only have one node for now) but this should not be tied to any of the sessions.