Messages in a Queue/Topic

hi
How do i check if there are any messages in the Queue/topic. i am using Platform edition
Thanks

Download an install software for browsing queues.
Not quite sure what "Platform" edition is. If your JMS provider is MQ, use MQ Explorer / rfhutil, otherwise I find Hermes very useful

Similar Messages

Expiration of messages in JMSTopics / Queue Subscription to topics.

Hi all,
I tried to use topics in one of my OSB flows.
i have 2 doubts in this regard.
1. Is there a way in with i can subscribe my JMS queues to JMS topics?
2. If in my OSB flow i subscribe directly to the topic(instead of my queue subscribing to topic and my OSB flow subscibing to queue), even after my flow has taken the message from the topic, the message is still retained in the topic. How do i get rid of these retained messages in the queue dynamically. I dont want to delete those messages manually.

I'm not familiar with OSB particulars (this is a JMS forum -- OSB has its forum), but I can try answer your questions with respect to WL JMS only.
1. There's no direct facility at the WebLogic Server layer for subscribing a queue to a topic. The standard approaches are to write a basic MDB for the purpose, or configure a Messaging Bridge.
2. Are the messages in the subscription getting deleted? If not, then the problem is either in your app or at the OSB layer (failure to acknowledge/commit received messages). If so, then messages are likely accumulating in another subscription -- you can check for other subscriptions on the console, and keep in mind that distributed topics implicitly create subscriptions for forwarding messages between members. As you know, a message that is sent to a topic must be acknowledged/filtered-out/committed by all subscriptions before it is fully deleted.
It would be interesting to know the details about your use case, as I suspect it is a fairly common one. In particular, why do want to subscribe a queue to a topic subscription in the first place? I can then forward your write-up to OSB and JMS Product Managers, which might help accelerate the release of certain features on our roadmap. (email tom . barnes at oracle . com)
Tom

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.

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 ?

My problem in Weblogic and Message Driven Bean for Topic

