Session keeps renewing when checking the status of a job in a JBoss EAP 7.2 application server.

Session keeps renewing when checking the status of a job in a JBoss EAP 7.2 application server.

When checking the status of a job in a JBoss EAP 7.2 application server, the session keeps renewing, causing the user to be logged in indefinitely. This issue can occur due to several reasons, and the following steps can help identify and resolve the problem:

1. Check the JBoss EAP 7.2 documentation and the specific JMS or messaging component used in the application to ensure that the session timeout is set correctly. The default session timeout is usually 30 minutes, but it can be configured differently depending on the application's requirements.

2. Verify that the application code is not keeping the session alive unnecessarily. Check if the application code is using the session's renew method or setting the session's maxInactiveInterval explicitly. If so, ensure that the code is using the correct value for the session timeout.

3. Check if there are any deadlocks or circular references in the application code that could be preventing the session from expiring. Use the JBoss EAP 7.2 console or log files to identify any suspicious activity or errors related to the session or the job processing.

4. Verify that the JBoss EAP 7.2 server's session timeout is set correctly. Check the standalone.xml or domain.xml configuration file to ensure that the session-timeout element is set to the desired value.

5. Check if there are any network or connectivity issues that could be preventing the session from expiring. Use network monitoring tools to identify any packet loss, latency, or other issues that could be affecting the session's expiration.

6. If the issue persists, try disabling session tracking for the JMS or messaging component used in the application. This can be done by setting the jms-client-context-service.session-tracking property to false in the standalone.xml or domain.xml configuration file. However, this may have performance implications and should be used as a last resort.

7. If none of the above steps resolve the issue, consider contacting the JBoss EAP 7.2 support team for further assistance. They may be able to provide additional insights or solutions based on the specific application and configuration.