APAR status
Closed as program error.
Error description
JMSOutput node fails to get the username and password from its defined JMS node account name. This causes the JMSOutput node to attempt JNDI lookup and JMS Connection creation without providing any username and password which results in a message flow failure with javax.naming.AuthenticationException error. The generated BIP4640E error will have exception text as: ' Not permitted: invalid name or password, Failure to obtain JNDI administered objects'. The node cannot obtain a JNDI Administered Object, because some of the values specified are incorrect. Check the JNDI Administered configuration for the JMS provider used by the node. Either: Modify the JNDI Administered objects and rebuild the bindings or Change the Configurable Service attributes associated with this JMS Provider and restart the integration server or Change the node attributes and redeploy the message flow. : Failure to obtain JNDI administered objects' Similarly JMS Connection failures can also occur if the security is enabled at the JMS server end.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus version 9.0 and version 10.0 using the JMSOutput node with security credentials. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: JMSOutput node fails to get the username and password from its defined JMS node account name. This causes the JMSOutput node to attempt JNDI lookup and JMS Connection creation without providing any username and password which results in a message flow failure with javax.naming.AuthenticationException The generated BIP4640E error will have exception text as: ' Not permitted: invalid name or password, Failure to obtain JNDI administered objects'. The node cannot obtain a JNDI Administered Object, because some of the values specified are incorrect. Check the JNDI Administered configuration for the JMS provider used by the node. Either: Modify the JNDI Administered objects and rebuild the bindings or Change the Configurable Service attributes associated with this JMS Provider and restart the integration server or Change the node attributes and redeploy the message flow. : Failure to obtain JNDI administered objects' Similarly JMS Connection failures can also occur if the security is enabled at the JMS server end.
Problem conclusion
The product now correctly authenticates to jms/jndi service providers. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.13 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT22568
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-09-28
Closed date
2018-06-12
Last modified date
2018-06-12
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
INTEGRATION BUS
Fixed component ID
5724J0540
Applicable component levels
[{"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":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
12 June 2018