MDB's and determining queues/topics

Hi,
I was reading recently that MDB's only allow you specify whether they consume queues or topics in their deployment descriptors, not which particular queue or topic. There were further comments to the effect that app server vendors will provide this level of granularity in a proprietary manner.
Are there plans to allow this finer level of granularity in a standard manner or is it deemed that the existing solution is sufficient ?
I don't particularly look forward to huge "if" clauses in the onMessage, or session beans, to deal with determining the specific queue or topic involved.
Any comments ?
Cheers,
mairt

It is true that the actual name of the que/topic is not specified in the ejb-jar.xml.
In case of weblogic it is specified in weblogic-ejb-jar.xml in( as you said a proprietary fashion)
by this tag <destination-jndi-name>titan-ReservationQueue</destination-jndi-name>
This helps you avoid those huge if blocks you have anticipated.
Well it is something we have to live with as of now.

Similar Messages

Multiple Apps and Multiple Queues/Topics

          In WL7, is it possible to have two applications both do the same JNDI lookup and get
          different queues? This is possible with EJB's because Weblogic has its own local
          JNDI lookup that the java:comp/env/ejb/XXX references, however you cannot do the
          local lookup with JMS queues/topics. My situation is that I may have more than one
          client on a given box, and the messages going into a queue are destined for specific
          clients, but the programs are both looking up the same queue (e.g., jms/UpdateCache).
          Is the only way to do this through using filters? I don't want to make any code changes
          from one client app to the next.


You can configure same queue/topic on multiple servers by using
          JNDINameReplicated=false on the queue/topic so each queue/topic is only
          known locally. Then you can use dedicated connection Factory for each
          server and you can use different url to connect to different server.
          e.g.
          # two connection factories deployed on two different WLS servers
          # myserver1 has url like this: 192.0.0.1:7001
          # myserver2 has url like this: 192.0.0.2:7001
          # two JMS Servers deployed on two different WLS servers
          # each JMS server has an identical queue
          # you do not need to specify JNDIName for the queue if you can use
          createQueue
          # queueSession.createQueue("./exampleQueue1");
          # client (sender/consumer) using 192.0.0.1:7001 to get initialContext
          will use "cf1" and
          # lookup queue on myserver1
          # client (sender/consumer) using 192.0.0.2:7002 to get initialContext
          will use "cf2" and
          # lookup queue on myserver2
          # port of config.xml
          <JMSConnectionFactory
          JNDIName="jms.connection.exampleFactoryFormyServer1"
          Name="cf1" Targets="myserver1"/>
          <JMSConnectionFactory
          JNDIName="jms.connection.exampleFactoryFormyServer2"
          Name="cf2" Targets="myserver2"/>
          <JMSServer Name="exampleJMSServer1" Targets="myserver1">
          <JMSQueue
          JNDIName="jms.queue.exampleQueue1"
          JNDINameReplicated="false"
          Name="exampleQueue1"/>
          </JMSServer>
          <JMSServer Name="exampleJMSServer2" Targets="myserver2">
          <JMSQueue
          JNDIName="jms.queue.exampleQueue1"
          JNDINameReplicated="false"
          Name="exampleQueue1"/>
          </JMSServer>
          "David Cherryhomes" <[email protected]> wrote in message
          news:[email protected]...
          >
          > In WL7, is it possible to have two applications both do the same JNDI
          lookup and get
          > different queues? This is possible with EJB's because Weblogic has its own
          local
          > JNDI lookup that the java:comp/env/ejb/XXX references, however you cannot
          do the
          > local lookup with JMS queues/topics. My situation is that I may have more
          than one
          > client on a given box, and the messages going into a queue are destined
          for specific
          > clients, but the programs are both looking up the same queue (e.g.,
          jms/UpdateCache).
          > Is the only way to do this through using filters? I don't want to make any
          code changes
          > from one client app to the next.

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
          >

MDB rollback to Queues/Topics

