Program to consume the JMS queue

Hi, I' m new to WebLogic stuff. Got a question over here. There's a JMS queue that we want to have a program (not those built in stuff from weblogic) to see if they re consumed. Similar stuff would be displayed like
 ABCD Queue consumers: 1 / consumers high: 0 ...messages: 10 / messages received: 19........
 as if we get into the console page to check the JMS queues.
 I've got no clues yet. We don't wanna check the number of files from C:\Original and the destination folder C:\Destin......if so, it'd be an easy task but that s not what we wanted....

As with any WebLogic subsystem, you can get all statistics programmatically using standard JMX mbeans (see the JMX developer guide). The console uses these beans, as does the WLST scripting language. In addition, there are helper methods in the public weblogic.jms.extensions package that simplify access to these beans.
I think there are various mbean and WLST samples on dev2dev, including one called "JMSStats.java". Note that JMSStats.java, and some other samples were written for versions 8.1 and earlier. They use deprecated methods that don't have access to all runtime statistics for 9.0 and later versions.
Tom

Similar Messages

Exception in the XML consuming from JMS Queue

In the CEP application we have a business flow like we want to consume an xml message from the JMS queue.
While CEP is consuming the message sometimes we are getting an exception.
But this issue occurs rarely and we have no idea about the root cause.
I am attaching the trace of this exception.
It seems this exception is from weblogic server itself.
Also this could be an interface problem, since its showing a casting error.
The Bug description:
When we send a meter event through SOAP UI in the CEP visualizer when the event is consumed CEP also shows this exception.
This may not halt the analysis process of the event, but this unwanted piece of code/lines have to be avoided.
<OutageEvent xmlns:ns1="http://www.accenture.com/INDE"; xmlns:wsa="http://www.w3.org/2005/08/addressing"; xmlns="http://www.accenture.com/INDE"><meterId xmlns="">203</meterId><outageType xmlns="">Permanent Outage</outageType><premiseId xmlns="">1111</premiseId><timeEvent xmlns="">2010-07-30T</timeEvent><heName xmlns="">SAMPLEHE</heName></OutageEvent>
<Jul 30, 2010 11:01:50 AM IST> <Error> <JMSAdapter> <BEA-2041118> <Setup for JMS task for destination JMS_OI_MeterState_MeterEvent_Queue at provider t3://10.212.182.30:8002 failed with exception: weblogic.jms.common.JMSException: [JMSClientExceptions:055039]A system error has occurred. The error is java.lang.ClassCastException: weblogic.workarea.StringWorkContext
weblogic.jms.common.JMSException: [JMSClientExceptions:055039]A system error has occurred. The error is java.lang.ClassCastException: weblogic.workarea.StringWorkContext
at weblogic.jms.client.JMSSession.handleException(JMSSession.java:3121)
at weblogic.jms.client.JMSConsumer.receiveInternal(JMSConsumer.java:650)
at weblogic.jms.client.JMSConsumer.receive(JMSConsumer.java:526)
at weblogic.jms.client.WLConsumerImpl.receive(WLConsumerImpl.java:184)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveMessage(AbstractPollingMessageListenerContainer.java:405)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:308)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:261)
at com.bea.core.asyncbeans.internal.DefaultMessageListenerContainer.receiveAndExecute(DefaultMessageListenerContainer.java:59)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:982)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:974)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:876)
at com.bea.core.asyncbeans.internal.WorkManagerTaskExecutor$1.run(WorkManagerTaskExecutor.java:38)
at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.ClassCastException: weblogic.workarea.StringWorkContext
at weblogic.rjvm.MsgAbbrevInputStream.readContext(MsgAbbrevInputStream.java:243)
at weblogic.workarea.spi.WorkContextEntryImpl.<init>(WorkContextEntryImpl.java:47)
at weblogic.workarea.spi.WorkContextEntryImpl.readEntry(WorkContextEntryImpl.java:97)
at weblogic.workarea.WorkContextLocalMap.receiveRequest(WorkContextLocalMap.java:151)
at weblogic.jms.common.JMSWorkContextHelper.readWorkContext(JMSWorkContextHelper.java:89)
at weblogic.jms.common.MessageImpl.readExternal(MessageImpl.java:2275)
at weblogic.jms.common.TextMessageImpl.readExternal(TextMessageImpl.java:354)
at weblogic.jms.common.JMSConsumerReceiveResponse.readExternal(JMSConsumerReceiveResponse.java:133)
at weblogic.messaging.dispatcher.DispatcherObjectHandler.readResponse(DispatcherObjectHandler.java:154)
at weblogic.messaging.dispatcher.DispatcherProxy.unmarshalResponse(DispatcherProxy.java:269)
at weblogic.messaging.dispatcher.DispatcherProxy.dispatchSyncTranFuture(DispatcherProxy.java:134)
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:338)
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:386)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
at weblogic.jms.client.JMSSession.receiveMessage(JMSSession.java:886)
at weblogic.jms.client.JMSConsumer.receiveInternal(JMSConsumer.java:647)
at weblogic.jms.client.JMSConsumer.receive(JMSConsumer.java:526)
at weblogic.jms.client.WLConsumerImpl.receive(WLConsumerImpl.java:184)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveMessage(AbstractPollingMessageListenerContainer.java:405)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:308)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:261)
at com.bea.core.asyncbeans.internal.DefaultMessageListenerContainer.receiveAndExecute(DefaultMessageListenerContainer.java:59)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:982)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:974)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:876)
at com.bea.core.asyncbeans.internal.WorkManagerTaskExecutor$1.run(WorkManagerTaskExecutor.java:38)
at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
11:01:50,548 INFO MeterInputConverter : 81 - Accepted the input xml :<?xml version="1.0" encoding="UTF-8" ?><MeterEvent xmlns:inde="http://www.accenture.com/INDE"; xmlns:wsa="http://www.w3.org/2005/08/addressing"; xmlns="http://www.accenture.com/INDE">;
<meterId xmlns="">103</meterId>
<outageType xmlns="">RESUME</outageType>
<premiseId xmlns="">1111</premiseId>
<timeEvent xmlns="">2010-07-30T</timeEvent>
<lastGasp xmlns="">false</lastGasp>
<heName xmlns="">CURRENT</heName>
</MeterEvent>

