[jboss-jira] [JBoss JIRA] (AS7-6460) Attribute check-for-live-server must set on live server to faillback

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on AS7-6460:
----------------------------------------------

Miroslav Novak <mnovak at redhat.com> made a comment on [bug 908261|https://bugzilla.redhat.com/show_bug.cgi?id=908261]

After discussion with dev it was agreed that this is a feature. Can it be documented in EAP 6 doc?

PR:
https://github.com/FranciscoBorges/hornetq/commit/8d828124365a5f4de236d6228a114dffa13d2d08

This is a feature which was documented in above pull request.

Assigning bz to doc team.
                
> Attribute check-for-live-server must set on live server to faillback
> --------------------------------------------------------------------
>
>                 Key: AS7-6460
>                 URL: https://issues.jboss.org/browse/AS7-6460
>             Project: Application Server 7
>          Issue Type: Task
>          Components: JMS
>    Affects Versions: 7.2.0.Alpha1
>            Reporter: Miroslav Novak
>            Assignee: Jeff Mesnil
>             Fix For: 7.2.0.CR1
>
>         Attachments: standalone-full-ha-backup.xml, standalone-full-ha-live.xml
>
>
> When there is live/backup pair with replicated journal then it should be sufficient to set attribute "check-for-live-server" in messaging subsystem only on backup to force backup server to shutdown when live server comes alive again. Problem is this won't happen.
> Only when attribute "check-for-live-server" is set on live server then failback is successful (backup shutdown itself)
> It's not well documented where "check-for-live-server" should be set in HornetQ project documentation:
> http://docs.jboss.org/hornetq/2.3.0.CR1/docs/user-manual/html_single/index.html#ha.allow-fail-back
> This issue was hit with EAP 6.1.0.DR2 (HQ 2.3.0.CR1).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira