Table of Contents
Advertisement
6. Click on the extended tab and set the maximum message length attribute to a
MQJMS2013 error
About this task
During WebSphere Partner Gateway communication with WebSphere MQ, you can
receive the following error:
MQJMS2013 invalid security authentication
To resolve the error, perform the following steps:
1. Check which user ID the application is being run under.
2. Check to verify that user ID being used is in the mqm group (or some other
3. If the user ID is not in the mqm group, then add it to the mqm group and issue
java.security.InvalidKeyException: Illegal key size or default parameter
If you try to upload the PKCS#12 file with a stronger cryptography than the one
supported by default, or if you use a key with an illegal key size that is not
supported by default, this exception is thrown. To resolve this error, you must
obtain the unrestricted strength cryptography policy files and install them, if it is
legal to do so. See the section on changing the cryptographic strength in WebSphere
Partner Gateway Hub Configuration Guide.
The MDN status of 'unknown' for AS transactions
Upon completion of an upgrade to WebSphere Partner Gateway v6.2, the AS
Viewer in the Community Console will show an unknown state for the MDN
Status on AS transactions that occurred prior to the upgrade. This is a limitation of
the migration procedures and utilities.
Servers fail to start after applying fixes
The servers (Dmgr, NodeAgent, and AppServers) might fail to start if you have
recently applied a fix or fix pack with the Update Installer. The SystemOut.log will
not contain any information about the failure. However, the startServer.log
shows:
ADMU3011E: Server launched but failed initialization. startServer.log,
SystemOut.log(or job log in zOS) and other log files under
/home/dwhare/WebSphere61/profiles/Dmgr01/logs/dmgr should contain
failure information.
The problem is caused by applying a fix or fix pack as root when the WebSphere
Application Server environment is set up to run as a non-root user.
Note: For existing installations, the root or non-root installer who owns the
currently installed files is the only user who can perform subsequent installation or
removal operations on that installation.
The reason the servers fail to start is that the OSGI cache was not updated after
applying the fix pack because of an issue with the permission. To verify this, check
the <WAS_PROFILE_HOME>/configuration/ directory for a log file with a string of
numbers as the file name. This file will contain an error like:
value greater than the size of the message.
group with sufficient authority).
the runmqsc REFRESH SECURITY(*) command.
Chapter 17. Troubleshooting
181
Advertisement
Table of Contents
