Documentation does not explicitly state that you need to create JMS resources before running the MQ Failover Sample Application following the asadmin deploy instructions. (ID 6198003) (Sun Java System Application Server Enterprise Edition 8.2 Release Notes)

Sun Java System Application Server Enterprise Edition 8.2 Release Notes

Previous: On Windows, setup-one-machine-cluster hangs but works on Solaris; mqfailover requires Ctrl+C to cancel and then must be re-run. (ID 6195092)
Next: On Linux, a runtime error is displayed during certificate creation in web services/security samples. (ID 6198239)

Documentation does not explicitly state that you need to create JMS resources before running the MQ Failover Sample Application following the `asadmin` deploy instructions. (ID 6198003)

Description

The error thrown is as follows:

/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 done using asadmin deploy commands, and that the provided ant targets to deploy the sample application should be used.

Solution

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