MDB listening on Socket instead of Queue

Hi all,
Is it possible for to make MDB listen on socket instead of queues using JCA. Can anyone please help me on this.
Thanks in advance

Hi,
Thanks for the reply. In the example provided, it is for mail. Since we have javax.mail.Message message API we can use this. How about Socket.Here am lost. Can you please tell how to go with this.
I also had tried the above one, but while deploying MDB, I error as MDB is in failed state with Exception as Resource Adaptor "EchoXMLRP" is not deployed. Where as i had already deployed it. Also i had deployed "EchoXMLRP" as Resource Adaptor Module. But when i view the same its not present in standalone Resource Adaptor, instead its there in Modules.

Similar Messages

MDB listening to multiple queues?

          Is it possible to configure an MDB to listen to more than one Queue ?


No.
          _sjz.
          "Jim" <[email protected]> wrote in message news:3d496d70$[email protected]..
          >
          > Is it possible to configure an MDB to listen to more than one Queue ?

Making MDB listen to a queue

Hi all,
Can any one tell me how to make an MDBean listen to a Queue Using JDev wizard.
Kindly help....

mshreedhaaran wrote:
Hi,
Thanks to the below post(s) -
<a class="jive-link-external" href="http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html">http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html</a>
<a class="jive-link-external" href="http://www-128.ibm.com/developerworks/websphere/library/techarticles/0604_kesavan/0604_kesavan.html">http://www-128.ibm.com/developerworks/websphere/library/techarticles/0604_kesavan/0604_kesavan.html</a>
I have been able to get this far (ofcourse explained very well step by step in these posts). So MDB on WLS can pick messages from a Queue on MQ Server on the same machine.
If someone can highlight what <font face="tahoma,verdana,sans-serif" size="1" color="#000">changes</font> I have to make to get the MDB to pick message from the Queue when MQ Server is on a different machine.
Thanks in advance.
best regards,
MuraliIt's helpful to me, Thanks for your sharing! Now I understand more about it, It's quite useful.

Steps listen to an Oracle AQ queue in IBM Websphere Application Server 7.0

I need to listen to an Oracle AQ queue in a Java EE application that runs under Websphere app server @7.0.
I'd really like to use a MDB to access the Messages in AQ
I can't really find any documentation on this, and I can't find a resource adapter that lets me do this using JCA.
Can anyone tell me what's required to get this to work?
I was able to find the
product\11.2.0\oc4j\j2ee\home\connectors\ojms.rar
but how to configure the same inside WAS

Hi ,
I have attempted to deploy an ADF 11g JSF application into WAS 7 and I am finding that an NPE is being thrown when the Trinidad (1.2.9) ResourceServlet is trying to load various artefacts on a page request.
[28/05/09 12:46:34:568 EST] 00000019 servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet resources in application ic-web. Exception created : java.lang.NullPointerException
     at com.ibm.ws.webcontainer.srt.SRTServletResponse.setContentType(SRTServletResponse.java:1191)
     at javax.servlet.ServletResponseWrapper.setContentType(ServletResponseWrapper.java:140)
     at org.apache.myfaces.trinidad.webapp.ResourceServlet._setHeaders(ResourceServlet.java:445)
     at org.apache.myfaces.trinidad.webapp.ResourceServlet.doGet(ResourceServlet.java:207)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:726)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
     at org.apache.myfaces.trinidad.webapp.ResourceServlet.service(ResourceServlet.java:162)
Does anyone have any thoughts about what might be causing this?
This application deploys fine into WLS 10g.
Thanks and regards,
Andrew
Edited by: user11207057 on 27-May-2009 21:12

MDB listening to a Oracle AQ, holding ADT messages...

