| Author | Message | 
		
		  | anar | 
			  
				|  Posted: Tue Aug 10, 2010 4:21 am    Post subject: number of concurrent MQ Client connections |   |  | 
		
		  | Apprentice
 
 
 Joined: 28 Jun 2010Posts: 31
 
 
 | 
			  
				| Hi. 
 Whether there's a parameter controlling the number of concurrent client connections?
 I got a following situation:
 - ASP.NET WebService client puts messages to some queue_01.
 - some other application (application_B) Gets from the queue_01 and processes the messages.
 
 If I run simultaneously 10 ASP.NET clients to Put messages in the queue_01 only 2 messages at a time Put in the queue_01. Other 8 clients are still waiting till those 2 messages will be retrieved (Get) by the application_B.
 - how to enable all clients' messages being Put in queue without waiting others' ?
 
 NOTE: platform and product version info:
 Server OS: HP-UX 11.31 v3
 MQ Server: 7.0.1.2
 
 Thanks in advance.
 
 Best Regards,
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | anar | 
			  
				|  Posted: Tue Aug 10, 2010 5:07 am    Post subject: |   |  | 
		
		  | Apprentice
 
 
 Joined: 28 Jun 2010Posts: 31
 
 
 | 
			  
				| additional info: tried the below, with no changes in the Put behavior of the concurrent clients.
 - MQPMO_ASYNC_RESPONSE on the client MQPutMessageOptions
 - alter qlocal(Q.01) DEFPRESP(ASYNC)
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Tue Aug 10, 2010 10:24 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| How about turning off conversation sharing on the channel?  _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | anar | 
			  
				|  Posted: Tue Aug 10, 2010 10:58 pm    Post subject: MQCNO_NO_CONV_SHARING & SHARECNV(1) |   |  | 
		
		  | Apprentice
 
 
 Joined: 28 Jun 2010Posts: 31
 
 
 | 
			  
				| Thanks for the clue. 
 tried the MQCNO_NO_CONV_SHARING in the client side and SHARECNV(1) on the chl definition. unfortunately no change in the behavior.
 
 - anything that I could have missed?
 
 the channel is:
 
 
   
	| Code: |  
	| dis chl(CHL.CLI.02)
 2 : dis chl(CHL.CLI.02)
 AMQ8414: Display Channel details.
 CHANNEL(CHL.CLI.02)                     CHLTYPE(SVRCONN)
 ALTDATE(2010-08-11)                     ALTTIME(09.54.55)
 COMPHDR(NONE)                           COMPMSG(NONE)
 DESCR( )                                HBINT(300)
 KAINT(AUTO)                             MAXINST(999999999)
 MAXINSTC(999999999)                     MAXMSGL(4194304)
 MCAUSER(mqm)                            MONCHL(QMGR)
 RCVDATA( )                              RCVEXIT( )
 SCYDATA( )                              SCYEXIT( )
 SENDDATA( )                             SENDEXIT( )
 SHARECNV(1)                             SSLCAUTH(REQUIRED)
 SSLCIPH( )                              SSLPEER( )
 TRPTYPE(TCP)
 |  |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | anar | 
			  
				|  Posted: Wed Aug 11, 2010 1:22 am    Post subject: licensing |   |  | 
		
		  | Apprentice
 
 
 Joined: 28 Jun 2010Posts: 31
 
 
 | 
			  
				| - How could the licensing restrict number of concurrent Post's? - Does this sound reasonable, providing I try with the "90 days free trial" edition?
 
 Best Regards,
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Wed Aug 11, 2010 9:40 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| I hope your qmgr is not a mainframe without CAF attached... 
 There is a limit of 7 client connections to a MF without Client Attachment Facility...
  _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | anar | 
			  
				|  Posted: Thu Aug 12, 2010 1:35 am    Post subject: connection logic change |   |  | 
		
		  | Apprentice
 
 
 Joined: 28 Jun 2010Posts: 31
 
 
 | 
			  
				| Actually the connection logic in the WebService side seems was the cause. After modifying that now I could hit 24 concurrent Posts from the WebService in stress tests.
 Will try further, but have no clues yet for "why 24" .
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |