Stop MDB from listening to a JMS queue

Hello,
From time to time we would like to stop the processing done in our application.
The processing is started by onMessage() in MDB. Is it possible to tell the MDB
to stop listening
to the JMS queue or stop the delivery of messages by JMS ? We do not intent to
stop the processing of messages that have already started by only to stop processing
of further messages (the ones still in the JMS queue).
We are using 6.1SP3.
Any help is appreciated.
Eric Poupaert,
Approach Belgium SA.

If you can tune the number of messages that should be sent to the MDB to 0, that would
temporarily stop the MDB from consuming messages. Thsi is the "Messages maximum"
parameter on ur connectionfactory. WL6 doesnt support changing this value to 0 but there
were some newsgroup discussions last year that it might be supported in a future
release. Maybe its fixed in 8?
Eric Poupaert wrote:
Hello,
From time to time we would like to stop the processing done in our application.
The processing is started by onMessage() in MDB. Is it possible to tell the MDB
to stop listening
to the JMS queue or stop the delivery of messages by JMS ? We do not intent to
stop the processing of messages that have already started by only to stop processing
of further messages (the ones still in the JMS queue).
We are using 6.1SP3.
Any help is appreciated.
Eric Poupaert,
Approach Belgium SA.

Similar Messages

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
          >

HT204266 I have got a transparent pic of a speaker on my ipod and cannot get rid of it,it is stopping me from listening to my music as the volume is not working

How can I get rid of a transparent picture of a speaker on my Ipod? it appeared fromno where and it is stopping me from listening to my music, and from seeing whats on the screen,

- Try a reset. Nothng is lost:
Reset iPod touch: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears
- Insert and remove tha headphone plug a couple of times.
- Restore from backup
- Restore to factory defaults/new iPod

Need to publish message from database to a JMS Queue using Java

I need to publish messages to a Websphere JMS Queue whenever any changes happen on a particular column of a table in oracle 11g. For that I have written a trigger on that particular table which in turn will invoke one java procedure. I have written the java procedure using a standalone java class and uploaded the java class as a schema object. While executing the procedure it is throwing error as it is not able to instantiate some of the java classes. I don't know how to provide the reference of different jar files while executing the java class. Can anyone help me on this.

Welcome to the forum!
>
I have written the java procedure using a standalone java class and uploaded the java class as a schema object. While executing the procedure it is throwing error as it is not able to instantiate some of the java classes. I don't know how to provide the reference of different jar files while executing the java class.
>
Clarify your statement. First you say 'standalone java class' but then you talk about instantiating java 'classes' and referencing 'different jar files'. If you are executing your Java class inside Oracle then any Java classes that your java class is referencing also have to be loaded into Oracle or it won't be able to reference or execute them.
How do you plan to ' publish messages to a Websphere JMS Queue '? Where is this queue you are talking about?
Why are you using a Java procedure and class instead of PL/SQL?
What is your 4 digit Oracle version (result of SELECT * FROM V$VERSION)?

Configuring a BEA WebLogic 7.0 Server and MDB to Listen on an Oracle Queue

I am tasked with configuring a BEA WebLogic 7.0 SP1 Server, and deploying an MDB to listen to a queue created in Oracle Advanced Queuing. Has anyone had any experience in making this work? And if so, could you send me some sample code/XML that illustrates such?
Thanks!

See my reply at Deploying MDB on BEA WebLogic 7.0 to listen to Oracle AQ

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

Weblogic app server: MDB is unable connect to JMS Queue!

29-Jun-2006 16:22:23 o'clock SGT> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: YCCEventsMDB is unable to connect to the JMS destination: jms/citos/ycds/RecvYCCEvents_Q. Connection failed after 7 attempts. The MDB will attempt to reconnect every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
<29-Jun-2006 16:22:23 o'clock SGT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: YCCEventsMDB is unable to connect to the JMS destination: jms/citos/ycds/RecvYCCEvents_Q. The Error was:
[EJB:011009]Unable to create a JNDI InitialContext to lookup the JMS destination.
javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: ycds_app_svr]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:41)
     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:618)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
     at

Any update on this. I am getting the same error.

Stop nmbd from listening on external interface?

I've installed a Mac mini (with OS X Lion Server) as a file server and local gateway between my organization's local network and ISP's private network.
Issues with NAT and DHCP are separate, and not much of an immediate concern for now, but the nmbd acting up on the local network is a real stopper.
The connection scheme is as follows:
My LAN is connected to en0 (internal Ethernet port) and is located in Apple's idiotic 192.168.2.0/24 range (for now).
The ISP network is somewhere in the 10/8 range and is connected to en3 (USB Ethernet adapter)
In system settings, own LAN (en0) is set above all else.
The problem is that if Mac's nmbd winning election and become a responsible name server, the name resolution in the workgroup fails with "no route to host" message, until I turn on any MacBook located in the same workgroup, which winning election over the server.
When i make a check with server itself, it's SMB name (and the <name>.local alias) is always resolved to the address of external (en3) adapter.
The question is - how to tell this idiot to do the right thing and stop acting like it have a brain?