Can somebody explain the MDB rollback behaviour in Queues and Topics.
My specific questions are:
1) When a MDB, listening to a Queue, performs a rollback, does the message go back to the head of the queue (assumption is that the message should go back to the head of the queue)? Is this somewhere in the spec? Seems like different providers have different interpretations, all the JMS providers do not gurantee this behaviour.
2) If we replace the queue with Topic, where does the message go on a rollback?
3) Where does the message go when there are multiple subscribers to the Topic? Can the other subscribers that did consume the message successfully get the message again, if a subscriber performs a rollback?
The JMS specification does not cover these situation very well, so we are left to the mercy of the JMS providers.
4) Can somebody share the experience in this context, if we are trying to build a 'JMS agnostic' solution, how should we handle this rollback?
Thanks

1. Its dependent on the JMS provider. In ActiveMQ 4.x it is replayed to the consumer a number of times before being placed on the head of the queue - so ordering is maintained if the message is successfully processed by the same consumer.
However ordering is often broken if the message is put back on the head of the queue if you have multiple consumers, since they compete for messages. Though if you have multiple consumers anyway, you often loose total ordering unless you use a technique like Exclusive Queues or Message Groups.
2. Typically it'll be replayed to the same consumer again. Most JMS providers provide a way to customize the redelivery policy; how many times will it be redelivered before sending to a dead letter queue, what is the replay exponential back off time etc.
3. Yes. Each topic subscriber gets their own copy of the message. It doesn't matter if one consumer does or does not process the message; other consumers are unaffected.
4. I'd just retry the operation and rely on the MDB/JMS providers dead letter queue and you should be fine.
BTW if ever you need a tool to browse the dead letter queues and maybe move messages from the dead letter queue back to the originating queue, you could try Hermes
http://www.hermesjms.com/
James
http://logicblaze.com/

Creating a MDB and Distributed Queue in Clustered env in weblogic 9.2

I have created 3 managed servers and all these managed servers are in the cluster.
          Now i create JMS module for this cluster and create the Connection factory 'QUEUE_CF_8' and distributed Queue 'DIS_QUEUE_8' targeting to the cluster.
          I create a MDB and JMS client and deploy them in the cluster.JMS client sends the message to the distributed queue and MDB is listening to the distributed queue
          When i deploy the MDB , it is deploys perfectly . But when i run the client it fails with the following exception
          [java] javax.naming.NameNotFoundException: Unable to resolve 'QUEUE_CF_8'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'QUEUE_CF_8'. Resolved '']; remaining name 'QUEUE_CF_8'
          When i view the JNDI tree for all the managed servers , i can see the Connection factory and the distributed queue.
          Also i deploy the MDB to the cluster and no submoduletargets are specified.
          Let me know what is that iam missing.

<?xml version='1.0' encoding='UTF-8'?>
          <weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
          <connection-factory name="Queue_CF_8">
          <sub-deployment-name>Server_group_4</sub-deployment-name>
          <jndi-name>QUEUE_CF_8</jndi-name>
          <security-params>
          <attach-jmsx-user-id>false</attach-jmsx-user-id>
          </security-params>
          </connection-factory>
          <uniform-distributed-queue name="DIS_QUEUE_8">
          <sub-deployment-name>Server_group_4</sub-deployment-name>
          <jndi-name>DIS_QUEUE_8</jndi-name>
          <load-balancing-policy>Round-Robin</load-balancing-policy>
          </uniform-distributed-queue>
          </weblogic-jms>
          But the problem was with the clustering.
          Thanks for your time..

JMS Queue/Topic MDB

Es posible crear Queue/Topic diamicamente
Es posible crear los MDB dinamicamente.
de que manera se puede implementar.
gracias.

