[jboss-jira] [JBoss JIRA] Updated: (JBAS-8636) UnifiedInvokerProxyHA constructor creates an invalid initial client

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated JBAS-8636:
-----------------------------------

    Description: 
The UnifiedInvokerProxyHA constructors call the superclass constructors and then set the subsystem to "invokerha". Problem is the superclass constructors create the remoting Client before the subsystem is set, resulting in the incorrect default "invoker" subsystem being used for that client.

This results in problems (probably NPE or ClassCastException) when UnifiedInvokerProxyHA.invoke tries to handle response values. It expects the response to be an HARMIResponse, and it won't be because the wrong server-side invoker is used.

This affects clients who run in the AS and have disabled the legacy client interceptors logic that directly routes calls to the locally deployed bean. This is a fairly unusual combination.

  was:
The UnifiedInvokerProxyHA constructors call the superclass constructors and then set the subsystem to "invokerha". Problem is the superclass constructors create the remoting Client before the subsystem is set, resulting in the incorrect default "invoker" subsystem being used for that client.

This results in problems (probably NPE or ClassCastException) when UnifiedInvokerProxyHA.invoke tries to handle response values. It expects the response to be an HARMIResponse, and it won't be because the wrong server-side invoker is used.

This affects clients who run in the AS and have disabled both the legacy client interceptors and the remoting client logci that directly routes calls to the locally deployed bean. This is an unusual combination.



> UnifiedInvokerProxyHA constructor creates an invalid initial client
> -------------------------------------------------------------------
>
>                 Key: JBAS-8636
>                 URL: https://jira.jboss.org/browse/JBAS-8636
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.1.0.GA,  6.0.0.M5, 6.0.0.CR1
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: 6.0.0.Final
>
>
> The UnifiedInvokerProxyHA constructors call the superclass constructors and then set the subsystem to "invokerha". Problem is the superclass constructors create the remoting Client before the subsystem is set, resulting in the incorrect default "invoker" subsystem being used for that client.
> This results in problems (probably NPE or ClassCastException) when UnifiedInvokerProxyHA.invoke tries to handle response values. It expects the response to be an HARMIResponse, and it won't be because the wrong server-side invoker is used.
> This affects clients who run in the AS and have disabled the legacy client interceptors logic that directly routes calls to the locally deployed bean. This is a fairly unusual combination.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira