Fixes are available
APAR status
Closed as program error.
Error description
When using the WebSphere MQ Resource Adapter, defining a property called "clientID" on an activation specification for a message-driven bean (MDB) results in the following failure when the MDB is deployed on JBOSS: WARN ?org.jboss.system.ServiceController? Problem starting service jboss.j2ee:service=EJB,plugin=invoker, binding=message-inflow-driven-bean, jndiName=local/apupdatesmdb@23716998 org.jboss.deployment.DeploymentException: Error for ActivationSpec class com.ibm.mq.connector.inbound.ActivationSpecImpl as JavaBean - nested throwable: (java.beans.IntrospectionException: No property found for: clientID on JavaBean An example of an activation specification that sets this property is shown below: <activation-config-property> <activation-config-property-name>clientID </activation-config-property-name> <activation-config-property-value>MDB1 </activation-config-property-value> </activation-config-property>
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Any applications/MDB being deployed in a JBOSS server environment and defining a clientID attribute on an activation spec. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java **************************************************************** PROBLEM SUMMARY: To set the Client ID value for the MDB, there are two options "clientId" and "clientID" (note the change in case). When clientID value is used, there is no property descriptor to store and handle the clientID value. Currently, only clientId value is considered to be a valid way to set the clientid information. Hence when customer uses the clientID property the RA code throws an exception stating it is an invalid property.
Problem conclusion
Code is modified to support clientID value as a valid property. Both clientID and clientId property compliment's each other. get/set clientID internally will call get/set clientId so that the functionality is not changed. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v6.0 Platform Fix Pack 6.0.2.8 -------- -------------------- Windows U200309 AIX U825517 HP-UX (PA-RISC) U824678 HP-UX (Itanium) U825875 Solaris (SPARC) U825511 Solaris (x86-64) U825872 iSeries tbc_p600_0_2_8 Linux (x86) U825181 Linux (x86-64) U825874 Linux (zSeries) U825516 Linux (Power) U825182 Linux (s390x) U825873 v7.0 Platform Fix Pack 7.0.1.0 -------- -------------------- Windows U200306 AIX U823774 HP-UX (PA-RISC) U823665 HP-UX (Itanium) U823667 Solaris (SPARC) U823772 Solaris (x86-64) U824344 iSeries tbc_p700_0_1_0 Linux (x86) U823664 Linux (x86-64) U823773 Linux (zSeries) U823668 Linux (Power) U823666 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
IZ52710
Reported component name
WMQ LIN X86 V6
Reported component ID
5724H7204
Reported release
602
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-05
Closed date
2009-06-30
Last modified date
2009-06-30
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 LIN X86 V6
Fixed component ID
5724H7204
Applicable component levels
R602 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023