Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

3
Replies
211
Views
 Mohamed Raffie Sheik Ameer (Raffie) Digitran Tech Solutions Inc Lead System Architect
Digitran Tech Solutions Inc
US
Raffie Member since 2012 8 posts
Digitran Tech Solutions Inc
Posted: July 25, 2017
Last activity: September 5, 2017
Posted: 25 Jul 2017 12:37 EDT
Last activity: 5 Sep 2017 11:10 EDT
Closed
Solved

Error while configuring Listener at EAP 6.4

Report
Hello,
I have handfull of Queue's and their corresponding QCF's available at the EAP ear file.
Show More
Hello,
I have handfull of Queue's and their corresponding QCF's available at the EAP ear file. No issues with that.
In addition to this, i am planning to add Listener to it and i added the below entry to the prbeans.jar and its failing..
<!-- MDB>
<message-driven id="MessageDriven_ILossResponseListener">
<description>Message Driven Bean for JMS Listener ILossResponseListener</description>
<ejb-name>ILossResponseListener</ejb-name>
<ejb-class>com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination id="MessageDrivenDestination_ILossResponseListener">
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
<env-entry>
<env-entry-name>PRListener</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>ILossResponseListener</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>UseCMT</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>false</env-entry-value>
</env-entry>
<ejb-local-ref id="EJBLocalRef_ILossResponseListener_EngineBMTLocal">
<description />
<ejb-ref-name>ejb/EngineBMTLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.pega.pegarules.internal.etier.interfaces.EngineLocalHome</local-home>
<local>com.pega.pegarules.internal.etier.interfaces.EngineLocal</local>
<ejb-link>EngineBMT</ejb-link>
</ejb-local-ref>
<ejb-local-ref id="EJBLocalRef_ILossResponseListener_EngineCMTLocal">
<description />
<ejb-ref-name>ejb/EngineCMTLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.pega.pegarules.internal.etier.interfaces.EngineLocalHome</local-home>
<local>com.pega.pegarules.internal.etier.interfaces.EngineLocal</local>
<ejb-link>EngineCMT</ejb-link>
</ejb-local-ref>
</message-driven>
<!-- Response Listener Start -->
<container-transaction>
<method>
<ejb-name>ILossResponseListener</ejb-name>
<method-name>onMessage</method-name>
<method-params>
<method-param>javax.jms.Message</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>

Error:

Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014185: Exception while parsing ejb-jar.xml: /content/JBOSS_OC_PRPC7.1.6.ear/prbeans.jar/META-INF/ejb-jar.xml


Show Less
Data Integration Installation and Deployment
Posted: 5 years ago
Posted: 26 Jul 2017 15:19 EDT
Paul Gentile (PaulGentile_GCS) PEGA Principal Engineer, Technical Support, 1:1 Customer Engagement
Pegasystems Inc.
US
Report

One part of that descriptor fragment needs to be applied to the "enterprise-beans node of the ejb-jar.xml" and the other section goes down further in that file in the "assembly-descriptor node". If that was followed, please attached your ejb-jar.xml file.
Posted: 5 years ago
Posted: 2 Aug 2017 2:57 EDT
Sudhakar Reddy Yaparla (YSudhakarReddy) JPMorgan Chase & Company
JPMorgan Chase & Company
US
Report

Hi,

Could you please post complete stack trace, it would be helpful to identify the root cause.

Accepted Solution

Posted: 5 years ago
Posted: 4 Aug 2017 7:59 EDT
Penchalanarasimhulu Vendipalli (Narasimha522) PEGA Senior Technical Solutions Engineer
Pegasystems Inc.
IN
Report

Please add Debug for below two classes in prlogging.xml file

 

com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener

 

com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot

 

And I also suspects that the queue name from MQ side was not as per standard queue name can you remove java:jboss/jms/ form MQ queue name try redeploying the MDB component.

 

Please refer the below  

 

Your ejb-jar.xml should look like this:

<?xml version="1.0" encoding="UTF-8"?>  

<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"  

          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  

          xsi:schemaLocation="http://java.sun.com/xml/ns/javaee  

                            http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"  

          version="3.0"  

>  

    <enterprise-beans>  

        <message-driven>  

            <ejb-name>MyMDB</ejb-name>  

            <ejb-class>  

                com.foo.MyMDB  

            </ejb-class>  

Show More

Please add Debug for below two classes in prlogging.xml file

 

com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener

 

com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot

 

And I also suspects that the queue name from MQ side was not as per standard queue name can you remove java:jboss/jms/ form MQ queue name try redeploying the MDB component.

 

Please refer the below  

 

Your ejb-jar.xml should look like this:

<?xml version="1.0" encoding="UTF-8"?>  

<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"  

          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  

          xsi:schemaLocation="http://java.sun.com/xml/ns/javaee  

                            http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"  

          version="3.0"  

