Known Issues for JBI Clustering

The following are known issues for working with Java CAPS JBI components in a clustered environment:

• 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 issue, 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

  See asadmin help for usage information.

• CR 6883003

  A web application is unable to find the WSDL file on a second instance when the web service is deployed in a GlassFish cluster where the first node includes the DAS and a node agent, and the second node includes just a node agent.

  To work around this issue, on the second cluster instance create a directory hierarchy for DAS and copy or create a symbolic link to the WSDL file in the location where the web application expects to find it. For example:

  mkdirhier /opt/glassfish/domains/domain1/applications/j2ee-modules/WebAppName/WEB-INF/wsdl/client/WSDLName/

  cd /opt/glassfish/domains/domain1/applications/j2ee-modules/WebAppName/WEB-INF/wsdl/client/WSDLName/

  cp /opt/glassfish/nodeagents/ClusterNodeAgent/InstanceName/applications/j2ee-modules/WebAppName/WEB-INF/wsdl/client/WSDLName/WSDLName.wsdl

  ln -s /opt/glassfish/nodeagents/ClusterNodeAgent/InstanceName/applications/j2ee-modules/WebAppName/WEB-INF/wsdl/client/WSDLName/WSDLName.wsdl