| Author |
Message
|
| dp111443 |
 Posted: Tue Nov 23, 2004 12:13 am Post subject: deployement problems |
 |
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Environment
--------------
Intel Linux running RedHat Enterprise Server Edition 3.1
I am running:
Websphere MQ 5.3 CSD 07
DB2 8.1 CSD06
WBIMB vs5 CSD04
I am having deployment problems from my WBIMB Eclypse Toolkit console and get the following errors:
--------------------------------------------------
BIP2087E: Broker GBSCC01T was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure.
------------------------------------------------------------------------
BIP2066E: Broker GBSCC01T (UUID 52360f60-0001-0000-0080-ff3518a2a51b) was unable to retrieve an internal configuration response message for execution group '$SYS_mqsi' within the 360 second Configuration Timeout.
The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to reduce the response turnaround time or increase it to allow for large and complex deployments.
Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if there is a problem with the execution group. You should check that your system is not running short of resources, for example, you may need to increase the WebSphere MQ log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Message Brokers Toolkit. If there are no other failure diagnostics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. Contact your IBM support center if you are unable to resolve the problem.
------------------------------------------------------------------------
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker GBSCC01T.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker GBSCC01T was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker GBSCC01T. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center.
----------------------------------
on the linux server I get
Nov 22 15:00:11 gblabl10 MQSIv500[4074]: (GBSCC01T)[16384]BIP2066E: Broker GBSCC01T (UUID 52360f60-0001-0000-0080-ff3518a2a51b) was unable to retrieve an internal configuration response message for execution group 'default' within the 360 second Configuration Timeout. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 2400: ImbAdminAgent::receiveEGResponse: :
Nov 22 15:00:15 gblabl10 MQSIv500[5294]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5294'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:16 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5294, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:16 gblabl10 MQSIv500[5298]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5298'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:17 gblabl10 MQSIv500[5302]: (GBSCC01T.default)[16384]BIP2201I: Execution Group started: process '5302'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '2a01b860-0001-0000-0080-ff3518a2a51b'; executionGroupLabel 'default'; defaultExecutionGroup 'false'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.2a01b860-0001-0000-0080-ff3518a2a51b: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:17 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5298, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:17 gblabl10 MQSIv500[5306]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5306'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:18 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5306, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:18 gblabl10 MQSIv500[5310]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5310'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:19 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5310, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:19 gblabl10 MQSIv500[5314]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5314'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:20 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5314, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:20 gblabl10 MQSIv500[5318]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5318'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:21 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5318, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:22 gblabl10 MQSIv500[5322]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5322'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:22 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5322, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:33 gblabl10 MQSIv500[5373]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5373'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:34 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5373, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:34 gblabl10 MQSIv500[5376]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5376'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:35 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5376, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:35 gblabl10 MQSIv500[5385]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5385'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:36 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5385, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:36 gblabl10 MQSIv500[5388]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5388'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:37 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5388, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:37 gblabl10 MQSIv500[5391]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5391'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:38 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5391, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:38 gblabl10 MQSIv500[5394]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5394'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:39 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5394, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:39 gblabl10 MQSIv500[5397]: (GBSCC01T.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '5397'; thread '16384'; additional information: brokerName 'GBSCC01T'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'GBSCC01T'; trusted 'false'; dataSourceName 'GBSCC01T'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '52360f60-0001-0000-0080-ff3518a2a51b'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : GBSCC01T.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Nov 22 15:00:40 gblabl10 MQSIv500[4090]: (GBSCC01T)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 5397, has shutdown. : GBSCC01T.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 22 15:00:58 gblabl10 kernel: application bug: bipservice(4075) has SIGCHLD set to SIG_IGN but calls wait().
Nov 22 15:00:58 gblabl10 kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
Nov 22 15:01:59 gblabl10 kernel: application bug: bipservice(4075) has SIGCHLD set to SIG_IGN but calls wait().
Nov 22 15:01:59 gblabl10 kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
Nov 22 15:02:59 gblabl10 kernel: application bug: bipservice(4075) has SIGCHLD set to SIG_IGN but calls wait().
Nov 22 15:02:59 gblabl10 kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
I have looked through forums, etc and checked authorisations and still cannot figure out what the problem is. The toolkit
shows that the execution group that I created isn't running and I can't deploy to it. It could be at a higher level where it can'
see the actualy broker. all the MQ elements are ok too. I can send messages to and back between the config mgr queue mgr and the
broker queue mgr.
I can confirm that the broker and DB2 are running on the linux server.
the wbimb user is part of the mqbrkrs group.
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
 |
