Out of support


This documentation supports the 8.1 version of BMC Atrium Single Sign-On, which is in "End of Version Support." However, the documentation is available for your convenience. You will not be able to leave comments.

Click here to view the documentation for a supported version of Remedy Single Sign-On.

Session sharing in HA mode issue

In BMC Atrium Single Sign-On High Availability (HA) mode, session sharing can fail in some specific network environments when the default protocol (multicast) is used by ApacheMQ. ApacheMQ is a third party component which is used by Atrium Single Sign-On to inform all nodes in the cluster about sessions’ creation and termination events. If  session sharing fails, change the configuration settings to an alternative protocol.

To configure point-to-point sessions sharing

Perform the following on each node in the HA cluster.

  1. Navigate to the <AtriumSSOinstallationDirectory>/tomcat/webapps/atriumsso/WEB-INF/classes/ directory.
  2. Edit the activemq.xml file.
  3. Replace the following tag:
    <transportConnector uri="ssl://localhost:0?transport.needClientAuth=true&amp;daemon=true" discoveryUri="multicast://default?daemon=true&amp;group=atsso" />

    <transportConnector uri="ssl://<hostname>:<port>?transport.needClientAuth=true&amp;daemon=true " />

    hostname — The host name of the current node.
    port — The port which will be used for the sessions sharing on this node.
  4. Replace the following tag:
    <networkConnector uri="multicast://default?daemon=true&amp;group=atsso" />

    <networkConnector uri="static:(ssl://< hostname>:<port>?daemon=true[,ssl://< hostname>:<port>?daemon=true,…])"/>

    hostname — The host name of another node in the HA cluster.
    port — The port which is used by another node for session sharing.


    The <hostname>:<port> pair is specified on another node in the <transportConnector /> tag.
  5. Save the file.


  • Shutdown all the nodes in the cluster after configuring point-to-point session sharing.
  • Do not start all the nodes at the same time. Start each node beginning from the first node only after the previous node is fully started.

Was this page helpful? Yes No Submitting... Thank you