I was working on a recently built Solaris 9 server with a fresh copy of MQ installed.
During application testing, we were getting 2195 errors from our application when establishing more than 3 concurrent connects to MQ.
After a day of wasted de-bugging of our application, we put it down to the system, and it seems we may have been correct. There is an install chapter in the MQ V6.0 documentation that should NOT be overlooked.
Quoting the Websphere MQ 6.0 Install Guide
WebSphere® MQ uses semaphores, shared memory, and file descriptors, and it is probable that the default resource limits are not adequate.
Review the system’s current resource limit configuration.
As the root user, load the relevant kernel modules into the running system by typing the following commands:
modload -p sys/msgsys
modload -p sys/shmsys
modload -p sys/semsys
Then display your current settings by typing the following command:
sysdef
Check that the following parameters are set to the minimum values required by WebSphere MQ, or higher.
You can see their minimum value tables in the Resource limit configuration Chapter of the MQ 6.0 Install Guide.
Sean said,
June 17, 2009 @ 11:30
Where can I find some companies or people with MQ knowledge in Australia?
Sean said,
June 17, 2009 @ 11:31
even better if Message Driven Processor knowledge…
lantrix said,
June 18, 2009 @ 13:00
The company I work for has MQ knowledge, having implemented IBM WebSphere MQ based middle-ware and messaging systems for both Government and Telecommunications companies in Australia.
If you would like, you can get contact details of the Australian Offices at the website.
Otherwise, if you want I can contact you directly and can introduce you to someone who can discuss your requirements.
RSS feed for comments on this post · TrackBack URI