| kirani |
| Posted: Tue Nov 23, 2004 12:17 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
since your broker and config mgr on on different machines, please make sure your channels are up and running between config mgr queue manager and Broker queue manager.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| shanson |
| Posted: Tue Nov 23, 2004 2:16 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
When a successful response from a complete deploy has been received by the config mgr, it issues a second configuration request to the broker to re-take out the subscriptions it has on certain $SYS topics (needed to keep the message flow start/stop status and subscriptiuons view up to date). The BIP1536 message is issued by the config mgr when this second request returns an unsuccessful response. So I don't think the problem is to do with channels as messages are flowing to and fro.
The BIP2066 message is issued by the admin agent process in the broker when it does not get a response back from the DataFlowEngine process (execution group) - in this case for the subscription request.
A common cause of BIP1536 is a security problem - the config manager's userid is not recognised by the broker. You need to make sure that the Linux system has a userid for the config manager's Windows userid. |
|
| Back to top |
|
|
| dp111443 |
| Posted: Wed Nov 24, 2004 5:57 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Thanks shanson,
your right that the queue managers and the channels are ok as I have tested this both ways.
I think by looking at the sys logs is that the broker starts up ok but the execution group (default) falls over soon after.
the user on the config mgr pc is 'wbimb'. same as the broker userid on the linux broker.
as anyone seen this before?
thanks,
Dharmesh
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
| shanson |
| Posted: Wed Nov 24, 2004 6:51 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| Sounds like a message flow you are deploying is starting up and then causing a crash? Any messages in the event log? If you have several flows try deploying them one at a time to find the culprit. |
|
| Back to top |
|
|
| rajmq |
| Posted: Mon Nov 29, 2004 7:41 am Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi,
Did you solved the problem ??
Cheers,
RJ |
|
| Back to top |
|
|
| samgunddi |
| Posted: Fri Jan 28, 2005 12:00 pm Post subject: |
|
|
Acolyte
Joined: 17 May 2004
Posts: 54
|
Hi,
I am experiencing a similar problem, Did you solve it?
Thanks in adv. |
|
| Back to top |
|
|
| vmurali_au |
| Posted: Mon Apr 25, 2005 3:18 am Post subject: |
|
|
Voyager
Joined: 26 Mar 2004
Posts: 76
|
Same problem for me too.
But i have both the configmgr & broker in the same PC.
I have created sender & reciver channels between both and when deployed the channels get started and mesage flows. But after some time i get the above same 3 errors. |
|
| Back to top |
|
|
| MikeC |
| Posted: Fri May 06, 2005 7:40 am Post subject: |
|
|
Acolyte
Joined: 30 Jun 2003
Posts: 55
Location: Toronto, Canada
|
I'm having the same problem too. Deploy fails with BIP1536S, BIP2066E and BIP2087E and syslog shows BIP2060W. The channels are running between the broker (AIX) and configmgr. I have increased the Configuration Timeout to 1/2 an hour (1800 secs.) and still no luck. I read something about setting the LANG environment variable to EN_US, but that didn't help either. .. (For me at least).
Has anyone made any headway with this?
_________________
-Mike. |
|
| Back to top |
|
|
| JT |
| Posted: Fri May 06, 2005 8:15 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
When this occurs, check the broker queue manager for messages on the 'SYSTEM.BROKER.xxxxx' queues. A build-up of messages indicates a problem.
Additionally, check to see if the input handle count is at least 1. A value of 0 also indicates a problem. |
|
| Back to top |
|
|
| solomita |
| Posted: Thu Jun 30, 2005 8:03 pm Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
I am having the same problem - has anyone resolved this? I have the same user id on the windows box that the config mgr is created with as the id on the linux box where the broker is created at hte customer.
On my machine, they are different but I added the windows id to the linux box. What groups should this be part of?
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| Schwabinger7 |
| Posted: Mon Oct 24, 2005 6:03 am Post subject: |
|
|
Newbie
Joined: 02 Apr 2004
Posts: 9
Location: Gothenburg / Sweden
|
We experience the same problem on a RH ES 3.0. We use the WMB6 TK & CFGMGR to administer a WBIMB5.0 Broker on the same box, both are using the same qmgr. Has anyone resolved this?
Thank you in advance!
//Stephan |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Oct 24, 2005 6:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Schwabinger7 wrote: |
We experience the same problem on a RH ES 3.0. We use the WMB6 TK & CFGMGR to administer a WBIMB5.0 Broker on the same box, both are using the same qmgr. Has anyone resolved this?
Thank you in advance!
//Stephan |
This sounds like a completely different problem to me.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ayanc |
| Posted: Mon Oct 24, 2005 8:31 pm Post subject: |
|
|
Voyager
Joined: 15 Nov 2004
Posts: 88
|
Hi,
I am not sure about the linux environment. Our config manager is in windows and broker in HP UX .
There are two things we check in order to resolve such a similar problem.
1. Communication channels
The above you have already checked. So, I may presume that it is fine.
2. The message flow
If your message flow has a problem then it crashes the EG.
Solution: Try with a message flow which you are sure is running fine. If you don't have one then create a very very simple message flow.
However at this stage you must kill the DataFlowEngine process in your linux env. You will find that after you kill the process it starts up under a new process ID (at least it does in HP UX).
Now you must redeploy the message flow.
Thanks. |
|
| Back to top |
|
|
|
|
