| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to manage MQ Client Java connexion ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| opmind |
 Posted: Tue Oct 05, 2004 5:17 am Post subject: How to manage MQ Client Java connexion ? |
 |
|
Acolyte
Joined: 04 Dec 2001
Posts: 68
|
Hello there,
I'm not a developper and I have a serious problem. We hava a WAS application which is putting and getting message to/from MQseries, using MQ Client for Java.
The problem is that this application creates // connexions to MQSeries ( so much ) and our Queue Manager can't accept ( Because I don't want  ) too much DEF.SVRCONN connexion.
The question is, How can we manage so much java client connexion to let active in // only 5 or 10 simultaneous connexion ?
Thx a lot for answers.
Cyril |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Tue Oct 05, 2004 6:51 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
Getting applications to not use SYSTEM.DEF.SVRCONN is a good idea but WHY do you want the number of connections to be so low?
A single CPU box with a WMQ v5.3 queue manager can easily handle 400 connections at a time. Actually, at my clients site, we have an older SPARC box 1 CPU & 1MB memory handling 1200 connections from a variety of WebLogic domains that are running JMS/Java apps. The MQ box is busy but nothing serious.
For JMS/Java applications, have the developer / JMS Admin configure the connection pool's min / max values to be reasonable (i.e. use the 1 to 10 rule for starters - 1 connection for up to 10 threads.).
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| csmith28 |
| Posted: Tue Oct 05, 2004 4:18 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Most definitly, do not allow Applications to use your SYSTEM.DEF.SVRCONN Channel. The SYSTEM.DEF.SVRCONN channel is only supposed to be used as a template for creation SVRCONN channels.
For example if you run the following command:
| Code: |
| echo "define chl(DEV.APP.SVRCONN.CL01) chltype(SVRCONN)" | runmqsc MQMGRNAME |
MQ will create the channel on the named MQManager with the name "DEV.APP.SVRCONN.CL01" based on the attributes of the SYSTEM.DEF.SVRCONN channel.
So, if you allow your applictions to use the SYSTEM.DEF.SVRCONN channel and the developers suddenly want to send a message larger than 4meg or a message you would have to modify your default SVRCONN Channel Model. If an application wanted to specify an MCAUSER well then your pooched.
Alway define a unique SVRCONN channel for each application.
Note: The Maximumun number of channels that can run on your MQManager is 200 by default unless you add a MaxChannels = number stanza in your qm.ini file.
5 or 10 simultaneous "connections" is not outrageous by any means.
Relax, MQSeries is not a resource hog.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue Oct 05, 2004 5:48 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| Quote: |
| Note: The Maximumun number of channels that can run on your MQManager is 200 by default unless you add a MaxChannels = number stanza in your qm.ini file. |
The default is 100 not 200 and for Windows, those values are in the registry (Use WMQ Services to set it rather than editing the registry).
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| 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
|
|
|
|