>  

    <enterprise-beans>  

        <message-driven>  

            <ejb-name>MyMDB</ejb-name>  

            <ejb-class>  

                com.foo.MyMDB  

            </ejb-class>  

            <messaging-type>javax.jms.MessageListener</messaging-type>  

            <transaction-type>Container</transaction-type>  

            <activation-config>  

                <activation-config-property>  

                    <activation-config-property-name>  

                        destinationType  

                    </activation-config-property-name>  

                    <activation-config-property-value>  

                        javax.jms.Queue  

                    </activation-config-property-value>  

                </activation-config-property>  

                <activation-config-property>  

                    <activation-config-property-name>  

                        destination  

                    </activation-config-property-name>  

                    <activation-config-property-value>  

                        ${jms.queue.mymdb}  

                    </activation-config-property-value>  

                </activation-config-property>  

                <activation-config-property>  

                    <activation-config-property-name>  

                        useJNDI  

                    </activation-config-property-name>  

                    <activation-config-property-value>  

                        false  

                    </activation-config-property-value>  

                </activation-config-property>                  

                <activation-config-property>  

                    <activation-config-property-name>  

                        channel  

                    </activation-config-property-name>  

                    <activation-config-property-value>  

                        ${jms.queue.manager.channel}  

                    </activation-config-property-value>  

                </activation-config-property>                  

                <activation-config-property>  

                    <activation-config-property-name>  

                        hostName  

                    </activation-config-property-name>  

                    <activation-config-property-value>  

                        ${jms.queue.manager.host}  

                    </activation-config-property-value>  

                </activation-config-property>                  

                <activation-config-property>  

                    <activation-config-property-name>  

                        queueManager  

                    </activation-config-property-name>  

                    <activation-config-property-value>  

                        ${jms.queue.manager.name}  

                    </activation-config-property-value>  

                </activation-config-property>                  

                <activation-config-property>  

                    <activation-config-property-name>  

                        port  

                    </activation-config-property-name>  

                    <activation-config-property-value>  

                        ${jms.queue.manager.port}  

                    </activation-config-property-value>  

                </activation-config-property>                  

                <activation-config-property>  

                    <activation-config-property-name>  

                        transportType  

                    </activation-config-property-name>  

                    <activation-config-property-value>  

                        CLIENT  

                    </activation-config-property-value>  

                </activation-config-property>                  

            </activation-config>  

        </message-driven>  

    </enterprise-beans>  

</ejb-jar>  

  •         Notice the values with ${...}? Those are the system properties which you should define in the standalone.xml.

 

  •         Create also jboss-ejb3.xml descriptor to connect you MDB to the resource adapter:

<?xml version="1.0" encoding="UTF-8"?>  

<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"  

               xmlns="http://java.sun.com/xml/ns/javaee"  

               xmlns:mdb="urn:resource-adapter-binding"  

               xmlns:sec="urn:security"  

               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  

               xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"  

               version="3.1"  

               impl-version="2.0"  

>  

    <assembly-descriptor>  

        <mdb:resource-adapter-binding>  

            <ejb-name>MyMDB</ejb-name>  

            <mdb:resource-adapter-name>wmq.jmsra.rar</mdb:resource-adapter-name>  

        </mdb:resource-adapter-binding>  

    </assembly-descriptor>  

</jboss:ejb-jar>  

 

And now in the standalone.xml define the system properties and activate properties replacement in the descriptors. Here is a snippet from standalone.xml:

......  

    <system-properties>  

        <!-- JMS properties for ejb-jar.xml -->  

        <property name="jms.queue.manager.channel"  value="QUEUE_MANAGER_CHANNEL"/>  

        <property name="jms.queue.manager.host"     value="QUEUE_MANAGER_HOST"/>  

        <property name="jms.queue.manager.name"     value="QUEUE_MANAGER_NAME"/>  

        <property name="jms.queue.manager.port"     value="QUEUE_MANAGER_PORT"/>  

        <property name="jms.queue.mymdb"            value="MYMDB_QUEUE"/>  

    </system-properties>  

......  

        <subsystem xmlns="urn:jboss:domain:ee:1.1">  

        <spec-descriptor-property-replacement>true</spec-descriptor-property-replacement>  

        <jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>  

    </subsystem>  

......  

 

Here you need add your QCF and queue name replacing MQ details, let me know if you still face issue.

 

and which mode you are trying to process the message is it Container Managed or Bean Managed? if container managed you need to check the container Based check box in MDBListener rule form in the provided information it is mentioned as false i.e

<env-entry-name>UseCMT</env-entry-name>

<env-entry-type>java.lang.String</env-entry-type>

<env-entry-value>false</env-entry-value>

 

Thanks,

Narasimha

 


Show Less

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

Pega Collaboration Center 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