Hi !
I'm trying to set a MDB to listen for incoming messages on an Oracle AQ. When I created the queue, I specified that the queue should contain payload of type ADT. I'm using Bea Weblogic server 8.1 sp4 and Oracle 10.2.0. The creation of the connection to the queue is implemented as a start up class and bound to the context during server start up.
However it fails to start up, I get the following exception:
<20.mar.2007 kl 11.03 CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB:
MyWebLogicMDB is unable to connect to the JMS destination: AQJMSQueue. The Erro
r was:
oracle.jms.AQjmsException: JMS-137: Innholdsfabrikk mÕ angis for mÕl med ADT-inn
hold
oracle.jms.AQjmsException: JMS-137: Innholdsfabrikk mÕ angis for mÕl med ADT-inn
hold
at oracle.jms.AQjmsError.throwEx(I)V(AQjmsError.java:288)
at oracle.jms.AQjmsConsumer.<init>(Loracle.jms.AQjmsSession;Ljavax.jms.D
estination;IILjava.lang.String;Ljava.lang.Object;Loracle.jms.AQjmsSelector;Ljava
.lang.String;Z)V(AQjmsConsumer.java:385)
at oracle.jms.AQjmsConsumer.<init>(Loracle.jms.AQjmsSession;Ljavax.jms.D
estination;IILjava.lang.String;Ljava.lang.Object;Loracle.jms.AQjmsSelector;Ljava
.lang.String;)V(AQjmsConsumer.java:254)
at oracle.jms.AQjmsSession.createReceiver(Ljavax.jms.Queue;Ljava.lang.St
ring;Ljava.lang.Object;)Ljavax.jms.QueueReceiver;(AQjmsSession.java:1631)
at oracle.jms.AQjmsSession.createReceiver(Ljavax.jms.Queue;Ljava.lang.St
ring;)Ljavax.jms.QueueReceiver;(AQjmsSession.java:1553)
at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(Ljavax
.jms.Destination;Ljava.lang.String;III)V(JMSConnectionPoller.java:1720)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection()V(JM
SConnectionPoller.java:2019)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS()V(JMSConnec
tionPoller.java:1180)
at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling
()V(JMSConnectionPoller.java:846)
at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start()V(Messag
eDrivenBeanPoolInfoImpl.java:234)
at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans()V(EJBDe
ployer.java:1660)
at weblogic.ejb20.deployer.EJBDeployer.start(Z)V(EJBDeployer.java:1488)
at weblogic.ejb20.deployer.EJBModule.start()V(EJBModule.java:689)
at weblogic.j2ee.J2EEApplicationContainer.start([Lweblogic.j2ee.J2EEAppl
icationContainer$Component;)V(J2EEApplicationContainer.java:2127)
at weblogic.j2ee.J2EEApplicationContainer.activate([Lweblogic.management
.configuration.ComponentMBean;)V(J2EEApplicationContainer.java:2168)
at weblogic.j2ee.J2EEApplicationContainer.activate()V(J2EEApplicationCon
tainer.java:2115)
at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivat
ion(Z)V(SlaveDeployer.java:3082)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(ZZ)V(SlaveDeployer.java:1751)
at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeploye
r.java:359)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e()V(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131
at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:361)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
The problem is that the MDB cannot be set up to dequeue the message because the payload factory has to be set for the consumer in order to receive messages from queues which have messages with ADT payload.
So my questions are:
1) Is there a way to set the payload factory to use in the MDB? (deployment desc.)
2) Do MDB support AdtMessages?
3) Are there any other ways to listen to an Oracle queue which has ADT type?
mvh
jb

Hi,
I'm also having the same identical problem with an EJB 3.0 MDB listening to an AQ queue (via OJMS) with a payload type of ADT. I can successfully dequeue messages from a queue with a JMS payload type, but as soon as I point it to and ADT type queue I get:
oracle.jms.AQjmsException: JMS-137: Payload factory must be specified for destinations with ADT payloads
I can't however seem to find anything in the Oracle documentation that shows how to do this, and which class corresponds to this "payload factory".
The following link seems to suggest that OJMS supports ADT types in addition to the standard JMS message types:
http://www.oracle.com/technology/tech/java/oc4j/904/collateral/OC4J-FAQ-JMS-904.html
although I'm not sure if this is true for Message Driven Beans.
Could you please confirm whether MDB's support ADT message types?
Many thanks
Phil