Hello to all
I used this page (http://www.ecomputercoach.com/index.php/component/content/article/90-weblogic-jms-queue-setup.html?showall=1)
for setup JMS Server, Queue, Connection Factory on Weblogic Server
and I created a Message Driven Bean ,I used those Queue , and all things was OK
But I wanted to setup a Topic and use it in this manner
I created a Topic like previous steps for setup Queue
(http://www.ecomputercoach.com/index.php/component/content/article/90-weblogic-jms-queue-setup.html?showall=1)
Except in Step 3 ,I selected Topic instead of Queue
then I created a Message Driven Bean in JDeveloper , my Message Driven Bean is like this:
@MessageDriven(mappedName = "jndi.testTopic")
<p>
public class aliJMS1_MessageDrivenEJBBean implements MessageListener {
    public void onMessage(Message message) {
      if(message instanceof TextMessage ){
        TextMessage txtM=(TextMessage) message;
        try{
          System.out.println(txtM.getText());
        }catch(Exception ex){
          ex.printStackTrace();
</p>
When I deploy the Application , Weblogic shows me this error:
+<Aug 30, 2011 11:32:28 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: aliJMS1_MessageDrivenEJBBean is unable to connect to th+
e JMS destination: jndi.testTopic. The Error was:
+[EJB:011011]The Message-Driven EJB attempted to connect to the JMS destination with the JNDI name: jndi.testTopic. However, the object with+
the JNDI name: jndi.testTopic is not a JMS destination, or the destination found was of the wrong type (Topic or Queue).>
And when I send message to the topic The Message Dirven Bean dosen't work
But when I create an ordinary Java application like this (it uses that Tpoic) :
import java.io.*;
import java.util.*;
import javax.transaction.*;
import javax.naming.*;
import javax.jms.*;
public class TopicReceive implements MessageListener
    public final static String JNDI_FACTORY =
        "weblogic.jndi.WLInitialContextFactory";
    public final static String JMS_FACTORY =
        "jndi.testConnectionFactory";
    public final static String TOPIC = "jndi.testTopic";
    private TopicConnectionFactory tconFactory;
    private TopicConnection tcon;
    private TopicSession tsession;
    private TopicSubscriber tsubscriber;
    private Topic topic;
    private boolean quit = false;
    public void onMessage(Message msg) {
        try {
            String msgText;
            if (msg instanceof TextMessage) {
                msgText = ((TextMessage)msg).getText();
            } else {
                msgText = msg.toString();
            System.out.println("JMS Message Received: " + msgText);
            if (msgText.equalsIgnoreCase("quit")) {
                synchronized (this) {
                    quit = true;
                    this.notifyAll();
        } catch (JMSException jmse) {
            jmse.printStackTrace();
    public void init(Context ctx, String topicName) throws NamingException,
                                                           JMSException {
        tconFactory = (TopicConnectionFactory)ctx.lookup(JMS_FACTORY);
        tcon = tconFactory.createTopicConnection();
        tsession = tcon.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
        topic = (Topic)ctx.lookup(topicName);
        tsubscriber = tsession.createSubscriber(topic);
        tsubscriber.setMessageListener(this);
        tcon.start();
    public void close() throws JMSException {
        tsubscriber.close();
        tsession.close();
        tcon.close();
    public static void main(String[] args) throws Exception {
        InitialContext ic = getInitialContext("t3://127.0.0.1:7001");
        TopicReceive tr = new TopicReceive();
        tr.init(ic, TOPIC);
        System.out.println("JMS Ready To Receive Messages (To quit, send a \"quit\" message).");
        synchronized (tr) {
            while (!tr.quit) {
                try {
                    tr.wait();
                } catch (InterruptedException ie) {
        tr.close();
    private static InitialContext getInitialContext(String url) throws NamingException {
        Hashtable env = new Hashtable();
        env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
        env.put(Context.PROVIDER_URL, url);
        env.put("weblogic.jndi.createIntermediateContexts", "true");
        return new InitialContext(env);
It's OK and shows messages When I send message to the Topic
Now I want know why the Message Driven Bean doesn't work for those Topic
I want create a Message Driven Bean for Topic in the same way I created for Queue
I don't know what is problem , please advice me
Thanks

Could you try adding a activationconfig to the message-driven bean, for example,
@MessageDriven(mappedName = "jndi.testTopic", activationConfig = {
        @ActivationConfigProperty(propertyName = "destinationName", propertyValue = "jndi.testTopic"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic")
public class aliJMS1_MessageDrivenEJBBean implements MessageListener {
    public void onMessage(Message message) {
      if(message instanceof TextMessage ){
        TextMessage txtM=(TextMessage) message;
        try{
          System.out.println(txtM.getText());
        }catch(Exception ex){
          ex.printStackTrace();
}

Message not deleting from Topic after successfully dequeue

Hi All,
Help please..
I need to design a process where message have to produce into a AQ JMS topic and later i have to consume the message from the same topic and publish to a Queue.
In order to move on this i have created a sample My_Topic1 and My_Queue1 with below syntax
Topic:-
EXEC dbms_aqadm.create_queue_table (queue_table=>'MY_Topic1', queue_payload_type=>'sys.aq$_jms_text_message', multiple_consumers=>true );
EXEC dbms_aqadm.create_queue(queue_name=>'MY_Topic1', queue_table=>'MY_Topic1');
EXEC dbms_aqadm.start_queue(queue_name=>'MY_Topic1');
Queue:-
EXEC dbms_aqadm.create_queue_table (queue_table=>'My_Queue1', queue_payload_type=>'sys.aq$_jms_text_message', multiple_consumers=>false);
EXEC dbms_aqadm.create_queue(queue_name=>'My_Queue1', queue_table=>'My_Queue1');
EXEC dbms_aqadm.start_queue(queue_name=>'My_Queue1');
Now i created Foreign server and create local and destination topic of queue.topics name and also created Data source of XAType.
Now my bpel process getting a message(which as one element of sting type) from a web service and i am producing the same message to Topic. Once the message published to topic in a separate composite my JMS Adaptor dequeue/Consume the message from the topic and subscribe it to queue.
The Above scenario working as expected but here what my observation on this
1)When i dequeue message from a topic using bpel process successfully i am able to subscribe the message to queue but the message still remain in the topic i think it suppose to get of the topic once successfully dequeued.
Even i check the subscriber topic table and one subscriber is listening to the topic.
2)If in case any error generated at the time of subscribing to the queue the message should rollback( because i am using XA Transaction) but i think it is not happening as i can see in my topic view aq$my_topic1 MGS_STATE changed to PROCESSED.
Can some one please let me know where i am going wrong.
Thanks in advance.
Regards,
Tarak.
Edited by: Tarak on Sep 9, 2012 8:47 PM

The behavior should be the process consume a message from the topic and will try to do its job. If this process fail, {code]
But in this message not there in topic even it is failed in soa process.....i am very much interested how this XA is working that the reason i am trying all this.What to do with a failed/expired message is usually configurable, but doesn't make sense to place it in the same topic again... If the messages are failing too quickly better to adjust the max_retries and retry_delay...I agress in real senario we will move to error queue. But in that case also some how we need to read the message from queue and publish to the end system.
I am just trying to understand the behavior and what i came to know is after all the retire fails message not going to topictable _E. But when i pass Expire time property or time to live then it is moving to error table.What do you mean? What server was restarted, the database or the soa server? Messages that still didn't reach the max retry number will still be retried...Wheni am bouncing my managed server soa_server1 i can see the invoke activity is trying to publish the message into queue... this is happens after server restart and suppose not to happen....
But thanks alot for the inputs...
Regards,
Tarak.

Can I create a new Queue/Topic in client application?

In sun's JMS turorial the application client sends messages to the queue, which is created administratively, using the j2eeadmin command. Can I create a new destination(queue or topic) in my client's code?
Thanks very much.

Thank you very much, flhood. This is my first time to gain aid from website except my school's BBS.
But I still cann't solve the problem, here is my code, can you help me to check it if there is anywhere that I might do wrong?( I omit the try/catch part)
QueueConnectionFactory queueConnectionFactory =null;
QueueConnection queueConnection =null;
QueueSession queueSession =null;
Queue queue =null;
Queue tempQueue =null;
QueueSender queueSender =null;
TextMessage message =null;
final int NUM_MSGS;
Context jndiContext =null;
jndiContext =new InitialContext();
queueConnectionFactory =(QueueConnectionFactory)jndiContext.lookup("QueueConnectionFactory");
queueConnection =queueConnectionFactory.createQueueConnection();
queueSession =queueConnection.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
queueConnection.start();
queue =queueSession.createQueue("MyQueue");
tempQueue =queueSession.createTemporaryQueue();(Actually I don't know why I shall need a tempQueue if I have the queue.)
queueSender =queueSession.createSender(queue);
message =queueSession.createTextMessage();
NUM_MSGS=10;
for (int i =0;i <NUM_MSGS;i++){
message.setText("This is message "+(i +1));
System.out.println("Sending message:"+message.getText());
queueSender.send(message);
These codes run well if I lookup in the JNDI for the existing queue "MyQueue", but when I try to make it dynamically, the resutlt shows(I only use texteditor+j2sdk1.4+j2ee1.3.1):
Java(TM) Message Service 1.0.2 Reference Implementation (build b14)
Sending message:This is message 1
Exception occurred:javax.jms.InvalidDestinationException: No Destination found f
or name: MyQueue
I use deloytool to check the destionation, of course the "MyQueue" hasn't been created, but I use try/catch to brace these two line:
queue =queueSession.createQueue("MyQueue");
queueSender =queueSession.createSender(queue);
Nothing gain.
They are really puzzling me!

How to make message transfer to a topic from a business service synchrouns?

hi,
I am posting a message to a JMS queue using a business service (say A) and then I am fetching that message from that queue and using a proxy service (B) and a business service (C) for transferring that message to a topic, now I want that my business service A gets the same message that it initially posted as a response back from the topic to make the whole message transfer synchronous, but the problem is that as I select topic on my JMS transport configuration page of business service the text box where I need to specify the URI for the topic gets blocked,hence I am unable to get a response from the topic, can anybody help me out with this as I really want to make this synchronous.
Edited by: user12826319 on Jul 21, 2010 4:36 AM

yes u got it correct...v require a synchronous message transfer to happen i believe d alternative can be that i send the message to topic directly using a business service and expect a response from the topic itself in the form of the message i initially posted, that thing I would manage but the real problem is to get a response to the business service when i use topic, because as i select topic on JMS transport configuration page of business service the end point URI textbox gets blocked...

How to view messages in Jms queue from OEM 12c Cloud Control

Hi All,
How can I view messages in a Jms queue from OEM 12c Cloud Control without logging into WebLogic Administration Console?
Thanks in Advance!!

EMCC 12c gets down to the JMS message queue/topic level in regards to the metrics being collected. It doesn't provide a view into the actual messages themselves. Are you trying to capture/track messages with a particular payload?

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".

How to configure appli specific Queue & Topics in destinations-service.xml

Hello All,
I am trying to configure JBoss Messaging 1.4.5GA in JBoss-4.3.0 (Enterprie Edition).
I am Configuring my application specific Queue and Topics in destinations-service.xml , but Queue is not getting register in jboss.
I am getting following error in jboss :
[ServiceConfigurator] Problem configuring service jboss.messaging.destination:service=Queue,name=jms/servers/logmon/MonitorInQueue
org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@1e32382 on mbean jboss.messaging.destination:service=Queue,name=jms/servers/logmon/MonitorInQueue; - nested throwable: (javax.management.AttributeNotFoundException: not found: DestinationManager)
at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:698)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:380)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
My destinations-service.xml is unsder "jboss-4.3.0\server\MySiteServer\deploy\jboss-messaging.sar" , not in deploy directory of jboss.
Is it right plcae to configure destination queue and topics ??
My destinations-service.xml is like given below :
<?xml version="1.0" encoding="UTF-8"?>
<server>
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=jms/servers/logmon/MonitorInQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml"> ( what is this line for ??)
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<depends optional-attribute-name="DestinationManager">jboss.messaging:service=DestinationManager</depends>
<depends optional-attribute-name="SecurityManager">jboss.messaging:service=SecurityManager</depends>
<attribute name="SecurityConf">
<security>
<role name="guest" read="true" write="true"/>
<role name="publisher" read="true" write="true" create="false"/>
<role name="noacc" read="false" write="false" create="false"/>
</security>
</attribute>
</mbean>
</server>
Please help me in configuring DestinationManager and SecurityManager also !!!
You can view attached destinations-service.xml.
Thanks in advance for your efforts to resolve my problem, Thanks !!!
Regards,
Rahul Aahir
mailme :[email protected]
Attachments:
destinations-service.xml (20.2 K)
Edited by: Rahul_Aahir9885 on Sep 16, 2010 9:31 AM

Unless there happen to be any JBoss experts reading this, you may have more success asking your question in a JBoss-specific forum.

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

Publishing message to JMS Queue on Weblogic from OSB proxy service

Hi,
1. I have created a JMS module: testModule and a JMS queue: testQueue in the weblogic admin console.
2. Created a business service with the above queue as endpoint.
3. Created a proxy service which publishes the message to the queue using the business service. I have used Publish activity to publish the message to the business service.
When i run the proxy service with the request message, then, no error is coming but, in the admin console when i click on JMS module->testModule->testQueue->Monitoring tab, i see nothing. There are no entries in the table so, how can i check if the message is properly published to the queue or not.
The queue is not listened by any service for consuming the messages.
Kindly help me in figuring out this issue.
Thanks in advance.

If the destination was a topic, the behavior would be expected. Messages only stays on a topic and are delivered to consumers if there are consumers or durable subscribers.
Did you check the server logs and see if there are any exceptions or warnings?
You can also turn on jms debugging by adding the following to your server startup script.
-Dweblogic.debug.DebugJMSFrontEnd=true
-Dweblogic.debug.DebugJMSBackEnd=true
The debugging messages wiill show up in the server log.

Removing superseded messages from the queue

Does JSMQ provide any way for a producer to remove a message from the queue which it queued some time ago but which it no longer wishes to send?
I am investigating the use of JSMQ in a military battlemap application connecting nodes over low bandwidth/unreliable connections. The reason we want to be able to remove messages is as follows: Say a producer sends a low priority message to the queue regarding a unit's position. Later on the same producer sends an update regarding the same unit to the queue. If the first message is still present in the queue (ie has not been sent yet) then we want the producer to be able to remove it as it is now superseded by the new message and we don't want to waste bandwidth sending the old message first.
I know we can set an expiry time on messages, but this doesn't really solve our problem. We want the original message to stay in the queue indefinately (until it is read by the consumer) unless it is superseded by a new message in which case we want to remove it.
Thanks
Roger

Hi Roger,
JMS does not support the removal of messages from a queue
as you described. I can't think of a way to not deliver the old
message once it was already sent.
Alternatives I can think of:
- Adjust the interval at which the consumer reads the messages
off the queue and/or the number of messages that are read;
so that the consumer will see the old and new messages
and can decide which one to use. This does not address the
bandwidth issue but allows the consumer to behave smarter.
- Similar to above, but on the producer side. The producer waits
for some interval before sending a message, in case an
updated position of a unit arrives at the producer. This might not
be good if a consumer needs to know the location of a unit as
soon as it is available.
- Use a topic instead of a queue. When using queues, old
messages (containing old positions) sent to a queue are kept
until the consumer reads it. With topics, if no consumers are
around, the message is tossed. However, if you really need old
messages to lie around (e.g. need to know last position of
unit), this won't suit your needs.
Sorry I don't have a straight answer for you, hope this helps
somewhat.
-i
http://wwws.sun.com/software/products/message_queue/index.html

Receiving messages from Service Bus Topics in node js without polling

Hi, I have node js client who subscribed to a Topic, currently I'm using a timer to invoke receiveSubscriptionMessage every few seconds to get messages from the Topic.
Is there a way to do this without polling?
Thanks.

You can implement message pump by OnMessage which will do the poll for you. Please read "How to receive messages from a queue" part from
http://azure.microsoft.com/en-us/documentation/articles/service-bus-dotnet-how-to-use-queues/

Messages in a Queue/Topic

Similar Messages

Maybe you are looking for