Hi Rolper
La capacidad de crear din�micamente un queue/topic depende de su abastecedor de JMS. La mayor�a de los abastecedores de JMS tienen un "API administrativo" para hacer esto - por ejemplo ArjunaMS (http://www.arjuna.com) proporciona un API comprensivo para crear queue y topics en runtime.
Hope this helps,
Tom Jenkinson

Regarding JMS-Queue/Topic in Proxy and Business service in OSB

Hi
I have one query regarding to the JMS-Queue/Topic.
I am published the message to the JMS-Queue/Topic.
----My Business-service configuration is---
General----Any xml
Tranport--jms://localhost:7001/MyConnectionFactory/RequestQueue
Response--None
I call this Business-service in proxy-service of Routing message was published successfully to thee Queue.
I try to dequeue the message from that queue for this
--- I take another proxy with---
General----Any xml
Tranport--jms://localhost:7001/MyConnectionFactory/RequestQueue
In meassage flow
Routing--second busines-service)
--- Second business-service configuration is---
General----Any xml
Tranport-File (C://temp)
Issue is when I publish the message to Queue,the message is also found in the file i.e C:temp. I don't now why this come to the file.*
Any suggestions
Thanks
Mani

Either I did not get an idea, but in your JMS proxy you are routing to File :)
If you don't want file, why route to 2nd BS ?

Web service which listens/replies over JMS Queues/Topics - HOW?

Hi all,
I need help - I have to implement the following Web Service for Weblogic 8.1:
- Simple Helloworld operation
- The Web service should listen on a Queue(or Topic) - say Queue1
- The response of the service should be put in another queue - predefined - say Queue2(or taken as propetry of the request "ReplyTO")
I looked for such an implementation in the available examples and forum topics, but without luck.
Please, give an example or a guide how to implement such a service if possible!
Thanks,
Ivo

Hi,
I have a work around to this problem please see if it suits you or you might already be knowing it.
Workaround is
1. Create a Simple Webservice as needed which puts a message in a Queue.
2. Create an MDB which listens to you Queue / Topic and call the created webserivce in the onMessage function of the MDB.
Vivek

Accessing JMS Queue/Topic located in different Managed server on same domai

Our use-case is as follows.
In our weblogic domain we have SOA_Cluster and a stand alone managed server. All the custom JMS resources belong to a JMS server that is targeted to stand alone JMS server. We are trying to access JMS Queues/Topics located in the stand alone managed server from JMS adapter (part of SOA Cluster).
I am wondering what should be our adapter configuration in this scenario. In going through JMS adapter use-cases (below is the link), there is a mention of how to access resources located in Remote weblogic Domain. I am wondering if the same applies to us OR if there is better way to access JMS resources for our use case.
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10231/adptr_jms.htm#CJAHAFGF
Appreciate your feedback.

Yes, the same applies for your case but no need to enable trust. Rest of the things will remain same.
Better you post weblogic related questions in Weblogic forum.
Regards,
Anuj

Deploy the larger rulebases and determinations-server to WSL 10.3.5 slow

On : 10.1.0.27 version, Oracle Policy Automation
Determination Server
WLS managed server
ACTUAL BEHAVIOR
Deploy the larger rulebases and determinations-server to WSL 10.3.5
It takes around 20 minutes to deploy.
Often the WLS times out during the deployment and we find the only way of getting the determinations-server to run again is to restart the WLS managed server.
EXPECTED BEHAVIOR
No time or delay to deploy.
Business impact
On the way deploy rule base WLS server sometimes timeout.

The customer improved as follows solution.
The customer have changed the way deploy the rulebases and this has reduced the deployment time dramatically.
They have 3 rulebases and one of Billing is the largest by far.
They have split the billing into an out of the box determinations-server and are deploying it as a war.
The whole process is now acceptable.
=== ODM Data Collection ===
<Info> <WebService> <c17ssit1.lab.gov> <opasit1_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <bfeae85a12c63a65:-b8294b1:13ad04153dd:-8000-0000000000000003> <1352114445944> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
<Warning> <Socket> <c17ssit1.lab.gov> <opasit1_server1> <ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1352204469466> <BEA-000450> <Socket 328 internal data record unavailable (probable closure due idle timeout), event received 0>
<Warning> <Socket> <c17ssit1.lab.gov> <opasit1_server1> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1352204534404> <BEA-000450> <Socket 342 internal data record unavailable (probable closure due idle timeout), event received -32>

