Samples

This section describes known and associated solutions related to the sample code included with the Application Server 8.2 product.

setup-one-machine-cluster Hangs (ID 6195092)

On the Windows platform, the mqfailover command requires pressing Control+C keys to exit the hung process. You must rerun the setup-one-machine-cluster process.

From install_dir\samples\ee-samples\failover\apps\mqfailover\docs\index.html, run the following commands:

• Console 1

  cd install_dir\samples\ee-samples asant start-mq-master-broker1

• Console 2

  cd install_dir\samples\ee-samples asant start-mq-cluster-broker1

• Console 3

  cd install_dir\samples\ee-samples asant start-mq-cluster-broker2

• Console 4

  cd install_dir\samples\ee-samples asadmin start-domain domain1

If you have already executed asant setup-one-machine-cluster-without-ha or asant setup-one-machine-cluster-with-ha for any other Enterprise Edition sample, execute asant configure-mq. Otherwise, execute asant setup-one-machine-cluster-and-configure-mq. In this case, the command appears to succeed:

start_nodeagent: [echo] Start the node agent cluster1-nodeagent 
[exec] Command start-node-agent executed successfully.

But then the system hangs indefinitely.

Solution

None. This problem similarly affects all Enterprise Edition samples that use this ant target on Windows. A workaround is to press Control+C to exit the hung process and then rerun it.

Documentation Not Explicitly States the Need to Create JMS Resources Before Running the Message Queue Failover Sample Application (ID 6198003)

After you complete the asadmin deploy instructions and run the Message Queue failover sample application, the following error message is dilsplayed:

/opt/SUNWappserver/domains/domain1/config/sun-acc.xml -name 
MQFailoverTestClient -textauth -user j2ee -password j2ee
Nov 18, 2004 10:50:17 PM com.sun.enterprise.naming.NamingManagerImpl 
bindObjects
SEVERE: NAM0006: JMS Destination object not found: jms/durable/TopicA
Nov 18, 2004 10:50:18 PM com.sun.enterprise.naming.NamingManagerImpl 
bindObjects
SEVERE: javax.naming.NameNotFoundException
javax.naming.NameNotFoundException

The documentation does not explicitly state that JMS resources must be manually created if manual deployment is performed by using the asadmin deploy commands. The documentation also fails to mention that that the provided ant targets should be used to deploy the sample application .

Solution

Use the asant deploy target for the build.xml script, which creates the required JMS resources to run the application.