Troubleshooting
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 Network Deployment > WebSphere Application Server Network Deployment 7.0.0.x > Feature Pack for SCA, Version 1.0.1 (All operating systems) > Migrating, coexisting, and interoperating > Messaging resources >
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
++ Related material
AMQ8568 RC=2495 mqjbnd was not found, or AMQ8351 Java environment has not been configured correctly
UnsatisfiedLinkError: mqjbnd (Not found in java.library.path), CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd' was not found. [3=mqjbnd]
IZ84448: WEBSPHERE MQ V7 JAVA/JMS CLIENT FAILS TO LOAD MQJBND LIBRARY WHEN USING A JNI BINDINGS CONNECTION
Product Synonym
WMQ MQ WAS
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21410038