Skip to main content

WebSphere MQ client connection failures due to resource shortages - Middleware News

WebSphere MQ client connection failures due to resource shortages
Technote (troubleshooting) - Middleware News


Problem(Abstract)
Your WebSphere MQ client suddenly fails when attempting to connect to your MQ server.

Symptom
You receive many FDCs for the AMQRMPPA and RUNMQLSR processes. The FDCs indicate a shortage of system resources.

xecP_E_NO_RESOURCE
rrcE_CREATE_THREAD_ERROR
xecL_E_TOO_MANY_HANDLES
rc 1450 (NO_SYSTEM_RESOURCES) from WriteFile
rc 12 (ENOMEM = insufficient system resources)

Cause
Recent changes to your Security Exit program caused the resource problem.

Diagnosing the problem
The following errors were reported in FDC files on the server:

Probe Id :- XC035007
Component :- xcsCreateThread
Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzlaa0.exe
Major Errorcode :- xecP_E_NO_RESOURCE
Comment1 :- Not enough space

Probe Id :- ZT049001
Component :- zutPreReadMachineIniFile
Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqmsrvn.exe
Major Errorcode :- xecF_E_UNEXPECTED_RC
Minor Errorcode :- xecU_W_KEY_NOT_FOUND

Probe Id :- ZS266000
Component :- lpiObtainQMDetails
Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqmsrvn.exe
Major Errorcode :- xecF_E_UNEXPECTED_RC
Minor Errorcode :- MQRC_UNEXPECTED_ERROR

Probe Id :- ZC000040
Component :- zcpCreatePipe
Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe
Major Errorcode :- xecF_E_UNEXPECTED_RC
Minor Errorcode :- xecL_E_TOO_MANY_HANDLES

Probe Id :- ZX005025
Component :- zxcProcessChildren
Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe
Major Errorcode :- zrcX_PROCESS_MISSING

Probe Id :- XY195001
Component :- xstSemaphoreRequest
Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqxssvn.exe
Major Errorcode :- xecL_E_TOO_MANY_HANDLES
Comment1 :- Failed to create Event semaphore:Global\mqm.qmgrs.MAIL1!STATION
Comment2 :- Not enough storage is available to process this command.

Probe Id :- XC381009
Component :- xcsDisplayMessageForSubpool
Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\RUNMQLSR.exe
Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC
Comment1 :- WinNT error 1450 from WriteFile.
Comment2 :- Insufficient system resources exist

Refer to the WebSphere MQ Messages manual, chapter 8, for a list of MQ reason codes and their meanings.

Resolving the problem
Make corrections to your security exit so that it does not leak system resources like handles and memory.



AMQ9508 RUNMQSC Command Fails
Technote (troubleshooting)


Problem(Abstract)

You make a user a member of the mqm group. You logon with that uid, test with the RUNMQSC command and fail with the following:

$ RUNMQSC
Starting MQSeries Commands.
AMQ9508: Program cannot connect to the queue manager.
No MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.

Resolving the problem
WebSphere MQ caches group membership for all users at startup. You must restart the queue manager to pick up changes in group membership.



AMQ9524 and AMQ9508 reason code MQRC_SECURITY_ERROR (2063)
Technote (troubleshooting)



Problem(Abstract)

Your queue manager fails to connect to another WebSphere® MQ Solaris queue manager. The connection fails with: AMQ9524 - queue manager not available.


Symptom
Error logs shows:

AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'SDQA41' failed with reason code
2063 MQRC_SECURITY_ERROR.

AMQ9509: Program cannot open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object 'ICTXXT01'
queue manager 'SDQA41' failed with reason code 2085.

Cause

The issue is with the userid "mqm" being created LOCALLY. The Solaris box was using NIS+. The security error was due to a conflict between the local userid and NIS+ userid.

Resolving the problem
Delete the local userid "mqm".


Additional information
2063 0x0000080f MQRC_SECURITY_ERROR
2085 0x00000825 MQRC_UNKNOWN_OBJECT_NAME

FDC's report the following:

MQSeries First Failure Symptom Report
| =====================================
| Host Name :- XXXXXXXX (SunOS 5.6)
| PIDS :- 5765B75
| LVLS :- 520
| Product Long Name :- MQSeries for Sun Solaris 2 (Sparc)
| Vendor :- IBM
| Probe Id :- ZF048015
| Application Name :- MQM
| Component :- zfu_as_searchprincipallist
| Build Date :- Nov 7 2000
| CMVC level :- p000-L001106
| Build Type :- IKAP - (Production)
| UserID :- 00011001 (root)
| Program Name :- amqzlaa0_nd
| Process :- 00014376
| Thread :- 00000003
| QueueManager :- SDQA41
| Major Errorcode :- krcE_UNEXPECTED_ERROR
| Minor Errorcode :- OK
| Probe Type :- INCORROUT
| Probe Severity :- 2
| Probe Description :- AMQ6125: An internal MQSeries error has occurred.
|
+--------------------------------------------------------------

MQM Function Stack
zlaMainThread
zlaProcessMessage
zlaProcessMQIRequest
zlaMQCONN
zsqMQCONN
kpiMQCONN
kqiAuthorityChecks
gpiCheckObjectAuthority
zfu_as_checkobjectauthority
zfu_as_calculateauthority
zfu_as_searchprincipallist
xcsFFST

Comments

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201

IBM WebSphere MQ – Common install/uninstall issues for MQ Version on Windows - Middleware News

Creating a log file when you install or uninstall WebSphere MQ WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). If you install the MQ server or client through launchpad , MQPARMS or setup.exe , then a log file is automatically generated in %temp% during installation. Alternatively you can supply parameters on the installation MSI command msiexec to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). If you uninstall through the Windows Add/Remove programs option, no log file is generated. You should either uninstall from the MSI command line and supply parameters to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). For details on how to enable MSI logging, see the following article in the WebSphere MQ product documentation: Advanced installation using msiexec For details on how to enable system-w