[GLASSFISH-19601] [UB] describe how MQ cluster name is generated for a given GlassFish cluster Created: 29/Jan/13 Updated: 14/Mar/13
|Affects Version/s:||9.1.1, v2.1, v2.1.1, V3, v3.0.1, 3.1, 3.1.1, 3.1.2, 188.8.131.52|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
see Summary. This issue is first filed to 'jms' to provide text for doc, then please transfer to 'docs'
|Comment by David Zhao [ 30/Jan/13 ]|
glassfish will pass <gfClusterName>_MQ to MQ for the property of "imq.cluster.clusterid". Please see MQ-275 for details of the doc issue.
|Comment by amyk [ 30/Jan/13 ]|
According to the following GlassFish forum post, MQ broker sees MYCLSTRDEV_MQ for imq.cluster.clusterid without the '_'s in MY_CLSTR_DEV
|Comment by Mike Fitch [ 30/Jan/13 ]|
Changed component to docs. Changed fix version to 4.0_b76_EE7MS5 for any changes that would go into the configure-jms-cluster man page or the JMS Availability or New Cluster console help pages.
|Comment by Mike Fitch [ 14/Mar/13 ]|
Added information about name length restrictions to the cluster-name operand in the create-cluster and configure-jms-cluster subcommand man pages. Fix available in main-docs build 4.0-b15, which was picked up by GlassFish as of revision 59613, 18-FEB-2013.
Added [UB] to the summary so remaining book-related changes will get tracked.
Changed Fix Version to 4.0 for remaining book-related changes.