I am sure that there is a better way to do this using the /etc/X11/nvidia.conf file, but I am not very familiar with that one. The way that I am familiar is to put this line at the top of the session file that startx uses:
disper -s
Note that I am not backgrounding it using the '&'. You do not want to do that because then the script will hang until the display switch complete. You also want to put it before the conkys because then the display switch happens before conky is started.
I face similar issues with dzen and trayer. I get around it by using the following bash script to determine the screen sizes:
#!/bin/bash
OUT=$(disper -p 2> /dev/null )
NUMBER=$(( ${1:-1} + 1 ))
MONITOR=$(echo "$OUT" | sed -e '/xinerama/!d' \
-e 's/[a-z ]*: //' \
-e 's/$/,/' \
-e 's/[A-Z0-9-]*,/|&|/'$NUMBER \
-e 's/,//g' \
-e 's/[^|]*|$[A-Z0-9-]*$|.*/\1/')
source <(echo "$OUT" | sed -e '/metamode/!d' \
-e "s/$MONITOR: nvidia-auto-select @$[0-9]*$x$[0-9]*$ +$[0-9]*$+$[0-9]$/|W=\1;H=\2;X=\3;Y=\4;|/" \
-e 's/[^|]*|$[0-9XYWH=;]*$|.*/\1/')
case $2 in
w) echo $W ;;
h) echo $H ;;
x) echo $X ;;
y) echo $Y ;;
*) echo "X=$X"
echo "Y=$Y"
echo "W=$W"
echo "H=$H"
esac
I am sure that the script could be improved upon, but that's how I take care of it.
Just out of curiosity, does your disper function properly? Mine stopped working a couple weeks ago.

How can I stop it from uploading and clear the queue?

I'm having a hell of a time uploading these photos to my picasa account. After several attempts to get it working, it is now upload all 1,000+ photos and videos about 4 times. It's been going for almost 24 hours now and I just want to cancel and start over. Right now I can only pause uploading but I can't clear the queue. Any help would be greatly appreciated. Thanks.

I have to agree the reply came off a bit condesending. People are at all different level of tech competency and that is no reason to make others feel badly. Most of the people on the board are kind and helpful but others.
That's one thing I love about Major Geeks online they are always helpful and you can ask a "foolish" question and never made to feel badly by the people who are members and are just donating time to help others... it's really nice!
I don't automatically update for a month I want to make sure all the bugs are out and find out if there are any problems. I have dyslexia and do not always have time to get through all the information. The new rules and regulations is pages and pages long. And trying to read it on my Iphone 4s was awful. I finally gave up and just agreed. I am not concerned about Youtube as I am losing Google maps. It's not like they put Mapquest in, which is what I always check after Google to see if there is a better way to get where I am going.

MDB,MDB container or JMS adapter stops processing messages from JMS queue

Hi guys,
we have created a component using Enterprise Java Beans, let's say a product catalog, deployed it on a Glassfish v2 instance, and connected it to a legacy system using JMS and Sun MQ v4.1 as messaging system. The catalog component thus starts one MDB that listens on a JMS queue, let's say a queue named catalog_business_events_in, and waits for incoming messages, i.e. in our case update events. The problem is, that in general this approach works well, but sometimes the MDBs/JMS adapter stops for some reason fetching and processing messages from the JMS queue. We don't know why - no exceptions, etc.. Seems to be a Glassfish EJB container, JMS adapter or Sun MQ configuration issue. It seems to be that our component is not the problem.
The messages are compressed/uncompressed by Sun MQ automatically. We actually have 2 Sun MQ instances in clustered mode running to have some kind of failover - no HA cluster, yet. Sun MQ instances are accessed from Glassfish instances running in different Glassfish clusters - so we have a dedicated Sun MQ cluster not a Sun MQ instance per Glassfish instance. Each Glassfish instance is configured such that it knows both Sun MQ instances to allow automatic failover.
Has someone an idea, why the MDBs/ MDB container/ JMS adapter - stops processing messages? We are kind of puzzled as it happens more often now and apparently when traffic is (very) low not high!
Thanks for your help.
Cheers,
Martin
Edited by: east1979 on Jan 13, 2009 8:06 AM

Hi Manoj,
I have a very similar if not identical issue,
Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
15/11/12 09:10:08 JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
TION TO CONTINUE.
15/11/12 09:10:15 Communication Error. See real time job log for details.
Dump available:
https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
Version of DS:14.0.3.273
Any comments?
Thansk and kind Regards,
Kenneth

Single MDB on a clustered JMS queues(2)

I have 2 JMS servers in a cluster and each server has a JMS queue, which forms the distributed destination. Now I need a MDB to listen on both these queues. Is it possible?
Thanks
-Ankur

