MQ broker has terminated unexpectedly - Websphere

This is a discussion on MQ broker has terminated unexpectedly - Websphere ; Dear all, I get an AIX machine running WAS 5.0.2.3 and had the Tivoli Identity Manager 4.5.1 installed. From the SystemOut.log, I found the following error, [3/5/05 0:13:36:970 CST] 91e2dbb JMSEmbeddedPr A MSGS0051I: Queue Manager open for business [3/5/05 0:13:37:005 ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: MQ broker has terminated unexpectedly

  1. MQ broker has terminated unexpectedly

    Dear all,

    I get an AIX machine running WAS 5.0.2.3 and had the Tivoli Identity Manager
    4.5.1 installed. From the SystemOut.log, I found the following error,

    [3/5/05 0:13:36:970 CST] 91e2dbb JMSEmbeddedPr A MSGS0051I: Queue Manager
    open for business
    [3/5/05 0:13:37:005 CST] 91e2dbb JMSEmbeddedPr A MSGS0052I: Starting the
    Broker
    [3/5/05 0:13:37:537 CST] 69222da8 BrokerDFEThre E MSGS0201E: Unable to start
    the Broker because WebSphere Embedded Messaging
    Server support not been installed
    [3/5/05 0:16:37:628 CST] 91e2dbb BrokerManager E MSGS0252E: The Broker has
    terminated unexpectedly
    [3/5/05 0:16:38:075 CST] 91e2dbb JMSService E MSGS0001E: Starting the
    JMS Server failed with exception: java.lang.Excepti
    on: MSGS0252E: The Broker has terminated unexpectedly
    at
    com.ibm.ws.messaging.BrokerManager.pingDFE(BrokerM anager.java:344)
    at
    com.ibm.ws.messaging.BrokerManager.startFlows(Brok erManager.java:808)
    at
    com.ibm.ws.messaging.BrokerManager.startBroker(Bro kerManager.java:251)
    at
    com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start (JMSEmbeddedProviderImpl.j
    ava:194)
    at com.ibm.ws.messaging.JMSService.start(JMSService.j ava:288)
    at
    com.ibm.ws.runtime.component.ContainerImpl.startCo mponents(ContainerImpl.jav
    a:543)
    at
    com.ibm.ws.runtime.component.ContainerImpl.start(C ontainerImpl.java:418)
    at
    com.ibm.ws.runtime.component.ServerImpl.start(Serv erImpl.java:183)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:12 8)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225 )
    at java.lang.reflect.Method.invoke(Native Method)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.ja va:94)

    after that the Tivoli Identity Manager seems having difficulty in processing
    jobs, does anyone have this error before? Any ideas to solve this problem?

    Thank you.

    Derek



  2. Re: MQ broker has terminated unexpectedly

    This is your problem:
    [3/5/05 0:13:37:537 CST] 69222da8 BrokerDFEThre E MSGS0201E: Unable to start
    the Broker because WebSphere Embedded Messaging Server support not been
    installed

    Sunit


    "Derek" wrote in message
    news:d1u215$3b7q$1@news.boulder.ibm.com...
    > Dear all,
    >
    > I get an AIX machine running WAS 5.0.2.3 and had the Tivoli Identity
    > Manager
    > 4.5.1 installed. From the SystemOut.log, I found the following error,
    >
    > [3/5/05 0:13:36:970 CST] 91e2dbb JMSEmbeddedPr A MSGS0051I: Queue Manager
    > open for business
    > [3/5/05 0:13:37:005 CST] 91e2dbb JMSEmbeddedPr A MSGS0052I: Starting the
    > Broker
    > [3/5/05 0:13:37:537 CST] 69222da8 BrokerDFEThre E MSGS0201E: Unable to
    > start
    > the Broker because WebSphere Embedded Messaging
    > Server support not been installed
    > [3/5/05 0:16:37:628 CST] 91e2dbb BrokerManager E MSGS0252E: The Broker
    > has
    > terminated unexpectedly
    > [3/5/05 0:16:38:075 CST] 91e2dbb JMSService E MSGS0001E: Starting the
    > JMS Server failed with exception: java.lang.Excepti
    > on: MSGS0252E: The Broker has terminated unexpectedly
    > at
    > com.ibm.ws.messaging.BrokerManager.pingDFE(BrokerM anager.java:344)
    > at
    > com.ibm.ws.messaging.BrokerManager.startFlows(Brok erManager.java:808)
    > at
    > com.ibm.ws.messaging.BrokerManager.startBroker(Bro kerManager.java:251)
    > at
    > com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start (JMSEmbeddedProviderImpl.j
    > ava:194)
    > at com.ibm.ws.messaging.JMSService.start(JMSService.j ava:288)
    > at
    > com.ibm.ws.runtime.component.ContainerImpl.startCo mponents(ContainerImpl.jav
    > a:543)
    > at
    > com.ibm.ws.runtime.component.ContainerImpl.start(C ontainerImpl.java:418)
    > at
    > com.ibm.ws.runtime.component.ServerImpl.start(Serv erImpl.java:183)
    > at com.ibm.ws.runtime.WsServer.start(WsServer.java:12 8)
    > at com.ibm.ws.runtime.WsServer.main(WsServer.java:225 )
    > at java.lang.reflect.Method.invoke(Native Method)
    > at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.ja va:94)
    >
    > after that the Tivoli Identity Manager seems having difficulty in
    > processing
    > jobs, does anyone have this error before? Any ideas to solve this problem?
    >
    > Thank you.
    >
    > Derek
    >
    >




+ Reply to Thread