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

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...
Post a Comment
Read more

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...
Post a Comment
Read more

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