MDB messages dont get processed from Queues when involving a remote Topic in transaction

Using WLS 6.1 SP4 on winXP Pro boxes, I have come across a peculiar problem:
          I have several MDBs that process ObjectMessages from queues and forward their payload (wrapped in another new ObjectMessage) to other queues, all of which are located within the same WLS server.
          Right now I'm adding a new MDB that gets messages from a remote Topic with a durable subscription, and forwards the payload to local queues after some processing.
          When the Topic is local as well, there is no problem. But when the Topic is set up in a remote machine, only the MDB that has the remote durable subscription works the way it should. It receives the remote message and forwards it to the corresponding local queue. But then the messages in those local queues dont get processed. The 'Messages Received' count rises and the 'Messages' count stays at 0, as if the messages had been correctly processed and acknowledged, but no onMessage() method is called besides the one from the MDB that has the durable subscription to the remote Topic (I can tell because there's no further processing from the queue those messages get put in). It's as if those messages were simply received and acknowledged without being passed to other MDBs by WLS.
          * All queue MDBs use Required container-managed transaction management and auto-acknowledge
          * All queue MDBs have default durability for their queue subscriptions
          * The topic MDB has a durable subscription stored in a filestore
          * Lookup of the remote Topic is done via JNDI
          Since the processing and forwarding of messages occurs the way it should when everything is local, I am inclined to believe one of two things:
          a) There's some issue with the way WLS treats messages (or even just payloads) when they come from a remote server
          b) WLS is doing something I'm not aware of when propagating a transaction that begins with the delivery of a message from a remote JMS Topic when it involves further forwarding of messages in local JMS Queues.
          Any help will be appreciated.
          regards,
          .munir estevane


Is the durable subscriber forwarder rolling back its transactions?
          That would cause the behavior you describe (eg the message gets
          placed in the queue, but is never made visible). What do
          the pending counts on the destination queue look like?
          Munir Estevane wrote:
          > Using WLS 6.1 SP4 on winXP Pro boxes, I have come across a peculiar problem:
          >
          > I have several MDBs that process ObjectMessages from queues and forward their payload (wrapped in another new ObjectMessage) to other queues, all of which are located within the same WLS server.
          > Right now I'm adding a new MDB that gets messages from a remote Topic with a durable subscription, and forwards the payload to local queues after some processing.
          >
          > When the Topic is local as well, there is no problem. But when the Topic is set up in a remote machine, only the MDB that has the remote durable subscription works the way it should. It receives the remote message and forwards it to the corresponding local queue. But then the messages in those local queues dont get processed. The 'Messages Received' count rises and the 'Messages' count stays at 0, as if the messages had been correctly processed and acknowledged, but no onMessage() method is called besides the one from the MDB that has the durable subscription to the remote Topic (I can tell because there's no further processing from the queue those messages get put in). It's as if those messages were simply received and acknowledged without being passed to other MDBs by WLS.
          >
          > * All queue MDBs use Required container-managed transaction management and auto-acknowledge
          > * All queue MDBs have default durability for their queue subscriptions
          > * The topic MDB has a durable subscription stored in a filestore
          > * Lookup of the remote Topic is done via JNDI
          >
          > Since the processing and forwarding of messages occurs the way it should when everything is local, I am inclined to believe one of two things:
          > a) There's some issue with the way WLS treats messages (or even just payloads) when they come from a remote server
          > b) WLS is doing something I'm not aware of when propagating a transaction that begins with the delivery of a message from a remote JMS Topic when it involves further forwarding of messages in local JMS Queues.
          >
          > Any help will be appreciated.
          >
          > regards,
          > .munir estevane

How to have a module listening a socket port?

Hi,
who know how to make a module of adapter and let it listening a socket port?
thanks in advance

Hi,
Take a look at this blog,
/people/saravanakumar.kuppusamy2/blog/2005/12/15/socket-integration-with-xi
Regards,
Bhavesh

MDB Listening to remote queue

          Hi,
          Could any of you please let me know what needs to be done to configure my MDB
          to listen to a remote queue in a different domain (also using wls 7.0).
          I tried adding the <provider-url> element in the weblogic-ejb-jar.xml but looks
          like that didnt work.
          Thanks,
          -Sri


