Skip to main content

MQJE001: Completion Code '2', Reason '2495' when using WebSphere Application Server 7.0.0.5 with WebSphere MQ - Middleware News

MQJE001: Completion Code '2', Reason '2495' when using WebSphere Application Server 7.0.0.5 with WebSphere MQ - Middleware News


Problem

You are using WebSphere Application Server 7.0.0.5 and you see the following errors in the SystemErr.log file:

... SystemErr R com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2495'.
... SystemErr R MQJE001: Completion Code '2', Reason '2495'.

The MQ return code 2495 has the following short name:

$ mqrc 2495
2495 0x000009bf MQRC_MODULE_NOT_FOUND

You also see the following in the SystemOut.log file:

... FfdcProvider I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/ffdc/server1_6880688_09.10.19_04.52.57.1421628786892879991737.txt com.ibm.ejs.jms.JMSRegistration.installBundle 571
[10/19/09 4:52:57:283 EDT] 00000000 JMSRegistrati E WMSG1603E: An internal error occurred. It was not possible to register the WebSphere MQ JMS client with the application server due to exception org.osgi.framework.BundleException: An error occurred trying to read the bundle
at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:94)
at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:823)

You look at the FFDC file and this is the main information:

... FFDC Exception:org.osgi.framework.BundleException SourceId:com.ibm.ejs.jms.JMSRegistration.installBundle ProbeId:571 Reporter:com.ibm.ejs.jms.JMSRegistrationHelper@2e822e82
org.osgi.framework.BundleException: An error occurred trying to read the bundle
at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:94)
...
Caused by: java.io.IOException: The directory "/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/configuration/org.eclipse.osgi/bundles/131/1" could not be created
at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:68)
... 41 more

Cause

The issue happened after applying the latest fix pack for WebSphere Application Server.
The following script was executed as a last step for adjusting the WebSphere MQ resource adapter
configuration when migrating profiles between maintenance level 7.0.0.0 and later levels:
/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/osgiCfgInit.sh

For more information see:


WebSphere Application Server Version 7.0
Adjusting the WebSphere MQ resource adapter configuration when migrating profiles between maintenance level 7.0.0.0 and later levels

This script initialized the configuration and changed the owner/group of the subdirectory org.eclipse.osgi in the following directory to the user who runs the script, say "root":
/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/configuration

$ ls -l
drwxr-xr-x 3 mqm mqm 4096 Oct 20 00:18 org.eclipse.core.runtime
drwxr-xr-x 3 root system 256 Oct 20 00:18 org.eclipse.osgi
drwxr-xr-x 3 mqm mqm 256 Oct 20 00:18 org.eclipse.update


Miscellaneous:

In this scenario, the user "mqm" was used to perform the first system tasks that resulted in the ownership of the above files by "mqm:mqm". Then the script was run from the user "root" and the updated file had a file ownership changed to "root:system". Then when the application server was started under the user "mqm", the mixture of file ownership for these files caused the problem.

If all the system administration tasks and the starting of the application servers were done under the user "root" then there will not be a conflict with the ownership of the files.
Resolving the problem
Change the owner/group for the files to the user that is mentioned in the Process
execution properties of the WebSphere Application Server environment, for the subdirectory org.eclipse.osgi in the directory:

/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/configuration

In this example the owner/group should be "mqm":

$ ls -l
drwxr-xr-x 3 mqm mqm 4096 Oct 20 00:18 org.eclipse.core.runtime
drwxr-xr-x 3 mqm mqm 256 Oct 20 00:18 org.eclipse.osgi
drwxr-xr-x 3 mqm mqm 256 Oct 20 00:18 org.eclipse.update
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