|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| MQRC_MAX_CONNS_LIMIT_REACHED code 2025 | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | loudcfla | 
			  
				|  Posted: Fri Aug 06, 2004 9:20 am    Post subject: MQRC_MAX_CONNS_LIMIT_REACHED code 2025 |   |  |  
		  | Acolyte
 
 
 Joined: 05 May 2002Posts: 58
 
 
 | 
			  
				| Hello, 
 We have MQseries 5.2 on the SunSolaris platform. We are getting 2025's which indicate insufficient client connections, at least that's ho wI read the book.
 
 Since I am the MVS MQ person, can someone tell me where this parm is on SunSolaris and what the parm is that I need to change?
 
 ALso does anyone have a recommended value or perhaps a method of determining what the value should be?
 
 Thanks much!
 |  |  
		  | Back to top |  |  
		  |  |  
		  | fjb_saper | 
			  
				|  Posted: Fri Aug 06, 2004 3:52 pm    Post subject: |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| Check out your queue manager settings runmqsc:
 dis qmgr all
 
 It should give you the max connection handles at any one time.
 
 Before changing anything I would take stock of who is connecting
 dis chl(*) type(svrconn)
 
 and check your queues (from memory)
 dis q(*) opprocs ipprocs
 
 This should give you an idea of how many handles are currently working with the queue manager. If you are quite short of the max and I expect you will be, you will need the help of the apps developers. You may have either a network problem (search this site for disconnect info (2059 ?) or an application is not releasing properly its MQ resources (I would expect that to be the case).
 
 Hope it helps some.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | OmPat | 
			  
				|  Posted: Fri Aug 06, 2004 6:11 pm    Post subject: |   |  |  
		  | Apprentice
 
 
 Joined: 20 Jul 2004Posts: 33
 Location: Charlotte
 
 | 
			  
				| are u reaching ur maxchannel limit... Try changing that from the default value of 100. FYI you can change the MAXCHANNEL property in QM.INI file. Hope that helps.. 
 
 
 Thanks,
 ~Om
 _________________
 IBM Certified WMQ V5.3 System Administrator
 IBM Certified WMQ V5.3 Solutions Designer
 Brainbench Certified MQ Expert
 IBM Certified WMQI V2.1 Solutions Expert
 IBM Certified WMQI V2.1 Specialist
 |  |  
		  | Back to top |  |  
		  |  |  
		  | kman | 
			  
				|  Posted: Mon Aug 09, 2004 7:41 pm    Post subject: |   |  |  
		  | Partisan
 
 
 Joined: 21 Jan 2003Posts: 309
 Location: Kuala Lumpur, Malaysia
 
 | 
			  
				| Different platform has different maxchannel limit. You should check the Clients manual. 
 I believe on Solaris it is 100.
 
 
 
   
	| Code: |  
	| An excerpt of a qm.ini file follows. It specifies that the TCP/IP listener is to listen
 on port 2500, the maximum number of current channels is to be 100 and the
 maximum number of active channels is to be 50.
 TCP:
 Port=2500
 CHANNELS:
 MaxChannels=100
 MaxActiveChannels=50
 |  
 
 I would suggest looking at the possible application problem of not closing down the connection properly once processing finishes, as suggested by fjb_saper. That is the likely causes you run out of channels.
 |  |  
		  | 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
 
 |  |  |  |