Issue Details (XML | Word | Printable)

Key: GLASSFISH-15686
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: David Zhao
Reporter: mathim
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.

using "configure-jms-cluster" in a non-recommended way could leave the system in inconsistent state

Created: 25/Jan/11 01:39 PM   Updated: 09/Jun/13 07:04 AM   Resolved: 09/Jun/13 07:04 AM
Component/s: jms
Affects Version/s: 3.1_b38
Fix Version/s: 4.0.1

Time Tracking:
Not Specified


tested on Oracle Enterprise Linux 5 (but the issue is platform independent)

Tags: 3_1-exclude 3_1-next 3_1_1-scrubbed 3_1_2-exclude bj-reviewed-t2 glassfish-3-1 jms
Participants: David Zhao, mathim, Nazrul and Satish Kumar

 Description  « Hide
  • Create a glassfish cluster
  • Create instances
  • use configure-jms-cluster to configure the cluster not to use Master Broker
    The command printed the following warning.

"WARNING: Please ensure that you have followed the instructions specified in the documentation before running this command with this option. Running this command without the required precautions can lead to inconsistent JMS behavior and corruption of configuration and message stores."

The above warning message doesn't say much. There is no way one would know what is wrong. The command doesn't mention that there are instances associated with the cluster and the command need to be executed before creating the instances.

Above all, the command executed and returned successfully.

When the test started the glassfish cluster after this command, the MQ Broker on two of the glassfish instances started with no master broker option and the MQ Broker on the third glassfish instance started with Master Broker Option. The third broker was waiting indefinitely to sync up with the Master Broker. it doesn't happen on all the systems. but can be consistently reproduced on the systems on which it shows up.

command probably should stop executing if it detects the conditions are not met and print clear messages, rather than leaving the system in insistent state.