Unexpected error in postMessage To Topic:JMS exception in getTopic Connection:Null error when try (77768)

All ports that are mentioned in Appendix F of Stat 5.6 SYS admin guide are open bidirectionally but I get the following error message when trying to add E-business objects to CSR:

Unexpected error in postMessage To Topic:JMS exception in getTopic Connection:Null

Stat 5.6.0 uses Jboss 5.1.0 and the messaging structure is different from Jboss 4.0.5 used in lower versions of Stat. For Jboss 5.1.0 three additional ports are being used and these ports need to be openned bidirectionally as well.

In addition to ports listed in Appendix F of Stat 5.6 SYS admin guide, ports 3873 and 4457 (assuming your site is using ports-default profile. If not add 100 to port number for any additional port profiles. For example if you are using ports-01 3873 becomes 3973) need to be open bidirectionally as well. There is also a random “anonymous” port that is generated each time the agent is started. JBoss Will select any random open port over 1001 but this can change when agent is restarted. But this port can be designated / hardcoded in an Stat agent .xml file and the agent will use this port every time it starts up.

To designate / hardcode a fixed port locate and open the following file on Stat server machine:

Stat_home\app\server\default\deploy\messaging\remoting-bisocket-service.xml

Find the following segment near the bottom of the file:

<!--Use these parameters to specify values for binding and connecting control connections to

work with your firewall/NAT configuration

<attribute name="secondaryBindPort">xyz</attribute>

<attribute name="secondaryConnectPort">abc</attribute>

-->

This segment is commented out as designated by the arrows <!--and -->.

You want to expose the secondaryBindPort and designate a specific port number.

Your modified segment should look like this where 12345 is a port of your choice.

<!-- Use these parameters to specify values for binding and connecting control connections to

work with your firewall/NAT configuration -->

<attribute name="secondaryBindPort">12345</attribute>

<!-- <attribute name="secondaryConnectPort">abc</attribute> -->