| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| setting MQSI_CONFIGSTORE_THREAD_TIMEOUT on IIB v9002 |
« View previous topic :: View next topic » |
| Author |
Message
|
| vickas |
 Posted: Tue Oct 31, 2017 1:15 am Post subject: setting MQSI_CONFIGSTORE_THREAD_TIMEOUT on IIB v9002 |
 |
|
Centurion
Joined: 18 Aug 2013
Posts: 126
|
Hie All ,
Can we set MQSI_CONFIGSTORE_THREAD_TIMEOUT environment variable on IIB v9.0.0.2 ?
from what we read, the default value specified is 6 seconds and that is for Websphere message broker .
can we set the environment variable for IIB v9002 also ?
If so, what is the impact of setting the variable to 15 secs?
In what way increasing the MQSI_CONFIGSTORE_THREAD_TIMEOUT environment variable can be helpful ? |
|
| Back to top |
|
 |
| abhi_thri |
| Posted: Tue Oct 31, 2017 1:27 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
Are you trying to fix a specific issue? As per the IBM link (see below) deployment could fail with the timeout error in certain scenarios.
http://www-01.ibm.com/support/docview.wss?uid=swg1PM79743
BIP2112E <broker> <execution group> MESSAGE BROKER INTERNAL
ERROR: DIAGNOSTIC INFORMATION 'CS0010',
'Failed to obtain a write lock due to a timeout.'
Are you seeing such timeouts during deployment? If not there won't be any benefit in changing the value.
PS: In general MQSI* environment variables should work in higher versions but please do try in out and see, cheers. |
|
| Back to top |
|
|
| vickas |
| Posted: Tue Oct 31, 2017 1:53 am Post subject: |
|
|
Centurion
Joined: 18 Aug 2013
Posts: 126
|
Hi Abhi ,
thanks for the response.
The issue comes up with network issue, which results in interruption of CPS fence server with default file system blocking of 10 seconds.
We encounter
esb Had[7676]: VCS ERROR V-16-1-10205 Group CPSFENCE is faulted on system
and then the broker restarts Automatically.
from the Article http://www-01.ibm.com/support/docview.wss?uid=swg1PM79743, it says that the default time-out
interval is 6 seconds.
Now that we have network issue and the CPS fence server blocks file system for 10 secs , and the default time-out val for broker is 6 secs , it restarts Automatically (Assumption).
jus wanted to know what can be impacted if we gona increase the MQSI_CONFIGSTORE_THREAD_TIMEOUT value ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 31, 2017 4:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| vickas wrote: |
Hi Abhi ,
thanks for the response.
The issue comes up with network issue, which results in interruption of CPS fence server with default file system blocking of 10 seconds.
We encounter
esb Had[7676]: VCS ERROR V-16-1-10205 Group CPSFENCE is faulted on system
and then the broker restarts Automatically.
from the Article http://www-01.ibm.com/support/docview.wss?uid=swg1PM79743, it says that the default time-out
interval is 6 seconds.
Now that we have network issue and the CPS fence server blocks file system for 10 secs , and the default time-out val for broker is 6 secs , it restarts Automatically (Assumption).
jus wanted to know what can be impacted if we gona increase the MQSI_CONFIGSTORE_THREAD_TIMEOUT value ? |
Would not fixing the network problem first be the better thing to do? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| vickas |
| Posted: Tue Oct 31, 2017 10:18 pm Post subject: |
|
|
Centurion
Joined: 18 Aug 2013
Posts: 126
|
Hi fjb ,
Thanks for the response.
Yes , network issue has been fixed.
But becuase of the n/w issue ( IF repeats ) & CPS default filesystem blocking time , we do not want our broker ( IIB v9.0.02) to get effected .
So , is that a good approach to increase the MQSI_CONFIGSTORE_THREAD_TIMEOUT to 12 secs ??
I want to know if this variable can be applied to IIB & what can be the impact. |
|
| Back to top |
|
|
| vickas |
| Posted: Tue Nov 28, 2017 3:48 am Post subject: |
|
|
Centurion
Joined: 18 Aug 2013
Posts: 126
|
@ mqjeff , anything from your side ?
@ All , can we know when and why does the broker issues stop configuration message to all execution groups and stops itself soon after encountering the following exception ?
19:55:24 (Msg 1/1) BIP2152I: Configuration message received from broker
19:55:24 BIP2153I: About to 'Stop' an execution group
19:55:56 BIP2002W: The IBM Integration Bus service has stopped
| Code: |
[b]19:55:22 AgentFramework[9770]: VCS CRITICAL V-16-10061-639 CoordPoint:coordpoint:monitor:Administrator intervention is required because either the local node cannot access the coordination point server [xx.xxx.xxx.xxx]:443 or it is not registered on the coordination point server. If split brain happens in this condition, all nodes in the cluster may panic. Ensure that the local node can access the coordination points and the keys are registered. Refer to the cpsadm (1m) man page for more information.
19:55:23 VCS ERROR V-16-1-54031 Resource coordpoint (Owner: Unspecified, Group: CPSFENCE) is FAULTED on sys[/b] |
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
