Fixes are available
APAR status
Closed as program error.
Error description
WebSphere MQ FTE agent at 7.0.4.1 running on Linux RedHat, 64 bit, using WebSphere MQ 7.1 as the agent's queue manager fails to start when using -trace option although the javalibrarypath property is correctly set to use the 32 bit WebSphere MQ java libraries in the agent.properties file. The exception is this: [23/05/2012 17:33:55:066 CEST] 00000001 RASImpl I BFGUT0001I: The trace specification has changed to "=all". [23/05/2012 17:33:55:632 CEST] 0000000b AgentRecovery E BFGAG0068E: The agent cannot establish a bindings mode connection to queue manager 'XXXX' and will now end. The agent cannot find a bindings library: CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd' was not found. [3=mqjbnd] [23/05/2012 17:33:55:633 CEST] 00000001 AgentRuntime E BFGAG0061E: The agent ended abnormally. If the trace option is not used, the agent starts ok.
Local fix
Do not start or run trace.
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere MQ File Transfer Edition Version using a BINDINGS mode connection to a WebSphere MQ queue manager in a non-default install location. Platforms affected: MultiPlatform **************************************************************** PROBLEM SUMMARY: If the agent queue manager has been installed to a non-default location, the agent would fail to start with trace enabled with MQRC_MODULE_NOT_FOUND (MQRC 2495). This occurred because with trace enabled the native library information would be configured before the agent property files had successfully been loaded into the system. Because of this the code would wrongly believe the native library location had not been specified, and would default to the system default installation location.
Problem conclusion
The code has been altered to ensure that the native library path information is not set until the agent property files have been loaded into the system. This allows the correct native library path information to be set, and the agent will start as normal. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Platform v7.5 -------- -------------------- Multiplatforms 7.5.0.1 Platform v7.0 -------- -------------------- Multiplatforms 7.0.4.2 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
Temporary fix
Comments
APAR Information
APAR number
IC83936
Reported component name
WMQ FILE TRANSF
Reported component ID
5724R1000
Reported release
704
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-06-07
Closed date
2012-06-29
Last modified date
2012-06-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ FILE TRANSF
Fixed component ID
5724R1000
Applicable component levels
R704 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 June 2012