| Author |
Message
|
| srikanthc60 |
 Posted: Fri Aug 28, 2015 1:32 pm Post subject: BIP1047E: The operation timed out waiting for a response. |
 |
|
Voyager
Joined: 21 Jul 2013
Posts: 79
|
Hi All,
One of our dev broker is giving time out errors for any command that we run against it.
I tried increasing the time out to greater that is there currently for the broker(300 to 2400). Even though it is giving time out errors.
Configuration change timeout = '2400' seconds
Internal configuration timeout = '240' seconds
Syslog has lot of errors like following for all of the EG's running on the broker.
BIP4512S: java.lang.NoClassDefFoundError: com.ibm.phpj.reflection.XAPIDebugProperty was thrown while loading Java user-defi
ned node class com.ibm.broker.php.PhpComputeElementDebugProperty. : MYDEV_BROKER.271e5002-4f01-0000-0080-c6166c6f60d3: com.ibm.broker.plugin.MbNodeDirector: 0: registerNodeClasses:
After a bunch of above errors (around 16) below entries are coming in sequence for
each EG running.
| Quote: |
BIP2116E: Message broker internal error: diagnostic information 'Fatal Error; exception thrown before initialisation complet
ed', 'Initialise execution group manager', '23462072', '1', '17', '16'. : MYDEV_BROKER.823a44f2-4e01-0000-0080-b7024c081190: /build/slot1/S800_P/src/DataFlowEngine/ImbMain.cpp: 231: ImbMain::ProgressChecker::~ProgressChecker: :
Aug 28 14:09:48 izadie4 user:err|error WebSphere Broker v8004[23462072]: (MYDEV_BROKER.EG2)[1]BIP2203E: An execution group has encountered a problem whilst starting. : MYDEV_BROKER.823a44f2-4e01-0000-0080-b7024c0811
90: /build/slot1/S800_P/src/DataFlowEngine/ImbMain.cpp: 1417: ImbMain::start: :
Aug 28 14:09:48 izadie4 user:err|error WebSphere Broker v8004[23462072]: (MYDEV_BROKER.EG2)[1]BIP5024E: The creation and preprocessing of the XML schemas in message set '/MQHA/MYDEV/data/mqsi/components/MYDEV_BRO
KER/823a44f2-4e01-0000-0080-b7024c081190/config/XMAP/' has failed. : MYDEV_BROKER.823a44f2-4e01-0000-0080-b7024c081190: /build/slot1/S800_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1897: ImbJ
avaExceptionUtils::throwableToNativeException: :
Aug 28 14:09:48 izadie4 user:err|error WebSphere Broker v8004[23462072]: (MYDEV_BROKER.EG2)[1]BIP4395E: Java exception: 'java.lang.NoClassDefFoundError'; thrown from class name: 'java.lang.ClassLoader', method name: 'd
efineClassImpl', file: 'ClassLoader.java', line: '-2' : MYDEV_BROKER.823a44f2-4e01-0000-0080-b7024c081190: /build/slot1/S800_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1915: ImbJavaExceptionU
tils::throwableToNativeException: :
Aug 28 14:09:48 izadie4 user:err|error WebSphere Broker v8004[23593400]: (MYDEV_BROKER.EG1)[1]BIP2116E: Message broker internal error: diagnostic information 'Fatal Error; exception thrown before initialisation completed'
, 'Initialise execution group manager', '23593400', '1', '17', '16'. : MYDEV_BROKER.6fdb81f4-4e01-0000-0080-9e135226df9c: /build/slot1/S800_P/src/DataFlowEngine/ImbMain.cpp: 231: ImbMain::ProgressChecker::~ProgressChecker::
Aug 28 14:09:48 izadie4 user:info WebSphere Broker v8004[23462072]: (MYDEV_BROKER.EG2)[1]BIP2204I: Execution group using process '23462072' thread '1' stopped. : MYDEV_BROKER.823a44f2-4e01-0000-0080-b7024c081190: /build/slot1/S800_P/src/DataFlowEngine/ImbMain.cpp: 1504: ImbMain::start: :
Aug 28 14:09:48 izadie4 user:err|error WebSphere Broker v8004[23593400]: (MYDEV_BROKER.EG1)[1]BIP2203E: An execution group has encountered a problem whilst starting. : MYDEV_BROKER.6fdb81f4-4e01-0000-0080-9e135226df9c:
/build/slot1/S800_P/src/DataFlowEngine/ImbMain.cpp: 1417: ImbMain::start: :
Aug 28 14:09:48 izadie4 user:err|error WebSphere Broker v8004[23593400]: (MYDEV_BROKER.EG1)[1]BIP5024E: The creation and preprocessing of the XML schemas in message set '/MQHA/MYDEV/data/mqsi/components/MYDEV_BROKER
/6fdb81f4-4e01-0000-0080-9e135226df9c/config/XMAP/' has failed. : MYDEV_BROKER.6fdb81f4-4e01-0000-0080-9e135226df9c: /build/slot1/S800_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1897: ImbJava
ExceptionUtils::throwableToNativeException: :
Aug 28 14:09:48 izadie4 user:err|error WebSphere Broker v8004[23593400]: (MYDEV_BROKER.EG1)[1]BIP4395E: Java exception: 'java.lang.NoClassDefFoundError'; thrown from class name: 'java.lang.ClassLoader', method name: 'defi
neClass', file: 'ClassLoader.java', line: '287' : MYDEV_BROKER.6fdb81f4-4e01-0000-0080-9e135226df9c: /build/slot1/S800_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1915: ImbJavaExceptionUtils::
throwableToNativeException: :
Aug 28 14:09:48 izadie4 user:info WebSphere Broker v8004[23593400]: (MYDEV_BROKER.EG1)[1]BIP2204I: Execution group using process '23593400' thread '1' stopped. : MYDEV_BROKER.6fdb81f4-4e01-0000-0080-9e135226df9c: /buil
d/slot1/S800_P/src/DataFlowEngine/ImbMain.cpp: 1504: ImbMain::start: :
Aug 28 14:09:48 izadie4 user:warn|warning WebSphere Broker v8004[26542492]: (MYDEV_BROKER)[15936]BIP2060W: The broker has detected that the Execution Group EG2, process ID 23462072, has shutdown. : MYDEV_BROKER.agen
t: /build/slot1/S800_P/src/AdminAgent/ImbAdminAgent.cpp: 5429: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Aug 28 14:09:48 izadie4 user:warn|warning WebSphere Broker v8004[26542492]: (MYDEV_BROKER)[15679]BIP2060W: The broker has detected that the Execution Group EG1, process ID 23593400, has shutdown. : MYDEV_BROKER.agent:
/build/slot1/S800_P/src/AdminAgent/ImbAdminAgent.cpp: 5429: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Aug 28 14:09:48 izadie4 user:info WebSphere Broker v8004[29687876]: (MYDEV_BROKER.EG1)[1]BIP2208I: Execution group (64) started: process '29687876'; thread '1'; additional information: brokerName 'MYDEV_BROKER' (operat
ion mode 'advanced'); executionGroupUUID '6fdb81f4-4e01-0000-0080-9e135226df9c'; executionGroupLabel 'EG1'; queueManagerName 'MYDEV'; trusted 'false'; userId 'MYDEV'; migrationNeeded 'false'; brokerUUID '4148848a-01f0-
11e2-8440-ac1433330000'; filePath '/opt/IBM/mqsi/8.0.0.4'; workPath '/MQHA/MYDEV/data/mqsi'; ICU Converter Path ''; ordinality '2'. : MYDEV_BROKER.6fdb81f4-4e01-0000-0080-9e135226df9c: /build/slot1/S800_P/src/DataFlowEng
ine/ImbMain.cpp: 762: ImbMain::start: :
Aug 28 14:09:48 izadie4 user:info WebSphere Broker v8004[15728764]: (MYDEV_BROKER.EG2)[1]BIP2208I: Execution group (64) started: process '15728764'; thread '1'; additional information: brokerName 'MYDEV_BROKER' (ope
ration mode 'advanced'); executionGroupUUID '823a44f2-4e01-0000-0080-b7024c081190'; executionGroupLabel 'EG2'; queueManagerName 'MYDEV'; trusted 'false'; userId 'MYDEV'; migrationNeeded 'false'; brokerUUID '4148848a
-01f0-11e2-8440-ac1433330000'; filePath '/opt/IBM/mqsi/8.0.0.4'; workPath '/MQHA/MYDEV/data/mqsi'; ICU Converter Path ''; ordinality '7'. : MYDEV_BROKER.823a44f2-4e01-0000-0080-b7024c081190: /build/slot1/S800_P/src/DataF
lowEngine/ImbMain.cpp: 762: ImbMain::start: :
|
Could any one help me to identify the issue with the broker !! 
Thanks in Advance!!!
|
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Aug 28, 2015 11:10 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I take it that you have already done the following
1) restarted the broker
2) rebooted the system that the broker is running on
If you haven't then please do 2) and report back.
My next step would be to reboot, not try starting the problem broker, create a new broker and check that it works
If that does work then I'd delete both brokers and re-create the old broker from the scripts that I have in my toolbox.
Dropping and re-crerating a broker using scripts can take less than 5 minutes. Sometimes it is a 'no-brainer' solution.
Finally, think back to what you were doing before this problem started.
There may even be some FDC files that might give a better insight to the problem.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Aug 28, 2015 11:21 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Re-creating a broker is like the old Windows solution - just reboot - if not then reinstall everything.
It's a cop out. We have brokers that have been around for many years and upgrades.
I had some odd problems with some recently after migration to IIB 9 and it even got to the point that I was tempted to trash them and start again.
However perseverance (and PMRs) uncovered the cause in the end and recreation would not have helped.
It's most likely to be something to do with what's deployed to the execution group.
Clear the contents of the EG and try again to prove that.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Aug 28, 2015 11:45 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| zpat wrote: |
Re-creating a broker is like the old Windows solution - just reboot - if not then reinstall everything.
It's a cop out. We have brokers that have been around for many years and upgrades.
I had some odd problems with some recently after migration to IIB 9 and it even got to the point that I was tempted to trash them and start again.
However perseverance (and PMRs) uncovered the cause in the end and recreation would not have helped.
It's most likely to be something to do with what's deployed to the execution group.
Clear the contents of the EG and try again to prove that. |
Very true but this is a Dev Broker. We have no isea about what else is running on this system. Perhaps something else has used all the available RAM?
Beside, sometimes things get into a mess on Dev systems. After all DEV is where you make ALL your mistakes(hopefully).
If this was UAT or PROD then yes I'd follow your approach. 
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| srikanthc60 |
| Posted: Sat Aug 29, 2015 12:04 am Post subject: |
|
|
Voyager
Joined: 21 Jul 2013
Posts: 79
|
Thanks for the reply!!
We found that the issue is with TMRDIR for jar files that doesn't have proper permissions..some one have removed the permissions.. Restsrted the broker after giving permissions back..It is working fine now!! |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Tue Mar 01, 2016 1:17 pm Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| srikanthc60 wrote: |
| We found that the issue is with TMRDIR for jar files that doesn't have proper permissions |
Could you elaborate on the nature of the cause and the solution? I may have a similar problem.
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine. |
|
| Back to top |
|
|
| srikanthc60 |
| Posted: Wed Mar 02, 2016 1:16 pm Post subject: |
|
|
Voyager
Joined: 21 Jul 2013
Posts: 79
|
Permissions for the TMRDIR where jar files will be placed related to Broker does not have proper permissions.
It should have proper permissions for others to read this directory to access the JAR required by the broker. |
|
| Back to top |
|
|
| Tibor |
| Posted: Mon Mar 21, 2016 8:13 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
|
| Back to top |
|
|
|
|