Hi,
I will forward this to the weblogic JMS team, to see if they have any insight for us.
Regards,
Seth

How to keep a back up of messages from the JMS queues?

Hi,
I need to keep a back up of messages which are coming in the JMS queue before they get consumed. This is for recovery purpose.
I checked file store option but it doesnt have any time stamp on messages so dont know how to trace back messges if needed from file store.
Please let me know if you guys have any idea to handle this.
Thanks in advance
Bips

No. Not with Time Machine at least.
If you tell Time Machine to backup the external then you will have it.
Or you can manually copy it to another disk for storage outside of Time Capsule/TimeMachine.
Allan

Checking message in the JMS queue

Hi there,
Is there a way to check the message is in the JMS queue? I tried to use the QueueBrowser. However, it always return me an enumeration = null
when I run the following "QueueBrowser.getEnumeration()". I am using JRun 3.0 application server.
And by the way, how would to know whether the message has been consumed by the receiver in a point to point model? We could still managed to send out messages even when the receiver client is not started. I understand that the receiver client would be able to receive those messages once they are started as the messages are in the queue. However, what if the queue is destroyed (some catastrophic event happen to the JMS provider) before the receiver client is started?

I have no problem using the QueueBrowser:
      QueueConnection qc;
      qc = qcf.createQueueConnection();
      QueueSession session;
      session = qc.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
      QueueBrowser browser = session.createBrowser(queue);
      Enumeration enum = browser.getEnumeration();The used JMS provider must support a persistence mode. When the server is restarted and there were messages in the queue, they are restored.
When receiving messages you can use autoacknowledge mode without transaction which means when receive() is called, the message is deleted from the queue. In transacted mode in addition to receive() you have to call commit() on the session in order to delete the message in the queue.
When using clientacknowledge you have to call message.acknowlegde() after receive().

How to read the messages in the JMS Queue using JMX

Hi,
          I want to read messages in the JMS queue using JMX. I was able to read using QueueBrowser but want to modify priority of the messages using JMX.
          I tried to use JMSDestinationRuntimeMBean but it does not allow us to read messages unless we pass the message Id. Is there any way that I can get all the messages in the queue.
          I am using Weblogic 8.1 SP4
          Can someone please help me in this regard.
          Thanks,
          Kiran.
          Edited by KGudipati at 10/22/2007 1:22 AM

Hi,
As far as i know, JMS Object Messages is not supported by XI JMS adapter.
you need to have the JMS provider to transform the message to bytes messages.
(Refer to SAP note 856346)

How to check the jms Queue is persistance or not in jboss application serve

