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
Tks

Probably 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

Similar Messages

  • JMS Exception DisconnectMonitor timed out after 299s.

    Hi,
    Could anone please suggest regarding below exception and the parameter which can be configured for this timeout in JMS.
    Thanks,
    JMS exception class = java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
    weblogic.jms.common.LostServerException: java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
         at weblogic.jms.client.JMSConnection.dispatcherPeerGone(JMSConnection.java:1436)
         at weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapperState.java:692)
         at weblogic.messaging.dispatcher.DispatcherWrapperState.timerExpired(DispatcherWrapperState.java:617)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.ExecuteThreadLite.execute(ExecuteThreadLite.java:72)
         at weblogic.work.ExecuteThreadLite.run(ExecuteThreadLite.java:56)
    Caused by: java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
         at weblogic.messaging.dispatcher.DispatcherWrapperState.onDisconnect(DispatcherWrapperState.java:396)
         at weblogic.rmi.extensions.AbstractDisconnectMonitorDelegate.deliverDisconnectEvent(AbstractDisconnectMonitorDelegate.java:156)
         at weblogic.rmi.extensions.AbstractDisconnectMonitorDelegate.access$400(AbstractDisconnectMonitorDelegate.java:25)
         at weblogic.rmi.extensions.AbstractDisconnectMonitorDelegate$Timer.run(AbstractDisconnectMonitorDelegate.java:234)
         at java.lang.Thread.run(Unknown Source)

    Hi,
    The Error message :
    JMS exception class = java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
    Indicates that the server hosting the remote JMS resource has been disconnected and a Disconnection error message has been delivered to the JMS resource listerners.
    This can happen due to following reasons:
    1: The network connection has gone down in such a way that only Weblogic's internal heartbeat mechanism manages to detect the problem. Among other possibilities, this can be due to a hardware failure, server crash, or even an overly enthusiastic firewall.
    2: You have a slow network connection and are receiving a very large message, so Weblogic's internal heartbeats fail to get through (they end up queued up behind the large message).
    This causes Weblogic to think the connection is lost even though it is actively receiving packets.
    you can try increasing the following JMS property values:
    Click on the Name of the server (On which you have deployed your application and queues etc...)in the left Pane
    Goto --> Protocols-->General--> Advanced Options
    Increase the following Parameters
    Complete Message Timeout:
    Idle Connection Timeout:
    Maximum Message Size:
    Thanks,
    Sandeep

  • BC4J send messaging adapter gets JMS exception

    Running a 9i standalone application based on BC4J. The following code is trying to send a single VO to an 8i queue. Note: prior to entering this routine, I have already called the .writeXML() method on the same VO and looked at the text and the XML all looks great.
    AdapterMessage[] msgs = new AdapterMessage[1];
    try {
    // set up queue connection
    msgs[0] = AdapterMessage.newViewObjectMessage( vo );
    sendMessage( msgs );
    public void sendMessage( AdapterMessage[] messages)
    try
    ApplicationModule am = QWsetup.ApplicationModule();
    BC4JSendingAdapter adapter = new BC4JSendingAdapter();
    adapter.setShowTrace(true);
    adapter.sendMessage( am, messages);
    catch(AdapterFailureException e)
    System.err.println("sendMessage error: "+e.getMessage()+"\n"+
    e.getOriginalException());
    e.printStackTrace();
    I step into the adapter.sendMessage line and get the following in my message window...
    [2] Creating JDBC Connection...
    [3] oracle.jdbc.driver.OracleDriver
    [4] jdbc:oracle:thin:@pgia05.pginw.com:1521:qmpgit
    [5] Creating Topic Connection...
    [6] Creating Topic Session...
    [7] Creating Topic...
    [8] Publishing message...
    [9] Done.
    sendMessage error: JMS exception while processing message
    java.lang.NullPointerException

    Hi Roger,
    I've been looking into your error message: JMS Exception while processing message.
    I was able to reproduce this error message. In my case I was trying to send a BESAdapter message without setting its mandatory properties. My code was:
    BESAdapterMessage a = (BESAdapterMessage)BESAdapterMessage.newViewObjectMessage(empvo);
    BESAdapterMessage[] messages = new BESAdapterMessage[] {a};
    try
    am.sendMessage(messages);
    There are two mandatory properies of the adapter that must be set that I forgot. I found the answer in the help. If you do a search for BESAdapterMessage you will find page Using the Adapter Message class for message payloads. Scroll down this page to the section: Using the BESAdapterMessage Subclass.
    Although you are using the adapter classes without the modeler you may find some of the other help topics in the UML Modeling Help useful. Look under Modeling Activities for e-business Integration -> Creating Messaging Adapters.
    I have raised a bug to put more validation in so that the error message will specify that properties have not been sent. Here is the abstract from help:
    The BESAdapterMessage class (oracle.bm.ebiadapters.BESAdapterMessage) is a subclass of AdapterMessage. It provides additional functionality which is needed by the e-business integration generators to achieve full integration. In addition to setting the payload, the BESAdapterMessage class allows you to set metadata properties which are mapped to JMS header fields. Some of these properties are mandatory and some are optional. For example, the setEventName(String eventName) and setEventKey(String eventKey) methods can be used to set the mandatory Event Name and Event Key properties. Once set, these properties are mapped to JMS header properties to allow the JMS messages to be correctly propagated between Oracle AQ queues.
    I've also raised a doc. bug to look again at the doc in this area.
    Thank you very much for taking the time to report on this problem. We are reliant on input from people like you to continue to improve our product.
    Rgds
    Susan

  • For which JMS exceptions do I have to reconnect?

    Hi,
              I have a plain Java application that listens to a JMS queue on BEA WebLogic 7.0. I would like to automatically reconnect whenever it is necessary, e.g. in case of a restart.
              My question: Is it necessary to reconnect whenever an JMS exception is received in the ExceptionListeners of the Connection/Session?
              Or in other words: Can/Should I call the reconnect code (close session, close connection, connect again) on all exceptions that I receive in the listeners or are there some exceptions that can/should be ignored, e.g. there was some problem that is signaled to the listeners but the connection/session/queue is still working and reconnecting can be avoided?
              If so, how can the "serious" exceptions be determined? By the type (e.g. weblogic.jms.common.LostServerException)?
              Of course, I would like to avoid a reconnect, because it seems to be an expensive call.
              Thanks for any help,
              Peter

    I think that except in the cases of multicast pub/sub "DataOverrun" and "SequenceGap" exceptions and applications that throw RuntimeExceptions or Errors from "onMessage()" , exception listeners exceptions are infrequent and, in my experience, pretty much always indicative of a true failure that requires reconnect (machine or server failure).
              Unfortunately, I don't think there is a way to distinguish application generated RuntimeExceptions/Errors from other JMS exceptions thrown to onException(). (Best practice, don't allow apps to do this.)

  • Resend message after catching JMS Exception

    Hi,
    If i resend message after catching JMS Exception is there any chance that the message will be send to the destination queue? (without reconnecting to the queue).
    thanks!

    The problem is you don't really know if its already been sent or not. Then if the broker's gone down you need to recreate your connection, sessions, producers, consumers etc.
    Its much easier to just use a JMS provider which supports auto-reconnection for you which totally hides and fixes all these problems
    http://activemq.apache.org/how-can-i-support-auto-reconnection.html
    James
    http://logicblaze.com/
    Open Source SOA

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

  • 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}&lt;Warning&gt; &lt;EJB&gt; &lt;BEA-010061&gt;
    &lt;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&gt;{color}
    Configuration Details:
    ##config.xml:
    &lt;?xml version='1.0' encoding='UTF-8'?&gt;
    &lt;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]"&gt;
    &lt;name&gt;efpdomain&lt;/name&gt;
    &lt;domain-version&gt;10.3.0.0&lt;/domain-version&gt;
    &lt;security-configuration&gt;
    &lt;name&gt;efpdomain&lt;/name&gt;
    &lt;realm&gt;
    &lt;sec:authentication-provider xsi:type="wls:default-authenticatorType"&gt;&lt;/sec:authentication-provider&gt;
    &lt;sec:authentication-provider xsi:type="wls:default-identity-asserterType"&gt;
    &lt;sec:active-type&gt;AuthenticatedUser&lt;/sec:active-type&gt;
    &lt;/sec:authentication-provider&gt;
    &lt;sec:role-mapper xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"&gt;&lt;/sec:role-mapper&gt;
    &lt;sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-authorizerType"&gt;&lt;/sec:authorizer&gt;
    &lt;sec:adjudicator xsi:type="wls:default-adjudicatorType"&gt;&lt;/sec:adjudicator&gt;
    &lt;sec:credential-mapper xsi:type="wls:default-credential-mapperType"&gt;&lt;/sec:credential-mapper&gt;
    &lt;sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"&gt;&lt;/sec:cert-path-provider&gt;
    &lt;sec:cert-path-builder&gt;WebLogicCertPathProvider&lt;/sec:cert-path-builder&gt;
    &lt;sec:name&gt;myrealm&lt;/sec:name&gt;
    &lt;/realm&gt;
    &lt;default-realm&gt;myrealm&lt;/default-realm&gt;
    &lt;credential-encrypted&gt;{3DES}hcdd+yZGXk5DHgRKqCM7E86l4+VxPcZ9Ut7rB6WaXqMyvbtDjDUKNCKbMQdCN/BEYCv5E0N4Hms9kntfqhaduDO1WGMtbmJL&lt;/credential-encrypted&gt;
    &lt;node-manager-username&gt;weblogic&lt;/node-manager-username&gt;
    &lt;node-manager-password-encrypted&gt;{3DES}Q2xO0EiChbay/HkRiorTjg==&lt;/node-manager-password-encrypted&gt;
    &lt;/security-configuration&gt;
    &lt;server&gt;
    &lt;name&gt;AdminServer&lt;/name&gt;
    &lt;listen-address&gt;192.168.12.240&lt;/listen-address&gt;
    &lt;/server&gt;
    &lt;server&gt;
    &lt;name&gt;efpserver_man1&lt;/name&gt;
    &lt;listen-port&gt;8011&lt;/listen-port&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;listen-address&gt;192.168.12.240&lt;/listen-address&gt;
    &lt;xml-registry&gt;XMLEFP&lt;/xml-registry&gt;
    &lt;jta-migratable-target&gt;
    &lt;user-preferred-server&gt;efpserver_man1&lt;/user-preferred-server&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;/jta-migratable-target&gt;
    &lt;/server&gt;
    &lt;server&gt;
    &lt;name&gt;efpserver_man2&lt;/name&gt;
    &lt;listen-port&gt;8012&lt;/listen-port&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;listen-address&gt;192.168.12.240&lt;/listen-address&gt;
    &lt;xml-registry&gt;XMLEFP&lt;/xml-registry&gt;
    &lt;jta-migratable-target&gt;
    &lt;user-preferred-server&gt;efpserver_man2&lt;/user-preferred-server&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;/jta-migratable-target&gt;
    &lt;/server&gt;
    &lt;cluster&gt;
    &lt;name&gt;efpcluster&lt;/name&gt;
    &lt;cluster-address&gt;192.168.12.240:8011,192.168.12.240:8012&lt;/cluster-address&gt;
    &lt;multicast-address&gt;239.192.0.0&lt;/multicast-address&gt;
    &lt;/cluster&gt;
    &lt;embedded-ldap&gt;
    &lt;name&gt;efpdomain&lt;/name&gt;
    &lt;credential-encrypted&gt;{3DES}q/XQGirHcAcgi4iwPiXIkRHP8xte4xVBgJwjM+qMwbk=&lt;/credential-encrypted&gt;
    &lt;/embedded-ldap&gt;
    &lt;configuration-version&gt;10.3.0.0&lt;/configuration-version&gt;
    &lt;app-deployment&gt;
    &lt;name&gt;efp&lt;/name&gt;
    &lt;target&gt;efpcluster&lt;/target&gt;
    &lt;module-type&gt;ear&lt;/module-type&gt;
    &lt;source-path&gt;applications\efp.ear&lt;/source-path&gt;
    &lt;security-dd-model&gt;DDOnly&lt;/security-dd-model&gt;
    &lt;/app-deployment&gt;
    &lt;xml-registry&gt;
    &lt;name&gt;XMLEFP&lt;/name&gt;
    &lt;document-builder-factory&gt;weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl&lt;/document-builder-factory&gt;
    &lt;sax-parser-factory&gt;weblogic.apache.xerces.jaxp.SAXParserFactoryImpl&lt;/sax-parser-factory&gt;
    &lt;transformer-factory&gt;weblogic.apache.xalan.processor.TransformerFactoryImpl&lt;/transformer-factory&gt;
    &lt;/xml-registry&gt;
    &lt;jms-server&gt;
    &lt;name&gt;eFpJMSServer&lt;/name&gt;
    &lt;target&gt;efpserver_man1 (migratable)&lt;/target&gt;
    &lt;persistent-store&gt;eFpJMSJDBCStore&lt;/persistent-store&gt;
    &lt;/jms-server&gt;
    &lt;jms-server&gt;
    &lt;name&gt;eFpJMSServer2&lt;/name&gt;
    &lt;target&gt;efpserver_man2 (migratable)&lt;/target&gt;
    &lt;persistent-store&gt;eFpJMSJDBCStore2&lt;/persistent-store&gt;
    &lt;/jms-server&gt;
    &lt;migratable-target&gt;
    &lt;name&gt;efpserver_man1 (migratable)&lt;/name&gt;
    &lt;notes&gt;繧ｷ繧ｹ繝・&Beta;逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶€よ焔蜍輔〒蜑企勁縺励&uarr;縺・〒縺上□縺輔＞縲・/notes&gt;
    &lt;user-preferred-server&gt;efpserver_man1&lt;/user-preferred-server&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;/migratable-target&gt;
    &lt;migratable-target&gt;
    &lt;name&gt;efpserver_man2 (migratable)&lt;/name&gt;
    &lt;notes&gt;繧ｷ繧ｹ繝・&Beta;逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶€よ焔蜍輔〒蜑企勁縺励&uarr;縺・〒縺上□縺輔＞縲・/notes&gt;
    &lt;user-preferred-server&gt;efpserver_man2&lt;/user-preferred-server&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;/migratable-target&gt;
    &lt;jdbc-store&gt;
    &lt;name&gt;eFpJMSJDBCStore&lt;/name&gt;
    &lt;prefix-name&gt;WLJMS_&lt;/prefix-name&gt;
    &lt;data-source&gt;eFpNonXADataSource&lt;/data-source&gt;
    &lt;target&gt;efpserver_man1 (migratable)&lt;/target&gt;
    &lt;/jdbc-store&gt;
    &lt;jdbc-store&gt;
    &lt;name&gt;eFpJMSJDBCStore2&lt;/name&gt;
    &lt;prefix-name&gt;WLJMS2_&lt;/prefix-name&gt;
    &lt;data-source&gt;eFpNonXADataSource&lt;/data-source&gt;
    &lt;target&gt;efpserver_man2 (migratable)&lt;/target&gt;
    &lt;/jdbc-store&gt;
    &lt;jms-system-resource&gt;
    &lt;name&gt;eFPJMS&lt;/name&gt;
    &lt;target&gt;efpcluster&lt;/target&gt;
    &lt;sub-deployment&gt;
    &lt;name&gt;eFPServer&lt;/name&gt;
    &lt;target&gt;eFpJMSServer&lt;/target&gt;
    &lt;/sub-deployment&gt;
    &lt;sub-deployment&gt;
    &lt;name&gt;eFPServer2&lt;/name&gt;
    &lt;target&gt;eFpJMSServer2&lt;/target&gt;
    &lt;/sub-deployment&gt;
    &lt;descriptor-file-name&gt;jms/efpjms-jms.xml\JMS Description-jms.xml&lt;/descriptor-file-name&gt;
    &lt;/jms-system-resource&gt;
    &lt;admin-server-name&gt;AdminServer&lt;/admin-server-name&gt;
    &lt;jdbc-system-resource&gt;
    &lt;name&gt;eFpDataSource&lt;/name&gt;
    &lt;target&gt;efpcluster&lt;/target&gt;
    &lt;descriptor-file-name&gt;jdbc/eFpDataSource-2004-jdbc.xml&lt;/descriptor-file-name&gt;
    &lt;/jdbc-system-resource&gt;
    &lt;jdbc-system-resource&gt;
    &lt;name&gt;eFpNonXADataSource&lt;/name&gt;
    &lt;target&gt;efpcluster&lt;/target&gt;
    &lt;descriptor-file-name&gt;jdbc/eFpNonXADataSource-6172-jdbc.xml&lt;/descriptor-file-name&gt;
    &lt;/jdbc-system-resource&gt;
    &lt;/domain&gt;
    ##JMS Description-jms.xml
    &lt;?xml version='1.0' encoding='UTF-8'?&gt;
    &lt;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]"&gt;
    &lt;connection-factory name="ConnectionFactory"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;jms/ConnectionFactory&lt;/jndi-name&gt;
    &lt;security-params&gt;
    &lt;attach-jmsx-user-id&gt;false&lt;/attach-jmsx-user-id&gt;
    &lt;/security-params&gt;
    &lt;/connection-factory&gt;
    &lt;connection-factory name="XAConnectionFactory"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;jms/XAConnectionFactory&lt;/jndi-name&gt;
    &lt;transaction-params&gt;
    &lt;transaction-timeout&gt;3600&lt;/transaction-timeout&gt;
    &lt;xa-connection-factory-enabled&gt;true&lt;/xa-connection-factory-enabled&gt;
    &lt;/transaction-params&gt;
    &lt;security-params&gt;
    &lt;attach-jmsx-user-id&gt;false&lt;/attach-jmsx-user-id&gt;
    &lt;/security-params&gt;
    &lt;/connection-factory&gt;
    &lt;uniform-distributed-queue name="ActiveActivityQueue"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;queue/efpActiveActivityQueue&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;forward-delay&gt;-1&lt;/forward-delay&gt;
    &lt;reset-delivery-count-on-forward&gt;true&lt;/reset-delivery-count-on-forward&gt;
    &lt;/uniform-distributed-queue&gt;
    &lt;uniform-distributed-topic name="AdminTopic"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;topic/efpAdminTopic&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;/uniform-distributed-topic&gt;
    &lt;uniform-distributed-topic name="AuditTopic"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;topic/efpAuditTopic&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;/uniform-distributed-topic&gt;
    &lt;uniform-distributed-topic name="ErrorTopic"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;topic/efpErrorTopic&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;/uniform-distributed-topic&gt;
    &lt;uniform-distributed-topic name="FreeTextTopic"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;topic/efpFreeTextTopic&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;/uniform-distributed-topic&gt;
    &lt;uniform-distributed-topic name="ReportingTopic"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;topic/efpReportingTopic&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;/uniform-distributed-topic&gt;
    &lt;/weblogic-jms&gt;
    -----

    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)

  • While deploying Campaign Optimizer test , Getting JMS Exception.

    Getting below error when test is deployed to satging but it fails to start.
    Below port is defined in DynamoMessagingDSSGlobal.xml and entries looks fine in XML and scenario Manager, Is anyone having any idea how to resolve this and why its coming.
    CONTAINER:atg.process.ProcessException; SOURCE:javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    Complete Log trace is:
    info Wed May 23 18:40:07 CDT 2012 1337816407980 /atg/epub/cache/SelectiveCacheInvalidator Deployment 204100073 contains no repository items. Not flushing any caches
    ed May 23 18:40:07 CDT 2012' dynamo.log G-Data/servers/AdminServer/logs$ grep 'W
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407688 /atg/epub/DeploymentAgent state changing : new = DONE_APPLY : current = ACTIVE_APPLY : previous = DONE_PREPARE
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407689 /atg/epub/SecondaryCacheInvalidator Returning because this service is not active
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407706 /atg/epub/DeploymentAgent state changing : new = ACTIVE_ACTIVATE : current = DONE_APPLY : previous = ACTIVE_APPLY
    **** info Wed May 23 18:40:07 CDT 2012 1337816407798 /atg/epub/cache/SelectiveCacheInvalidator Found 0 repository item(s) in this deployment
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407799 /atg/epub/SecondaryCacheInvalidator Returning because this service is not active
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407801 /atg/epub/DeploymentAgent refreshing/updating VFS : /atg/epub/file/ConfigFileSystem
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager Error adding process /CampaignOptimizer/tests/CO_05232012-abt90002.sdl; rolling back the transaction CONTAINER:atg.process.ProcessException; SOURCE:javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14849)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager Caused by :javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.dms.patchbay.ElementManager.getOutputPort(ElementManager.java:245)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.dms.patchbay.ElementManager.createObjectMessage(ElementManager.java:496)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14822)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor --- CONTAINER:atg.process.ProcessException; SOURCE:javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14849)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor Caused by :javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.dms.patchbay.ElementManager.getOutputPort(ElementManager.java:245)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.dms.patchbay.ElementManager.createObjectMessage(ElementManager.java:496)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14822)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor
    **** Warning Wed May 23 18:40:07 CDT 2012 1337816407974 /atg/commerce/claimable/ClaimableRepository invalidateCaches() called, but no cache invalidation will happen because it's been disabled by something
    **** Warning Wed May 23 18:40:07 CDT 2012 1337816407975 /atg/commerce/catalog/ProductCatalog invalidateCaches() called, but no cache invalidation will happen because it's been disabled by something
    **** info Wed May 23 18:40:07 CDT 2012 1337816407975 /atg/search/repository/RefinementRepository Starting invalidateCaches(): /atg/search/repository/RefinementRepository
    **** info Wed May 23 18:40:07 CDT 2012 1337816407976 /atg/search/repository/RefinementRepository Starting premierInvalidateCaches(): /atg/search/repository/RefinementRepository
    **** info Wed May 23 18:40:07 CDT 2012 1337816407977 /atg/search/repository/RefinementRepository Completed premierInvalidateCaches(): /atg/search/repository/RefinementRepository
    **** Warning Wed May 23 18:40:07 CDT 2012 1337816407978 /atg/commerce/pricing/priceLists/PriceLists invalidateCaches() called, but no cache invalidation will happen because it's been disabled by something
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407979 /atg/epub/DeploymentAgent state changing : new = DONE_ACTIVATE : current = ACTIVE_ACTIVATE : previous = DONE_APPLY
    **** info Wed May 23 18:40:07 CDT 2012 1337816407980 /atg/epub/cache/SelectiveCacheInvalidator Deployment 204100073 contains no repository items. Not flushing any caches
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407981 /atg/epub/SecondaryCacheInvalidator Returning because this service is not active

    Can you post the dynamoMessaging.xml if you still have this issue

  • Problem with JMS Correlation i Async/Sync bridge

    This is my scenario:
    I’m receiving a request message from the JMS-adapter and forward this via a async/sync bridge to CRM. I’m using a synchronous proxy in CRM. I want to send the response from this proxy back to MQ via the JMS adapter and put my original JMS Message ID in the JMS Correlation ID in the response message.
    I’ve read about how to configure this in the pdf-document “How to Correlate JMS messages”.
    I did as suggested and that is as follows.
    1.     In my receiver channel I set the Correlation Setting “Set XI Conversation ID To”=JMSMessageID.
    2.     In my integration process (“async/sync-bridge”) I set the Conversation ID in my async send step to the Conversation ID of my request message.
    3.     In my sender channel I set the Correlation Setting “Set JMSCorrelationID To”=XI Conversation ID.
    When I test my scenario I get the following error:
    “New JMS message cannot be correlated with the XI message although it is configured. Unable to set because correlation value is null. Correlation rule: XI_CONVERSATIONID, correlated property: JMSCorrelationID”
    I thought that my Conversation ID should carry the value of my initial JMS Message ID. I know that this is not null.
    Can somebody please help me?
    Kind regards.
    /Helé

    Hi Wallace,
    I tried to set the Conversation ID to the Correlation ID instead but I still get the same error.
    The sending application needs to correlate the request message with the corresponding response and since we are using MQ this is the way to do it.
    regards.
    /Helé

  • JMS transport warning when start server

    When I start a WebLogic 9 server instance with one application deployed, I get the following warning message 5-6 times before the server changes its state to RUNNING:
    <WSEE>Warning: JMS queue 'weblogic.wsee.DefaultQueue' is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:227>
    Although the server instance still appears to start fine, these messages clog up the console - since I don't intend to use JMS transport with this server, is there any way to get rid of these messages?
    Thanks,
    David

    Hai
    I am using weblogic9.2. I too got the same problem in my machine. I have solved this problem by changing the configuration in the config.xml file.
    Go to
    <WEBLOGIC HOME>\user_projects\domains\<USER_DOMIN>\config\config.xml
    Open the config.xml and check the following
    <app-deployment>
    <name>webservicesJwsSimpleEar</name>
    <target>AdminServer</target>
    <module-type>ejb</module-type>
    <source-path>C:\bea\user_projects\applications\base_domain/server/examples/build/webservicesJwsSimpleEar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    if it is there comment this tag and save the config.xml file. Make sure that the server is not running while doing the changes. Now Start the server again.
    Comment out as like follows
    "<!--" <app-deployment>
    <name>webservicesJwsSimpleEar</name>
    <target>AdminServer</target>
    <module-type>ejb</module-type>
    <source-path>C:\bea\user_projects\applications\base_domain/server/examples/build/webservicesJwsSimpleEar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment> "-->"
    Its working for me try this
    Regards
    Ramesh
    Edited by ramesh.s at 04/04/2007 2:58 AM

  • Concurrency for JMS Sender Adapter - Async/Sync Bridge

    Hi,
    We have implemented a number of Async/Sync bridges using JMS Adapters, and are encountering problems scaling the solution.
    Async-Sync Bridge Scenario:
    JMS Sender Adapter -> Integration Server -> Sync ABAP Proxy (CRM) ->  JMS Receiver Adapter
    The bridge is using the Adapter Framework modules: RequestResponseBean & ResponseOnewayBean within the Sender Adapter.
    The problem is that concurrency of processing seems to be driven from the number of Java Server Cluster Nodes on the Adapter Engine.  The JMS sender adapters do not appear to read from the external messaging system (MQ) in a concurrent fashion.  They appear to process in a sequential manner per Adapter:
    1. Read from request Message Queue (MQ)
    2. Send request for processing (IS)
    3. Wait response message
    4. Receive response message
    5. Write response message to Message Queue (MQ)
    6. Read from request Message Queue (MQ)
    7. Send request for processing (IS)
    8. Wait response message
    9....
    We need to be able to introduce some means of scaling the solution so that mesages can be read from the MQ request message queue in a concurrent manner.  Hopefully we can do this without adding more javer server nodes to the Adapter Engine.
    We were looking intot he possibility of tuning AS Java properties that control the number of connections to the Messaging System of the Adapter Engine but this has not provided a solution.
    Any information on  this topic would be much appreciated.
    regards
    Murray

    As far as I know, the only wasy for JMS adapter to do concurrent reads from a queue is by having multiple server nodes. This is document in note 856346, point 6.2
    Thanks
    KK

  • Null Pointer Exception using JDBC-ODBC bridge on Linux

    Wonder if anyone can help me with this one?
    I am attempting to use the JDBC-ODBC bridge on Fedora with J2SDK 1.4.2_04, however I am getting a NullPointerException whenever I get the connection. I can get the JDBC connection to work but it is a requirement that ODBC be used.
    The code is as simple as it can get.
    import java.sql.*;
    public class TestClass
       public static void doConnection()
          try
               Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
               Connection cn = DriverManager.getConnection("jdbc:odbc:DB");
          catch (Exception e)
               e.printStackTrace();
       public static void main(String[] args)
          doConnection();
    }Running this program using java -verbose TestClass I get the following output.
    [Loaded sun.jdbc.odbc.JdbcOdbc from /usr/java/j2sdk1.4.2_04/jre/lib/rt.jar]
    [Loaded java.lang.UnsatisfiedLinkError from /usr/java/j2sdk1.4.2_04/jre/lib/rt.jar]
    [Loaded java.sql.SQLException from /usr/java/j2sdk1.4.2_04/jre/lib/rt.jar]
    [Loaded java.sql.SQLWarning from /usr/java/j2sdk1.4.2_04/jre/lib/rt.jar]
    java.lang.NullPointerException
    [Loaded java.lang.StackTraceElement from /usr/java/j2sdk1.4.2_04/jre/lib/rt.jar]
    at sun.jdbc.odbc.JdbcOdbcDriver.initialize(JdbcOdbcDriver.java:436)
    at sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:153)
    at java.sql.DriverManager.getConnection(DriverManager.java:512)
    at java.sql.DriverManager.getConnection(DriverManager.java:193)
    at TestClass.doConnection(TestClass.java:13)
    at TestClass.main(TestClass.java:96)
    [Loaded java.lang.Shutdown from /usr/java/j2sdk1.4.2_04/jre/lib/rt.jar]
    [Loaded java.lang.Shutdown$Lock from /usr/java/j2sdk1.4.2_04/jre/lib/rt.jar]
    The UnsatisfiedLinkError suggests to me that a library cannot be found, but I don't know what library.
    As far as I know I have configured ODBC correctly. I can achieve connectivity to my database using other tools and I still get this same error irrespective of whether the DSN is valid or not.
    I have installed the unixODBC rpm.
    Any help/insite would be greatly appreciated.

    This is the output of ldd. Everything appears to be resolved.
    linux-gate.so.1 => (0x00cf5000)
    libodbcinst.so => /usr/sybase/lib/libodbcinst.so (0x001d5000)
    libjava.so => libjava.so (0x008af000)
    libjvm.so => /usr/java/j2sdk1.4.2_04/jre/lib/i386/client/libjvm.so (0x002a7000)
    libc.so.6 => /lib/i686/libc.so.6 (0x00d77000)
    libdbtasks7.so => /usr/sybase/lib/libdbtasks7.so (0x00eb2000)
    libdl.so.2 => /lib/libdl.so.2 (0x00111000)
    libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x00115000)
    libm.so.6 => /lib/i686/libm.so.6 (0x008fb000)
    libverify.so => libverify.so (0x0016e000)
    libnsl.so.1 => /lib/libnsl.so.1 (0x00180000)
    libpthread.so.0 => /lib/i686/libpthread.so.0 (0x006d0000)
    /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00157000)
    libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00b75000)
    The ODBC is a Sybase driver and is loaded from elsewhere. I will check for any known compatibility issues.

  • JMS Exception: Connection not found

    I get a Connection not found exception when creating a TopicSession to communicate with a remote server. Here's the situation. I have several MDBs listening to one jms topic on Weblogic 6.1. They work properly sending and receiving jms messages from the topic when run within one server.
    However, I have a second Weblogic 6.1 server with the same named jms connection factory and topic as on the first machine with the MDBs deployed. I am trying to send jms messages from a stateless session bean within the first server to the second server's topic to trigger the MDBs deployed on that machine.
    I create a connection using the InitialContext and get the topic but when I try and create the TopicSession, it breaks. Here's the code:
    Properties myEnvironment = new Properties();
    myEnvironment.setProperty(Context.INITIAL_CONTEXT_FACTORY, WEBLOGIC_ICF);
    myEnvironment.setProperty(Context.PROVIDER_URL, "t3://<serverAddress>:7031");
    Context myContext = new InitialContext(myEnvironment);
    TopicConnectionFactory myTCFactory = (TopicConnectionFactory) myContext.lookup(CONNECTION_FACTORY);
    Topic myTopic = (Topic) myContext.lookup(TOPIC_NAME);
    TopicConnection myTopicConnection = myTCFactory.createTopicConnection();
    // Connection is not null but breaks here:
    TopicSession myTopicSession = myTopicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
    And here is the error message that results.
    weblogic.jms.common.JMSException: Connection not found
    at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:121)
    at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:509)
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:272)
    at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:268)
    at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:245)
    at com.informore.scenariomanager.util.ScmEventJMSUtil.openTopicConnection(Unknown Source)
    at com.informore.scenariomanager.components.topicdispatcher.ejb.TopicDispatcherEJB.sendTopicMessage(Unknown Source)
    at com.informore.scenariomanager.components.topicdispatcher.ejb.TopicDispatcherEJB.handleMessagesPosted(Unknown Source)
    at com.informore.scenariomanager.components.topicdispatcher.ejb.TopicDispatcherEJB.processJMSMessage(Unknown Source)
    at com.informore.scenariomanager.components.topicdispatcher.ejb.TopicDispatcherEJB_44hyzr_ELOImpl.processJMSMessage(TopicDispatcherEJB_44hyzr_ELOImpl.java:200)
    at com.informore.scenariomanager.components.topicdispatcher.ejb.TopicDispatcherMDB.onMessage(Unknown Source)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    I've tried using "org.omg.CORBA.ORBInitialHost" and "org.omg.CORBA.ORBInitialPort" to no avail. And, because I will potentially need MDBs running on the current and several other remote servers, I don't want to have to specify only one target machine. Any help or suggestions GREATLY appreciated!
    Thanks.

    Thanks !
    I had the same problem on wls 7.0 and it solved it.
    I tried to send a JMS from server to server and got :
    weblogic.jms.common.JMSException: Connection not found
    at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:134)
    The problem was that the two servers had the same name !
    Ilan.

  • JMS Exception when server goes down (Urgent) ?

    Hi All,
    I have three topics in the JMS Server which is on the top of Web logic server 8.1.
    On the client side I have Swing thick cleint.For each topic I have a listener.
    When the web logic server goes down ( I shut down manually ) Only one listener is recieving the Exception and the Swing client reacts accordingly.
    After this ,
    Client continousoly checks whether the server is up or not. Once the server is up again the Exception is thrown that server is down ( I guess now the second listener is recieving the message).
    After some time again the third listener recives the message.....
    and the client reacts on that exception 3 times.
    How can I get rid of this ?
    thanks in advance.
    san

    Hi,
    this is probably a very good question to ask support. 'Logical' deployment sequence
    was added to the WebLogic only recently (6.1sp?) ('logical' means that first datasources
    are deployed, then EJB's and then web-apps, deployment-order parameter was added etc).
    So, for applications where shutdown sequence is important there must be a document which
    describes how server shutdown works.
    On the other hand, this may not be as important as deployment sequence, because running
    instance can crash at any time and it should not affect anything.
    Jen <[email protected]> wrote:
    Repost
    Hi,
    Most of my ejbs use connection from the connection pool. At the weblogic server shut
    down time (heavy load), I can see the jsps call the ejb, sometime jsp can't find
    the bean because it's removed from jndi. sometime jsp found the bean but when the
    bean try to talk to database, ejb can't use the connection because the datasource
    is removed from jndi. Also my shutdown class waits for the threads finish up, and
    the threads calls the ejb and do the db operation, and the conn is cut when the db
    operation is half way. So, the order of events when server shut down is important
    to me. I am wondering how other people deal with it. Thanks --
    Dimitri

Maybe you are looking for