| Author |
Message
|
| sebastia |
 Posted: Tue Jan 16, 2007 1:41 am Post subject: BIP1100E - how to increase timeout value. |
 |
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
I am getting the "BIP1100E" error =
"Broker BKNAME had not responded before the timeout occurred."
I am trying to increase the timeout value (90 seconds) using
mqsichangebroker BKNAME -g 300
and/or
mqsichangebroker BKNAME -k 300
but the timeout is NOT changed.
Well, the value in
/var/mqsi60/registry/BKNAME/CurrentVersion
it IS changed !?!?
("ConfigurationDelayTimeout" and "ConfigurationTimeout"
Need a machine Re-Start maybe ?
Any clue ?
Sebastian. |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Tue Jan 16, 2007 2:01 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi sebastia,
Did you try to figure out why the broker is not responding in time ? I've never had to increase the timeout...it works quite well on the default...
Is this error while connecting to the broker or when ur deploying something to it ?
What is your configuration details, broker and system..
Regards. |
|
| Back to top |
|
|
| sebastia |
| Posted: Tue Jan 16, 2007 2:13 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
The problem comes at a MQSIDEPLOY time, of course.
The machine is AIX 5.3, MB v 6.0.0.3, MQ 6.0.2.0
Let me re-visit the MQ logs just in case there is a MQ problem ...
Thanks ! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jan 16, 2007 2:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
mqsichangebroker has to be run when the broker is stopped.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sebastia |
| Posted: Tue Jan 16, 2007 3:02 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Thanks, Jeff - but MB complains if you try with Broker non-stopped,
so I couldn't DO that mistake.
Well, in fact I did, but received a beautifull
"BIP8018E: Component running." message ... ( )
First, I do
mqsistop BKNAME
then
mqsichangebroker BKNAME -g 300
with "Successfull completion". But I understand the change has not been done on the Broker, as it was STOPPED.
Now we go "mqsistart BKNAME" .. and I have deduced I need a "Config Deploy" - am I right ?
So I run
mqsideploy -n myconfig.config -b BKNAME
and get the first timeout :
BIP1100E: Broker BKNAME had not responded before the timeout occurred.
Second timeout comes if I try to deploy a BAR file ... quite the same.
>>>> What is the MQ "path" the deploy follows, so I can check it ?
(MQ log is clean).
Sebastian. |
|
| Back to top |
|
|
| sebastia |
| Posted: Tue Jan 16, 2007 3:11 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
well - we followed the Deploy path
... and there was a large queue
... and there was a stopped channel.
Thanks Elvis, Jeff ! |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Jan 16, 2007 7:16 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
BIP1100E means that you need to tell mqsideploy to wait for a longer period of time. But the timeout you need to specify is the -w flag on mqsideploy... not mqsichangebroker.
| Code: |
| '-w timeoutValue' value in seconds to wait for the broker to reply to the deploy request |
|
|
| Back to top |
|
|
| sebastia |
| Posted: Tue Jan 16, 2007 8:20 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Thanks a lot MATT -
--- >>> that IS the reason why the Timeout was NOT changing !!!!
() |
|
| Back to top |
|
|
| pragatid |
| Posted: Tue Oct 14, 2008 10:53 pm Post subject: |
|
|
Newbie
Joined: 14 Oct 2008
Posts: 1
|
| mqmatt wrote: |
BIP1100E means that you need to tell mqsideploy to wait for a longer period of time. But the timeout you need to specify is the -w flag on mqsideploy... not mqsichangebroker.
| Code: |
| '-w timeoutValue' value in seconds to wait for the broker to reply to the deploy request |
|
Dear Matt,
we too have similar problem wherein the broker times out when we try to deploy the bar file.
Here is the command we use:
$ mqsideploy -q msgbrk1 -b BRKER01 -e default -a /var/mqm/TryMQBar.bar -w 300
The error that we get is :
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1045I: Connecting to the Configuration Manager...
BIP1039I: Deploying BAR file '/var/mqm/TryMQBar.bar' to broker 'BRKER01' (execution group 'default') ...
BIP1100E: Broker BRKER01 had not responded before the timeout occurred.
Could you please help us on this.
Ths system that we use for bar file deployment is AIX.
Pragati D |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Oct 15, 2008 4:42 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Hi Pragatid,
Look in your broker/Config Manager's system log for error messages. If there's nothing, try increasing the timeout further. Or breaking down the BAR file into smaller ones.
Also, there's a bug in v6.1 which means that deployment can be slower; if you're using MB v6.1.0.2, raise a PMR. There's a fix that might improve things for you.
-Matt |
|
| Back to top |
|
|
|
|
