[jboss-jira] [JBoss JIRA] (AS7-4847) modcluster doesn't expose the jvmRoute information via cli. Can't execute *-context operations without it properly.

[Simeon Pinder (JIRA)]

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

Simeon Pinder commented on AS7-4847:
------------------------------------

So to be a little clearer, there are several ways to set what becomes the unique mod cluster node identifier:
- do nothing
- explicitly set 'jboss.mod_cluster.jvmRoute' property
- use ui/config properties files to explicitly set the 'instance-id'
but regardless there is always a modcluster node identifier.  Note: even when there is no explicit setting of this value by the last two there is still a jvmRoute identifier available if even the default.

The request from this bug is that there is a property added to the modcluster system that reliably reports whatever that identifier is regardless of mechanism it was set.

Mod cluster node members need to be able to reliably know their identifier to recognize the vhosts and contexts that apache has associated with it as described by getProxyInfo for example.
                
> modcluster doesn't expose the jvmRoute information via cli. Can't execute *-context operations without it properly.
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-4847
>                 URL: https://issues.jboss.org/browse/AS7-4847
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 7.1.2.Final (EAP)
>         Environment: EAP6
>            Reporter: Simeon Pinder
>            Assignee: Paul Ferraro
>            Priority: Critical
>              Labels: rhq
>
> The modcluster subsystem needs to expose the 'jvmRoute' identifier via cli for the modcluster subsystem at the configuration level(at subsystem=modcluster/mod-cluster-config=configuration level).  Without this information it is ambiguous how and which contexts will be affected when you execute the following operations:
> disable, disable-context, enable, enable-context, stop, stop-context.
> The other configuration attributes/operations target cluster-wide configuration, but the previous list of operations can only be executed at the cluster member/node level. In other words, a modcluster group could have 30 members/nodes but the above CLI operations will only affect the virtual-hosts and contexts for one of those nodes as uniquely identified by the jvmRoute.  There is currently no consistent way to determine what a valid cluster identifier should be.
> The jvmRoute can be explicitly set via the 'jboss.mod_cluster.jvmRoute' property or is automatically generated. Either way the correct jvmRoute or modcluster node identifier information needs to be correctly exposed as read-only information for the modcluster subsystem.
> This post (https://community.jboss.org/message/632900), mentions an 'instance-id' on the web subsytem but it is also 'undefined' even for systems where the jvmRoute has been explicitly set or autogenerated.  
> As the identifier is used by modcluster the identifier should be exposed consistently.
> Additionally there is no way to read whether a specific context is enabled/disabled. That issue probably needs it's another JIRA though.
>        

--
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