Fixes are available
APAR status
Closed as program error.
Error description
To help debug a connection problem with a remote integration node, you may want to enable CMP API and MQ Java Client tracing under Window -> Preferences -> Integration Development -> Unit Test Settings in the toolkit. Enabling the MQ Java Client trace and providing a trace file does not work. The trace file is not be created, and the following error appears in the CMP API trace if enabled: com.ibm.broker.config.proxy.MQBrokerConnectionParameters.enableM QJavaClientTracing() threw an exception: (No such file or directory). Stack trace follows. java.io.FileNotFoundException: (No such file or directory)
Local fix
Manual enable MQ Java Client tracing in the toolkit: 1. Create a com.ibm.mq.commonservices properties file by: a) Creating a new text file. b) Adding the following content to the text file replacing <FOLDER> with the name of a folder on your local file system: Diagnostics.MQ=enabled Diagnostics.Java=wmqjavaclasses Diagnostics.Java.Trace.Detail=high Diagnostics.Java.Trace.Destination.File=enabled Diagnostics.Java.Trace.Destination.Console=enabled Diagnostics.Java.Trace.Destination.Pathname=<FOLDER> Diagnostics.Java.FFDC.Destination.Pathname=<FOLDER> Diagnostics.Java.Errors.Destination.Filename=<FOLDER>/AMQJAVA.LO G 2. Shut down the toolkit. 3. Back up the <TOOLKIT_INSTALL_DIR>\eclipse.ini file. 4. Add the following line to the end of the <TOOLKIT_INSTALL_DIR>\eclipse.ini file replacing <FULLY_QUALIFIED_LOCATION_OF_PROPERTIES_FILE_FROM_ABOVE>: -Dcom.ibm.mq.commonservices=<FULLY_QUALIFIED_LOCATION_OF_PROPERT IES_FILE_FROM_ABOVE> 5. Restart the toolkit. MQ Java Client tracing is now enabled. To manually disable MQ Java Client tracing: i. Shut down the toolkit. ii. Remove the line added to the eclipse.ini file in step 4 above. iii. Restart the toolkit.
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Toolkit V9.0 who enable MQ Java Client trace. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The MQ trace file was not handled correctly, and the MQ trace API used no longer supported a file being passed in.
Problem conclusion
The MQ Java Client trace now uses a folder instead of a file, and the trace now works. Note that a restart of the toolkit is needed for changes to the MQ Java Client tracing preferences to be picked up by the toolkit. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.0 9.0.0.3 Interim Fix 001 The latest available maintenance can be obtained from: 'Recommended fixes for WebSphere Message Broker Toolkit' http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27009742 If the maintenance level is not yet available, information on its planned availability can be found in 'WebSphere Message Broker Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT07995
Reported component name
IB TOOLKIT
Reported component ID
5724J0531
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-04-01
Closed date
2016-06-06
Last modified date
2016-06-06
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
IB TOOLKIT
Fixed component ID
5724J0531
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020