Cluster Configuration

The following is a known issue for configuring GlassFish ESB cluster instances:

• Issue 1909

  When you configure cluster instances using the GlassFish Admin Console, the configuration does not propagate to any new cluster instances. This is because instances are configured individually. In some cases, this can cause deployment to fail.

  To work around this, configure each cluster instance individually or use the following asadmin command to configure all instances in the cluster:

  asadmin update-jbi-application-variable --component=sun-jms-binding name=value

  Usage: asadmin update-jbi-application-variable [--terse=false] [--echo=false] [--interactive=true] [--host localhost] [--port 4848|4849] [--secure | -s] [--user admin_user] [--passwordfile file_name] [--target target(Default server)] --component Component Name (name=value)[,name=value]*|property file

• Installing the GlassFish ESB Platinum Pack in a clustered environment fails due to an issue with the encoder shared library.

  To work around this issue, before you install the Platinum Pack, do the following:

  1. Shut down all components in the cluster that use the encoder shared library, such as the File BC and FTP BC.

  2. Uninstall the encoder library from the cluster.

  3. Stop the cluster and the application server.

     The Platinum Pack should now install successfully in the clustered environment.