Can an MDB listens to remote queue

In my application , i have created a queue and MDB for that queue.
this MDB should also listen to the queue in another system that is remote queue.how is this possible.
because the queue will be in remote system. and MDB will be in my system. the queue to which this MDB should listen will be in specified in deplyment descriptors. then how it will identify that the queue is local or remote.
Please clarify me as we have a release near.

Hello Sairam,
I have used MDB in WebLogic Server. You can add the Destination Queue, Connection factory, etc information in weblogic-ejb-jar.xml.
I am not sure what is to be used in Oracle Server.
Simple search in Oracle Website gave me some links..
http://www.oracle.com/technology/tech/java/oc4j/ejb3/how_to/howtoejb30mdb/doc/how-to-ejb30-mdb.html
Search the Oracle website for more information.
Thanks and regards,
Pazhanikanthan. P

Similar Messages

  • MDBs listen on remote queue

    How do you configure MDBs to listen on a remote queue in OAS 10g 10.1.3?
    I've tried using the SonicMQ example in the container services guide as a template, but I haven't been able to get it to work.
    Thanks.
    Dan

    Ok I understand now. When you said remote I thought you meant a destination outside the service bus, and not an MQ remote queue. Unfortunately I have little advice to give. The documentation states:
    When you create an MQ service, select the transport protocol as mq and specify the Endpoint URI in the Transport Configuration >page. Specify the Endpoint URI in mq://local-queue-name?conn=mq-connection-resource-ref format where
    local-queue-name is the name of the local queue configured on the MQ server
    mq-connection-resource-ref points to the location of the MQ connection resource I don't know if it's possible to use a remote queue directly, my knowledge of MQ is limited. Hopefully someone else can help. Or you could contact support and ask if remote queues are supported.

  • MDB Listening to remote queue

              Hi,
              Could any of you please let me know what needs to be done to configure my MDB
              to listen to a remote queue in a different domain (also using wls 7.0).
              I tried adding the <provider-url> element in the weblogic-ejb-jar.xml but looks
              like that didnt work.
              Thanks,
              -Sri
              

    Posting the actual error helps. This error usually occurs due
              to a naming conflict. Make sure that:
              All local and remote:
              WL servers are named differently
              WL JMS servers are named differently
              WL JMS stores are named differently
              Tom, BEA
              P.S. For future reference, a google search of
              this newsgroup often quickly leads to answers. In this
              case search for "Connection not found" or "invocableFind".
              Sri wrote:
              > Tom, I did. But I still get this error...
              >
              > [exec] <Jun 10, 2003 9:27:57 AM EDT> <Error> <EJB> <010020> <EJB-20 - Messa
              > geDriven - Couldn't start the JMS connection: weblogic.jms.common.JMSException:
              > Connection not found
              > [exec] weblogic.jms.common.JMSException: Connection not found
              > [exec] at weblogic.jms.dispatcher.InvocableManager.invocableFind(Invoca
              > bleManager.java:134)
              > [exec] at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Req
              > uest.java:592)
              > [exec] at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(Dispatche
              > rImpl.java:275)
              > [exec] at weblogic.jms.client.JMSConnection.start(JMSConnection.java:54
              > 7)
              > [exec] at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectio
              > n(JMSConnectionPoller.java:1228)
              > [exec] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.startCo
              > nnection(MessageDrivenBeanPoolInfoImpl.java:150)
              > [exec] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(M
              > essageDrivenBeanPoolInfoImpl.java:223)
              > [exec] at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(
              > EJBDeployer.java:1560)
              > [exec] at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:14
              > 06)
              > [exec] at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:391)
              > [exec] at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationC
              > ontainer.java:1039)
              > [exec] at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicati
              > onContainer.java:1025)
              > [exec] at weblogic.management.deploy.slave.SlaveDeployer.setActivationS
              > tateForAllApplications(SlaveDeployer.java:617)
              > [exec] at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDe
              > ployer.java:376)
              > [exec] at weblogic.management.deploy.DeploymentManagerServerLifeCycleIm
              > pl.resume(DeploymentManagerServerLifeCycleImpl.java:235)
              > [exec] at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleLi
              > st.java:65)
              > [exec] at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
              > [exec] at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
              > [exec] at weblogic.Server.main(Server.java:32)
              > [exec] >
              >
              > Tom Barnes <[email protected]> wrote:
              >
              >>Check your server logs for Warning and/or error messages.
              >>
              >>Make sure that you specified a correct:
              >>
              >>provider-url
              >>
              >>destination-jndi-name
              >>
              >>connection-factory-jndi-name (needed if you disabled the default
              >>connection factories in the remote domain)
              >>
              >>Sri wrote:
              >>
              >>>Hi,
              >>>
              >>>Could any of you please let me know what needs to be done to configure
              >>
              >>my MDB
              >>
              >>>to listen to a remote queue in a different domain (also using wls 7.0).
              >>
              >>>I tried adding the <provider-url> element in the weblogic-ejb-jar.xml
              >>
              >>but looks
              >>
              >>>like that didnt work.
              >>>
              >>>Thanks,
              >>>-Sri
              >>
              >
              

  • Making MDB listen to a queue

    Hi all,
    Can any one tell me how to make an MDBean listen to a Queue Using JDev wizard.
    Kindly help....

    mshreedhaaran wrote:
    Hi,
    Thanks to the below post(s) -
    <a class="jive-link-external" href="http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html">http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html</a>
    <a class="jive-link-external" href="http://www-128.ibm.com/developerworks/websphere/library/techarticles/0604_kesavan/0604_kesavan.html">http://www-128.ibm.com/developerworks/websphere/library/techarticles/0604_kesavan/0604_kesavan.html</a>
    I have been able to get this far (ofcourse explained very well step by step in these posts). So MDB on WLS can pick messages from a Queue on MQ Server on the same machine.
    If someone can highlight what <font face="tahoma,verdana,sans-serif" size="1" color="#000">changes</font> I have to make to get the MDB to pick message from the Queue when MQ Server is on a different machine.
    Thanks in advance.
    best regards,
    MuraliIt's helpful to me, Thanks for your sharing! Now I understand more about it, It's quite useful.

  • MDB listening to multiple queues?

              Is it possible to configure an MDB to listen to more than one Queue ?
              

    No.
              _sjz.
              "Jim" <[email protected]> wrote in message news:3d496d70$[email protected]..
              >
              > Is it possible to configure an MDB to listen to more than one Queue ?
              

  • Listening to multiple queues

    Hi all,
    Can a MDB listen to multiple queues. If so how will be the deployment descriptor
    Thanks
    Hashin

    No.
              _sjz.
              "Jim" <[email protected]> wrote in message news:3d496d70$[email protected]..
              >
              > Is it possible to configure an MDB to listen to more than one Queue ?
              

  • MDB connecting to Remote Distributed Queue

    Hi,
    I am trying to deploy a MDB in weblogic 10.0 and this will listen to a Distributed Queue in another weblogic version10 server.
    my MDB code looks like
    @MessageDriven(mappedName = "jms/DMSQueue", activationConfig = {
              @ActivationConfigProperty(propertyName = "initial-context-factory ", propertyValue = "weblogic.jndi.WLInitialContextFactory"),
              @ActivationConfigProperty(propertyName = "connectionFactoryJndiName", propertyValue = "jms/cf"),
              @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
              @ActivationConfigProperty(propertyName="destination", propertyValue="jms/DMSQueue"),     
              @ActivationConfigProperty(propertyName = "destinationJndiName", propertyValue = "jms/DMSQueue"),          
              @ActivationConfigProperty(propertyName = "providerAdapterJNDI", propertyValue = "java:/RemoteJMSProvider"),
              @ActivationConfigProperty(propertyName = "provider-url", propertyValue = "t3://10.54.115.171:80")          
    public class TestMdb implements MessageListener {
         public void onMessage(Message message) {
              System.out.println("Received Message: " + message);
    if the I configure the bean for a local Queue it works properly.
    But if I provide the url of the remote Queue, it does not get connected.
    my ejb-jar.xml
    contains only
    <enterprise-beans>
    <message-driven>
    <ejb-name>ejbsms</ejb-name>
    <ejb-class>hmil.TestMdb</ejb-class>      
    </message-driven>
    </enterprise-beans>
    I guess we need to provide the security credentials of the remote server and may be missing some thing else.
    Please guide me on what changes required in annotations to get it working
    I prefer to use container independent propertyName
    Edited by: user13583038 on Jan 3, 2011 4:08 AM

    You can try posting JMS related questions to the JMS newsgroup.

  • MDB listening on Socket instead of Queue

    Hi all,
    Is it possible for to make MDB listen on socket instead of queues using JCA. Can anyone please help me on this.
    Thanks in advance

    Hi,
    Thanks for the reply. In the example provided, it is for mail. Since we have javax.mail.Message message API we can use this. How about Socket.Here am lost. Can you please tell how to go with this.
    I also had tried the above one, but while deploying MDB, I error as MDB is in failed state with Exception as Resource Adaptor "EchoXMLRP" is not deployed. Where as i had already deployed it. Also i had deployed "EchoXMLRP" as Resource Adaptor Module. But when i view the same its not present in standalone Resource Adaptor, instead its there in Modules.

  • Urgent : MDB stops listening to the queues after some time  !!!

    Hi,
    I am using OJMS with OC4J 10.1.2 and db 9.2.0.5. I have a web application which send messages into the queue very frequently.
    But the problem is the MDBs stop listening to the queues after some time (1-2 days) and no more messages will be dequeued from that point.
    All these messages will move to the exception queue after their expiry.
    But the dequeing agains resumes after restarting the OC4J !.
    I guess, at some point mdbs are either becoming busy (locked ) or some exception occured while dequeing, hence they stop listening to the queues.
    Please throw some light on this issue as it is very crucial in my project.
    Regards
    Prashanth

    I've noticed this lately as well, with my iPhone 4. I couldn't confidently pin it directly on any particular iOS update, but my iPhone used to automatically connect up via Bluetooth with my Prius's handsfree feature, and now it doesn't. I work with a CE-based device at my job, with Bluetooth capability, and I used to test out that feature by having it discover my iPhone. This no longer works either.
    What I have found (not really a solution, but it does work and may be a clue for Apple) is that if I simply go to the Settings app then the General -> Bluetooth screen and let it sit there, it will pair right up with my car within a few seconds. Bluetooth is always on, and always says "Now Discoverable" at the bottom of the settings screen.

  • MDB listening to a Oracle AQ, holding ADT messages...

    Hi !
    I'm trying to set a MDB to listen for incoming messages on an Oracle AQ. When I created the queue, I specified that the queue should contain payload of type ADT. I'm using Bea Weblogic server 8.1 sp4 and Oracle 10.2.0. The creation of the connection to the queue is implemented as a start up class and bound to the context during server start up.
    However it fails to start up, I get the following exception:
    <20.mar.2007 kl 11.03 CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB:
    MyWebLogicMDB is unable to connect to the JMS destination: AQJMSQueue. The Erro
    r was:
    oracle.jms.AQjmsException: JMS-137: Innholdsfabrikk mÕ angis for mÕl med ADT-inn
    hold
    oracle.jms.AQjmsException: JMS-137: Innholdsfabrikk mÕ angis for mÕl med ADT-inn
    hold
    at oracle.jms.AQjmsError.throwEx(I)V(AQjmsError.java:288)
    at oracle.jms.AQjmsConsumer.<init>(Loracle.jms.AQjmsSession;Ljavax.jms.D
    estination;IILjava.lang.String;Ljava.lang.Object;Loracle.jms.AQjmsSelector;Ljava
    .lang.String;Z)V(AQjmsConsumer.java:385)
    at oracle.jms.AQjmsConsumer.<init>(Loracle.jms.AQjmsSession;Ljavax.jms.D
    estination;IILjava.lang.String;Ljava.lang.Object;Loracle.jms.AQjmsSelector;Ljava
    .lang.String;)V(AQjmsConsumer.java:254)
    at oracle.jms.AQjmsSession.createReceiver(Ljavax.jms.Queue;Ljava.lang.St
    ring;Ljava.lang.Object;)Ljavax.jms.QueueReceiver;(AQjmsSession.java:1631)
    at oracle.jms.AQjmsSession.createReceiver(Ljavax.jms.Queue;Ljava.lang.St
    ring;)Ljavax.jms.QueueReceiver;(AQjmsSession.java:1553)
    at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(Ljavax
    .jms.Destination;Ljava.lang.String;III)V(JMSConnectionPoller.java:1720)
    at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection()V(JM
    SConnectionPoller.java:2019)
    at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS()V(JMSConnec
    tionPoller.java:1180)
    at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling
    ()V(JMSConnectionPoller.java:846)
    at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start()V(Messag
    eDrivenBeanPoolInfoImpl.java:234)
    at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans()V(EJBDe
    ployer.java:1660)
    at weblogic.ejb20.deployer.EJBDeployer.start(Z)V(EJBDeployer.java:1488)
    at weblogic.ejb20.deployer.EJBModule.start()V(EJBModule.java:689)
    at weblogic.j2ee.J2EEApplicationContainer.start([Lweblogic.j2ee.J2EEAppl
    icationContainer$Component;)V(J2EEApplicationContainer.java:2127)
    at weblogic.j2ee.J2EEApplicationContainer.activate([Lweblogic.management
    .configuration.ComponentMBean;)V(J2EEApplicationContainer.java:2168)
    at weblogic.j2ee.J2EEApplicationContainer.activate()V(J2EEApplicationCon
    tainer.java:2115)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivat
    ion(Z)V(SlaveDeployer.java:3082)
    at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
    llApplications(ZZ)V(SlaveDeployer.java:1751)
    at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeploye
    r.java:359)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
    e()V(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131
    at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:361)
    at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
    >
    The problem is that the MDB cannot be set up to dequeue the message because the payload factory has to be set for the consumer in order to receive messages from queues which have messages with ADT payload.
    So my questions are:
    1) Is there a way to set the payload factory to use in the MDB? (deployment desc.)
    2) Do MDB support AdtMessages?
    3) Are there any other ways to listen to an Oracle queue which has ADT type?
    mvh
    jb

    Hi,
    I'm also having the same identical problem with an EJB 3.0 MDB listening to an AQ queue (via OJMS) with a payload type of ADT. I can successfully dequeue messages from a queue with a JMS payload type, but as soon as I point it to and ADT type queue I get:
    oracle.jms.AQjmsException: JMS-137: Payload factory must be specified for destinations with ADT payloads
    I can't however seem to find anything in the Oracle documentation that shows how to do this, and which class corresponds to this "payload factory".
    The following link seems to suggest that OJMS supports ADT types in addition to the standard JMS message types:
    http://www.oracle.com/technology/tech/java/oc4j/904/collateral/OC4J-FAQ-JMS-904.html
    although I'm not sure if this is true for Message Driven Beans.
    Could you please confirm whether MDB's support ADT message types?
    Many thanks
    Phil

  • How to handle failure when sending messages to remote queues from OAS10.1.3

    Hi,
    Here is my problem. IN my project, I have a MDB which is looking for message in a queue and once a message arrived, it supposed to send the message to remote queues.
    Assume that there are 3 remote queues, and my mdb is trying to send the message to all the 3 remote queues,
    1) My problem is, If one of the remote queue is not reachable or down, then the MDB should be able to resend it several times until it reaches the failed remote queue.
    2) At the same time, I dont want to resend the messages(duplicate) to the queues which are successful ones.
    Please suggest me some solution for this in JMS.
    My MDB deployed at 10.1.3 and assume that remote queue can be in either another 10.1.3 or WAS 6.0(Optional).
    Thanks and regards,
    SS.

    Hi,
    1) My problem is, If one of the remote queue is not reachable or down, then the MDB should be able to resend it several times until it reaches the failed remote queue.
    Not very sure what is your question, depending on if you want to resend the message if one of three queues is down.
    If the message has to arrive to a certain destination while mdb received it, you may try to reconnnect and resend the message in a couple of times. Perhaps you need a couter or timeout to limit the number of time to retry or the period to retry.
    Is that what you are asking.
    2) At the same time, I dont want to resend the messages(duplicate) to the queues which are successful ones.
    While sending message to a queue, those implementation is within the exception try/catch block, so any resend failure (JMSException) will fall into the catch block I guess. And we can probably use that exception to determine if the message is able to send to remote queue, if not, keep resending util it is over the limit of retries. For example:
    onMessage(Message){
    resend(message, counter);
    public void resend(message, counter) {
    try{
    if (counter <= retryLimit){
    .... // do the reconnect or/and resend operation
    }catch(exception e){
    resend(message, counter++);
    If the above is not what you are asking, please clarify a bit.
    Rocky

  • Remote queue in XI server for IBM MQSeries

    Dear All,
    my scenario is IBM MQSeries -> message via sender JMS adapter -> XI -> receiver RFC adapter -> R/3.
    now for IBM MQSeries to send a message to XI via a transmission queue in MQSeries - it needs a remote queue name and  queue  manager name in XI server.
    So now where can i find these information regarding remote queue name and  queue  manager name in XI server. I currently do not know whether in XI server, currently is there any remote queue or not? So how to find this information. If we do not have remote queue manager in XI currently, then how to install a remote queue name and  queue  manager in XI server.
    It is slightly urgent. So i request you all to please reply quickly.
    Thanks and Regards,
    Rajeev Gupta

    Dear Sebastin,
    Thanks for your inputs.
    I have to connect to MQSeries 5.2.1 to XI server.
    am getting the below error in Communicatin Channel Monitoring for my sender JMS adapter:
    Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<IP_ADRESS>:<MQ_QUEUE_MANAGER>'
    at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
    at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
    at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
    com.ibm.mq.MQException: Message catalog not found
    at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:171)
    at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:228)
    i have written '<IP_ADRESS>:<MQ_QUEUE_MANAGER>' just to hide the data - i am getting <IP_ADRESS> as IP Adress i gave in JMS adapter and <MQ_QUEUE_MANAGER> as Queue Manager i gave in JMS adapter.
    i am using the correct IP and 1414 port of MQSeries server. I have used a MQQueueManager defined in MQSeries. i have deployed JMS adapter properly in XI server.
    So can anybody suggest what could be the possible reason of this error and how to rectify it. It is slightly urgent.
    One more question - should the queue manager in MQSeries server be a local or remote queue manager..........i was not able to create a remote queue manager in MQSeries 5.2.1 as by default it is creating a local queue manager.......
    Thanks and Regards,
    Rajeev Gupta

  • Count the number of message in remote queue.

    Does any method in MQSeries or JMS, can count the number of message in remote queue.
    I try to use QueueBrowser to browser, but got exception when browse the remote queue.
    thanks.

    You cannot read from, browse or query a remote MQ Queue, only write to it. Try www.mqseries.net or ibm website for any ways around this...

  • OSB10 and MQ remote queue

    Hi all,
    we are trying to connect OSB to a MQ remote queue but we have some troubles ...
    We installed WebSphere MQ 7.0.1.3:
    mqm@bsrplab0008:/export/home/mqm > dspmqver
    Name: WebSphere MQ
    Version: 7.0.1.3
    CMVC level: p701-7013TRIAL
    BuildType: IKAP - (Production)
    And we created into MQ below objects:
    - Create a queue manager
    - Start a queue manager
    - Define a queue
    with below MQ commands:
    crtmqm -q MQ.TESTQUEUE.MANAGER
    strmqm MQ.TESTQUEUE.MANAGER
    runmqsc MQ.TESTQUEUE.MANAGER
    define qlocal (mq.test.queue)
    About OSB we performed below steps:
    - Add the client jar to OSB classpath (/products/software/osb103/domains/OSBDomain/lib/com.ibm.mq.jar)
    - Create MQConnection:
    Connection Type mqTcpModeType
    MQ Host Name 11.0.4.35
    MQ Port Number 1414
    MQ Queue Manager Name MQ.TESTQUEUE.MANAGER
    MQ Queue Manager Channel Name CHL.WMQ.TESTQUEUE
    SSL Required false
    WebSphere MQ Version v6
    MQ Connection Pool Size 10
    MQ Connection Timeout 1800
    MQ Connection Max Wait 3
    - A MQ proxy (where Tmp_OSB_WMQ is the project folder in OSB):
    Service Type Any XML Service
    Protocol mq
    Endpoint URI mq://MQ.TEST.QUEUE?conn=Tmp_OSB_WMQ/MQConnection
    Polling Interval 1000
    Is Response Required DISABLED
    Backout Threshold 0
    Process RFH2 Headers DISABLED
    Content Streaming Disabled
    We suppose the problem could be how we defined ‘MQ Queue Manager Channel Name’ into MQ:
    runmqsc MQ.TESTQUEUE.MANAGER
    DEFINE CHANNEL('CHL.WMQ.TESTQUEUE') CHLTYPE(SVRCONN)
    end
    --> I'm not a MQ expert :-) and it is the first time that I'm working with MQ ...
    From OSB there is no error when we activate the project …
    But while on MQ server we can successfully send/receive messages on the target queue:
    ./amqsput MQ.TEST.QUEUE
    ./amqsget MQ.TEST.QUEUE
    We don’t get any message from OSB MQ proxy.
    Do you have any hints ? Did you connect successfully OSB and MQ using MQ transport provided by OSB ?
    Thanks in advance
    ferp

    Ciao Atheek,
    thanks a lot for your feedback.
    I run the command yu suggested:
    mqm@bsrplab0008:/var/mqm/qmgrs > runmqsc MQ_TEST_MANAGER
    5724-H72 (C) Copyright IBM Corp. 1994, 2009. ALL RIGHTS RESERVED.
    Starting MQSC for queue manager MQ_TEST_MANAGER.
    dis qs (mq_test_osb_queue) IPPROCS
    1 : dis qs (mq_test_osb_queue) IPPROCS
    AMQ8450: Display queue status details.
    QUEUE(MQ_TEST_OSB_QUEUE) TYPE(QUEUE)
    CURDEPTH(0) IPPROCS(0)
    end
    --> so IPPROCS is 0 !
    But the queue manager is running:
    mqm@bsrplab0008:/var/mqm/qmgrs > dspmq -m MQ_TEST_MANAGER
    QMNAME(MQ_TEST_MANAGER) STATUS(Running)
    And from AMQxxx logs I don’t see any particular error message:
    10/03/11 15:20:25 - Process(10551320.1) User(mqm) Program(amqzxma0_nd)
    Host(bsrplab0008)
    AMQ8003: WebSphere MQ queue manager 'MQ_TEST_MANAGER' started.
    EXPLANATION:
    WebSphere MQ queue manager 'MQ_TEST_MANAGER' started.
    ACTION:
    None.
    10/03/11 15:20:26 - Process(15204570.1) User(mqm) Program(amqzmgr0)
    Host(bsrplab0008)
    AMQ5022: The Channel Initiator has started. ProcessId(12910698).
    EXPLANATION:
    The Channel Initiator process has started.
    ACTION:
    None.
    On OSB we enabled MQ-debug information (<java:alsb-mqconnection-debug>true</java:alsb-mqconnection-debug>) and when we test our OSB MQ business service we get below exception:
    ####<Oct 4, 2011 9:49:53 AM CEST> <Debug> <AlsbMqConnection> <bsrpdev0012> <BsizzOSBServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1317714593237> <BEA-000000> <MQOC.processing request headers>
    ####<Oct 4, 2011 9:49:53 AM CEST> <Debug> <AlsbMqConnection> <bsrpdev0012> <BsizzOSBServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1317714593243> <BEA-000000> <OMC.run: Sending outbound request to mq://MQ_TEST_OSB_QUEUE?conn=Tmp_OSB_WMQ/MQConnection>
    ####<Oct 4, 2011 9:49:53 AM CEST> <Debug> <AlsbMqConnection> <bsrpdev0012> <BsizzOSBServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1317714593243> <BEA-000000> <864039808:MQCP.borrowObject>
    ####<Oct 4, 2011 9:49:53 AM CEST> <Debug> <AlsbMqConnection> <bsrpdev0012> <BsizzOSBServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1317714593243> <BEA-000000> <502013420:MQCPF.makeObject>
    ####<Oct 4, 2011 9:49:53 AM CEST> <Debug> <SFTPTransport> <bsrpdev0012> <BsizzOSBServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1317714593253> <BEA-381830> <Created 0 tasks>
    ####<Oct 4, 2011 9:49:53 AM CEST> <Debug> <AlsbMqConnection> <bsrpdev0012> <BsizzOSBServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1317714593296> <BEA-000000> <MQCC.getQueueManagerConnection: error
    com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
    MQJE016: MQ queue manager closed channel immediately during connect
    Closure reason = 2009
    at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:212)
    at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)
    at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:338)
    at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:84)
    at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:168)
    at com.ibm.mq.MQQueueManagerFactory.obtainBaseMQQueueManager(MQQueueManagerFactory.java:772)
    at com.ibm.mq.MQQueueManagerFactory.procure(MQQueueManagerFactory.java:697)
    at com.ibm.mq.MQQueueManagerFactory.constructQueueManager(MQQueueManagerFactory.java:657)
    at com.ibm.mq.MQQueueManagerFactory.createQueueManager(MQQueueManagerFactory.java:153)
    at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:526)
    at com.bea.wli.sb.resources.mqconnection.MQConnectionPoolFactory.makeObject(MQConnectionPoolFactory.java:281)
    at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)
    at com.bea.wli.sb.resources.mqconnection.MQConnectionPool.borrowObject(MQConnectionPool.java:58)
    at com.bea.wli.sb.resources.mqconnection.MQConnectionContext.getQueueManagerConnection(MQConnectionContext.java:140)
    at com.bea.wli.sb.transports.mq.MQOutboundMessageContext.send(MQOutboundMessageContext.java:565)
    at com.bea.wli.sb.transports.mq.MQTransportProvider.sendMessageAsync(MQTransportProvider.java:501)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:599)
    at com.bea.wli.sb.transports.Util$1.invoke(Util.java:82)
    at $Proxy73.sendMessageAsync(Unknown Source)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:547)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:482)
    at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:544)
    at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:422)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:296)
    at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:68)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:125)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:123)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:128)
    at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:441)
    at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:169)
    at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:136)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:572)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_1030_WLStub.invoke(Unknown Source)
    at com.bea.alsb.console.test.TestServiceClient.invoke(TestServiceClient.java:179)
    at com.bea.alsb.console.test.actions.DefaultRequestAction.invoke(DefaultRequestAction.java:117)
    at com.bea.alsb.console.test.actions.DefaultRequestAction.execute(DefaultRequestAction.java:70)
    at com.bea.alsb.console.test.actions.ServiceRequestAction.execute(ServiceRequestAction.java:80)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
    at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
    at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.processActionPerform(SBConsoleRequestProcessor.java:91)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
    at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.process(SBConsoleRequestProcessor.java:191)
    at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
    at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
    at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
    at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
    at com.bea.alsb.console.common.base.SBConsoleActionServlet.doGet(SBConsoleActionServlet.java:49)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1129)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:687)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
    at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.processAction(StrutsStubImpl.java:76)
    at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
    at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
    at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
    at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:220)
    at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
    at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
    at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
    at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
    at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
    at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
    at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
    MQJE016: MQ queue manager closed channel immediately during connect
    Closure reason = 2009
    at com.ibm.mq.MQv6InternalCommunications.checkControlFlags(MQv6InternalCommunications.java:747)
    at com.ibm.mq.MQv6InternalCommunications.establishChannel(MQv6InternalCommunications.java:663)
    at com.ibm.mq.MQv6InternalCommunications.initialize(MQv6InternalCommunications.java:213)
    at com.ibm.mq.MQv6InternalCommunications.<init>(MQv6InternalCommunications.java:109)
    at com.ibm.mq.MQSESSIONClient.MQCONNX(MQSESSIONClient.java:1337)
    at com.ibm.mq.MQSESSIONClient.MQCONN(MQSESSIONClient.java:1246)
    at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:184)
    at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)
    at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:338)
    at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:84)
    at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:168)
    at com.ibm.mq.MQQueueManagerFactory.obtainBaseMQQueueManager(MQQueueManagerFactory.java:772)
    at com.ibm.mq.MQQueueManagerFactory.procure(MQQueueManagerFactory.java:697)
    at com.ibm.mq.MQQueueManagerFactory.constructQueueManager(MQQueueManagerFactory.java:657)
    at com.ibm.mq.MQQueueManagerFactory.createQueueManager(MQQueueManagerFactory.java:153)
    at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:526)
    at com.bea.wli.sb.resources.mqconnection.MQConnectionPoolFactory.makeObject(MQConnectionPoolFactory.java:281)
    at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)
    at com.bea.wli.sb.resources.mqconnection.MQConnectionPool.borrowObject(MQConnectionPool.java:58)
    at com.bea.wli.sb.resources.mqconnection.MQConnectionContext.getQueueManagerConnection(MQConnectionContext.java:140)
    at com.bea.wli.sb.transports.mq.MQOutboundMessageContext.send(MQOutboundMessageContext.java:565)
    at com.bea.wli.sb.transports.mq.MQTransportProvider.sendMessageAsync(MQTransportProvider.java:501)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:599)
    at com.bea.wli.sb.transports.Util$1.invoke(Util.java:82)
    at $Proxy73.sendMessageAsync(Unknown Source)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:547)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:482)
    at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:544)
    at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:422)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:296)
    at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:68)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:125)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:123)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:128)
    at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:441)
    at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:169)
    at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:136)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:572)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_1030_WLStub.invoke(Unknown Source)
    at com.bea.alsb.console.test.TestServiceClient.invoke(TestServiceClient.java:179)
    at com.bea.alsb.console.test.actions.DefaultRequestAction.invoke(DefaultRequestAction.java:117)
    at com.bea.alsb.console.test.actions.DefaultRequestAction.execute(DefaultRequestAction.java:70)
    at com.bea.alsb.console.test.actions.ServiceRequestAction.execute(ServiceRequestAction.java:80)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
    at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
    at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.processActionPerform(SBConsoleRequestProcessor.java:91)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
    at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.process(SBConsoleRequestProcessor.java:191)
    at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
    at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
    at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
    at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
    at com.bea.alsb.console.common.base.SBConsoleActionServlet.doGet(SBConsoleActionServlet.java:49)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1129)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:687)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
    at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.processAction(StrutsStubImpl.java:76)
    at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
    at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
    at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
    at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:220)
    at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
    at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
    at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
    at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
    at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
    at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
    at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<Oct 4, 2011 9:49:53 AM CEST> <Error> <WliSbTransports> <bsrpdev0012> <BsizzOSBServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1317714593310> <BEA-381916> <Error occured when connecting to MQ: Error trying to access queue MQ_TEST_OSB_QUEUE>
    Thanks in advance
    ferp

  • DefaultMessageListenerContainer Does receive message from remote Queue

    I am developing an application where I need to consume JMS messages from JMS Queue on remote weblogic server 10.3.3.0. My application is deployed WLS 10.3.2.0 and I using Spring 2.5.6. In my spring configuration, I have used Springframework's DefaultMessageListenerContainer to listen to the Queue on remote server.
    Now I have two scenarios in which DMLC does not consumer messages without server restart.
    Scenario 1: When the Remote server on which the JMS queue resides is restarted. DMLC stops consuming message from the Queue on remote server. After I restart my server, it starts consuming messages. But I want that DMLC starts consuming messages without the restarting server at my end.
    Scenario 2: When the remote server is running and I update/Redploy my application on WLS at my end. In this case also, DMLC stops receiving messages and I have to restart server at my end.
    Could anyone please help sorting out this issue?

    This seems like a Spring question, you might want to ty the Spring forums. I'm not sure why you would get the behaviour you see.

Maybe you are looking for