BWagent fails to start throwing an InvalidDestinationException error.

BWagent fails to start throwing an InvalidDestinationException error.

book

Article ID: KB0094124

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks -
Not Applicable -

Description

Description:
 BWagent configured with DB and EMS. BWagent fails to start with an InvalidDestinationException error.
Symptoms:
Following error seen in the console logs.
++++

Caused by: com.tibco.tibems.qin.TibQinException: Connection to the server failed for member "<<Hostname>>.com.db9ed245-f8c5-49b6-9451-4dfb9d911b97.AdminClientObserver".
        at com.tibco.tibems.qin.TibQinGroupConnectionImpl._createGroupConnection(TibQinGroupConnectionImpl.java:1369) ~[com.tibco.tibems.qin_1.1.0.001.jar:na]
        at com.tibco.tibems.qin.TibQinGroupConnectionImpl.initialize(TibQinGroupConnectionImpl.java:1960) ~[com.tibco.tibems.qin_1.1.0.001.jar:na]
        at com.tibco.tibems.qin.TibQinGroupConnectionFactory.createGroupConnection(TibQinGroupConnectionFactory.java:73) ~[com.tibco.tibems.qin_1.1.0.001.jar:na]
        at com.tibco.neo.gms2.qin.QinGroupConnectionFactory.newGroupConnection(QinGroupConnectionFactory.java:86) ~[com.tibco.neo.gms2.qin_1.1.0.001.jar:na]
        ... 19 common frames omitted
Caused by: javax.jms.InvalidDestinationException: Not allowed to create destination
        at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:551) ~[tibjms.jar:6.2.0]

++++

Cause:

BW uses dynamic queues/topics for communication. The "javax.jms.InvalidDestinationException: Not allowed to create destination"  error message is a result of the EMS server not being configured to handle dynamic queue/topics.

Issue/Introduction

BWagent fails to start throwing an InvalidDestinationException error.

Resolution

Note that the issue is on the EMS server side.  Creation of dynamic queues and topics by applications are allowed on the EMS server only if queues.conf/topics.conf files has a ‘>’ entry in it. The default installation allows creation of dynamic queues and topics and has a ‘>’ entry in their conf files.  You also need to grant the following permissions for the EMS user being used (if not using admin user).


grant topic "$sys.monitor.>" user=<<username>> all

grant admin user=<<username>> view-connection,view-server