Posting the actual error helps. This error usually occurs due
          to a naming conflict. Make sure that:
          All local and remote:
          WL servers are named differently
          WL JMS servers are named differently
          WL JMS stores are named differently
          Tom, BEA
          P.S. For future reference, a google search of
          this newsgroup often quickly leads to answers. In this
          case search for "Connection not found" or "invocableFind".
          Sri wrote:
          > Tom, I did. But I still get this error...
          >
          > [exec] <Jun 10, 2003 9:27:57 AM EDT> <Error> <EJB> <010020> <EJB-20 - Messa
          > geDriven - Couldn't start the JMS connection: weblogic.jms.common.JMSException:
          > Connection not found
          > [exec] weblogic.jms.common.JMSException: Connection not found
          > [exec] at weblogic.jms.dispatcher.InvocableManager.invocableFind(Invoca
          > bleManager.java:134)
          > [exec] at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Req
          > uest.java:592)
          > [exec] at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(Dispatche
          > rImpl.java:275)
          > [exec] at weblogic.jms.client.JMSConnection.start(JMSConnection.java:54
          > 7)
          > [exec] at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectio
          > n(JMSConnectionPoller.java:1228)
          > [exec] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.startCo
          > nnection(MessageDrivenBeanPoolInfoImpl.java:150)
          > [exec] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(M
          > essageDrivenBeanPoolInfoImpl.java:223)
          > [exec] at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(
          > EJBDeployer.java:1560)
          > [exec] at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:14
          > 06)
          > [exec] at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:391)
          > [exec] at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationC
          > ontainer.java:1039)
          > [exec] at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicati
          > onContainer.java:1025)
          > [exec] at weblogic.management.deploy.slave.SlaveDeployer.setActivationS
          > tateForAllApplications(SlaveDeployer.java:617)
          > [exec] at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDe
          > ployer.java:376)
          > [exec] at weblogic.management.deploy.DeploymentManagerServerLifeCycleIm
          > pl.resume(DeploymentManagerServerLifeCycleImpl.java:235)
          > [exec] at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleLi
          > st.java:65)
          > [exec] at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
          > [exec] at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
          > [exec] at weblogic.Server.main(Server.java:32)
          > [exec] >
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>Check your server logs for Warning and/or error messages.
          >>
          >>Make sure that you specified a correct:
          >>
          >>provider-url
          >>
          >>destination-jndi-name
          >>
          >>connection-factory-jndi-name (needed if you disabled the default
          >>connection factories in the remote domain)
          >>
          >>Sri wrote:
          >>
          >>>Hi,
          >>>
          >>>Could any of you please let me know what needs to be done to configure
          >>
          >>my MDB
          >>
          >>>to listen to a remote queue in a different domain (also using wls 7.0).
          >>
          >>>I tried adding the <provider-url> element in the weblogic-ejb-jar.xml
          >>
          >>but looks
          >>
          >>>like that didnt work.
          >>>
          >>>Thanks,
          >>>-Sri
          >>
          >

Can an MDB listens to remote queue

In my application , i have created a queue and MDB for that queue.
this MDB should also listen to the queue in another system that is remote queue.how is this possible.
because the queue will be in remote system. and MDB will be in my system. the queue to which this MDB should listen will be in specified in deplyment descriptors. then how it will identify that the queue is local or remote.
Please clarify me as we have a release near.

Hello Sairam,
I have used MDB in WebLogic Server. You can add the Destination Queue, Connection factory, etc information in weblogic-ejb-jar.xml.
I am not sure what is to be used in Oracle Server.
Simple search in Oracle Website gave me some links..
http://www.oracle.com/technology/tech/java/oc4j/ejb3/how_to/howtoejb30mdb/doc/how-to-ejb30-mdb.html
Search the Oracle website for more information.
Thanks and regards,
Pazhanikanthan. P

MDBs listen on remote queue

