ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Global Cache timeout settings

Post new topic  Reply to topic
 Global Cache timeout settings « View previous topic :: View next topic » 
Author Message
twodouble8
PostPosted: Wed Feb 02, 2022 10:28 pm    Post subject: Global Cache timeout settings Reply with quote

Newbie

Joined: 02 Feb 2022
Posts: 1

Hello,

I'm currently facing an issue where there is connection issue to the global cache which I am troubleshooting separately. However, I have noticed when there is connection issue, the java code that is accessing the global cache will be running roughly for 600 seconds. Is there any configurations that can reduce this timeout ?

Below is the code that is used to access global cache:

try {
globalMap = MbGlobalMap.getGlobalMap(MAP_NAME);
strValue = (String) globalMap.get(strKey);
} catch (MbException mbe) {
System.out.println(mbe.getMessage());
mbe.printStackTrace();
}

Below is the error message:
[BIPmsgs:7164]BIP7164E: The message flow failed to connect to the global cache. A client
attempted to connect to WebSphere eXtreme Scale grid 'WMB' by using connection string 'local'. This connection attempt failed with the following error: 'timeout'. Ensure that the grid is available. If this grid is the integration node gl
obal cache, look for any previous errors relating to the catalog servers or container servers. : Failed to get session with grid, rolling back to previous method

Many thanks.
Back to top
View user's profile Send private message
abhi_thri
PostPosted: Mon Feb 07, 2022 11:21 am    Post subject: Re: Global Cache timeout settings Reply with quote

Knight

Joined: 17 Jul 2017
Posts: 516
Location: UK

twodouble8 wrote:
However, I have noticed when there is connection issue, the java code that is accessing the global cache will be running roughly for 600 seconds. Is there any configurations that can reduce this timeout ?


hi...I guess you are running into the default transaction timeout of 600 seconds.

Depending on how you are configuring the WXSServer (config service or policy) the overrideObjectGridFile param can be configured to change it - https://www.ibm.com/docs/en/app-connect/11.0.0?topic=properties-wxsserver-policy

https://www.ibm.com/docs/en/wxs/8.6.1?topic=properties-transactiontimeout-property
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Global Cache timeout settings
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.