[jboss-jira] [JBoss JIRA] Commented: (JBAS-6235) Delay the join in into a cluster and prevent starting timers, RMI calls ... before 'up and ready' state

[Brian Stansberry (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12440815#action_12440815 ] 

Brian Stansberry commented on JBAS-6235:
----------------------------------------

Not joining the cluster until everything else is started isn't really possible, because the proper startup of some of that "everything else" requires that the node has joined the cluster.

But, clustered services should still work properly during the startup/shutdown period. To the extent they aren't, that's something we need to address on a case by case basis.  Could you open a thread on http://www.jboss.com/index.html?module=bb&op=viewforum&f=155 and give more details about your specific issues?

> Delay the join in into a cluster and prevent starting timers, RMI calls ... before 'up and ready' state
> -------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6235
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6235
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Deployers, Remoting
>            Reporter: Wolf-Dieter Fink
>            Assignee: Brian Stansberry
>
> If applications become complex it is, more or less, difficult to ensure a save startup or shutdown of a JBoss node especially within a clustered environment.
> Due to this it might be good to start all services and applications before the node join in into a cluster and accept calls or timer-activation.
> Also do it vice-versa in case of shutdown.
> This shortens the time during the application can no work correctly and will throw Exceptions or not work correctly.
> The behaviour becomes more strange if the 'TransactionSticky' features (since 4.2.3 see JBAS-4455) is used, because the UserTransaction service is deployed 'long' before the application-ears are.

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