[jboss-jira] [JBoss JIRA] (AS7-5334) JGroups protocol properties not always being applied to protocol configurations

Brian Stansberry (JIRA) jira-events at lists.jboss.org
Fri Aug 10 10:44:06 EDT 2012


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

Brian Stansberry commented on AS7-5334:
---------------------------------------

Yuck.

Alternative proposal: User trying to override the socket-binding values via the JGroups properties results in an error.

I don't want to introduce back doors around the AS's socket management layer. Doing so eliminates the ability to provide admins with a complete view of the sockets the AS is opening.
                
> JGroups protocol properties not always being applied to protocol configurations 
> --------------------------------------------------------------------------------
>
>                 Key: AS7-5334
>                 URL: https://issues.jboss.org/browse/AS7-5334
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Richard Achmatowicz
>            Assignee: Richard Achmatowicz
>             Fix For: 7.1.3.Final (EAP)
>
>
> In JGroups subsystem processing, JGroups protocol properties are updated correctly in the model but not always correctly applied to the runtime configuration. 
> For example, specifying an MPING.mcast_port as a property of the protocol MPING will be overridden by the value of the multicast port in the associated socket binding.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list