hi,
i am using jboss as application server for jms and database is postgres.For an message store i am using the "*database store*".while starting the jms adding queue it is adding the messages to the jms queue after starting the jms receiver the datas are received sucessfully....afte some 10 to 13 hours i am getting java.lang.OutOfMemoryError in jms..so i checked the postgres table space.Table space is increased gradually...I think that the after receiver received that message the messages are not deleted in the database.how to debugg the the secnario in jboss as wel as in database.....how to chaeck the queue is in persistance or not persistance...
regards.
naresh govindaswamy.

Send a request to the server somehow, so that the server is aware of this. AJAX may be very useful in this if you want to do this asynchronously.
its very urgently This is irrelevant information. That's your problem. We don't care less or more. Some users here will even refuse to help you if you're putting pressure.

Consuming a jms queue from a multithread application

Hi
Thank you for reading my post.
I have an application which shuld consume message of a queue.
my application is multithread and what i want to know is:
- How i can ask queue to remove a message after my thread finished its work with the message, by this way i can ensure that if my thread face an exception after it read the message my message will not lose.
- As it is multithread application, How i can ensure that a message is not delivered to two or more thread? is there any way to consume the messages in a synchronized way?
Will synchronized access restrict the performance?
Thanks

This is running in a J2DK environment. For my thread pool, I just copied one from a Sun tutorial on multi-threading then modified it. I creaed a seperate package with three classes. Here is my thread pooling package. I basically use a Vector to hold threads when they are not working. And you can set a limit as to the max number of active threads.
package threadpooling;
* @author cferris
* This class is simple to wrap the runnable
* thread for the worker thread around other
* needed parameters like salon id and source.
public class TaskWrapper {
// Define the needed instance fields.
public Runnable taskAtHand = null;
public String taskType = "";
 // Overloaded constructor.
 public TaskWrapper(Runnable task) {
 // Just set the runnable
 taskAtHand = task;
 taskType = "WorkerThread";
 } // of overloaded contructor
 // Overloaded constructor.
 public TaskWrapper(Runnable task, String taskType) {
 // Just set the instance fields
 taskAtHand = task;
 this.taskType = taskType;
 } // of overloaded contructor
package threadpooling;
* @author cferris
* This class is for tracking the number of
* active threads so we don't go over the set
* limit. This class basically synchronizes
* the methods that update the active thread
* counter.
import java.util.*;
public class ThreadPool {
// Define the instance fields.
// First define instance fields for the
// management of the thread pools - pm.
protected Vector poolOfThreads = new Vector();
private static LinkedList taskQueue = new LinkedList();
private static int poolSize = 0;
private static boolean pmAvailable = true;
private static boolean daemon = false;
public static boolean shutDown = false;
// Instance field for the management of
// the threads - tm.
private static int activeThreads = 0;
private static int maxReached = 0;
private static int numTimesReached = 0;
private static boolean tmAvailable = true;
// Define constants
private static final int MAX_LIMIT_DEFAULT = 32;
 // The constructor.
 public ThreadPool() {
 this(MAX_LIMIT_DEFAULT, false);
 } // of constructor
 // Overload the constructor with max number of active jobs.
 public ThreadPool(int poolSize, boolean daemon) {
 this.poolSize = poolSize;
 this.daemon = daemon;
 poolOfThreads = new Vector();
 taskQueue = new LinkedList();
 salonTracker = new Vector();
 // Load up and initialize the threads.
 for (int i=0; i < poolSize; i++) {
 Thread thread = new WorkerThread(this, i);
 thread.setDaemon(daemon);
 thread.start();
 poolOfThreads.add(thread);
 } // of overloaded constructor
 // Overload this method to allow just the runnable task.
 public void assignWork(Runnable work) {
 // Create the wrapper
 TaskWrapper wrapper = new TaskWrapper(work, "A task");
 assignWork(wrapper);
 } // of overloaded assignWork
 // Push a unit of work (work thread) on the the worker thread.
 public synchronized void assignWork(TaskWrapper work) {
 // First increament the active thread count.
 increment();
 // Wait until we can access the linked list
 try {
 if (!pmAvailable)
 wait();
 } catch(InterruptedException e) { }
 pmAvailable = false;
 notifyAll();
 taskQueue.addLast(work);
 pmAvailable = true;
 notifyAll();
 } // of assignWork
 // Get the next unit of work (work thread).
 public synchronized TaskWrapper getNextWorkAssignment() {
 // Wait until we can access the linked list
 try {
 if (!pmAvailable)
 wait();
 } catch(InterruptedException e) { }
 pmAvailable = false;
 notifyAll();
 TaskWrapper nextTask;
 if (!taskQueue.isEmpty())
 nextTask = (TaskWrapper)taskQueue.removeFirst();
 else
 nextTask = null;
 pmAvailable = true;
 notifyAll();
 return nextTask;
 } // of getNextWorkAssignment
 // Return the number of tasks waiting on the work queue.
 public synchronized int workWaiting() {
 // Wait until we can access the linked list
 try {
 if (!pmAvailable)
 wait();
 } catch(InterruptedException e) { }
 pmAvailable = false;
 notifyAll();
 int qSize = taskQueue.size();
 pmAvailable = true;
 notifyAll();
 return qSize;
 } // of workWaiting
 // Wait until all the tasks have been completed.
 public void waitForCompletion() {
 int prev = 0;
 // Continue checking untill all the threads have
 // completed and been removed.
 while(!poolOfThreads.isEmpty()) {
 // Lets record the difference
 if (poolOfThreads.size() != prev) {
 System.out.println("waiting for " + poolOfThreads.size() + " to complete");
 prev = poolOfThreads.size();
 // Loop through the thread pool and check each thread.
 for (int t = 0; t < poolOfThreads.size(); t++)
 if (!((WorkerThread)poolOfThreads.get(t)).working)
 // This thead is done so remove it.
 poolOfThreads.remove(t);
 } // of while
 } // waitForCompletion
 // Set the max number of allow threads.
 public synchronized void setPoolSize(int newLimit) {
 // just set the limit.
 // Check if available
 while (!tmAvailable) {
 try {
 wait();
 catch(InterruptedException ie) {
 System.exit(5);
 // Ok, lock the object while we update it.
 tmAvailable = false;
 notifyAll();
 poolSize = newLimit;
 // Reset the max counters/trackers too
 maxReached = 0;
 numTimesReached = 0;
 // Create additional threads in the pool if needed
 if (poolSize > poolOfThreads.size())
 // Load up and initialize the threads.
 for (int i = poolOfThreads.size(); i < poolSize; i++) {
 Thread thread = new WorkerThread(this, i);
 thread.start();
 poolOfThreads.add(thread);
 // Done, now release the object.
 tmAvailable = true;
 notifyAll();
 } // of setPoolSize.
 // The method to increment thread counter.
 private synchronized void increment() {
 // Check if available
 while (!tmAvailable) {
 try {
 wait();
 catch(InterruptedException ie) {
 // logger.fatal("Synchronized error in ThreadPool ");
 // logger.fatal("Error message is: " + ie.getMessage());
 System.exit(5);
 // Ok, lock the object while we update it.
 tmAvailable = false;
 notifyAll();
 activeThreads++;
 // Check if this is the highest number of threads
 // that has been active, if not then set so.
 if (activeThreads > maxReached)
 maxReached = activeThreads;
 if (activeThreads == poolSize)
 numTimesReached++;
 // Done, now release the object.
 tmAvailable = true;
 notifyAll();
 } // of increment
 // The method to increment thread counter.
 public synchronized void decrement() {
 // Check if available
 while (!tmAvailable) {
 try {
 wait();
 catch(InterruptedException ie) {
 // logger.fatal("Synchronized error in ThreadPool ");
 // logger.fatal("Error message is: " + ie.getMessage());
 System.exit(5);
 // Ok, lock the object while we update it.
 tmAvailable = false;
 notifyAll();
 activeThreads--;
 // Done, now release the object.
 tmAvailable = true;
 notifyAll();
 } // of decrement
 // A method to determine if the maximum number of active
 // threads has been reached.
 public synchronized boolean limitNotReached() {
 boolean limit = false;
 // Check if available
 while (!tmAvailable) {
 try {
 wait();
 catch(InterruptedException ie) {
 // logger.fatal("Synchronized error in ThreadPool.");
 // logger.fatal("Error message is: " + ie.getMessage());
 System.exit(5);
 // Ok, lock the object while we update it.
 tmAvailable = false;
 notifyAll();
 if (activeThreads < poolSize)
 limit = true;
 // Done, now release the object.
 tmAvailable = true;
 notifyAll();
 return limit;
 } // of limitNotReached
 // A method to return the number of active threads.
 public synchronized int currentNum() {
 // Check if available
 while (!tmAvailable) {
 try {
 wait();
 catch(InterruptedException ie) {
 // logger.fatal("Synchronized error in ThreadPool");
 // logger.fatal("Error message is: " + ie.getMessage());
 System.exit(5);
 // Ok, lock the object while we update it.
 tmAvailable = false;
 notifyAll();
 int numberOf = activeThreads;
 // Done, now release the object.
 tmAvailable = true;
 notifyAll();
 return numberOf;
 } // of currentNum
package threadpooling;
* @author cferris
* This is the work thread that receives the
* taskes or unit of work that make up the
* thread pool.
public class WorkerThread extends Thread {
// Define need instance fields.
public boolean working = true;
public int id = 0;
private int pauseFactor = 1;
// The thread pool that this object belongs to.
public ThreadPool owner;
// Define the constructor for the seperate thread.
public WorkerThread(ThreadPool pooler, int id) {
 owner = pooler;
 this.id = id;
} // of contructor
// Wait for work or for system shutdown.
public void run() {
 // Define the work object.
 TaskWrapper unitOfWork = null;
 // Wait for work or until system is shutting down.
 do {
 unitOfWork = owner.getNextWorkAssignment();
 if (unitOfWork != null) {
 // First set name and then add salon to watch list.
 String taskName = unitOfWork.taskType + "-" + id;
 setName(taskName);
 // System.out.println("Starting thread - " + getName());
 unitOfWork.taskAtHand.run();
 // Done, now adjust tracker and reset the pause factor.
 owner.decrement();
 pauseFactor = 1;
 else {
 // No work so pause a bit
 try {
 sleep(150 * pauseFactor);
 } catch (InterruptedException e) { }
 // If consecutively pausing because of no work then
 // increase the pause time up to a point.
 if (pauseFactor < 49)
 pauseFactor++;
 } while (!owner.shutDown);
 // Set indicator this thread in the pool is done.
 working = false;
} // of run
}To use the thread pool just create a static instance of the ThreadPool in your main class
private static ThreadPool threadPool = new ThreadPool(getMaxThreads(), useDaemon());Then to launch a new thread use this.
 if (runOnSeperateThread()) {
 WriteTransThread task = new WriteTransThread(messasge);
 // Add to the thread pool.
 threadPool.assignWork(new TaskWrapper(task, "my thread"));
private boolean runOnSeperateThread() {
 // First check if mutli threading is turned on
 // and if there are open threads.
 if (multiThreadingOn && threadPool.limitNotReached())
 // Yes, there are open threads.
 return true;
 // Check if we can wait for an open thread.
 if (!multiThreadingOn || !waitForOpenThread)
 // No multi threading or waiting allowed.
 return false;
 // OK, wait for an open thread, wait for up
 // to 90 seconds.
 int j = 0;
 do {
 try {
 // Wait 1/2 a second.
 Thread.sleep(500);
 } catch(InterruptedException ignore) { };
 // Check again for an optn thread.
 if (threadPool.limitNotReached())
 // Ok to run on separate thread.
 return true;
 // Increament counter and wait again.
 j++;
 } while(j < 180);
 // If we got this far then we've waited long enough.
 logger.warn("Reached limit on waiting for an open thread in the pool");
 return false;
} // of runOnSeperateThreadThe WriteTransThread is a class that will extract the message body and write out its data to a table.
Last, before you end your program make sure all the threads have competed by calling the following.
// If multi-threading is activated then this method will
// wait for them to complete before returning. The
// max wait time is 300 secs or 5 minutes.
private void waitForThreadsToComplete(String message) {
 // First check for multi threading.
 if (prop.useMultiThread() && (threadPool.currentNum() > 0)) {
 int limit = 0;
 // Some threads are still active, wait
 logger.info("Waiting for threads to complete before " + message
 + " current thread count is " + threadPool.currentNum());
 do {
 limit++;
 try {
 Thread.sleep(500); // Sleep 1/2 a sec.
 } catch(InterruptedException ie) { } // Ignore the error for now.
 // Max waith is 300 sec or 5 min.
 } while ((threadPool.currentNum() > 0) && (limit < 600));
} // of waitForThreadsToComplete

Messages not making it to the jms queue...

We are having an interesting problem. AFter a fresh restart of our instnace, it will process a message fine. but, if we wait a few minutes, try another post, the message doesn't get put ot the queue, and it basically hangs the instance.
          I am not sure how to trouble shoot this since there are no errors sent to the logs. the console will show a stuckthread message eventually.
          I was wondering if anyone could help with what are some potential causes, and if there is anyway to get additional information out of the server. I have turned on the debug and set the level to info, but no additional information is getting generated.
          We've done print outs in the code right up to where the failure occurs.
          I"ve posted the code snippet that is being used. It failes when it gets to the code after GQ 5.
          Any help is appreicated.
          public boolean queueMessage(Serializable messageObj, String queueName)
          throws NamingException, JMSException, ResourceKeeperException, Exception {
          EventLogger.log(Level.DEBUG, "Trying to put a message in the " + queueName + " queue in GenericQueue.queueMessage(): ");
          try {
          if (messageObj != null)
          EventLogger.log(Level.DEBUG, "Serializable messageObj in GenericQueue.queueMessage(): " + messageObj.toString());
          else
          EventLogger.log(Level.DEBUG, "messageObj is not serializable");
          Hashtable ht = null;
          boolean inHash = false;
          //check to see if the queue is in the hashtable
          if (queues.containsKey(queueName)) {
          EventLogger.log(Level.DEBUG, "The Queue was in the hashTable in GenericQueue.queueMessage(): ");
          inHash = true;
          ht = (Hashtable) queues.get(queueName);
          else EventLogger.log(Level.DEBUG,"The Queue was not the hashTable using default values in GenericQueue.queueMessage(): ");
          Context ctx = InitialContext.getInitialContext();
          EventLogger.log(Level.DEBUG, "GQ 1");
          QueueConnectionFactory qconFactory = null;
          EventLogger.log(Level.DEBUG, "GQ 2");
          if (inHash)
          qconFactory = (QueueConnectionFactory) ctx.lookup((String) ht.get("jmsFactory"));
          EventLogger.log(Level.DEBUG, "GQ 3");
          else
          EventLogger.log(Level.DEBUG, "GQ 4");
          qconFactory = (QueueConnectionFactory) ctx.lookup(jmsFactory);
          EventLogger.log(Level.DEBUG, "GQ 5");
          QueueConnection qcon = qconFactory.createQueueConnection();
          EventLogger.log(Level.DEBUG, "GQ 6");
          QueueSession qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
          EventLogger.log(Level.DEBUG, "GQ 7");
          QueueSender qsender;
          EventLogger.log(Level.DEBUG, "GQ 8");
          Queue queue;
          EventLogger.log(Level.DEBUG, "GQ 9");
          queue = (Queue) ctx.lookup(queueName);

The "stuck thread" message is likely a good clue. Force a server thread dump when this occurs. Feel free to post the thread dump here.
          Side note: Make sure the "GenericQueue" method doesn't attempt to multi-thread access to any JMS session, consumer, or producer.
          Tom

How to access the JMS queues in the XI J2EE Engine?

Hi Gurus,
Can anybody know how to access the jms dead message queues in the WAS J2EE Engine?
I have read in the SAP documentation that we can use some JMS commands from the telnet. I don't know how to use those commands.
Can anybody provide a step-by-step process to access these queues?
Thanks
Kalyan

1) Open a command prompt
2) type
telnet localhost 50008
where the port is the same as your http, but with 8 as last digit.
3) Login
4) Issue the following set of commands
        jump 0
        add jms
        jms list deadmsgs
Check by man jms other possible options.
HTH
Peter

Get the JMS Queue property in BPEL

Hi,
Does anyone have idea on how to get the value of JMSXDeliveryCount which is a prorerty of JMS queue in BPEL. I want that value in the bpel flow to control the Flow on the basis of it. Plz suggest its urgent.
TIA.
Best Regards,
Amit Jain

Hi,
I have got the solution to above issue.
Once my JMS adapter picks the message, it passed the message to BPEL through mediator.
In Mediator assign, by using $in.property.jca.jms.JMSProperty.JMSXDeliveryCount I got the value.
Thanks & Regards,
Amit Jain

How to get an XMLBean off the jms queue

 Hello all,
 I think I can post an XMLBean to a JMS queue, but how to I read it off the JSM
 queue from within a MDB?
 When I cast the message from the onMessage(Message msg) event to my XMLBEan, I
 get a class cast exception.
 I want to post some form data to a MDB to kick off some processes.
 Here is the code that generates the XML bean and posts it to my jms :
 VCALENDARDocument vcaldoc = VCALENDARDocument.Factory.newInstance();
 VCALENDAR vcalendar = vcaldoc.addNewVCALENDAR();
 VEVENT vevent = vcalendar.addNewVevent();
 vcalendar.setProdid(form.getProdid());
 vcalendar.setVersion(form.getVersion());
 vevent.setDtstart(form.getDtstart());
 vevent.setDtend(form.getDtend());
 vevent.setSummary(form.getSummary());
 vevent.setOrganizer(form.getOrganizer());
 appointmentCtrl.sendAppointmentRequest(vcalendar, "12345");
 Here the code in the JMS Control:
 public interface AppointmentCtrl extends JMSControl,com.bea.control.ControlExtension
 * @jc:jms-property key="accountIdentifier" value="{accountID}"
 * @jc:jms-property key="transactionType" value="NOT SUPPORTED"
 public void sendAppointmentRequest(VCALENDAR vcalendar, String accountID);
 static final long serialVersionUID = 1L;
 Here is how I am trying to read it off the queue in my MDB:
 public void onMessage(Message msg)
 VCALENDAR vcalendar = (VCALENDAR)msg;
 System.out.println("Message received");
 System.out.println(vcalendar.getProdid());
 Here the error that i get:
 <Apr 10, 2004 2:02:16 AM CDT> <Warning> <EJB> <BEA-010065> <MessageDrivenBean
 th
 rew an Exception in onMessage(). The exception was:
 java.lang.ClassCastException.
 java.lang.ClassCastException
 at mdb.AppointmentEJB.onMessage(AppointmentEJB.java:24)
 at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
 at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.
 java:316)
 at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
 at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
 at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >
 <Apr 10, 2004 2:02:16 AM CDT> <Warning> <EJB> <BEA-010065> <MessageDrivenBean
 th
 rew an Exception in onMessage(). The exception was:
 java.lang.ClassCastException.
 java.lang.ClassCastException
 at mdb.AppointmentEJB.onMessage(AppointmentEJB.java:24)
 at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
 at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.
 java:316)
 at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
 at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
 at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >
 Any ideas what it should look like?
 Thanks,
 Marc


Hi trevenator,
If you are having issues with an iPod touch directing you to connect to iTunes, you may find the following article helpful:
If you can't update or restore your iPhone, iPad, or iPod touch
Regards,
- Brenden

MDBs in 9.1 continue to consume JMS queues even after being deleted

We have an MDB application that reads a batch message off of a JMS queue, archives it in a database, parses the batch message into individual messages and writes them onto other JMS queues to be consumed by another application. Everything was running fine in Weblogic 8.1.5. However, due to problems with XA drivers and the MSDTC(predictable SQL server crashes), we decided to upgrade to Weblogic 9.1 to take advantage of the LLR option.
 First, we had an issue where our MDBs were causing the following exception:
 ####<May 26, 2006 7:42:12 PM EDT> <Error> <JMX> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686932991> <BEA-149500> <An exception occurred while registering the MBean null.
 java.lang.IllegalArgumentException: Registered more than one instance with the same objectName : com.bea:ServerRuntime=wltest1,MessageDrivenEJBRuntime=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,Name=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,ApplicationRuntime=DataBrokerEAR1_2,Type=EJBPoolRuntime,EJBComponentRuntime=DataBrokerEJB new:[email protected] existing weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl@7db003
 at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:146)
 at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:133)
 at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:86)
 at weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$1.registered(RuntimeMBeanAgent.java:104)
 at weblogic.management.provider.internal.RegistrationManagerImpl.invokeRegistrationHandlers(RegistrationManagerImpl.java:205)
 at weblogic.management.provider.internal.RegistrationManagerImpl.register(RegistrationManagerImpl.java:85)
 at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:320)
 at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:257)
 at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:222)
 at weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl.<init>(EJBPoolRuntimeMBeanImpl.java:32)
 at weblogic.ejb.container.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:49)
 at weblogic.ejb.container.manager.MessageDrivenManager.initialize(MessageDrivenManager.java:503)
 at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:120)
 at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:146)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManager(MessageDrivenBeanInfoImpl.java:1481)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createDDMDManagers(MessageDrivenBeanInfoImpl.java:1378)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onDDMembershipChange(MessageDrivenBeanInfoImpl.java:1285)
 at weblogic.jms.common.CDS$DD2Listener.listChange(CDS.java:454)
 at weblogic.jms.common.CDSServer$DDHandlerChangeListener.statusChangeNotification(CDSServer.java:167)
 at weblogic.jms.dd.DDHandler.callListener(DDHandler.java:318)
 at weblogic.jms.dd.DDHandler.callListeners(DDHandler.java:344)
 at weblogic.jms.dd.DDHandler.run(DDHandler.java:282)
 at weblogic.jms.common.SerialScheduler.run(SerialScheduler.java:37)
 at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
 >
 ####<May 26, 2006 7:42:13 PM EDT> <Info> <EJB> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686933069> <BEA-010060> <The Message-Driven EJB: RhapsodyMDB has connected/reconnected to the JMS destination: weblogic.jms.DMB_BEAN_QUEUE.>
 
 Generally this happend after there were cluster communication issues. Multi-cast messages were lost and our MDB reconnects to the JMS queues as indicated by the below log:
 ####<May 30, 2006 5:19:06 PM EDT> <Info> <EJB> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '54' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1149023946040> <BEA-010060> <The Message-Driven EJB: DataBrokerMDB has connected/reconnected to the JMS destination: weblogic.jms.PHINMS_DMB_QUEUE.>
 ####<May 30, 2006 5:19:10 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023950228> <BEA-000112> <Removing RAPBEA3S jvmid:720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S from cluster view due to timeout.>
 ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951009> <BEA-000115> <Lost 2 multicast message(s).>
 ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951040> <BEA-000111> <Adding RAPBEA3S with ID 720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S to cluster: DMBstg_cluster view.>
 
 This would cause the queues to eventually have hundreds of consumers and cause the server to fail.
 Basically, it seems as though the MDBs that are supposed to stop continue and attempt to process, while new threads connect to the JMS queues.
 I tried undeploying our application and deleted it from the configuration. However there were consumers still on the respective queues and when I sent messages, I got an error indicating a "Class Not Found exception" due to the fact that the EJB was undeployed and deleted from the configuration, however the MDB component was not and continued to listen for messages. In 8.1.5, as soon as the application was undeployed, there were zero consumers on the JMS queues.
 I have read the posts about a soon to be released fix that would have the MDBs connect only to the queues locally and not go out the the cluster. Would this fix my issue?
 Is there something in the deployment descriptor to configure that will cause it to disconnect and now spawn so many consumers to the JMS queues?
 Why is it that the number of MDB consumers on the JMS queues stayed static in 8.1.5, but they are erratic in 9.1 even after I set our 9.1 server to use the 8.1.5 execute queue policy. Help would be much appreciated.

I recommend contacting customer support. There's a known problem with MDBs listening to distributed destinations that are local to the same cluster as the MDB, you're problem may be related (the clue is that the stack trace contains jms.dd.DDHandler.callListeners()). The problem is that the MDB connects to all physical queues in a distributed destination rather than just the local queue.
 Tom

How to delete the messages from JMS Queue

Hi,Can anybody help how to delete the messages from the JMS Queue.Thanks in advance.

You can dequeue the message using a JMS client or delete it using Weblogic Admin Console -
http://download.oracle.com/docs/cd/E17904_01/apirefs.1111/e13952/taskhelp/jms_modules/queues/ManageQueues.html
Regards,
Anuj

How to get the XML messages from JMS Queue in BPM

I have one requirement in my application.we are sending XML messages to the JMS Queue.How to get the XML messages from JMS Queue and how to Extract the details from XMl.
can you please send me the code to get the XML messages from the JMS Queue.
Thank you,

Hi,
Sure others will have some other ideas, but here's what I typically do to get the XML from a JMS queue. Inside the Global Automatic that pops the messages off the queue you'd have logic similar to this:
artifactInfoNodes as Any[]
xmlObject as Fuego.Xml.XMLObject = XMLObject()
load xmlObject using xmlText = message.textValue
. . . Once you have this, it's a matter of deciding what you want to do with the message. Most times you'll parse the XML (using XPATH statemens), set argument variables and create a work item instance.
Hope this helps,
Dan

Copying JMS Queues

I am writing Weblogic Integration(WLI) applications. When I deploy these apps I have to create some JMS queues in the server or I get warning messages in the Weblogic console. I have several Weblogic 10.3 servers that I need to deploy these WLI apps too.
I'm wondering if there is a way that I can copy the contents of the xml files that define the JMS queues from one server to another server? What files would need to be copied? I'm trying to find an easier way to create the JMS queues. Creating the queues in the console can get time consuming if you have alot of queues to create.
Any help is greatly appreciated!.....
John

Hi John,
There are multiple methods for automating WebLogic configuration, and WebLogic JMS (just like all other WebLogic subsystems), can be configured using almost any of them. Here are some:
-- On-line or off-line WLST script
-- Java program that makes JMX config mbean calls
-- If the JMS dest config is absolutely identical, then you can simply copy the JMS module XML file to the different domains, and then use the console, WLST, or JMX to modify the config.xml in order to reference it. The module's contain destination config, while the config.xml contains subdeployment, store, and JMS server config.
When working with multiple WebLogic domains, be careful to ensure that all domain names are different and all WebLogic server names are different (even if the WebLogic servers are in different domains). In addition, in certain cases all JMS server names must be different (even if they are in different domains -- applies to SAF feature apps that use cross-domain reply-to if I recall correctly).
Tom
PS. See also [ JMS Configuration Best Practices | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13738/best_practice.htm#CACJCGHG ]

Program to consume the JMS queue

Similar Messages

Maybe you are looking for