Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega MDB Listeners Connecting with Anonymous User in EMS

SA-65997

Summary



When JBoss starts, all the queues are connected with Pega username. However, when the listeners utilize the message, JBoss makes the connections as an anonymous user and uses the messages.


Error Messages



Not Applicable


Steps to Reproduce



Unknown


Root Cause



A defect or configuration issue in the operating environment.

Configure to add the username and password in jboss-ejb3.xml on all configured Tibco queues.


Resolution



Make the following change to the operating environment:

Change the below code, <message-driven id="MessageDriven_PegaCustomMDBListenerName">
            <ejb-name>PegaCustomMDBListenerName</ejb-name>
            <ejb-class>com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot</ejb-class>
            <activation-config>
                <activation-config-property>
                    <activation-config-property-name>destination</activation-config-property-name>
                    <activation-config-property-value>java:global/remoteJMS/SCL.Events.Pega.DESTINATION_QUEUE</activation-config-property-value>
                </activation-config-property>
                <!-- manually added by Pega SA [BEGIN] -->
                <activation-config-property>
                    <activation-config-property-name>connectionFactory</activation-config-property-name>
                    <activation-config-property-value>java:global/remoteJMS/XAQueueConnectionFactory</activation-config-property-value>
                </activation-config-property>
                <!-- manually added by Pega SA [END] -->

          </activation-config>
</message-driven>


to the below code.

<message-driven id="MessageDriven_PegaCustomMDBListenerName">
            <ejb-name>PegaCustomMDBListenerName</ejb-name>
            <ejb-class>com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot</ejb-class>
            <activation-config>
                <activation-config-property>
                    <activation-config-property-name>destination</activation-config-property-name>
                    <activation-config-property-value>java:global/remoteJMS/SCL.Events.Pega.DESTINATION_QUEUE</activation-config-property-value>
                </activation-config-property>
                <!-- manually added by Pega SA [BEGIN] -->
                <activation-config-property>
                    <activation-config-property-name>connectionFactory</activation-config-property-name>
                    <activation-config-property-value>java:global/remoteJMS/XAQueueConnectionFactory</activation-config-property-value>
                </activation-config-property>
                <!-- manually added by Pega SA [END] -->

                <activation-config-property>
                    <activation-config-property-name>user</activation-config-property-name>
                    <activation-config-property-value>USER_NAME</activation-config-property-value>
                </activation-config-property>
                <activation-config-property>
                    <activation-config-property-name>password</activation-config-property-name>
                    <activation-config-property-value>YOUR_PASSWORD</activation-config-property-value>
                </activation-config-property>

            </activation-config>
</message-driven>

 

Published October 10, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us