[jboss-jira] [JBoss JIRA] Commented: (JBAS-4574) AS ejb ha restart would fail

[Ben Wang (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-4574?page=comments#action_12369712 ] 
            
Ben Wang commented on JBAS-4574:
--------------------------------

Adrian, yes I do remeber 1475 issue. But I am not sure by including view id will solve the problem completely here.

4.0.5 currently uses default SingleRetryInterceptor for HA SLSB but it doesn't work in this case. Reason being that we cache the server info in the NamingContext implicitly so unless we flush it out, retry won't work even when you do jndi look up for the new naming stub.

I have thought about posting this to the forum. But I have discussed this with Brian before and I am creating a branch first to look into the solution further (I have an ad hoc one) before going to the forum, so that's the reason for this Jira.


> AS ejb ha restart would fail
> ----------------------------
>
>                 Key: JBAS-4574
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4574
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.0.5.GA
>            Reporter: Ben Wang
>         Assigned To: Ben Wang
>
> This is an issue discovered during a pre-sales opportunity. Basically, it can be reproduced like this:
> 1. Use a web tier (calling remote slsb ejb from jsp, e.g.) with 2 ejb tiers (for clustering, say, ejb1, ejb2)
> 2. access it first to ejb1
> 3. shutdown ejb1, and access it again will failover to ejb2
> 4. shutdown ejb2 and bring up ejb1, should produce error traces (I don't have now). Will attach it here later.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira