Skip to main content

AMQ5008 IBM Websphere MQ Explorer fails - Middleware News

AMQ5008 IBM Websphere MQ Explorer fails - Middleware News


Problem

You are trying to use the MQ Explorer on WebSphere MQ for Linux V6.0. You receive error messages, FDCs, and the following error message during the startup of the GUI:

Problems opening perspective
'com.ibm.mq.explorer.ui.internal perspective mqperspective'

Furthermore, the left navigational panel does not show any entries.

Symptom

AMQ5008: An essential WebSphere MQ process 4427 (amqzfuma) cannot be
found and is assumed to be terminated.

Cause

It is very likely that the UNIX group for the userid who is trying to launch the MQ Explorer does not exist in the local machine and a placeholder number is being used.
For example, when you use "ls -l" on files in the home directory of the user, there is a number, such as 102, instead of a group name.

Resolving the problem

The root user should ensure that the placeholder group number for the user in question is a fully registered group for the local machine, such as in the /etc/group file.

Additional information
Some symptoms for this problem can be found in the /var/mqm/errors/AMQERR01.LOG file, such as:

AMQ5008: An essential WebSphere MQ process 4427 (amqzfuma) cannot be
found and is assumed to be terminated.

AMQ6090: WebSphere MQ was unable to display an error message 893.
EXPLANATION:
MQ has attempted to display the message associated with return code
hexadecimal '893'. The return code indicates that there is no message text
associated with the message. Associated with the request are inserts 0 : 0 : : : .

The FDC file that corresponds to the above error message is likely to have:

Probe Id :- XC130004
Program Name :- amqzfuma
Major Errorcode :- STOP
Minor Errorcode :- OK
Probe Type :- HALT6109
Probe Severity :- 1
Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred.
FDCSequenceNumber :- 0
Arith1 :- 11 b
Comment1 :- SIGSEGV: address not mapped((nil))
+---
MQM Function Stack
zfuProcessMessage
zfuCacheAuthQueue
lpiSPIMQConnect
zstMQConnect
zifMQCONN
zsqMQCONN
kpiMQCONN
kqiAuthorityChecks
gpiCheckObjectAuthority
zfu_as_checkobjectauthority
zfu_as_calculateauthority
zfu_as_searchprincipallist
xcsFFST


Labels:

Comments

Post a Comment

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 ...
139 comments
Read more

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...
2 comments
Read more

Installing IBM Integration Bus on Linux - Middleware News

Before you begin Check the readme.html file for any updates to these installation instructions; see the product readmes web page. Check that you have enough memory and disk space; see IBM Integration Bus system requirements. Check that you have completed any prerequisite steps; see Preparing the system. If you are using Red Hat Linux 6.5 with WebKitGTK version webkitgtk.x86_64 1.2.6-5.el6, complete the steps in the following topic to work around problems with the Eclipse SWT browser: IBM Integration Toolkit on RedHat 6.5 crashes with "JVM terminated. Exit code=160" error. If you are using Red Hat Linux 6.x or 7.x, you might need the GTK2 32-bit drivers installed on Linux; for more information, see IBM Integration Toolkit on Linux becomes unresponsive after opening a DFDL or XSD file. If you are using Red Hat Linux 7.1, complete the steps in the following topic to work around problems with the Eclipse SWT browser: Internal web browser in IBM Integration Toolkit ...
19 comments
Read more