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

Not able to deploy MDB for JMS-MDB Listener in PRPC V7.1.5



JMS listener is generating invalid deployment descriptor (ejb-jar.xml) on PRPC 7.1.5 version. 

Error Messages

Below exception is seen in WAS logs:

Parse exception for [ public ID [ null ] and system ID [ null ] ] [ java.lang.IllegalStateException: Parent Translator (EnterpriseBeansTranslator(entity|session|message-driven,1696032023)) did not find a Child Translator for "message-driven-destination".

Steps to Reproduce

1. Create the JMS queue, queue connection factory and activiation spec to be used by the listener on WAS end.

2. Create the JMS-MDB rule instance and generate the XML from Update Deployment Descriptor button on JMS Properties tab.(attachment 1)

3. Add the code snippet generated in step 1 in ebj-jar.xml

4. Update imb-ejb-jar-bnd.xmi file based on details given in the PDN document.

5. Try redepolying the EAR after these changes, we got the execption in attachment 2.

Root Cause

Generated ejb-jar.xml is failing to deploy in application server.

PRPC generated 
ejb-jar.xml  is not compatible with ejb-jar_2_1.xsd. Hence it is not able to parse when application is deployed.


Below changes to ejb-jar.xml resolves the issue:

1. Remove below section from generated ejb-jar.xml

<message-driven-destination id="MessageDrivenDestination_CaseMgmtEventListener">




2.Add below tags to generated ejb-jar.xml


3.Remove doctype definition from ejb-jar.xml

 <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "">


Published January 31, 2016 - 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