How do you configure MDBs to listen on a remote queue in OAS 10g 10.1.3?
I've tried using the SonicMQ example in the container services guide as a template, but I haven't been able to get it to work.
Thanks.
Dan

Ok I understand now. When you said remote I thought you meant a destination outside the service bus, and not an MQ remote queue. Unfortunately I have little advice to give. The documentation states:
When you create an MQ service, select the transport protocol as mq and specify the Endpoint URI in the Transport Configuration >page. Specify the Endpoint URI in mq://local-queue-name?conn=mq-connection-resource-ref format where
local-queue-name is the name of the local queue configured on the MQ server
mq-connection-resource-ref points to the location of the MQ connection resource I don't know if it's possible to use a remote queue directly, my knowledge of MQ is limited. Hopefully someone else can help. Or you could contact support and ask if remote queues are supported.

MDB listening on AQ.

I have written a message driven bean that listens on an Oracle AQ. In v9.0.2 of OC4J I had a number of problems (e.g. the MDB would wait 240 seconds before accepting a second message, and the queue working in a LIFO way instead of a FIFO way). However, the developers preview (v9.0.3) of OC4J has fixed these 2 problems but introduced another. Now my messages never get dequeued from my AQ (they did in v9.0.2). Has anyone else encountered a similar problem using a MDB on Oracle AQs and v9.0.3 of OC4J?
Thanks,
Stephen Weatherly

Thanks for the reply, my MDB is transacted. In OC4J v9.0.3 my messages simply do not get dequeued when my MDB finishes it's processing. My MDB code runs and does what is expected, however, any messages delivered to it from the queue are not being automatically dequeued. In OC4J v9.0.2 after my MDB's code had finished successfully then the message would be dequeued by whatever process manages the delivering the message to the MDB, however in OC4J v9.0.3 this does not seem to happen. After my MDB has run the message remains on the queue. If I then restart the OC4J server then I receive the message again even though my MDB sucessfully processed the message the first time.
My MDB code is as follows:
package mdb;
import javax.ejb.*;
import javax.jms.*;
import javax.naming.*;
import java.util.*;
public class MessageLogger implements MessageDrivenBean
private final static int sleepTotal = 10 ;
private MessageDrivenContext messageContext;
public void ejbCreate()
System.out.println("MessageLogger.ejbCreate()");
public void onMessage(Message message)
System.out.println("Received message: " + message + " at " + new java.util.Date());
try
     oracle.jms.AQjmsTextMessage oracleMessage = (oracle.jms.AQjmsTextMessage) message;
     System.out.println("MessageLogger.onMessage() : " + oracleMessage.getText() );
//System.out.println("MessageLogger.onMessage() : " + message.getStringProperty("subject") + " " + message.getStringProperty("message"));
System.out.println("Sleeping...");
int sleepCount =0;
while (sleepCount < sleepTotal)
System.out.println("Sleeping: " + (1+(sleepCount++)) + " / " + sleepTotal );
try
Thread.sleep(1000);
catch (Exception e)
catch(Exception e)
throw new EJBException(e);
public void ejbRemove()
System.out.println("MessageLogger.ejbRemove()");
public void setMessageDrivenContext(MessageDrivenContext context)
this.messageContext = context;
My ejb-jar.xml looks like:
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
<ejb-jar>
     <description>A How-To demonstrating Message-Driven Beans</description>
     <enterprise-beans>
          <message-driven>
               <description></description>
               <ejb-name>MessageLogger</ejb-name>
               <ejb-class>mdb.MessageLogger</ejb-class>
               <message-driven-destination>
                    <destination-type>javax.jms.Queue</destination-type>
               </message-driven-destination>
          </message-driven>
     </enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>MessageLogger</ejb-name>
<method-name>onMessage</method-name>
<method-params>
<method-param>javax.jms.Message</method-param>
</method-params>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
My orion-ejb-jar.xml looks as follows:
<?xml version="1.0"?>
<!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
<orion-ejb-jar>
     <enterprise-beans>
          <message-driven-deployment name="MessageLogger"