MDB not dequeuing the Queue

Hi Guys.
Im working with oc4j_extended_101300 and a MDB with annotations
I've got a jsp that sends a message to the queue. This seems to work. I can see in the administrative console that the "Messages Waiting for Read" is modified each time I send a message.
But my MDB is not reading those messages. The onMessage() is never called.
The annotations in my MDB are:
@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName="messageListenerInterface", propertyValue="javax.jms.MessageListener"),
@ActivationConfigProperty(propertyName="connectionFactoryJndiName", propertyValue="jms/NewMessageFactory"),
@ActivationConfigProperty(propertyName="destinationName", propertyValue="jms/NewMessage"),
@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="messageSelector", propertyValue="RECIPIENT = 'MDB'") })
The Factory and the Queue are also defined in de jms.xml
Am I forgetting about a configuration somewhere??
I hope you can help.

Does your jsp put the selector value (RECIPIENT='MDB') in the Message object?
I think it would be like this:
on your Message object: setStringProperty("RECIPIENT","MDB");

How to view contenets of Queues/Topics?

I have been sending some XML files through my ESB flow to a JMS destination(Consumer). The flow will be successfull. But I cannot watch the contents of these JMS destination queues anywhere. I want to watch if the output data is correct in case I have some transformation in between.
I tried to watch contents in ESB control console and in App Server. But no luck.
Has anybody been successful in retreiving contents of Queues/Topics?
Thanks,
-vena

You can also view the messages in a queue through the mbean browser in EM.
Go to the administration page of the instance where your JMS destination is, under JMX section, click on System MBean Browser. Once there, the path should be oc4j->J2EEServer->standalone->JMSResource->JMS->JMSDestinationResource.
Then click on your queue name, and under the operations tab, there will be a browse option. If you want to see all messages, put in 0 for the count, then click "Invoke Operation".

Configuring an MDB to an MQSeries Queue

I want complete details as to how to configure an MDB to an MQSeries Queue.


From the JMS FAQ at http://e-docs.bea.com/wls/docs70/faq/jms.html
          Q. How do I integrate non-WebLogic JMS providers with WLS?
          A. Refer to the white paper, "Using Foreign JMS Providers with WebLogic
          Server" (jmsproviders.pdf) on
          http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          for a discussion on integrating MQ Series, IBus MessageServer, Fiorano,
          and SonicMQ.
          Or google search this newsgroup for "MQ".
          Tom
          Ranjit wrote:
          > I want complete details as to how to configure an MDB to an MQSeries Queue.

JMS,Queues/Topics,Weblogic8.1

Hi
Im newbie to JMS, and I would like to get start with
JMS,Queues/Topics on Weblogic8.1 .
Can anybody provide me urls which are easy to
understand as well as run the sample applications.
thnks..

Maybe its worth starting with a library that wraps up JMS for you so you can focus on POJOs and your application objects - like Lingo
http://lingo.codehaus.org/
James
http://logicblaze.com/

Cleanup JMS queue/topic messages

          how do I clean up all messages left on a queue/topic ? thx.


There is no purge command.
          In 8.1, delete and recreate the destination via the console,
          JMX, or extensions.JMSHelper, the JMS
          server doesn't even need to be booted. A timestamp
          in the destination configuration is automatically set to
          let JMS detect that the destination is a new version.
          In 7.0, delete the queue, shutdown the JMS server,
          reboot the JMS server, and then recreate the destination.
          In any version, shutting down the JMS server will delete
          non-persistent messages.
          You can delete topic subscriptions via the console.
          You can write a simple JMS client to drain the destination
          by consuming messages. (Multi-thread multiple consumers to
          speed this up considerably.)
          Queen Tsao wrote:
          > how do I clean up all messages left on a queue/topic ? thx.

MDB's and determining queues/topics

Similar Messages

Maybe you are looking for