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

Unable to create JMS MDB listener

SA-62849

Summary



Unable to create Java Messaging Service (JMS) Message Driven Bean (MDB) listener with WebLogic 12c application server.
The connection factory, JMS server, JMS module and topic are created (according to the Pega platform 7.31 installation guide). However, while producing the JMS MDB Jar file from the integration resource, the Test Connectivity option is disabled.
The Pega application is unresponsive and multiple errors occur on Application server console and PegaRules log.



Error Messages

  1. ERROR - Exception occurred while checking disk space on pulse.
  2. java.lang.OutOfMemoryError: GC overhead limit exceeded


Steps to Reproduce



Follow the instructions listed in the 'Deploying a JMS message-driven bean (MDB) that represents a JMS MDB listener in Pega 7' article to create the JMS MDB.
Refer to: https://community.pega.com/knowledgebase/articles/deploying-jms-message-driven-bean-mdb-represents-jms-mdb-listener-pega-7



Root Cause



The T3 protocol was not enabled in the WebLogic server which the JMS hasd to use for communication.


Resolution



As a local-change, enable the T3 protocol from the Administrator server.

 

Suggest Edit

Published March 27, 2019 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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