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

Richard Achmatowicz (JIRA) jira-events at lists.jboss.org
Fri Aug 10 10:37:06 EDT 2012


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

Richard Achmatowicz commented on AS7-5334:
------------------------------------------

This issue arose in part because it is not easy to access the values used to initialize the JGroups protocol instances, which pass through various levels of processing as services are initialized (XML processing, model initialization, runtime service initialization, JGroups component instance initialization). This will be remedied by AS7-4083.

By inspection using a debugger, protocol property overrides are being processed correctly except in the case where the property overrides a socket binding value. For example, if we specify value X for a multicast port in the socket binding group, and at the same time specify value Y for the multicast port as a protocol property, the value of X will be used.
   
Proposal:
- change property processing so that protocol properties override other sources of values
- add in minimal trace logging to make accessing the final protocol initialization values more accessible  


                
> 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