[mod_cluster-issues] [JBoss JIRA] Closed: (MODCLUSTER-18) Moving jvmRoute to the mod_cluster config
Paul Ferraro (JIRA)
jira-events at lists.jboss.org
Thu Mar 18 12:38:38 EDT 2010
[ https://jira.jboss.org/jira/browse/MODCLUSTER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro closed MODCLUSTER-18.
----------------------------------
Resolution: Out of Date
This isn't relevant anymore. jvmRoute is now reliably auto-generated under all deployment scenarios.
> Moving jvmRoute to the mod_cluster config
> -----------------------------------------
>
> Key: MODCLUSTER-18
> URL: https://jira.jboss.org/jira/browse/MODCLUSTER-18
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.0.0.Beta1
> Environment: The JVMRoute information is taking for the engine.
> Reporter: Jean-Frederic Clere
> Assignee: Paul Ferraro
> Priority: Minor
>
> Having it the mod_cluster means setting the engine property dynamically.
> What about something like
> < <Engine name="jboss.web" defaultHost="localhost" jvmRoute="${jboss.bind.address}">
--
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
More information about the mod_cluster-issues
mailing list