Fixes are available
APAR status
Closed as program error.
Error description
When using WebSphere MQ classes for JMS to create a real-time connection to a broker of WebSphere Event Broker or WebSphere Message Broker, with connection details specified within a connection name list, a NumberFormatException is thrown with a stack similar to: java.lang.Integer.parseInt(Integer.java:427) at java.lang.Integer.valueOf(Integer.java:565) at JmsReadablePropertyContextImpl.parseInt at JmsReadablePropertyContextImpl.getIntProperty at WMQConnectionFactory.createDirectConnection at WMQConnectionFactory.createProviderConnection at JmsConnectionFactoryImpl.createConnection This exception is also seen in a stack of the following form: 'java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:428) at java.lang.Integer.valueOf(Integer.java:565) at com.ibm.msg.client.jms.internal.JmsReadablePropertyContextImpl .parseInt(JmsReadablePropertyContextImpl.java:649) at com.ibm.msg.client.jms.internal.JmsReadablePropertyContextImpl .getIntProperty(JmsReadablePropertyContextImpl.java:267) at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createDi rectConnection(WMQConnectionFactory.java:7428) at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createPr oviderConnection(WMQConnectionFactory.java:6567) at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createCo nnection(JmsConnectionFactoryImpl.java:295) at com.ibm.mq.jms.MQConnectionFactory.createCommonConnection(MQCo nnectionFactory.java:6232) at com.ibm.mq.jms.MQTopicConnectionFactory.createTopicConnection( MQTopicConnectionFactory.java:114) at com.ibm.broker.jmsconnmgr.JMSConnectionManager.createConnectio n(JMSConnectionManager.java:1468) at com.ibm.broker.jmsconnmgr.JMSConnectionManager.accessConnectio nMap(JMSConnectionManager.java:912) at com.ibm.broker.jmsconnmgr.JMSConnectionManager.getConnection(J MSConnectionManager.java:408) at com.ibm.broker.jmsclientnodes.JMSClientInputNode.jmsConnection (JMSClientInputNode.java:1487) at com.ibm.broker.jmsclientnodes.JMSClientInputNode.run(JMSClient InputNode.java:567) Note: This problem is corrected in WebSphere MQ fixpack v7.0.1.7.
Local fix
LOCAL FIX: Upgrade to WebSphere MQ v7.0.1.7 or higher.
Problem summary
**************************************************************** USERS AFFECTED: This issue affects all users of WebSphere MQ V7.0 classes for JMS making a real-time connection to a broker of WebSphere Event Broker or WebSphere Message Broker with connection details specified in a connection name list. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java **************************************************************** PROBLEM SUMMARY: This issue was caused by the hostname and port properties from the connection name list not being correctly processed when creating a real-time connection from a WebSphere MQ classes for JMS application to a broker.
Problem conclusion
The hostname and port properties from the connection name list are now correctly handled and a real-time connection from the WebSphere MQ classes for JMS application to a broker can be successfully created. The code fix for this problem is included in the WebSphere MQ classes for JMS fix pack 7.0.1.7. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.9 -------- -------------------- Windows U200337 AIX U849391 HP-UX (PA-RISC) U849723 HP-UX (Itanium) U849728 Solaris (SPARC) U849724 Solaris (x86-64) U849730 iSeries 7.0.1.9 Linux (x86) U849725 Linux (x86-64) U849729 Linux (zSeries) U849726 Linux (Power) U849727 v7.1 Platform Fix Pack 7.1.0.2 -------- -------------------- Windows 7.1.0.2 AIX 7.1.0.2 HP-UX (Itanium) 7.1.0.2 Solaris (SPARC) 7.1.0.2 Solaris (x86-64) 7.1.0.2 iSeries 7.1.0.2 Linux (x86) 7.1.0.2 Linux (x86-64) 7.1.0.2 Linux (zSeries) 7.1.0.2 Linux (Power) 7.1.0.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
IV12486
Reported component name
WMQ AIX V7
Reported component ID
5724H7221
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-22
Closed date
2012-02-28
Last modified date
2012-04-25
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 AIX V7
Fixed component ID
5724H7221
Applicable component levels
R701 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023