[jboss-jira] [JBoss JIRA] (AS7-4923) Fix logging of "Standard expiration of session X failed; switching to a brute force cleanup. Problem is null"

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/AS7-4923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757769#comment-12757769 ] 

RH Bugzilla Integration commented on AS7-4923:
----------------------------------------------

Ladislav Thon <lthon at redhat.com> made a comment on [bug 900552|https://bugzilla.redhat.com/show_bug.cgi?id=900552]

Also affects 6.1.0.ER1.

Seen in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Clustering/view/EAP6-Failover/job/eap-6x-failover-http-session-jvmkill-dist-sync/38/console-perf18/
                
> 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.2.0.CR1
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira