[
https://issues.jboss.org/browse/AS7-4923?page=com.atlassian.jira.plugin.s...
]
Radoslav Husar commented on AS7-4923:
-------------------------------------
Interestingly this happens on other nodes in the cluster where the session was not
created:
{noformat}
perf18.log:[JBossINF] 19:54:12,862 WARN [org.apache.catalina.session.ManagerBase]
(ContainerBackgroundProcessor[StandardEngine[jboss.web]]) JBAS018080: Standard expiration
of session 7TYWbrkMf6UGi4WUu2Z3VUam failed; switching to a brute force cleanup. Problem is
null
perf19.log:[JBossINF] 19:54:15,654 WARN [org.apache.catalina.session.ManagerBase]
(ContainerBackgroundProcessor[StandardEngine[jboss.web]]) JBAS018080: Standard expiration
of session 7TYWbrkMf6UGi4WUu2Z3VUam failed; switching to a brute force cleanup. Problem is
null
perf20.log:[JBossINF] 19:54:15,425 WARN [org.apache.catalina.session.ManagerBase]
(ContainerBackgroundProcessor[StandardEngine[jboss.web]]) JBAS018080: Standard expiration
of session 7TYWbrkMf6UGi4WUu2Z3VUam failed; switching to a brute force cleanup. Problem is
null
perf21.log:[JBossINF] 19:48:12,501 INFO
[org.jboss.test.clusterbench.common.session.CommonHttpSessionServlet]
(ajp-perf21/10.16.90.60:8009-71) New session created: 7TYWbrkMf6UGi4WUu2Z3VUam.perf21
{noformat}
The client just left the session to expire
{noformat}
perf22.log:2012/05/26 19:48:05:409 EDT [DEBUG][RMI TCP Connection(24)-10.16.90.52] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - [Runner - 1975] Using #0 URL:
http://perf22:8080/clusterbench-passivating/session
perf22.log:2012/05/26 19:48:12:066 EDT [INFO ][Runner - 1975] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - [HttpSessionInvalidatorFactory] First
request. Will expire after: 366794 ms.
perf22.log:2012/05/26 19:48:12:703 EDT [DEBUG][Runner - 1975] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JvmRoute assigned: perf21
perf22.log:2012/05/26 19:48:12:703 EDT [DEBUG][Runner - 1975] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Session assigned:
7TYWbrkMf6UGi4WUu2Z3VUam
perf22.log:2012/05/26 19:48:12:704 EDT [INFO ][Runner - 1975] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - [RandomDelayRequestProcessorFactory]
Delaying request for 208 s - session 7TYWbrkMf6UGi4WUu2Z3VUam.perf21
perf22.log:2012/05/26 19:54:21:203 EDT [INFO ][Runner - 1975] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - [HttpSessionInvalidatorFactory] Setting
new state on HttpClient, session was - 7TYWbrkMf6UGi4WUu2Z3VUam.perf21
{noformat}
Fix logging of "Standard expiration of session X failed;
switching to a brute force cleanup. Problem is null"
-------------------------------------------------------------------------------------------------------------
Key: AS7-4923
URL:
https://issues.jboss.org/browse/AS7-4923
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.2.Final (EAP)
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Fix For: 7.1.3.Final (EAP)
I am seeing exception with missing reason
{noformat}
19:54:12,862 WARN [org.apache.catalina.session.ManagerBase]
(ContainerBackgroundProcessor[StandardEngine[jboss.web]]) JBAS018080: Standard expiration
of session 7TYWbrkMf6UGi4WUu2Z3VUam failed; switching to a brute force cleanup. Problem is
null
{noformat}
Looks like the actual exception is not well propagated to the message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira