HP BAC 8.03 - Message Broker Hangs (2565 Views)
Reply
Occasional Advisor
Vito Fresiello
Posts: 13
Registered: ‎05-05-2011
Message 1 of 3 (2,565 Views)
Accepted Solution

HP BAC 8.03 - Message Broker Hangs

Hi all,

 

I'm experiencing a problem with BAC GW (8.03, running on Win 2003).I'm not able to see new data in the GW, also

if the BPMs are correctly sending data.

The problem seems to be caused by the MESSAGE BROKER process, who hangs in LAUNCHED status (when in READY status, it immediately returns in LAUNCHED status).

I've already tried to stop services and Reconnect to DB (GW, DP), but nothing has changed.

 

Any help appreciated. Thnx.

 

From the logs I see:

jk.log:

[Wed Sep 21 10:02:35 2011] [2328:4760] [error] ajp_service::jk_ajp_common.c (1942): (wdeWorker) Connecting to tomcat failed. Tomcat is probably not started or is listening on the wrong port

[Wed Sep 21 10:02:35 2011] [2328:4760] [error] HttpExtensionProc::jk_isapi_plugin.c (1117): service() failed

[Wed Sep 21 10:02:37 2011] [2328:5456] [error] ajp_service::jk_ajp_common.c (1942): (wdeWorker) Connecting to tomcat failed. Tomcat is probably not started or is listening on the wrong port

[Wed Sep 21 10:02:37 2011] [2328:5456] [error] HttpExtensionProc::jk_isapi_plugin.c (1117): service() failed

 

 

 

topaz_all.ejb.log