Yes - thats the usual purpose of distributed queues, to allow consumers to consume from the distributed queue (wherever its hosted).
Though distributed destinations are JMS provider specific so do check your providers documentation on using distributed queues. In some providers, like ActiveMQ, distributed queues look and act just like regular queues so they just work from inside a JMS client or MDB.
James
http://logicblaze.com/

HowTo:Publish Msg to JMS queue deployed in a Weblogic Cluster from a client

Hello All-
I am new to Weblogic and need help from this forum. Forgive me for my ignorance. I am learning.
Below is a brief about the context and the issues that we are facing:
Background
=======
1. We have Oracle Service Bus (OSB) installed on top of Oracle Weblogic Server (ver 10.3). In OSB we have developed a proxy service that listens to a JMS queue for an incoming message
2. The Weblogic environment is a cluster having 2 managed servers listening to different ports and it is front-ended by a Apache Load Balancer.
3. Our requirement is to post an XML message from a Java client to the JMS queue which will then initiate the proxy service deployed. We are using t3 protocol to post the message from the client to the JMS queue
Issue
====
1. To post an XML message from the client, how do we give the address of the JMS queue in the clustered environment to enable failover/loadbalancing if one managed server goes down. I understand from your earlier posts in this forum that directly hitting the JMS queue on a particular managed server will not enable failover/loadbalancing in case one of them goes down
2. Do we need to modify any config file in the Apache Proxy Plugin?
3. Do we need to provide the address of the Apache proxy in the client to send the message?
Kindly clarify and let me know me know if you need any additional information.
Greatly appreciate your help!!!
Regards,
Dibya

Hi Dibya,
Please refer to : http://weblogic-wonders.com/weblogic/2010/05/13/apache-proxy-as-static-content-repository/#comment-1379
Thanks
Jay SenSharma

Connecting to SeeBeyond JMS queue

Hello everybody,
we have J2EE application on Oracle Application Server. Right now we try to add MDB that has to listen on SeeBeyond JMS Queue. What do I need to specify in configure orion-ejb-jar.xml?
thanks

The howto is not a standalone resource adpater example, so the RA's archive file .rar is wrapped in an EAR file.
So if you deploy a standalone resource adapter, you will deploy a .rar file. But also you could embed your resource adapter file - .rar inside an application .ear file, as the howto example. so the structure looks like:
.ear -- .rar
-- .jar
-- xml descriptors
-- native libraries
If you take a look at build.xml it shows how the ear file is constructed.
-Frances

Populating Database records to WLS JMS queue

Hi All,
Please suggest which is the performance effective approach in populating WLS JMS queue from the database tables?
As I have to produce millions of records from the DB into the JMS queue and assuming using DB adapter and retreiving bulky data is a long running process.
Please suggest whether I can write a pl/sql stored proc and populate the WLS JMS queue? or is there any other most optimistic approach to transfer data from db into WLS JMS queue?
Thanks,
Sudha

Thanks Eric for the quick reply. Also, going through the other forum:
Re: Publish message from Oracle database PL/SQL to a remote WLS JMS queue
Just want to know which one would be performance effective one in the below whether using Java stored Procedures or populating AQ and WLS Messagin bridge?
1) Java Stored Procedure can use JMS APIs to publish messages to WLS JMS destinations. JMS standard API jar file and WLS JMS client jars that you use need to be loaded into database.
2) From PL/SQL, you can publish message to AQ using AQ PL/SQL APIs, then configure WLS Messaging Bridge to forward messages from AQ to WLS JMS.

JMS Queue Messages not picked up.

Hello,
We are facing below issue frequently, any help in this regard would be highly appreciated.
We have 2 MDB's listening to the a queue on WLS 8.1 SP2. We are using Message Selector to identify which of the 2 MDB's should pick up the message.
The issue is that if too many messages are queued up, then the MDB at times doesn't pick them up, even when free instances of MDB are available in the Bean Pool.
But if we restart the server then all the messages are picked up instantly. Server restart acts as some kind of Trigger for the Queued Messages to be picked up instantly.
We have been trying to explore as to why this happens, but havent still resolved it.
Any ideas would be appreciated.
Thanks.
Khyati

Hello,
We are facing below issue frequently, any help in this regard would be highly appreciated.
We have 2 MDB's listening to the a queue on WLS 8.1 SP2. We are using Message Selector to identify which of the 2 MDB's should pick up the message.
The issue is that if too many messages are queued up, then the MDB at times doesn't pick them up, even when free instances of MDB are available in the Bean Pool.
But if we restart the server then all the messages are picked up instantly. Server restart acts as some kind of Trigger for the Queued Messages to be picked up instantly.
We have been trying to explore as to why this happens, but havent still resolved it.
Any ideas would be appreciated.
Thanks.
Khyati

Stop MDB from listening to a JMS queue

Similar Messages

Maybe you are looking for