[jboss-jira] [JBoss JIRA] (WFLY-7247) Wildfly 10 JSESSIONIDSSOs not being created

[Matt Smith (JIRA)]

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

Matt Smith commented on WFLY-7247:
----------------------------------

I have also been experiencing this issue on Wildfly 9.0.1 and 9.0.2 (and 10).  For me a single app out of about 8 that are deployed on the server always comes up without the SSO mechanism registered after a service restart.  The other apps never exhibit this issue.  Disabling and re-enabling the app brings it up with SSO registered.  This pattern is 100% reliable - it happens on both nodes of our 2-node UAT cluster and all three nodes of our production cluster.  Having a HTTPd reverse proxy server in front of the Wildfly server seems to trigger the behaviour.

> Wildfly 10 JSESSIONIDSSOs not being created
> -------------------------------------------
>
>                 Key: WFLY-7247
>                 URL: https://issues.jboss.org/browse/WFLY-7247
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 10.0.0.Final, 10.1.0.Final
>            Reporter: M Wardell
>            Assignee: Jason Greene
>
> Found on wildfly 10.1 and 10.0.  With SSO enabled, the server can startup in a state where not all the deployments get the SSO auth mechanism.  Possibly caused by a missing dependency between the UndertowDeploymentInfoService and SingleSignOnService, which could be allowing the deployments to start before the SSO auth mechanism is registered in the host service.
> Issue in intermittent on startup.  After most startups the JESSSIONIDSSO is reliably generated during login.  After some startups the JSESSIONIDSSO is never created after login.
> Details in the referenced forum thread.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)