Exception!!!!! in JMS
Hi,
I am getting the following Error While sending msg to queue :
[20/Feb/2008:11:46:08 IST] WARNING [B2009]: Creation of consumer from connectio
n [email protected]:4529 on destination REQUEST_QUEUE failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: [B4182]: Consumer can not
be added to destination REQUEST_QUEUE [Queue], limit of 1 consumers would be exc
eeded
If anyone has a solution for it plz do let us know as soon as possible
Thanx
Hi,
It might be because you're using Sun Application Server Personal Edition 8.*. It does not allow multiple consumption, and that was a problem I had when I used that application server. If you're not using this AS, it might be either the limitation of your application server or the fact that connectionfactory set to accept creation of a new queue from a specific user rather than queue.
Similar Messages
-
How to notify the exceptions in JMS sychronous request-response processing?
Hi All,
Pl. help me with ur expertise in the foll. scenario we are facing.
Scenario:
I have a requirement where I need to notify the exceptions to my client while
the client request's are processed asynchronously and my client is waiting in
synchronous for the response.
The client is sending a message to one queue (QueueA) and waiting for response
in another queue (QueueB). The message from "QueueA" is picked up by a MDB listening
to "QueueA" and it throws an exception while processing some "business logic".
In this case how do I notify to my client who is waiting in another queue. i.e.
"QueueB" that there is an exception occurred while processing the business logic.
I am using JMSCorrelationID to uniquely identify a response for a request sent
by the client.
What are the possible options to handle exceptions in JMS for an implementation
like the one mentioned above.
Any comments/feedback/pointers will be REALLY REALLY appreciated.
Tks and regds
C R Baradwaj
Raghuram Bharadwaj C wrote:
> Tom,
>
> Once again thanks a lot for your prompt response!
>
> Yes, A Knows how many downstream queues are involved.
>
> For unanticipated multiple responses
>
> If I do a select for update in all the MDB's listening to "QueueB/QueueC/QueueD",
> only one response message will be sent to the "ResponseQ".
Does this run the risk of serializing the database access? If
B/C/D have no messages so that a new operation causes all
three to fire at once, will they end up serializing on their
respective selectForUpdate calls, losing parallelism?
>
> The response from all the datasource(s) are updated in the database by the MDB.
> The MDB which updates the database last will consolidate all the response(s) and
> send one final response to the "ResponseQ".
>
> This will be picked up the client who is waiting in the "ResponseQ". There wont
> be multiple message(s) placed in the "ResponseQ".
>
> In this situation, How do I handle exceptions that occur in downstream MDB's?
Use multiple responses. MDB's send error message on response.
Or have failing MDB put an error message in the database table, so
that the final responder can read the error message?
>
> Many Thanks in Advance,
> C R Baradwaj
>
>
>
>
>
>
>
>
>
>
> Tom Barnes <[email protected]> wrote:
>
>>
>>Raghuram Bharadwaj C wrote:
>>
>>>Thanks tom for your support!
>>>
>>>Let me explain more about the problem.
>>>
>>>Scenario
>>>========
>>>Lets take a simplest case where the client is sending a message to
>>
>>"QueueA" and
>>
>>>he is now waiting for a response in the "ResponseQ"
>>>
>>>The MDB listening to "QueueA" wakes up and split the message(s) into
>>
>>three and
>>
>>>passing it to the next layer of datasource specific queue(s). The queue(s)
>>
>>are
>>
>>>"QueueB", "QueueC" and "QueueD".
>>>
>>>The MDB listening to the datasource specific queue(s) picks up the
>>
>>datasource
>>
>>>request sends it to the datasource and gets the response back from
>>
>>the datasource.
>>
>>>The MDB also updates a table in the database with the response. The
>>
>>MDB also check(s)
>>
>>>after updating the database to see all response(s) from all the datasource(s)
>>>are reached. If yes, one of the MDB also sends a acknowledgement to
>>
>>the "ResponseQ".
>>
>>>
>>>The client listening to the "ResponseQ" gets the acknowledgement and
>>
>>hit the database
>>
>>>to collect all the response(s) from all the datasource(s). These response(s)
>>
>>are
>>
>>>formatted and sent a response to the client. We have also created uniqueid
>>
>>for
>>
>>>identifying each request. This uniqueid is set in the JMSCorrelationID.
>>
>>The client
>>
>>>uses the uniqueid to collect all the response(s) for the request he
>>
>>had sent.
>>
>>>Problem
>>>=======
>>>If an error/exception occurred in a one of the MDB which is listening
>>
>>to QueueB/QueueC/QueueD.
>>
>>>How do we handle this?
>>>
>>>Please let me know all the possibilities that you would have done in
>>
>>this case.
>>
>>>
>>Does A know how many downstream queues are involved? As part of its
>>transaction it can send a message to the responseQ stating which
>>queues to expect responses from. The client gets this message
>>and knows that it must get responses from all of B, C, D, etc.
>>before assuming success. On a failure, B, C, D, etc. can send
>>an error message back to the response Q, or the client can
>>simply timeout.
>>
>>This way there are no race conditions
>>involving unanticipated multiple responses or missing
>>responses, which I think the
>>algorithm you mention above can create.
>>Assuming just B and C (no D):
>> B detects C is done by checking the DB
>> C detects B is done by checking the DB **at the same time**
>> Two response messages get sent
>> - or -
>> B finishes detects C not done, and sends no message.
>> C finishes, B is finished but not reflected in DB yet, sends
>> no message.
>>
>>NOTE: Be aware that when a transaction commits, different
>>resources can response "faster" than others. The transaction
>>monitor has no control over this. So, if as part of the
>>same commit, a database insert and a queue insert is
>>performed, it is possible for a consumer to receive the
>>new message BEFORE the new database insert actually completes.
>>
>>
>>>
>>>Many Thanks in Advance,
>>>
>>>C R Baradwaj
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>Assuming that
>>>
>>>Tom Barnes <[email protected]> wrote:
>>>
>>>
>>>>One approach is to send an "error" message to QB that uses
>>>>the JMSCorrelationID the consumer is expecting. This will
>>>>wake up the consumer, and the consumer can react to
>>>>the error as needed.
>>>>
>>>>Another is to use two asynchronous listeners, one on the
>>>>response queue, and one on a temporary (client created)
>>>>queue. On error detection the MDB can send error messages
>>>>to the temporary queue.
>>>>
>>>>You may want to skim the book "Professional JMS" - as I
>>>>recall, it contains a section on queueing design patterns.
>>>>
>>>>Tom
>>>>
>>>>Raghuram Bharadwaj C wrote:
>>>>
>>>>
>>>>
>>>>>Hi All,
>>>>>
>>>>>Pl. help me with ur expertise in the foll. scenario we are facing.
>>>>>
>>>>>Scenario:
>>>>>I have a requirement where I need to notify the exceptions to my client
>>>>
>>>>while
>>>>
>>>>
>>>>>the client request's are processed asynchronously and my client is
>>>>
>>>>waiting in
>>>>
>>>>
>>>>>synchronous for the response.
>>>>>
>>>>>The client is sending a message to one queue (QueueA) and waiting
>>
>>for
>>
>>>>response
>>>>
>>>>
>>>>>in another queue (QueueB). The message from "QueueA" is picked up
>>
>>by
>>
>>>>a MDB listening
>>>>
>>>>
>>>>>to "QueueA" and it throws an exception while processing some "business
>>>>
>>>>logic".
>>>>
>>>>
>>>>>In this case how do I notify to my client who is waiting in another
>>>>
>>>>queue. i.e.
>>>>
>>>>
>>>>>"QueueB" that there is an exception occurred while processing the
>>
>>business
>>
>>>>logic.
>>>>
>>>>
>>>>>I am using JMSCorrelationID to uniquely identify a response for a
>>
>>request
>>
>>>>sent
>>>>
>>>>
>>>>>by the client.
>>>>>
>>>>>What are the possible options to handle exceptions in JMS for an implementation
>>>>>like the one mentioned above.
>>>>>
>>>>>Any comments/feedback/pointers will be REALLY REALLY appreciated.
>>>>>
>>>>>Tks and regds
>>>>>C R Baradwaj
>>>>
>
-
I am using weblogic server 6.0 service pack 2.
The problem is in runtime exception in JMS.
Here is an exception I am getting:
java.lang.RuntimeException: Client possibly malfunctioning as RuntimeException thrown
from the onMessage routine of the client
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1938)
at weblogic.jms.client.JMSSession.run(JMSSession.java:881)
at weblogic.jms.backend.BEServerSession.execute(BEServerSession.java:83)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
This occurs in the line
>bsender = bsession.createSender(bqueue);
of the class, in the onMessage method.
What is the reason for the exception? What can be done to fix it? I just need to
process several messages in parallel.
I have a startup class RateQuoteJMSResponse, that calls JMS.
This happens only when I have a message listeners pool. When I did not use the pool,
it worked OK. But I want to allow processing messages in parallel, and as I understand,
there is no other option except using ServerSessionPool.
When I tried to do that just with QueueReceiver, it worked OK:
qreceiver = qsession.createReceiver (queue);
qreceiver.setMessageListener (this);
qcon.start();
However, that way messages were not processed in parallel.
Here is my code:
package com.bbb.object.jms;
import java.io.*;
import java.util.*;
import javax.jts.*;
import javax.naming.*;
import javax.jms.*;
import com.bbb.object.*;
import com.bbb.object.RateQuote.*;
import org.apache.crimson.tree.*;
import org.w3c.dom.*;
import weblogic.jms.extensions.JMSHelper;
import weblogic.jms.ServerSessionPoolFactory;
public class RateQuoteJMSResponse implements MessageListener
private final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory";
private final static String JMS_FACTORY="weblogic.closs.jms.QueueConnectionFactory";
private final static String SESSION_POOL_FACTORY="weblogic.jms.ServerSessionPoolFactory:ClossJMSServer";
private final static int ALL_OCCUPIED = -1;
private static REServer servers [];
private static REServersThrottle throttle;
private QueueConnectionFactory qconFactory;
private QueueConnection qcon;
private QueueSession qsession;
private QueueSession bsession;
//private QueueReceiver qreceiver;
private QueueSender bsender = null;
private Queue queue;
private Queue bqueue;
private ServerSessionPoolFactory sessionPoolFactory;
private ServerSessionPool sessionPool;
private ConnectionConsumer consumer;
private int findUnoccupiedServer ()
for (int ii = 0; ii < servers.length; ii++)
if (servers[ii].isActive () && !servers [ii].isOccupied ())
return ii;
return ALL_OCCUPIED;
private synchronized void updateServers (ActiveServers activeServers)
for (int ii = 0; ii < servers.length; ii++)
boolean wasActive = servers[ii].isActive ();
boolean nowActive = activeServers.isAlive (servers[ii].getHostName ());
if (wasActive && !nowActive)
throttle.removeResource ();
Logging.debugInfoLog ("Resource removed");
else if (!wasActive && nowActive)
throttle.addResource ();
Logging.debugInfoLog ("Resource added");
servers [ii].setActive (nowActive);
// MessageListener interface
//public void processMessage (Message msgIn)
public void onMessage (Message msgIn)
Logging.debugInfoLog ("Starting onMessage");
ActiveServers activeServers = null;
try
activeServers = new ActiveServers();
catch (Exception ignored) {}
Logging.debugInfoLog ("Active Servers file read");
updateServers (activeServers);
Logging.debugInfoLog ("Servers updated");
throttle.getResource ();
Logging.debugInfoLog ("Resource got");
try
Logging.debugInfoLog ("0");
String msgTextIn;
ObjectMessage msgOut;
RateQuoteGetBase rateQuoteGet;
RateQuoteGetXML rateQuoteGetXML;
Logging.debugInfoLog ("1");
if (msgIn == null)
Logging.debugInfoLog ("2");
rateQuoteGet = new RateQuoteGetBase ("Cannot receive a rate quote back from JMS.");
msgTextIn = "";
else
Logging.debugInfoLog ("3");
if (msgIn instanceof TextMessage)
msgTextIn = ((TextMessage)msgIn).getText();
else
msgTextIn = msgIn.toString();
Logging.debugInfoLog ("4");
bqueue = (Queue) msgIn.getJMSReplyTo ();
Logging.debugInfoLog ("8");
bsender = bsession.createSender(bqueue);
Logging.debugInfoLog ("9");
bsender.setDeliveryMode (javax.jms.DeliveryMode.NON_PERSISTENT);
Logging.debugInfoLog ("10");
Logging.debugInfoLog ("Prepareing to find unoccupied server");
int selectedServer = findUnoccupiedServer ();
Logging.debugInfoLog ("Unoccupied server found: " + selectedServer);
if (selectedServer == ALL_OCCUPIED)
rateQuoteGet = new RateQuoteGetBase ("No nonoccupied rating engines found.");
msgTextIn = "";
else
servers [selectedServer].setOccupied ();
Logging.debugInfoLog ("Set occupied: " + selectedServer);
String hostname = servers [selectedServer].getHostName ();
int portId = servers [selectedServer].getPortId ();
rateQuoteGet = new RateQuoteGetBase (hostname, portId);
rateQuoteGetXML = new RateQuoteGetXML (new RateQuoteGet (rateQuoteGet));
rateQuoteGetXML.prepareXML ();
servers [selectedServer].setUnOccupied ();
Logging.debugInfoLog ("Set unoccupied: " + selectedServer);
if (!rateQuoteGetXML.hasErrorOccured ())
rateQuoteGet.sendXML (msgTextIn);
rateQuoteGet.prepareXML ();
Logging.debugInfoLog("Message Received: " + msgTextIn );
msgOut = bsession.createObjectMessage ();
msgOut.setObject (rateQuoteGet);
bsender.send (msgOut, javax.jms.DeliveryMode.NON_PERSISTENT,
javax.jms.Message.DEFAULT_PRIORITY, 18000000L);
Logging.debugInfoLog("Message Sent Back: " + rateQuoteGet.getXML());
Logging.debugInfoLog ("End of massage sent back");
rateQuoteGet.debugPrint ();
catch (JMSException jmse)
Logging.debugInfoLog ("5");
jmse.printStackTrace();
Logging.debugInfoLog ("6");
try
if (bsender != null)
bsender.close ();
catch (JMSException ignored) {}
finally
bsender = null;
Logging.debugInfoLog ("7");
try
throttle.freeResource ();
Logging.debugInfoLog ("Resource freed");
Logging.debugInfoLog ("Finishing onMessage");
catch (Exception ignored) {}
* Create all the necessary objects for receiving
* messages from a JMS queue.
public void init(Context ctx, String queueName, int countListeners) throws NamingException,
JMSException
//Logging.debugInfoLog ("Class name: " + this.getClass().getName());
qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
qcon = qconFactory.createQueueConnection();
qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
bsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
try
queue = (Queue) ctx.lookup(queueName);
catch (NamingException ne)
ne.printStackTrace ();
//queue = (Queue) ctx.lookup (queueName);
//queue = qsession.createQueue (queueName);
//queue = JMSHelper.createPermanentQueueAsync(ctx, "closs", "ClossJMSServer",
queueName, JNDI_FACTORY);
//JMSHelper.createPermanentQueueAsync(ctx, "ClossJMSServer", queueName, JNDI_FACTORY);
//queue = qsession.createQueue("ClossJMSServer/" + queueName);
//queue = createPermanentQueueAsync(ctx, jmsServerName, queueName, jndiName);
//ctx.bind(queueName, queue);
//qreceiver = qsession.createReceiver (queue);
//qreceiver.setMessageListener (this);
qcon.start();
sessionPoolFactory = (ServerSessionPoolFactory) ctx.lookup (SESSION_POOL_FACTORY);
sessionPool = sessionPoolFactory.getServerSessionPool ( qcon,
countListeners,
false,
Session.AUTO_ACKNOWLEDGE,
this.getClass().getName());
ConnectionConsumer consumer = qcon.createConnectionConsumer (queue, "", sessionPool,
3*countListeners);
* Close JMS objects.
public void close()
try
//if (qreceiver != null)
// qreceiver.close();
if (consumer != null)
consumer.close();
catch (JMSException ignored){}
//qreceiver = null;
consumer = null;
try
if (qsession != null)
qsession.close();
catch (JMSException ignored){}
qsession = null;
try
if (bsender != null)
bsender.close();
catch (JMSException ignored){}
bsender = null;
try
if (bsession != null)
bsession.close();
catch (JMSException ignored){}
bsession = null;
try
if (qcon != null)
qcon.close();
catch (JMSException ignored){}
qcon = null;
* Receive a JMS message.
//public Message receive() throws JMSException
// return qreceiver.receive ();
public static void main (String[] args) throws Exception
Message msg;
int len = args.length;
if (len %2 != 0 || len == 0)
Logging.debugInfoLog("Usage: java RateQuoteJMSResponse hostname portid hostname
portid ...");
return;
int reCount = len/2;
throttle = new REServersThrottle (0);
servers = new REServer [reCount];
for (int ii = 0; ii < reCount; ii++)
servers [ii] = new REServer (args [2*ii], args [2*ii + 1]);
//Logging.debugInfoLog ("Arguments: " + args[0] + " " + args[1]);
InitialContext ic = getInitialContext (ClickProperties.getInitialContext());
RateQuoteJMSResponse qr = new RateQuoteJMSResponse ();
qr.init (ic, ClickProperties.getJMSQueue(), reCount);
Logging.debugInfoLog("JMS Rating Engine Responser Is Ready To Receive Messages.");
// Wait until a "quit" message has been received.
//synchronized (qr)
// while (true)
// msg = qr.receive ();
// Logging.debugInfoLog ("Message received");
// qr.processMessage (msg);
//qr.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);
return new InitialContext(env);
And here is the output from weblogic console:
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <Active Servers file rea
d>
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <Throttle max increased
to: 1>
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <Resource added>
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <Servers updated>
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <Throttle count increase
d to: 1>
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <Resource got>
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <0>
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <1>
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <3>
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <4>
<May 15, 2002 11:11:57 AM EDT> <Debug> <Debug Info Log> <8>
java.lang.RuntimeException: Client possibly malfunctioning as RuntimeException t
hrown from the onMessage routine of the client
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1938)
at weblogic.jms.client.JMSSession.run(JMSSession.java:881)
at weblogic.jms.backend.BEServerSession.execute(BEServerSession.java:83)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
[config.xml]
Thanks. It creates a new class each time onMessage () is called. I thought it uses
an existing instance of the class.
"Zach" <[email protected]> wrote:
>You need to trap the exception inside the onMessage so you can see the
>exception that is being thrown by the bsession.createSender call. This
>stack trace doesn't give enough information. It is just a message saying
>your code failed to handle and leaked an exception out of the onMessage.
>If that is the line that failed, then try catch around it and look at the
>stack trace for that exception.
>
>_sjz.
>
>"Alexander Rabinowitz" <[email protected]> wrote in message
>news:[email protected]...
>>
>> I am using weblogic server 6.0 service pack 2.
>> The problem is in runtime exception in JMS.
>> Here is an exception I am getting:
>> java.lang.RuntimeException: Client possibly malfunctioning as
>RuntimeException thrown
>> from the onMessage routine of the client
>> at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1938)
>> at weblogic.jms.client.JMSSession.run(JMSSession.java:881)
>> at
>weblogic.jms.backend.BEServerSession.execute(BEServerSession.java:83)
>> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>>
>> This occurs in the line
>>
>> >bsender = bsession.createSender(bqueue);
>>
>> of the class, in the onMessage method.
>>
>> What is the reason for the exception? What can be done to fix it? I just
>need to
>> process several messages in parallel.
>
>
>
-
Exception Starting JMS listener bean on iAs 10.1.3.1 using Database Persist
Hi,
I'm getting this exception
Unexpected exception by JMS provider: javax.jms.InvalidDestinationException: Destination "oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl[SECOND]" has invalid type "class oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl" and cannot be used with OC4J JMS..
on deploy of an application containing the a Message Driven Bean
It is marked as failed in EM.
This is the relevant snippet from my orion-ejb-jar.xml
<message-driven-deployment name="CommunicatorMessageBean" destination-location="jmsResourceAdaptor/AutoWrap/Queues/SECOND" />
thanks in advance
DanThat seems to be a bug in the ADF Runtime Installer.
The file jsp-el-api.jar from JDev 10.1.3 must be copied manually to the oc4j container /applib directory - and if you have more than one oc4j instance on your application server it must be copied to all of them.
I have been in contact with Oracle Support because of this and hopefully a patch and/or proper documentation will be release soon. -
How to catch exception of JMS when call onMessage()?
I write a consumer client implement onMessage(),
in my main() method ...
try {
_adapter = new Adapter(checkConsumer,env);
_adapter.setSelector("client = 'Receive1'");
_adapter.start();
System.out.println("Hello...");
} catch(Exception e) {
_adapter = null;
System.out.println("Unable to start adapter: " + e.getMessage());
_adapter.start() will call onMessage() my onMessage like this
public void onMessage(Adapter adpt, Message message) {
try {
if(message instanceof TextMessage) {
// Write the text out as read String text = ((TextMessage)message).getText();
// Do CHECK Process adpt.demoOut("Receive CHECK Text is :" + text);
//System.out.println("class name is " + consumerName);
} else {
// This is just a message (no particular type) } } catch (Exception e) {
try {
adpt.warn("Error outputing data: " + message.getJMSMessageID());
} catch(Exception ignore) {
} adpt.warn("\tError: " + e.getMessage());
// Do some exception process }
If the JMS Server shutdown, how can I catch the exception?You might want to try with exception listener that JMS specification provides.
-
I have number of types exceptions being thrown in my application. Of them JMS, Database, user-defined and others. I am using MessageListener to receive messages from a queue. If I use ExceptionListener, I can only handle JMS exceptions in a class implementing ExceptionListener. I would like to handle all the exceptions together. Do you suggest a best way for this
thanks
ShivaI would have thought that you could build a class that not only implements javax.jms.ExceptionListener, but that could also be used to handle any other exceptions from other places in your code. You could add bean style methods to pass syncronous exceptions to the class as well as implementing any other ascynchronous exception handlers from your database or whatever.
E.g.
public class ExceptionHandler implements javax.jms.ExceptionListener, anyotherexceptionlistenerstyleinterface
public void handleException (Exception e)
public void onException (javax.jms.JMSException e)
Hope this helps a little,
Tom Jenkinson
Arjuna Technologies Limited -
Very Strange exception in JMS in JBoss, EJB3
My Client program is:
env.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NameingContextFactory");
env.put(Context.URL_PKG_PREFIXES,"org.jboss.naming:jnp.interfaces");
env.put(Context.PROVIDER_URL,"jnp://localhost:1099");
QueueConnectionFactory qconFactory;
QueueConnection connection;
QueueSession session;
QueueSender sender;
Queue queue;
TextMessage msg;
qconFactory = (QueueConnectionFactory) ctx.lookup("QueueConnectionFactory");
connection = qconFactory.createQueueConnection();
session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
queue = (Queue) ctx.lookup("queue/testQueue");
msg = session.createTextMessage();
sender = session.createSender(queue);
msg.setText("Hello World");
connection.start();
sender.send(msg);
session.close();
connection.close();
MY MDB is:
@MessageDriven(name="LongProcessMessageBean", activationConfig = {
@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination", propertyValue="queue/testQueue")
public class LongProcessMessageBean implements MessageListener {
@Resource
private MessageDrivenContext context;
public void onMessage(Message message) {
String name = null;
try {
if (message instanceof ObjectMessage) {
ObjectMessage objMessage = (ObjectMessage) message;
Object obj = objMessage.getObject();
if (obj instanceof TextMessage) {
System.out.println("My Message from the Consumer is:"+obj.toString());
} else {
System.err.println("Expecting ProcessDTO in Message");
} else {
System.err.println("Expecting Object Message");
I am getting exception as on console
19:22:18,328 INFO [STDOUT] MyException is::javax.naming.NamingException: Could not dereference object [Root exception is java.lang.ClassCastException: org.jboss.naming.LinkRefPair cannot be cast to org.jboss.naming.LinkRefPair]
How to get rid of this? please explain me.
Thanks,
RahulMy Client program is:
env.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NameingContextFactory");
env.put(Context.URL_PKG_PREFIXES,"org.jboss.naming:jnp.interfaces");
env.put(Context.PROVIDER_URL,"jnp://localhost:1099");
QueueConnectionFactory qconFactory;
QueueConnection connection;
QueueSession session;
QueueSender sender;
Queue queue;
TextMessage msg;
qconFactory = (QueueConnectionFactory) ctx.lookup("QueueConnectionFactory");
connection = qconFactory.createQueueConnection();
session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
queue = (Queue) ctx.lookup("queue/testQueue");
msg = session.createTextMessage();
sender = session.createSender(queue);
msg.setText("Hello World");
connection.start();
sender.send(msg);
session.close();
connection.close();
MY MDB is:
@MessageDriven(name="LongProcessMessageBean", activationConfig = {
@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination", propertyValue="queue/testQueue")
public class LongProcessMessageBean implements MessageListener {
@Resource
private MessageDrivenContext context;
public void onMessage(Message message) {
String name = null;
try {
if (message instanceof ObjectMessage) {
ObjectMessage objMessage = (ObjectMessage) message;
Object obj = objMessage.getObject();
if (obj instanceof TextMessage) {
System.out.println("My Message from the Consumer is:"+obj.toString());
} else {
System.err.println("Expecting ProcessDTO in Message");
} else {
System.err.println("Expecting Object Message");
I am getting exception as on console
19:22:18,328 INFO [STDOUT] MyException is::javax.naming.NamingException: Could not dereference object [Root exception is java.lang.ClassCastException: org.jboss.naming.LinkRefPair cannot be cast to org.jboss.naming.LinkRefPair]
How to get rid of this? please explain me.
Thanks,
Rahul -
I am seeing a similar problem under WebLogic 6.1. I also initially posted the
problem to the JMS newsgroup. My problem is also reported from JMS, however I am
using a TopicConnection. The problem seems to be intermittent and only shows up
after testing for a while sometimes as long as 30 minutes. I also reuse the
connection from application startup. It seems to me that creating a connection
for every message would incur a performance penalty.
The exception traceback is:
Start server side stack trace:
java.rmi.NoSuchObjectException: RemoteInvokable - id: '257'
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:609)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.java:42)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:639)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:311)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
Rana Ahmed wrote:
Please see the messages at the end as I first posted to the JMS group....
I am reusing the connection, I establish the connection
at application start-up and then use the same connection
for every send. And this error happens intermittently for
some of the send methods.
Rana
"Zach" <[email protected]> wrote in message
news:[email protected]...
This is not a JMS error. It is an RMI error. It looks like
your connection is gone. Are you creating a connection
for every send? Or are you reusing the connection over
and over again and this happens only some of the time?
_sjz.
"Rana Ahmed" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am using JMS (WebLogic 6.0 sp1) to communicate between two computers.
I
am
getting an intermittent error that happens when I try to send messageusing
QueueSender.send method, I get a JMSException that says:
weblogic.jms.common.JMSException: System error:
java.rmi.NoSuchObjectException: RemoteInvokable - id: '1417'
Can some body tell me what is the reason for this error and how do I fixit.
Rana -
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 -
Getting JMS Exception while starting the managed servers
Hi ,
I have Savvion BPM tool hosted on WebLogic server 10.3 version.Before the manage servers coming to Running state its throwing the below mention warning message.Can anybody help me to identify what could be the reason the managed server the below exceptions.
Thanks in advance...
<Jun 19, 2012 3:54:32 AM EDT> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server sbmejb2.>
<Jun 19, 2012 3:54:33 AM EDT> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server sbmejb2.>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
*<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLServiceMDB is unable to connect to the J*
MS destination: jms/BLAdminTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster addres
s "sbmejb1,sbmejb2">
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCacheSyncMDB is unable to connect to the
JMS destination: jms/BLCacheSyncTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLSessionMDB is unable to connect to the J
MS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.177.16.126:16103 for pr
otocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "sbmejb1" for domain "sb
m76" running in Production Mode>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLBizStoreMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCheckDueMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLEmailMDB is unable to connect to the JMS
destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLResumeWSMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MConsoleServiceMDB is unable to connect to
the JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EPServiceMDB is unable to connect to the J
MS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:42 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EventReaderBean is unable to connect to th
e JMS destination: jms/BPAdminTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>Hi Rohit,
Thanks for your response..
Below is the BLAdminTopic configuration.Please let me know if you need any further info.
Topic:BLAdminTopic
Type:Distributed Topic
JNDI:jms/BLAdminTopic
Sub Deployment :N/A
Target:N/A
BLAdminTopic@jmsnode1BL Topic jms/BLAdminTopic@jmsnode1BL BLAdminTopic@jmsnode1BL jmsnode1BL
BLAdminTopic@jmsnode2BL Topic jms/BLAdminTopic@jmsnode2BL BLAdminTopic@jmsnode2BL jmsnode2BL
Regards,
Jyotiranjan -
JMS Exception - unable to connect to the JMS destination
Hi,
I've configured WebLogic10R3 Cluster with one Admin Server and 2 Managed Servers.
I deployed the application to the Cluster. (Ie. both Managed 1 and Managed Server 2.)
I am geeting the following JMS destination not found exception while starting the Second Managed Server.
There are no errors occurred in the First Managed Server.
{color:#ff0000}<Warning> <EJB> <BEA-010061>
<The Message-Driven EJB: SysAuditLogger is unable to connect to the JMS destination: topic/efpAuditTopic.
The Error was: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server efpserver_man2
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:efpserver_man2.
Resolved 'weblogic .messaging.dispatcher'; remaining name 'S:efpserver_man2>{color}
Configuration Details:
##config.xml:
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/wls [http://www.bea.com/ns/weblogic/90/security/wls.xsd] [http://www.bea.com/ns/weblogic/920/domain] [http://www.bea.com/ns/weblogic/920/domain.xsd] [http://www.bea.com/ns/weblogic/90/security/xacml] [http://www.bea.com/ns/weblogic/90/security/xacml.xsd] [http://www.bea.com/ns/weblogic/90/security] [http://www.bea.com/ns/weblogic/90/security.xsd]">
<name>efpdomain</name>
<domain-version>10.3.0.0</domain-version>
<security-configuration>
<name>efpdomain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{3DES}hcdd+yZGXk5DHgRKqCM7E86l4+VxPcZ9Ut7rB6WaXqMyvbtDjDUKNCKbMQdCN/BEYCv5E0N4Hms9kntfqhaduDO1WGMtbmJL</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{3DES}Q2xO0EiChbay/HkRiorTjg==</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<listen-address>192.168.12.240</listen-address>
</server>
<server>
<name>efpserver_man1</name>
<listen-port>8011</listen-port>
<cluster>efpcluster</cluster>
<listen-address>192.168.12.240</listen-address>
<xml-registry>XMLEFP</xml-registry>
<jta-migratable-target>
<user-preferred-server>efpserver_man1</user-preferred-server>
<cluster>efpcluster</cluster>
</jta-migratable-target>
</server>
<server>
<name>efpserver_man2</name>
<listen-port>8012</listen-port>
<cluster>efpcluster</cluster>
<listen-address>192.168.12.240</listen-address>
<xml-registry>XMLEFP</xml-registry>
<jta-migratable-target>
<user-preferred-server>efpserver_man2</user-preferred-server>
<cluster>efpcluster</cluster>
</jta-migratable-target>
</server>
<cluster>
<name>efpcluster</name>
<cluster-address>192.168.12.240:8011,192.168.12.240:8012</cluster-address>
<multicast-address>239.192.0.0</multicast-address>
</cluster>
<embedded-ldap>
<name>efpdomain</name>
<credential-encrypted>{3DES}q/XQGirHcAcgi4iwPiXIkRHP8xte4xVBgJwjM+qMwbk=</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.0.0</configuration-version>
<app-deployment>
<name>efp</name>
<target>efpcluster</target>
<module-type>ear</module-type>
<source-path>applications\efp.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<xml-registry>
<name>XMLEFP</name>
<document-builder-factory>weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl</document-builder-factory>
<sax-parser-factory>weblogic.apache.xerces.jaxp.SAXParserFactoryImpl</sax-parser-factory>
<transformer-factory>weblogic.apache.xalan.processor.TransformerFactoryImpl</transformer-factory>
</xml-registry>
<jms-server>
<name>eFpJMSServer</name>
<target>efpserver_man1 (migratable)</target>
<persistent-store>eFpJMSJDBCStore</persistent-store>
</jms-server>
<jms-server>
<name>eFpJMSServer2</name>
<target>efpserver_man2 (migratable)</target>
<persistent-store>eFpJMSJDBCStore2</persistent-store>
</jms-server>
<migratable-target>
<name>efpserver_man1 (migratable)</name>
<notes>繧ｷ繧ｹ繝・Β逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶よ焔蜍輔〒蜑企勁縺励↑縺・〒縺上□縺輔＞縲・/notes>
<user-preferred-server>efpserver_man1</user-preferred-server>
<cluster>efpcluster</cluster>
</migratable-target>
<migratable-target>
<name>efpserver_man2 (migratable)</name>
<notes>繧ｷ繧ｹ繝・Β逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶よ焔蜍輔〒蜑企勁縺励↑縺・〒縺上□縺輔＞縲・/notes>
<user-preferred-server>efpserver_man2</user-preferred-server>
<cluster>efpcluster</cluster>
</migratable-target>
<jdbc-store>
<name>eFpJMSJDBCStore</name>
<prefix-name>WLJMS_</prefix-name>
<data-source>eFpNonXADataSource</data-source>
<target>efpserver_man1 (migratable)</target>
</jdbc-store>
<jdbc-store>
<name>eFpJMSJDBCStore2</name>
<prefix-name>WLJMS2_</prefix-name>
<data-source>eFpNonXADataSource</data-source>
<target>efpserver_man2 (migratable)</target>
</jdbc-store>
<jms-system-resource>
<name>eFPJMS</name>
<target>efpcluster</target>
<sub-deployment>
<name>eFPServer</name>
<target>eFpJMSServer</target>
</sub-deployment>
<sub-deployment>
<name>eFPServer2</name>
<target>eFpJMSServer2</target>
</sub-deployment>
<descriptor-file-name>jms/efpjms-jms.xml\JMS Description-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>eFpDataSource</name>
<target>efpcluster</target>
<descriptor-file-name>jdbc/eFpDataSource-2004-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>eFpNonXADataSource</name>
<target>efpcluster</target>
<descriptor-file-name>jdbc/eFpNonXADataSource-6172-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>
##JMS Description-jms.xml
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms [http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd]">
<connection-factory name="ConnectionFactory">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>jms/ConnectionFactory</jndi-name>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<connection-factory name="XAConnectionFactory">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>jms/XAConnectionFactory</jndi-name>
<transaction-params>
<transaction-timeout>3600</transaction-timeout>
<xa-connection-factory-enabled>true</xa-connection-factory-enabled>
</transaction-params>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<uniform-distributed-queue name="ActiveActivityQueue">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>queue/efpActiveActivityQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
</uniform-distributed-queue>
<uniform-distributed-topic name="AdminTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpAdminTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="AuditTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpAuditTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="ErrorTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpErrorTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="FreeTextTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpFreeTextTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="ReportingTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpReportingTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
</weblogic-jms>
-----Getting the following exception while trying to connect the JMS destination I am using weblogic 10.3.3 connecting to oracle AQ. The config has been done as per the 'Interoperating with Oracle AQ JMS' document from oracle. I could see that while deploying the application the number of connections in the database increasing to 15 and getting the following error message.
<Jun 15, 2011 4:14:29 PM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: SampleEJBBean is unable to connect to the JMS destination: jms/propQueue. Th
e Error was:
oracle.jms.AQjmsException: Internal error: Cannot obtain XAConnection weblogic.c
ommon.resourcepool.ResourceLimitException: No resources currently available in p
ool TestDataSource to allocate to applications, please increase the size of the
pool and retry..
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal
(ResourcePoolImpl.java:555)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
ePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
ePoolImpl.java:322)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
ava:438)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
ava:317)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
nPoolManager.java:93)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
nPoolManager.java:61)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:
1670)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
468)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
ce.java:355)
at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
at oracle.jms.AQjmsXAConnection.createXAQueueSession(AQjmsXAConnection.j
ava:214)
at weblogic.ejb.container.internal.JMSConnectionPoller.setUpQueueSession
s(JMSConnectionPoller.java:1545)
at weblogic.ejb.container.internal.JMSConnectionPoller.createJMSConnecti
on(JMSConnectionPoller.java:2047)
at weblogic.ejb.container.internal.JMSConnectionPoller.connect(JMSConnec
tionPoller.java:787)
at weblogic.ejb.container.internal.MDConnectionManager.startConnectionPo
lling(MDConnectionManager.java:244)
at weblogic.ejb.container.manager.MessageDrivenManager.start(MessageDriv
enManager.java:584)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.mdManagerSt
art(MessageDrivenBeanInfoImpl.java:1334)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.deployMessa
geDrivenBeans(MessageDrivenBeanInfoImpl.java:1314)
at weblogic.ejb.container.deployer.EJBDeployer.deployMessageDrivenBeans(
EJBDeployer.java:1669)
at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:14
93)
at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:614)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(Module
ListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
teDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:43)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
eDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartMod
ulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.ja
va:1269)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:43)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.
java:409)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleM
oduleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(Deploym
entStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(Ap
pContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.ac
tivate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.ac
tivateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Commit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.co
mmit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeplo
ymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(
DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.com
mit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) -
JMS Exception: Warning MessagingBridge 200026 Bridge "JMSMessagingBr
Hi,
I have 3 instances of weblogic server and in two of the instances we are getting the following exception:
<11-Apr-2011 3:55:09 EDT AM> <Warning> <MessagingBridge> <200026> <Bridge "JMSMessagingBridge" encountered some problems to one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (Exception caught was java.lang.Exception: weblogic.jms.common.LostServerException: weblogic.rjvm.PeerGoneEvent[source=weblogic.rjvm.RJVMImpl@163e0e9 - id: '90879289488185917S:10.28.0.18:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver' connect time: 'Sat Mar 19 05:56:04 EDT 2011'] - id: 90879289488185917S: 10.28.0.18:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver', reason: 'weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds'
at weblogic.jms.client.JMSConnection.jmsPeerGone(JMSConnection.java:812)
at weblogic.jms.dispatcher.DispatcherWrapperState.peerGone(DispatcherWrapperState.java:490)
at weblogic.rjvm.RJVMImpl$PeerGoneDeliverer.execute(RJVMImpl.java:1272)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:223)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:193)
)>
<11-Apr-2011 3:55:09 EDT AM> <Info> <MessagingBridge> <200020> <Bridge "JMSMessagingBridge" is stopped.>
<11-Apr-2011 3:55:19 EDT AM> <Info> <MessagingBridge> <200033> <Bridge "JMSMessagingBridge" is getting the connections to the two adapters.>
<11-Apr-2011 3:55:19 EDT AM> <Info> <MessagingBridge> <200031> <Bridge "JMSMessagingBridge" is configured to allow degradation of its quality of service in cases where the configured quality of service is not reachable.>
<11-Apr-2011 3:55:19 EDT AM> <Info> <MessagingBridge> <200030> <Bridge "JMSMessagingBridge" is configured to work in "Exactly-once" mode and it is actually working in "Duplicate-okay" mode.>
<11-Apr-2011 3:55:19 EDT AM> <Info> <MessagingBridge> <200028> <Bridge "JMSMessagingBridge" starts transferring messages.>
weblogic.jms.common.IllegalStateException: Connection is closed
at weblogic.jms.client.JMSConnection.getFrontEndDispatcher(JMSConnection.java:400)
at weblogic.jms.client.JMSConnection.checkClosed(JMSConnection.java:997)
at weblogic.jms.client.JMSConnection.setExceptionListener(JMSConnection.java:500)
at weblogic.jms.adapter.JMSBaseConnection.setExceptionListenerInternal(JMSBaseConnection.java:1151)
at weblogic.jms.adapter.JMSBaseConnection.setExceptionListener(JMSBaseConnection.java:1142)
at weblogic.jms.adapter.JMSConnectionHandle.setExceptionListener(JMSConnectionHandle.java:126)
at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:101)
at $Proxy83.setExceptionListener(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:852)
at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:942)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:223)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:193)
Please let us know the possible cause of the above exception
TksProbably it points to a network failure which took 240 seconds for WebLogic to decide the network failed and to timeout the operation.
It can also be the case the bridge was sending a relatively large message over a slow network, and WebLogic timed out before the send could complete.
I suggest you try to trace the underlying cause by enabling debug logs for RMI.
The issue doesn't seem JMS related - as it fails on reconnect attempt when it is establishing the connection or JNDI context prior to any JMS API gets called.
1. Verify your WL server logs, to see if the server is reporting errors are warnings.
2. Take some thread-dumps on your both unresponsive servers to see if you have stuck threads - perhaps due to some kind of dead-lock.
3. Try writing your own simple client, with your own timer thread, that merely periodically makes a simple RMI call to the server, and notifies you if the response time is greater than a few seconds to narrow it down.
-Akshay -
Reg: JMS Exception sending to queue null
Hi,
When i try to receive the data from the external system in the form of xml through JMS i am getting an exception like "JMS Exception Sending to queue null". Can somebody help me with this in resolving the issue.
Thanks & Regards,
P.Prasanna.Hi Tom,
Thank you very much for your help. This is the error i am getting now.
com.ford.vista.exception.VistaSystemException: exception caught in proxy
at com.ford.vista.business.common.VistaProxy.makeWrapperException(VistaProxy.java:197)
at com.ford.vista.business.common.VistaProxy.invoke(VistaProxy.java:125)
at $Proxy2.processOrderPublishing(Unknown Source)
at com.ford.vista.business.order.delegate.OrderTransactionBusinessDelegate.changeStatusEvent(OrderTransactionBusinessDelegate.java:340)
at com.ford.vista.integration.exinterface.service.MdbOagisInterfaceService.callService(MdbOagisInterfaceService.java:97)
at com.ford.vista.integration.exinterface.service.MdbInterfaceService.processMessage(MdbInterfaceService.java:178)
at com.ford.vista.integration.exinterface.service.MdbInterfaceService.processMessage(MdbInterfaceService.java:97)
at com.ford.vista.webservice.VistaTransactionWebService.processRequest(VistaTransactionWebService.java:61)
at com.ford.vista.webservice.VistaBaseWebService.doPost(VistaBaseWebService.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:61)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1064)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:598)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:206)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:80)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:214)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:623)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:457)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
--- nested ---
com.ford.vista.exception.VistaSystemException: JMS Exception sending to queue null
at com.ford.vista.integration.communicator.JmsMessagingCommunicator.send(JmsMessagingCommunicator.java:149)
at com.ford.vista.integration.communicator.JmsMessagingCommunicator.sendAndReceive(JmsMessagingCommunicator.java:82)
at com.ford.vista.integration.exinterface.service.ExternalInterfaceServiceBase.sendAndReceive(ExternalInterfaceServiceBase.java:80)
at com.ford.vista.integration.exinterface.service.ExternalInterfaceServiceBase.sendAndReceive(ExternalInterfaceServiceBase.java:49)
at com.ford.vista.integration.exinterface.service.CustomerInterfaceService.requestCustomerDetails(CustomerInterfaceService.java:124)
at com.ford.vista.integration.exinterface.service.InterfaceService.requestCustomerDetails(InterfaceService.java:355)
at com.ford.vista.business.customer.service.CustomerService.requestCustomerDetails(CustomerService.java:145)
at com.ford.vista.business.contract.helper.ContractBusinessFactory.convertContractCustomerListWithCustomer(ContractBusinessFactory.java:516)
at com.ford.vista.business.contract.helper.ContractBusinessFactory.createContractDTOWithCustomer(ContractBusinessFactory.java:332)
at com.ford.vista.business.contract.service.ContractService.getContractDetails(ContractService.java:154)
at com.ford.vista.business.order.helper.OrderBusinessFactory.addContractData(OrderBusinessFactory.java:1087)
at com.ford.vista.business.order.helper.OrderBusinessFactory.createOrderDetailsDto(OrderBusinessFactory.java:542)
at com.ford.vista.business.order.service.OrderService.getOrderByNumber(OrderService.java:888)
at com.ford.vista.business.order.helper.OrderPublishFactory.createOrderPublishRequestDTO(OrderPublishFactory.java:93)
at com.ford.vista.business.order.service.OrderPublishService.createPublishEntry(OrderPublishService.java:222)
at com.ford.vista.business.order.service.OrderPublishService.processOrderPublishing(OrderPublishService.java:157)
at java.lang.reflect.Method.invoke(Native Method)
at com.ford.vista.business.common.VistaProxy.invoke(VistaProxy.java:107)
at $Proxy2.processOrderPublishing(Unknown Source)
at com.ford.vista.business.order.delegate.OrderTransactionBusinessDelegate.changeStatusEvent(OrderTransactionBusinessDelegate.java:340)
at com.ford.vista.integration.exinterface.service.MdbOagisInterfaceService.callService(MdbOagisInterfaceService.java:97)
at com.ford.vista.integration.exinterface.service.MdbInterfaceService.processMessage(MdbInterfaceService.java:178)
at com.ford.vista.integration.exinterface.service.MdbInterfaceService.processMessage(MdbInterfaceService.java:97)
at com.ford.vista.webservice.VistaTransactionWebService.processRequest(VistaTransactionWebService.java:61)
at com.ford.vista.webservice.VistaBaseWebService.doPost(VistaBaseWebService.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:61)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1064)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:598)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:206)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:80)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:214)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:623)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:457)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
--- nested ---
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for ''
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:998)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:707)
at com.ibm.mq.jms.MQQueueConnection.(MQQueueConnection.java:206)
at com.ibm.mq.jms.MQQueueConnection.(MQQueueConnection.java:76)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:143)
at com.ford.vista.integration.communicator.JmsMessagingCommunicator.createQueueSession(JmsMessagingCommunicator.java:488)
at com.ford.vista.integration.communicator.JmsMessagingCommunicator.send(JmsMessagingCommunicator.java:134)
at com.ford.vista.integration.communicator.JmsMessagingCommunicator.sendAndReceive(JmsMessagingCommunicator.java:82)
at com.ford.vista.integration.exinterface.service.ExternalInterfaceServiceBase.sendAndReceive(ExternalInterfaceServiceBase.java:80)
at com.ford.vista.integration.exinterface.service.ExternalInterfaceServiceBase.sendAndReceive(ExternalInterfaceServiceBase.java:49)
at com.ford.vista.integration.exinterface.service.CustomerInterfaceService.requestCustomerDetails(CustomerInterfaceService.java:124)
at com.ford.vista.integration.exinterface.service.InterfaceService.requestCustomerDetails(InterfaceService.java:355)
at com.ford.vista.business.customer.service.CustomerService.requestCustomerDetails(CustomerService.java:145)
at com.ford.vista.business.contract.helper.ContractBusinessFactory.convertContractCustomerListWithCustomer(ContractBusinessFactory.java:516)
at com.ford.vista.business.contract.helper.ContractBusinessFactory.createContractDTOWithCustomer(ContractBusinessFactory.java:332)
at com.ford.vista.business.contract.service.ContractService.getContractDetails(ContractService.java:154)
at com.ford.vista.business.order.hel
Regards,
P.Prasanna. -
Weblogic: problem with JMS foreign server and Transaction
Hello everyone,
I am working with an enterprise application with Web Application Server Logic 10.3. L 'application uses the following components:
1) MDB 2.0
2) FOREIGN JMS SERVER -> WebSpereMQ
3) EJB SESSION
L 'MDB calls the session bean which uses in its ejb-jar.xml using a Wrapper for JMS QueueConnectionFactory with res-ref:
<resource- ref>
<res-ref-name> jms / iss / QCFIXP </ res-ref-name>
<res-auth> Container </ res-auth>
<res-sharing -scope> Shareable </ res-sharing-scope>
<resource- ref>
The MDB is CMT
<transaction-type> Container </ transaction-type>
while the session bean is BMT
<transaction-type> Bean </ transaction-type>
to call the QCFIXP in its transaction.
The QCFIXP ii an XA resource
When there is a rollback operation in SessionBean also in 'MDB
There 'an operation setRollbackOnly:
getMessageDrivenContext (). setRollbackOnly ();
After this operation on the MDB I do a JNDI look up the QueueConnectionFactory but sending the message on a queue I get the following exception:
javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA:
But if not using the "wrapper jms" in the session bean I did not take any exception and the application don' t have any error.
My doubt is :
Why if I use the JMS wrapper I get an error javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA?
Thanks in advance.
Michele
Edited by: user3501731 on 11-mag-2011 3.16Hi Tom,
Thanks very much for your responses and careful analysis you've done.
Following the source code of the MDB where error occurs.
Marked In bold the line where the exception is thrown.
public void onMessage(Message msg) {
// Utility.logger(AP.DEBUG, "Partito MDB 2");
processa(msg);
protected void processa(Message msg) {
Utility.logger(
AP.DEBUG,
"IXPReceiverMDB7.processa(Message msg) partito");
try {
long start = System.currentTimeMillis();
/* Utility.logger(
AP.DEBUG,
"IXPReceiverMDB.processa(Message msg) effettuo lookup");*/
ejb = myEjbLocalHome.create();
// individuo l'identificativo del messaggio in ricezione
String msgid = msg.getJMSMessageID();
Utility.logger(
AP.DEBUG,
"IXPReceiverMDB7.processa(Message msg) elaboro messaggio:"
+ msgid);
String charset = msg.getStringProperty("JMS_IBM_Character_Set");
Utility.logger(
AP.DEBUG,
"IXPReceiverMDB7.processa Charset:" + charset );
// invoco il processo di ricezione
boolean commitRequested = ejb.processa(ctlReq, encoding, msg);
// il valore di ritorno del processo di ricezione identifica o meno
// la necessita' di effettuare il rollback dell'intero processo
if (!commitRequested) {
getMessageDrivenContext().setRollbackOnly();
if (ctlReq) {
Utility.logger(
AP.INFO,
"IXPReceiverMDB7.processa(Message msg) spedisco il messaggio pilota del 'cleaning' con JMSCorrelationID = '"
+ msgid
+ "'");
msg.setJMSCorrelationID(msgid);
// Viene creata la QueueConnection
QueueConnectionFactory factory =
JmsFactoryDispenser.getSingleton().getFactory();
QueueConnection connection = factory.createQueueConnection();
// Viene ottenuta la 'session'
QueueSession session =
connection.createQueueSession(
false,
Session.AUTO_ACKNOWLEDGE);
// spedisco il messaggio sulla coda abbinata al processo di 'cleaning'
// della coda di controllo
IXPMessageManager msgManager = new IXPMessageManager(session);
msgManager.spedisci(msg, AP.PILOTQUEUE, "J", AP.STD_MESSAGE); session.close();
connection.close();
long end = System.currentTimeMillis();
Long durata = new Long (end - start);
Utility.logger(
AP.INFO,
"IXPReceiverMDB7 Tempo totale elaborazione messaggio: " +
msgid + " " +
durata.toString() + " mill" );
Utility.logger(
AP.DEBUG,
"IXPReceiverMDB7.processa(Message msg) terminato");
} catch (Throwable e) {
getMessageDrivenContext().setRollbackOnly();
try {
Utility.myExceptionHandler(
"E",
"1",
"4028",
"IXPReceiverMDB.onMessage()",
e);
} catch (Throwable ex) {
ex.printStackTrace();
Thanks in advance.
Edited by: serpichetto on 16-mag-2011 1.24 -
Problem with creation of the jms event generator
hi,
I have set up a weblogic workshop instance on one of my machines. It has a queue call OUT.QUEUE. The application writes message to this queue. I have set up an integration instance on another machine. I have created a Foreign JMS server to point to the first machine. I have also configured a queue which points to the one on the first machine. However when my integration server starts up, I keep getting the error.
[EJB:010196]'weblogic.jms.common.JMSException: Error creating session' Linked exception = 'weblogic.jms.dispatcher.DispatcherException: could not find JMS Server portalServer'
weblogic.jms.common.JMSException: Error creating session
at weblogic.jms.frontend.FESession.setUpBackEndSession(Lweblogic/jms/dispatcher/DispatcherId;)Lweblogic/jms/common/Sequencer;(FESession.java:809)
at weblogic.jms.frontend.FESession.consumerCreate(Lweblogic/jms/frontend/FEConsumerCreateRequest;)I(FESession.java:1049)
at weblogic.jms.frontend.FESession.invoke(Lweblogic/jms/dispatcher/Request;)I(FESession.java:2573)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine()Lweblogic/jms/dispatcher/Response;(Request.java:643)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(Lweblogic/jms/dispatcher/Request;)Lweblogic/jms/dispatcher/Response;(DispatcherImpl.java:179)
at weblogic.jms.client.JMSSession.consumerCreate(Ljava/lang/String;Lweblogic/jms/common/DestinationImpl;Ljava/lang/String;ZI)Lweblogic/jms/frontend/FEConsumerCreateResponse;(JMSSession.java:1860)
at weblogic.jms.client.JMSSession.createConsumer(Ljavax/jms/Destination;Ljava/lang/String;ZLjava/lang/String;B)Ljavax/jms/MessageConsumer;(JMSSession.java:1691)
at weblogic.jms.client.JMSSession.createReceiver(Ljavax/jms/Queue;Ljava/lang/String;)Ljavax/jms/QueueReceiver;(JMSSession.java:1530)
at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(Ljavax/jms/Destination;Ljava/lang/String;III)V(JMSConnectionPoller.java:1767)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection()V(JMSConnectionPoller.java:2119)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS()V(JMSConnectionPoller.java:1192)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(Lweblogic/time/common/Schedulable;)V(JMSConnectionPoller.java:984)
at weblogic.time.common.internal.ScheduledTrigger.run()Ljava/lang/Object;(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally()V(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:50)
at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
Caused by: weblogic.jms.dispatcher.DispatcherException: could not find JMS Server portalServer
at weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(Lweblogic/jms/dispatcher/DispatcherId;)Lweblogic/jms/dispatcher/Dispatcher;(DispatcherManager.java:318)
at weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(Lweblogic/jms/dispatcher/DispatcherId;)Lweblogic/jms/dispatcher/Dispatcher;(DispatcherManager.java:368)
at weblogic.jms.frontend.FESession.setUpBackEndSession(Lweblogic/jms/dispatcher/DispatcherId;)Lweblogic/jms/common/Sequencer;(FESession.java:807)
... 20 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.S:portalServer' Resolved weblogic.jms; remaining name 'S:portalServer'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Ljava/lang/String;Ljava/lang/String;Ljava/util/Hashtable;)Ljavax/naming/NameNotFoundException;(BasicNamingNode.java:924)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(Ljava/lang/String;Ljava/util/Hashtable;Ljava/lang/String;)Ljava/lang/Object;(BasicNamingNode.java:230)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(Ljava/lang/String;Ljava/util/Hashtable;Ljava/lang/String;)Ljava/lang/Object;(ServerNamingNode.java:154)
at weblogic.jndi.internal.BasicNamingNode.lookup(Ljava/lang/String;Ljava/util/Hashtable;)Ljava/lang/Object;(BasicNamingNode.java:188)
at weblogic.jndi.internal.BasicNamingNode.lookup(Ljava/lang/String;Ljava/util/Hashtable;)Ljava/lang/Object;(BasicNamingNode.java:196)
at weblogic.jndi.internal.BasicNamingNode.lookup(Ljava/lang/String;Ljava/util/Hashtable;)Ljava/lang/Object;(BasicNamingNode.java:196)
at weblogic.jndi.internal.WLEventContextImpl.lookup(Ljavax/naming/Name;Ljava/lang/String;)Ljava/lang/Object;(WLEventContextImpl.java:256)
at weblogic.jndi.internal.WLContextImpl.lookup(Ljava/lang/String;)Ljava/lang/Object;(WLContextImpl.java:363)
at javax.naming.InitialContext.lookup(Ljava/lang/String;)Ljava/lang/Object;(InitialContext.java:347)
at weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(Lweblogic/jms/dispatcher/DispatcherId;)Lweblogic/jms/dispatcher/Dispatcher;(DispatcherManager.java:314)
... 22 more
Any ideas?Hi experts/Sriram...
Thanks for the reply.
The -
>showing the line....
QS80_TAB-DEDMT=QS80_TAB-DEDMT+S80-DEDMT
Where should we change to get rid of this runtime error.
Here in my quality everthing is fine and we have uploaded patches in quality upto recent one sp80.But in prod. the patchlevel is sp71.Will it be the reason.
Please advice me on this as i have to complete the issue of F16.
Thanks and Regards,
V Sai. -
Exception in setting up message-driven bean container: [MQJMS1010: not impl
Problem
=======
We are trying to configure and deploy a Message Driven
Bean to listen on a WebSphere MQ queue, using LDAP to
share knowledge of the Queue & Connection Factory.
But when we start the Sun One domain we get an exception:
javax.jms.JMSException: MQJMS1010: not implemented
(see log file at the end of this email)
Can anybody help please ?
The configuration of the various components are listed
below:
WebSphere MQ Configuration
==========================
Version 5.3
Queue Manager
QM_Test
Queues
PATH_MFP.Case.Request
Queue Type: Local
Channels
Channel_Test
Channel Type: Server Connection
Protocol Type: TCP/IP
LDAP configuration
==================
ldap://localhost/o=mqtest
cn=MFP_LOCAL_Factory
javaFactory=com.ibm.mq.jms.MQQueueConnectionFactoryFactory
javaClassName=com.ibm.mq.jms.MQQueueConnectionFactory
javaReferenceAddress=#3#QMGR#QM_Test
javaReferenceAddress=#6#CHAN#Channel_Test
javaReferenceAddress=#14#TM#SYSTEM.DEFAULT.MODEL.QUEUE
cn=MFP_LOCAL_Case_Request_Queue
javaFactory=com.ibm.mq.jms.MQQueueFactory
javaClassName=com.ibm.mq.jms.MQQueue
javaReferenceAddress=#9#QU#PATH_MFP.Case.Request
javaReferenceAddress=#10#QMGR#QM_Test
EJB configuration
=================
ejb-jar.xml
<message-driven>
<display-name>ServerMessageDrivenBean</display-name>
<ejb-name>ServerMessageDrivenBean</ejb-name>
<ejb-class>nz.co.acc.emi.server.connector.mdb.ServerMessageDrivenBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
sun-ejb-jar.xml
<ejb>
<ejb-name>ServerMessageDrivenBean</ejb-name>
<jndi-name>MFP_LOCAL_Case_Request_Queue</jndi-name>
<mdb-connection-factory>
<jndi-name>MFP_LOCAL_Factory</jndi-name>
</mdb-connection-factory>
</ejb>
Sun One configuration
=====================
MFPProcessing: JNDI: External Resources
MFP_LOCAL_Factory Enabled javax.jms.QueueConnectionFactory
JNDI Name: MFP_LOCAL_Factory
Resource Type: javax.jms.QueueConnectionFactory
JNDI Lookup: cn=MFP_LOCAL_Factory
Factoryclass: com.sun.jndi.ldap.LdapCtxFactory
Properties:
java.naming.provider.url ldap://localhost:389/o=mqtest
java.naming.security.authentication none
MFP_LOCAL_Case_Request_Queue Enabled javax.jms.Queue
JNDI Name: MFP_LOCAL_Case_Request_Queue
Resource Type: javax.jms.Queue
JNDI Lookup: cn=MFP_LOCAL_Case_Request_Queue
Factoryclass: com.sun.jndi.ldap.LdapCtxFactory
Properties:
java.naming.provider.url ldap://localhost:389/o=mqtest
server.xml
<mdb-container steady-pool-size="10" pool-resize-quantity="2" max-pool-size="60" idle-timeout-in-seconds="600" monitoring-enabled="true" log-level="FINEST" />
<jms-service port="1240" admin-user-name="admin" admin-password="admin" init-timeout-in-seconds="30" enabled="true" log-level="FINE" />
Sun One log file
================
server.log
[01/Mar/2004:10:06:48] INFO ( 657): CORE1116: Sun ONE Application Server 7.0.0_01
[01/Mar/2004:10:06:51] INFO ( 657): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2_01] from [Sun Microsystems Inc.]
[01/Mar/2004:10:07:09] INFO ( 657): JMS5023: JMS service successfully started. Instance Name = domain1_MFPProcessing, Home = [C:/Sun/AppServer7/imq/bin].
[01/Mar/2004:10:07:13] INFO ( 657): JTS5014: Recoverable JTS instance, serverId = [100]
[01/Mar/2004:10:07:14] INFO ( 657): RAR5060: Install JDBC Datasources ...
[01/Mar/2004:10:07:14] INFO ( 657): RAR5059: Binding [JDBC DataSource Name: jdbc/MfsDataSourceJConn, Pool Name: MFSConnectionPool]
[01/Mar/2004:10:07:15] INFO ( 657): JMS5015: Install JMS resources ...
[01/Mar/2004:10:07:47] WARNING ( 657): [EntityContainer] Created EntityContainer....
[01/Mar/2004:10:07:49] INFO ( 657): LDR5010: All ejb(s) of [mfs] loaded successfully!
[01/Mar/2004:10:07:52] INFO ( 657): MDB00044: Deploying message-driven bean [emi:ServerMessageDrivenBean], consuming from [MFP_LOCAL_Case_Request_Queue]
[01/Mar/2004:10:07:52] FINE ( 657): Messages delivery is part of a container-managed tx
[01/Mar/2004:10:07:52] FINE ( 657): emi:ServerMessageDrivenBean:reconnect-delay-in-seconds=60, reconnect-max-retries=60, reconnect-enabled=true
[01/Mar/2004:10:07:53] INFO ( 657): MDB00028: [emi:ServerMessageDrivenBean]: Message-driven bean container using external connection factory object: [com.ibm.mq.jms.MQQueueConnectionFactory]
[01/Mar/2004:10:07:55] FINE ( 657): emi:ServerMessageDrivenBean: Setting message-driven bean pool max-pool-size=60, steady-pool-size=10, pool-resize-quantity=2, idle-timeout-in-seconds=600
[01/Mar/2004:10:07:55] FINE ( 657): Initializing server session factory
[01/Mar/2004:10:07:55] FINE ( 657): Created server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@11576d7
[01/Mar/2004:10:07:55] FINE ( 657): Created server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@2d5534
[01/Mar/2004:10:07:55] FINE ( 657): Created server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@34d75f
[01/Mar/2004:10:07:55] FINE ( 657): Created server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@127d15e
[01/Mar/2004:10:07:55] FINE ( 657): Created server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@12297d7
[01/Mar/2004:10:07:55] FINE ( 657): Created server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@1ecfeb
[01/Mar/2004:10:07:55] FINEST ( 657): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@11576d7
[01/Mar/2004:10:07:55] FINEST ( 657): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@2d5534
[01/Mar/2004:10:07:55] FINEST ( 657): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@34d75f
[01/Mar/2004:10:07:55] FINEST ( 657): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@127d15e
[01/Mar/2004:10:07:55] FINEST ( 657): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@12297d7
[01/Mar/2004:10:07:55] FINEST ( 657): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@1ecfeb
[01/Mar/2004:10:07:55] FINE ( 657): Created server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@e4776b
[01/Mar/2004:10:07:55] FINE ( 657): Created server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@15c458c
[01/Mar/2004:10:07:55] FINE ( 657): Created server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@da1515
[01/Mar/2004:10:07:55] FINE ( 657): Created server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@19e3e24
[01/Mar/2004:10:07:55] FINEST ( 657): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@e4776b
[01/Mar/2004:10:07:55] FINEST ( 657): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@15c458c
[01/Mar/2004:10:07:55] FINEST ( 657): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@da1515
[01/Mar/2004:10:07:55] FINEST ( 657): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@19e3e24
[01/Mar/2004:10:07:55] INFO ( 657): MDB0001: Create message-driven bean pool with maximum pool size [60], bean idle timeout [600] seconds
[01/Mar/2004:10:07:55] SEVERE ( 657): MDB00030: [emi:ServerMessageDrivenBean]: Exception in setting up message-driven bean container: [MQJMS1010: not implemented]
[01/Mar/2004:10:07:55] FINE ( 657): MDB00018: [emi:ServerMessageDrivenBean]: Closing message-driven bean container connection
[01/Mar/2004:10:07:55] WARNING ( 657): [AbstractPool]: Cancelled pool timer task at: Mon Mar 01 10:07:55 NZDT 2004
[01/Mar/2004:10:07:55] FINEST ( 657): Thread[main,5,main]: in cleanup() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@11576d7
[01/Mar/2004:10:07:55] FINE ( 657): Destroyed server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@11576d7
[01/Mar/2004:10:07:55] FINEST ( 657): Thread[main,5,main]: in cleanup() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@2d5534
[01/Mar/2004:10:07:55] FINEST ( 657): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@2d5534
[01/Mar/2004:10:07:55] FINE ( 657): Destroyed server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@2d5534
[01/Mar/2004:10:07:55] FINEST ( 657): Thread[main,5,main]: in cleanup() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@34d75f
[01/Mar/2004:10:07:55] FINE ( 657): Destroyed server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@34d75f
[01/Mar/2004:10:07:55] FINEST ( 657): Thread[main,5,main]: in cleanup() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@127d15e
[01/Mar/2004:10:07:55] FINE ( 657): Destroyed server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@127d15e
[01/Mar/2004:10:07:55] FINEST ( 657): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@127d15e
[01/Mar/2004:10:07:55] FINEST ( 657): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@11576d7
[01/Mar/2004:10:07:55] FINEST ( 657): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@34d75f
[01/Mar/2004:10:07:55] FINEST ( 657): Thread[main,5,main]: in cleanup() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@12297d7
[01/Mar/2004:10:07:55] FINE ( 657): Destroyed server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@12297d7
[01/Mar/2004:10:07:55] FINEST ( 657): Thread[main,5,main]: in cleanup() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@1ecfeb
[01/Mar/2004:10:07:55] FINE ( 657): Destroyed server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@1ecfeb
[01/Mar/2004:10:07:55] FINEST ( 657): Thread[main,5,main]: in cleanup() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@e4776b
[01/Mar/2004:10:07:55] FINEST ( 657): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@e4776b
[01/Mar/2004:10:07:55] FINEST ( 657): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@12297d7
[01/Mar/2004:10:07:55] FINE ( 657): Destroyed server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@e4776b
[01/Mar/2004:10:07:55] FINEST ( 657): Thread[main,5,main]: in cleanup() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@15c458c
[01/Mar/2004:10:07:55] FINE ( 657): Destroyed server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@15c458c
[01/Mar/2004:10:07:55] FINEST ( 657): Thread[main,5,main]: in cleanup() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@da1515
[01/Mar/2004:10:07:55] FINE ( 657): Destroyed server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@da1515
[01/Mar/2004:10:07:55] FINEST ( 657): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@1ecfeb
[01/Mar/2004:10:07:55] FINEST ( 657): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@15c458c
[01/Mar/2004:10:07:55] FINEST ( 657): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@da1515
[01/Mar/2004:10:07:55] FINEST ( 657): Thread[main,5,main]: in cleanup() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@19e3e24
[01/Mar/2004:10:07:55] FINE ( 657): Destroyed server session: com.iplanet.ias.ejb.containers.IASServerSessionImpl@19e3e24
[01/Mar/2004:10:07:55] SEVERE ( 657): MDB00017: [ServerMessageDrivenBean]: Exception in creating message-driven bean container: [javax.jms.JMSException: MQJMS1010: not implemented]
[01/Mar/2004:10:07:55] FINEST ( 657): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@19e3e24
[01/Mar/2004:10:07:55] SEVERE ( 657): javax.jms.JMSException
javax.jms.JMSException: MQJMS1010: not implemented
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:418)
at com.ibm.mq.jms.MQQueueConnection.createConnectionConsumer(MQQueueConnection.java:602)
at com.sun.enterprise.jms.ConnectionWrapperBase.createConnectionConsumer(ConnectionWrapperBase.java:151)
at com.sun.ejb.containers.MessageBeanHelperQueueImpl.doSetup(MessageBeanHelperQueueImpl.java:67)
at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:419)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:206)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:173)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:345)
at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:81)
at com.iplanet.ias.server.AbstractManager.load(AbstractManager.java:134)
at com.iplanet.ias.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:168)
at com.iplanet.ias.server.ApplicationServer.onStartup(ApplicationServer.java:269)
at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:162)
[01/Mar/2004:10:07:55] SEVERE ( 657): EJB5090: Exception in creating EJB container [javax.jms.JMSException: MQJMS1010: not implemented]
[01/Mar/2004:10:07:55] SEVERE ( 657): appId=emi moduleName=emiEjb_jar ejbName=ServerMessageDrivenBean
[01/Mar/2004:10:07:55] SEVERE ( 657): LDR5004: UnExpected error occured while creating ejb container
javax.jms.JMSException: MQJMS1010: not implemented
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:418)
at com.ibm.mq.jms.MQQueueConnection.createConnectionConsumer(MQQueueConnection.java:602)
at com.sun.enterprise.jms.ConnectionWrapperBase.createConnectionConsumer(ConnectionWrapperBase.java:151)
at com.sun.ejb.containers.MessageBeanHelperQueueImpl.doSetup(MessageBeanHelperQueueImpl.java:67)
at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:419)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:206)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:173)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:345)
at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:81)
at com.iplanet.ias.server.AbstractManager.load(AbstractManager.java:134)
at com.iplanet.ias.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:168)
at com.iplanet.ias.server.ApplicationServer.onStartup(ApplicationServer.java:269)
at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:162)
[01/Mar/2004:10:07:55] WARNING ( 657): CORE5021: Application NOT loaded: [emi]
[01/Mar/2004:10:07:55] INFO ( 657): WEB0100: Loading web module [mfs:mfs.war] in virtual server [MFPProcessing] at [mfs]
[01/Mar/2004:10:08:31] INFO ( 657): HTTP3072: HTTP listener http-listener-1 [http://ch042dysz0405:1080] ready to accept requests
[01/Mar/2004:10:08:31] INFO ( 657): CORE3274: successful server startup
[01/Mar/2004:10:08:33] INFO ( 657): CORE5053: Application onReady complete.Hi,
You have not created the jms destination queue object
jms/Warehouse
Your server logs says it cannot find the destination queue object.It has got nothing to do with jndi name of your bean
Create jms destination queue object using
asadmin>create-jms-resource instance <instance_name> resourcetype javax.jms.Queue --property imqDestinationName=<NAme> jms/Warehouse
Then use list-jms-resources <instance_name> to
find if jms/Warehouse destionation queue object has been created.
Get back in case of any issues
Maybe you are looking for
-
My problem is that I have been a Mobile Me user for the past couple of years, and because of that a second Apple ID was generated in addition to the one I've been using for years. When iCloud was introduced last fall I did everything I was supposed t
-
How do I reverse the displays?
I see how to rearrange the displays but how do I reverse them?
-
New JAAS Logon Module that calls RFC: Urgent
I want to build a new logon module that extends AbstractLoginModule. I want to call an RFC in ECC using JCA in this logon module. The purpose of this RFC call is to read the users roles in the backend, if they have a certain role I will dynamically a
-
Anyconnect for VPN Phone url redirect on FiOS
Hello, I have an ASA setup with Anyconnect for VPN Phone. The setup works great on comcast but for some reason the phone fails on FiOS and we cannot figure out why. I typed the url the phone uses into a web browser: https://< ip address of ASA>/VPN
-
Can I create a "play" button in the Tag Inspector extension
Hello, I am creating a Tag Inspector extension for changing the properties of a customized swf files. Can I create a "play" button in the property panel to preview the swf movie? I've checked the "Inspectors" folder in the "configuration" and cant fi