destination-location="java:comp/resource/RUB4/Queues/AQ.JMS_queue_1"
connection-factory-location="java:comp/resource/RUB4/QueueConnectionFactories/JMS_Queue_CF"
max-instances="1">
          </message-driven-deployment>
     </enterprise-beans>
     <assembly-descriptor>
     </assembly-descriptor>
</orion-ejb-jar>
And I have the following resource provider set up in my OC4J applications.xml file:
<resource-provider class="oracle.jms.OjmsContext" name="RUB4">
<description>Access to RUB4 database rubick</description>
<property name="url" value="jdbc:oracle:thin:aq/aq@rubick:1521:RUB4" />
<property name="username" value="aq" />
<property name="password" value="aq" />
</resource-provider>
Thanks for any assistence,
Steve

MBD in Oracle OC4J listening to SUN's MQ queue

I wonder if anyone knows if there's a way to have a Message Driven Bean deployed in Oracle's application server (OC4J) listening to a queue created in SUN's MQ.
I already managed to write clients that read the administered objects from Oracle's LDAP server (OID), but it seems that the OC4J application server has a bundled JMS provider (OracleAS JMS) and everything is oriented to use it instead of using an external JMS server.
There's also the possibility to use a JMS provider on Oracle's database (Oracle JMS) and in addition to all this to plug in the libraries to use an external WebSphere, SonicMQ or SwiftMQ provider.
Is there a way to use a MDB with both products MQ with OC4J?