2011-09-21 10:06:25,021 [ReconnectThread-Monitor-[LOCAL]] (RetryWork.java:70) WARN  - Work Thread failed retry in 5000ms. [name=ReconnectThread-Monitor-[LOCAL];attempt=231;reason=java.net.ConnectException: Connection refused: connect: tcp://PIPPO-01:2507]
2011-09-21 10:06:30,960 [ReconnectThread-Monitor-[LOCAL]] (RetryWork.java:70) WARN  - Work Thread failed retry in 5000ms. [name=ReconnectThread-Monitor-[LOCAL];attempt=232;reason=java.net.ConnectException: Connection refused: connect: tcp://PIPPO
-01:2507]
2011-09-21 10:06:36,899 [ReconnectThread-Monitor-[LOCAL]] (RetryWork.java:70) WARN  - Work Thread failed retry in 5000ms. [name=ReconnectThread-Monitor-[LOCAL];attempt=233;reason=java.net.ConnectException: Connection refused: connect: tcp://PIPPO-01:2507]
2011-09-21 10:06:42,932 [ReconnectThread-Monitor-[LOCAL]] (RetryWork.java:70) WARN  - Work Thread failed retry in 5000ms. [name=ReconnectThread-Monitor-[LOCAL];attempt=234;reason=java.net.ConnectException: Connection refused: connect: tcp://PIPPO-01:2507]
2011-09-21 10:06:48,870 [ReconnectThread-Monitor-[LOCAL]] (RetryWork.java:70) WARN  - Work Thread failed retry in 5000ms. [name=ReconnectThread-Monitor-[LOCAL];attempt=235;reason=java.net.ConnectException: Connection refused: connect: tcp://PIPPO-01:2507]
2011-09-21 10:06:52,324 [Reconnect-Bus Monitor] (MonitorBusJMX.java:82) ERROR - Failed to initialize bus monitor
com.sonicsw.mf.mgmtapi.runtime.ProxyRuntimeException
    at com.sonicsw.mq.mgmtapi.runtime.impl.BrokerProxy.getMetricsInfo(BrokerProxy.java:856)
    at com.mercury.infra.bus.monitor.MeasurementManager.initMap(MeasurementManager.java:119)
    at com.mercury.infra.bus.monitor.MeasurementManager.<init>(MeasurementManager.java:146)
    at com.mercury.infra.bus.monitor.BrokerInfoImpl.initManager(BrokerInfoImpl.java:63)
    at com.mercury.infra.bus.monitor.BrokerInfoImpl.<init>(BrokerInfoImpl.java:50)
    at com.mercury.infra.bus.monitor.BrokerSystemManagement.createBrokerInfo(BrokerSystemManagement.java:119)
    at com.mercury.infra.bus.monitor.BrokerSystemManagement.getBrokerInfo(BrokerSystemManagement.java:102)
    at com.mercury.infra.bus.monitor.MonitorBusJMX.initializeField(MonitorBusJMX.java:75)
    at com.mercury.infra.bus.monitor.MonitorBusJMX.access$200(MonitorBusJMX.java:26)
    at com.mercury.infra.bus.monitor.MonitorBusJMX$1.doWork(MonitorBusJMX.java:61)
    at com.mercury.infra.bus.jms.RetryWork.run(RetryWork.java:66)
    at java.lang.Thread.run(Thread.java:595)
Caused by...
com.sonicsw.mf.comm.InvokeTimeoutException: Domain1.accvbacgw-01:ID=PIPPO-01 - invoke()
    at com.sonicsw.mf.comm.jms.ConnectorClient.invoke(ConnectorClient.java:844)
    at com.sonicsw.mf.comm.jms.ConnectorClient.invoke(ConnectorClient.java:637)
    at com.sonicsw.mf.jmx.client.JMSConnectorClient.invoke(JMSConnectorClient.java:846)
    at com.sonicsw.mf.jmx.client.JMSConnectorClient.invoke(JMSConnectorClient.java:803)
    at com.sonicsw.mq.mgmtapi.runtime.impl.BrokerProxy.getMetricsInfo(BrokerProxy.java:854)
    at com.mercury.infra.bus.monitor.MeasurementManager.initMap(MeasurementManager.java:119)
    at com.mercury.infra.bus.monitor.MeasurementManager.<init>(MeasurementManager.java:146)
    at com.mercury.infra.bus.monitor.BrokerInfoImpl.initManager(BrokerInfoImpl.java:63)
    at com.mercury.infra.bus.monitor.BrokerInfoImpl.<init>(BrokerInfoImpl.java:50)
    at com.mercury.infra.bus.monitor.BrokerSystemManagement.createBrokerInfo(BrokerSystemManagement.java:119)
    at com.mercury.infra.bus.monitor.BrokerSystemManagement.getBrokerInfo(BrokerSystemManagement.java:102)
    at com.mercury.infra.bus.monitor.MonitorBusJMX.initializeField(MonitorBusJMX.java:75)
    at com.mercury.infra.bus.monitor.MonitorBusJMX.access$200(MonitorBusJMX.java:26)
    at com.mercury.infra.bus.monitor.MonitorBusJMX$1.doWork(MonitorBusJMX.java:61)
    at com.mercury.infra.bus.jms.RetryWork.run(RetryWork.java:66)
    at java.lang.Thread.run(Thread.java:595)

Please use plain text.
Honored Contributor
parkar
Posts: 2,296
Registered: ‎01-23-2010
Message 2 of 3 (2,553 Views)

Re: HP BAC 8.03 - Message Broker Hangs


The following steps should be followed in order to reconfigure the Message Broker:
1. Stop BAC (DPS first, then GW)
2. Stop the WebServer
3. Open the "<HPBAC>/conf/bus/jms.configuration.status.properties" properties file.
4. Change the line "message.broker.status=configured" to "message.broker.status=nonconfigured".
5. Execute "Connect To Database" on DPS and GW
6. Start the WebServer
7. Start BAC (DPS first, then GW

Pls let us know if u still face the issue
Cheers!

Nvr Blame a day in ur life....... Good day gives "happiness" & Bad day gives "experience" ......
Please use plain text.
Occasional Advisor
Vito Fresiello
Posts: 13
Registered: ‎05-05-2011
Message 3 of 3 (2,546 Views)

Re: HP BAC 8.03 - Message Broker Hangs

Hi, I post the solution...is the standard procedure you can find on similar issues in the forum.

As reconnecting to the DB is not sufficient to fix it , when the message broker is corrupted, a Sonic re-installation is needed.

Here's the procedure:

 

1. Re-installing sonic will result in data loss - any data that has been queued up in sonic waiting to be processed will be lost.

2. if this procedure is attempted, it is best to do it on both DPS and gateway servers. otherwise the sonic databases will be out of sync.

- stop BAC (GW first, then on the DPS)
- under HPBAC\Sonic directory leave only bin, installation and input directories delete all others
- execute HPBAC\Sonic\bin\install.bat
- execute HPBSM\Sonic\bin\installSP.bat (BSM 9.x and above)
- execute HPBSM\Sonic\bin\installPatch.bat (BSM 9.x and above)
- In HPBAC\conf\bus\jms.configuration.status.properties make sure that the entries below are set as shown

  (otherwise change)

   domain.manager.status=nonconfigured
   message.broker.status=nonconfigured
- next execute "Connect to Database" wizard
- start BAC (DPS first, then GW)



 

BR

 

Vito

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation