[jboss-jira] [JBoss JIRA] (WFLY-153) 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/WFLY-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774094#comment-12774094 ] 

RH Bugzilla Integration commented on WFLY-153:
----------------------------------------------

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

Still seeing this in EAP 6.1.0.ER8. For example:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http-session-shutdown-dist-sync/54/artifact/report/config/jboss-perf18/server.log
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http-session-undeploy-dist-sync/24/artifact/report/config/jboss-perf18/server.log
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http-session-jvmkill-dist-sync/43/artifact/report/config/jboss-perf18/server.log
                
> Fix logging of "Standard expiration of session X failed; switching to a brute force cleanup. Problem is null"
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-153
>                 URL: https://issues.jboss.org/browse/WFLY-153
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>            Reporter: Radoslav Husar
>            Assignee: Paul Ferraro
>             Fix For: 8.0.0.Alpha1
>
>
> 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