Does anyone have used the connector architecture to solve a case like this? I came across a page in the MQ documentation whith a short description of a JCA library that can be used to integrate the SUN's MQ JMS server to an application server different than the SUN's application server (by the way, this one comes with a bundled connector, so it's easy to make it work with MQ).

Authentication problem w MDB on WL8.1 and JMS Queue on WL6.1

          Hi,
          I'm having problems with a MessageDrivenBean that is deployed on a Weblogic 8.1
          server. It listens to a JMS Queue on a Weblogic 6.1 server.
          I'm getting the following error message upon deployment:
          [java.lang.SecurityException: Authentication for user system denied in realm wl_realm
          I've made sure that both servers are installed with the user "system" and a password
          of "password".
          This worked fine for two WL6.1 servers.
          Here's my ejb-jar.xml:
          <!DOCTYPE ejb-jar PUBLIC
          '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN'
          'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
          <ejb-jar>
              <enterprise-beans>
                  <message-driven>
                      <ejb-name>WebResponseJMSBean</ejb-name>
                      <ejb-class>com.ditech.webresponse.jms.WebResponseJMSBean</ejb-class>
                      <transaction-type>Container</transaction-type>
                      <message-driven-destination>
                          <destination-type>javax.jms.Queue</destination-type>
                      </message-driven-destination>
                  </message-driven>
              </enterprise-beans>
              <assembly-descriptor>
                  <container-transaction>
                      <description>Transaction attributes for 'WebResponseJMSBean' methods</description>
                      <method>
                          <ejb-name>WebResponseJMSBean</ejb-name>
                          <method-name>*</method-name>
                      </method>
                      <trans-attribute>NotSupported</trans-attribute>
                  </container-transaction>
              </assembly-descriptor>
          </ejb-jar>
          Here's my weblogic-ejb-jar.xml:
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC
          '-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
          'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
                  <ejb-name>WebResponseJMSBean</ejb-name>
                  <message-driven-descriptor>
                      <destination-jndi-name>com.ditech.jms.CowResponseQueue</destination-jndi-name>
                      <provider-url>t3://localhost:7003</provider-url>
                      <connection-factory-jndi-name>com.ptp.jms.AppOnlineConnectionFactory</connection-factory-jndi-name>
                  </message-driven-descriptor>
                  <jndi-name>ejb/WebResponseJMSBean</jndi-name>
              </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          Can anyone give me any suggestions?
          Thanks in advance,
          -Ben


          We are facing a similar issue, between MDB's and JMS Queues on 2 separated WebLogic
          8.1 domains. What I will test next week are:
          1. In the domain where my MDB's are deployed, configure Foreign JMS Servers/Connection
          Factories/Queues, for which passwords can be specified (not possible in weblogic-ejb-jar.xml)
          2. If No.1 does not work, I will add CredentialGenerated="false" in <SecurityConfiguration>
          in config.xml in both domains
          3. If No. 2 still does not work, I will specify run-as principal and security-role
          in my MDB DD files, and specify CredentialMapping via the WebLogic admin console.
          Maybe you can try the same?
          Eric Ma
          "B Liu" <[email protected]> wrote:
          >
          >Hi,
          >
          >I'm having problems with a MessageDrivenBean that is deployed on a Weblogic
          >8.1
          >server. It listens to a JMS Queue on a Weblogic 6.1 server.
          >
          >I'm getting the following error message upon deployment:
          >
          >[java.lang.SecurityException: Authentication for user system denied in
          >realm wl_realm
          >
          >I've made sure that both servers are installed with the user "system"
          >and a password
          >of "password".
          >
          >This worked fine for two WL6.1 servers.
          >
          >Here's my ejb-jar.xml:
          >
          ><!DOCTYPE ejb-jar PUBLIC
          >
          >'-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN'
          >
          >'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
          >
          >
          ><ejb-jar>
          >
          >    <enterprise-beans>
          >
          >        <message-driven>
          >
          >            <ejb-name>WebResponseJMSBean</ejb-name>
          >            <ejb-class>com.ditech.webresponse.jms.WebResponseJMSBean</ejb-class>
          >            <transaction-type>Container</transaction-type>
          >            <message-driven-destination>
          >                <destination-type>javax.jms.Queue</destination-type>
          >            </message-driven-destination>
          >
          >        </message-driven>
          >
          >    </enterprise-beans>
          >
          >    <assembly-descriptor>
          >
          >        <container-transaction>
          >
          >            <description>Transaction attributes for 'WebResponseJMSBean'
          >methods</description>
          >            <method>
          >                <ejb-name>WebResponseJMSBean</ejb-name>
          >                <method-name>*</method-name>
          >            </method>
          >            <trans-attribute>NotSupported</trans-attribute>
          >
          >        </container-transaction>
          >
          >    </assembly-descriptor>
          >
          ></ejb-jar>
          >
          >Here's my weblogic-ejb-jar.xml:
          >
          ><?xml version="1.0"?>
          >
          >
          >
          ><!DOCTYPE weblogic-ejb-jar PUBLIC
          >
          >'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
          >
          >'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
          >
          >
          ><weblogic-ejb-jar>
          >
          >    <weblogic-enterprise-bean>
          >
          >        <ejb-name>WebResponseJMSBean</ejb-name>
          >
          >        <message-driven-descriptor>
          >
          >            <destination-jndi-name>com.ditech.jms.CowResponseQueue</destination-jndi-name>
          >            <provider-url>t3://localhost:7003</provider-url>
          >            <connection-factory-jndi-name>com.ptp.jms.AppOnlineConnectionFactory</connection-factory-jndi-name>
          >        </message-driven-descriptor>
          >
          >        <jndi-name>ejb/WebResponseJMSBean</jndi-name>
          >
          >    </weblogic-enterprise-bean>
          >
          ></weblogic-ejb-jar>
          >
          >
          >Can anyone give me any suggestions?
          >
          >Thanks in advance,
          >-Ben
          >

Two MDB Listen on same topic

Dear All,
If I configure two separate MDBs to listen on the same Topic using Oracle JMS (i.e have a multi-consumer queue table,...), will each MDB receive the same message or will only the first MDB to have its onMessage method fired by the container get the message?
Stuart

If you use different subscriber names for the 2 MDBs, then both of them will each receive a separate copy of each message sent to that topic (this follows standard JMS topic semantics)

MDB listening to an Oracle AQ, holding ADT messages...

Hi !
          I'm trying to set a MDB to listen for incoming messages on an Oracle AQ. When I created the queue, I specified that the queue should contain payload of type ADT. I'm using Bea Weblogic server 8.1sp4 and Oracle 10.2.0. The creation of the connection to the queue is implemented as a start up class and bound to the context during server start up.
          However it fails to start up, I get the following exception:
          <20.mar.2007 kl 11.03 CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB:
          MyWebLogicMDB is unable to connect to the JMS destination: AQJMSQueue. The Erro
          r was:
          oracle.jms.AQjmsException: JMS-137: Innholdsfabrikk m? angis for m?l med ADT-inn
          hold
          oracle.jms.AQjmsException: JMS-137: Innholdsfabrikk m? angis for m?l med ADT-inn
          hold
          at oracle.jms.AQjmsError.throwEx(I)V(AQjmsError.java:288)
          at oracle.jms.AQjmsConsumer.<init>(Loracle.jms.AQjmsSession;Ljavax.jms.D
          estination;IILjava.lang.String;Ljava.lang.Object;Loracle.jms.AQjmsSelector;Ljava
          .lang.String;Z)V(AQjmsConsumer.java:385)
          at oracle.jms.AQjmsConsumer.<init>(Loracle.jms.AQjmsSession;Ljavax.jms.D
          estination;IILjava.lang.String;Ljava.lang.Object;Loracle.jms.AQjmsSelector;Ljava
          .lang.String;)V(AQjmsConsumer.java:254)
          at oracle.jms.AQjmsSession.createReceiver(Ljavax.jms.Queue;Ljava.lang.St
          ring;Ljava.lang.Object;)Ljavax.jms.QueueReceiver;(AQjmsSession.java:1631)
          at oracle.jms.AQjmsSession.createReceiver(Ljavax.jms.Queue;Ljava.lang.St
          ring;)Ljavax.jms.QueueReceiver;(AQjmsSession.java:1553)
          at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(Ljavax
          .jms.Destination;Ljava.lang.String;III)V(JMSConnectionPoller.java:1720)
          at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection()V(JM
          SConnectionPoller.java:2019)
          at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS()V(JMSConnec
          tionPoller.java:1180)
          at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling
          ()V(JMSConnectionPoller.java:846)
          at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start()V(Messag
          eDrivenBeanPoolInfoImpl.java:234)
          at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans()V(EJBDe
          ployer.java:1660)
          at weblogic.ejb20.deployer.EJBDeployer.start(Z)V(EJBDeployer.java:1488)
          at weblogic.ejb20.deployer.EJBModule.start()V(EJBModule.java:689)
          at weblogic.j2ee.J2EEApplicationContainer.start([Lweblogic.j2ee.J2EEAppl
          icationContainer$Component;)V(J2EEApplicationContainer.java:2127)
          at weblogic.j2ee.J2EEApplicationContainer.activate([Lweblogic.management
          .configuration.ComponentMBean;)V(J2EEApplicationContainer.java:2168)
          at weblogic.j2ee.J2EEApplicationContainer.activate()V(J2EEApplicationCon
          tainer.java:2115)
          at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivat
          ion(Z)V(SlaveDeployer.java:3082)
          at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
          llApplications(ZZ)V(SlaveDeployer.java:1751)
          at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeploye
          r.java:359)
          at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
          e()V(DeploymentManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131
          at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:966)
          at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:361)
          at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
          >
          The problem is that the MDB cannot be set up to dequeue the message because the payload factory has to be set for the consumer in order to receive messages from queues which have messages with ADT payload. (Text works OK)
          So my questions are:
          1) Is there a way to set the payload factory to use in the MDB? (deployment descriptor)
          2) Do MDB support AdtMessages?
          3) Are there any other ways to listen to an Oracle queue which has ADT type?
          mvh
          jb

I don't think there's a way to have MDBs call arbitrary proprietary JMS extensions.
          You might want to check if Oracle supplies some sort of configuration method - perhaps via destination or connection factory configuration, by passing extra information in the CF or destination JNDI name, by specifying a -D on the JVM command line, or by passing special properties through to their InitialContext.
          Another option is to code your own JMS wrapper classes around AQ that call the required extensions as needed.
          Tom

MDB listening on Socket instead of Queue

Similar Messages

Maybe you are looking for