Accessing AQ from MDB in JBoss

Question

Hi All,
I am trying to read the messages from AQ. I am able to read the messages through a JMS client but not able to get any breakthrough with MDB...kindly help.
I wrote a simple MDB....
package com.ameripath.billinginterface.mdb;
import java.util.Enumeration;
import java.util.Hashtable;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
@MessageDriven(activationConfig =
          @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Topic"),
          @ActivationConfigProperty(propertyName="destination", propertyValue="topic/OAQRequestTopic")
public class AQMDB implements MessageListener {
     public void onMessage(Message message) {
          String reqMsg = null;
System.out.println("!!!!!!!!!!!!!1Inside onMessage~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
updated Jboss-service.xml with...
<mbean code="jmx.service.oracle.aq.OAQDestination"
name="jmx.service.oracle.aq:service=OAQRequestTopic">
<attribute name="JndiName">topic/OAQRequestTopic</attribute>
<attribute name="JMSStyle">topic</attribute>
<attribute name="IsXA">false</attribute>
<attribute name="URL">jdbc:oracle:thin:@192.168.200.73:1521:INTORCL</attribute>
<attribute name="Username">oas_intgrtn</attribute>
<attribute name="Password">oas_intgrtn</attribute>
<attribute name="PayloadFactory"></attribute>
<attribute name="Schema">oas_intgrtn</attribute>
<attribute name="Destination">MULTI_QUEUE</attribute>
<depends>jboss:service=Naming</depends>
</mbean>
updated jms-ds.xml with....
<!-- The OAQ JMS provider loader -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=OAQJMSProvider">
<attribute name="ProviderName">OAQJMSProvider</attribute>
<attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
<!-- <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JBossMQProvider</attribute> -->
<attribute name="QueueFactoryRef">OAQQueueConnectionFactory</attribute>
<attribute name="TopicFactoryRef">OAQTopicConnectionFactory</attribute>
</mbean>
also updated standardjboss.xml with ...
<invoker-proxy-binding>
<name>oaq-message-driven-bean</name>
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>OAQJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<MaximumSize>5</MaximumSize>
<MaxMessages>5</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
<!-- for AQ -->
<container-configuration>
<container-name>OAQ Message Driven Bean</container-name>
<call-logging>false</call-logging>
<invoker-proxy-binding-name>oaq-message-driven-bean</invoker-proxy-binding-name>
<container-interceptors>
<interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
<interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
<interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor>
<!-- CMT -->
<interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
<interceptor transaction="Container" metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
<interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
<!-- BMT -->
<interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
<interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor>
<interceptor transaction="Bean" metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
<interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
</container-interceptors>
<instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
<instance-cache></instance-cache>
<persistence-manager></persistence-manager>
<container-pool-conf>
<MaximumSize>100</MaximumSize>
</container-pool-conf>
</container-configuration>
<!-- for AQ -->
I am getting this error on deployment of this MDB....
18:35:07,236 INFO [Ejb3AnnotationHandler] found EJB3: ejbName=AQMDB, class=com.
ameripath.billinginterface.mdb.AQMDB, type=MESSAGE_DRIVEN
18:35:07,548 INFO [Ejb3Deployment] EJB3 deployment time took: 500
18:35:07,627 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:service=E
JB3,jar=bi_pocapp.ejb3,name=AQMDB with dependencies:
18:35:08,189 WARN [ServiceController] Problem starting service jboss.j2ee:servi
ce=EJB3,jar=bi_pocapp.ejb3,name=AQMDB
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
Kindly suggest a fix
thanks in anticipation

Answer 1

Hi,
I´m facing exactly the same problem and weren´t able to solve it. Anyone was able to acomplish this?
Regards,
Vinicius