[jboss-jira] [JBoss JIRA] (WFLY-9014) Second remote EJB client connection prevents server from shutting down (Elytron, Remoting)

[Darran Lofthouse (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darran Lofthouse updated WFLY-9014:
-----------------------------------
    Priority: Major  (was: Blocker)


> Second remote EJB client connection prevents server from shutting down (Elytron,  Remoting)
> -------------------------------------------------------------------------------------------
>
>                 Key: WFLY-9014
>                 URL: https://issues.jboss.org/browse/WFLY-9014
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Remoting, Security
>            Reporter: Josef Cacek
>            Assignee: David Lloyd
>
> Second call of EJB client causes server stuck in some cases. When this happens administrator is not able to shutdown or reload such a server.
> *Scenario details:*
> Elytron is configured as security provider on servers and Elytron client API is used for authentication. Protected stateless beans are used.
> {noformat}
> EJB Client -> Entry bean on Server1 -> WhoAmI bean on Server2
> {noformat}
> * Client uses {{AuthenticationConfiguration}} with valid credentials for Server1; Client calls the Entry bean twice - the difference is in arguments provided. The arguments are subsequently used for authentication from Server1 to Server2 (using AuthenticationConfiguration):
> ** first call uses null for both username and password
> ** second call uses valid credentials for Server2
> * Entry bean  on Server1 calls WhoAmI bean on Server2 with credentials which was provided as method arguments;
> * WhoAmI bean on Server2 just returns caller principal
> The Client is executed twice, the second call doesn't finish



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)