| Author |
Message
|
| aayteka |
 Posted: Thu Jan 04, 2007 4:37 am Post subject: Message Broker is not working! |
 |
|
Novice
Joined: 26 Dec 2006
Posts: 15
|
Hi,
We have a running system with Message Broker 6.0, MQ 6.0, db2 8.1 on a redhat machine.
after 31 december the message broker has never worked.
In the process list (ps) I can see bipservice, bipbroker, biphttplistener.
ýn stdout file of broker
_______________________________
[@APPNAME@] WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] BasicResourcePool$AcquireTask.run(1276) | com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@671a8551 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30).
[@APPNAME@] WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] BasicResourcePool$AcquireTask.run(1276) | com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@671b0551 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30).
[@APPNAME@] WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] BasicResourcePool$AcquireTask.run(1276) | com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1f880554 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30).
2006-12-31 18:29:38.818523 Execution group started.
2006-12-31 18:29:39.063332 Execution group started.
2006-12-31 18:29:39.323098 Execution group started.
2006-12-31 18:29:39.646935 Execution group started.
............
................
__________________________________________________________
in the var/log/messages/
Dec 31 04:02:01 tradbix1 syslogd 1.4.1: restart.
Dec 31 20:29:38 tradbix1 WebSphere Broker v6000[27692]: (WBRK6_DEFAULT_BROKER)[99879856]BIP2060W: The broker has detected that the Execution Group EXEGRP, process ID 27708, has shutdown. : WBRK6_DEFAULT_BROKER.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 4038: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Dec 31 20:29:38 tradbix1 WebSphere Broker v6000[27692]: (WBRK6_DEFAULT_BROKER)[99879856]BIP2060W: The broker has detected that the Execution Group EXEGRP, process ID 6950, has shutdown. : WBRK6_DEFAULT_BROKER.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 4038: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Dec 31 20:29:39 tradbix1 WebSphere Broker v6000[27692]: (WBRK6_DEFAULT_BROKER)[99879856]BIP2060W: The broker has detected that the Execution Group EXEGRP, process ID 6969, has shutdown. : WBRK6_DEFAULT_BROKER.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 4038: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Dec 31 20:29:39 tradbix1 WebSphere Broker v6000[27692]: (WBRK6_DEFAULT_BROKER)[99879856]BIP2060W: The broker has detected that the Execution Group EXEGRP, process ID 6988, has shutdown. : WBRK6_DEFAULT_BROKER.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 4038: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Dec 31 20:29:39 tradbix1 WebSphere Broker v6000[27692]: (WBRK6_DEFAULT_BROKER)[99879856]BIP2060W: The broker has detected that the Execution Group EXEGRP, process ID 7007, has shutdown. : WBRK6_DEFAULT_BROKER.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 4038: ImbAdminAgent::startAndMonitorADataFlowEngine: :
............
..................
_________________________________________
I have restarted the broker but the same problem has occured.
I have restarted queue manager and broker but the same problem has occured.
I have restarted the server (machine) but the same problem has occured.
I have reset the files under /var/mqm and home/db2inst1 but the same problem has occured.
Is anybody know the solution? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Jan 04, 2007 4:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Hopefully you have opened a PMR with IBM support by now.
Hopefully, you are running 6.0.0.3 of MB.
What was the last change made to the machine? The change of date should not have caused this problem.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| aayteka |
| Posted: Thu Jan 04, 2007 4:57 am Post subject: |
|
|
Novice
Joined: 26 Dec 2006
Posts: 15
|
We haven't opened any pmr yet.
We are using MB 6.0
We didn't change anything for weeks. But at 29 december I have manually closed more than 100 connections (remaining connections) with using the MQ explorer screens. This issue was discussed in the following topic,
http://www.mqseries.net/phpBB2/viewtopic.php?t=34204
So isn't this a common problem? and has a common solution?
We have reset /var/mqm and home/db2inst1. What can cause this problem? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 04, 2007 5:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
As discussed in your previous thread, what you're doing (using SYSTEM.ADMIN.SVRCONN for application connection) is a bit uncommon.
And no, this isn't a common problem. I think you are in PMR territory if you're on the latest release (i.e. missed off the 0.3 from your previous post).
When you say "We have reset..." what do you mean by that?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| aayteka |
| Posted: Thu Jan 04, 2007 5:32 am Post subject: |
|
|
Novice
Joined: 26 Dec 2006
Posts: 15
|
| Quote: |
| When you say "We have reset..." what do you mean by that? |
We have a clear backup of these directories (we have get after installation) and we have replaced the current content of these directories with the clear ones. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 04, 2007 5:39 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Not convinced clearing out /var/mqm was an especially good move. Without deleting the queue manager first. Same (I think) true for the DB2, though not my area of expertise.
This is sounding increasingly PMR like. Especially if you're on the latest release.
Other (fairly drastic) option would be to delete & rebuild queue manager & broker from backed-up definitions. I'd be inclined to give IBM a rattle first though.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| aayteka |
| Posted: Thu Jan 04, 2007 7:30 am Post subject: |
|
|
Novice
Joined: 26 Dec 2006
Posts: 15
|
The problem was the log file under /var/mqsi/component/BROKER_NAME/XXXXXX/stderr has the size of 2gb. I have deleted that log file and Broker started successfully.
If it is possible, I will change the logging mechanism in order to handle this kind of situations.
thanks for your help. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 04, 2007 7:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| aayteka wrote: |
| The problem was the log file under /var/mqsi/component/BROKER_NAME/XXXXXX/stderr |
| aayteka wrote: |
| We have reset /var/mqm |
I notice a slight discrepancy...
I'm far happy at the thought of scratching the broker's strerr output than scratching the queue manager's records.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| aayteka |
| Posted: Mon Jan 08, 2007 6:15 am Post subject: |
|
|
Novice
Joined: 26 Dec 2006
Posts: 15
|
Hi,
about the log file size problem, I was not in the developper group of the message broker project, but as far as I know stderr log file is controlled by standard message broker (not our application).
So is anybody know that can we set a size limit to that file or set a rolling mechanism?
thanks |
|
| Back to top |
|
|
| aayteka |
| Posted: Sun Apr 29, 2007 9:12 pm Post subject: |
|
|
Novice
Joined: 26 Dec 2006
Posts: 15
|
| The below problem has occured again and the application failed again! So is anybody know that can we set a size limit to "/var/mqsi/component/BROKER_NAME/XXXXXX/stderr" file or set a rolling mechanism? |
|
| Back to top |
|
|
|
|
