PQ72263: CUSTOM PROPERTIES OF THE GENERIC JMS PROVIDER ARE IGNORED | |||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When configuring a new JMS provider through the "Generic JMS Providers" section of the admin console, some JMS providers -such as WebMethods Enterpise -require either Java properties to be passed to the InitialContext or set in the system properties.Local fix The admin onsole does not provide a method to set such properties for a JMS provider. The "Custom Properties" appear to use reflection rather than setting Java properties. This Fix is so that the Custom Properties on the Generic JMS Provider are not ignored, but are stored in the connection factory reference and any java.naming.* properties will be passed through on the Hashtable to the JNDI context factory. LOCAL FIX:ン If two apps in the same server need to access different JMS providers -each requiring additional properties, the jndi.properties approach is workable. Each app can pick up a different jndi.properties file. If 2 JMS Providers are accessed from a single app and these providers need the additional properties, then this fix is required.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users of the * * Generic JMS provider with an external * * provider JNDI namespace context that * * requires configurable JNDI java.naming * * and javax.naming properties set on its * * InitialContext constructor. * **************************************************************** * PROBLEM DESCRIPTION: The current Generic JMS Provider * * definition ignores java.naming and * * javax.naming custom properties and * * does not pass them through to the * * Initial Context. * **************************************************************** * RECOMMENDATION: * **************************************************************** Generic JMS Provider JNDI Custom Properties ignored.Problem conclusion The Generic JMS Provider Custom Properties field can now specify java.naming and javax.naming properties which will now be passed through in the Hashtable parameter for the external JNDI InitialContext constructor.Temporary fix ZE FIX ERROR PQ75057 03/06/26Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PQ72263
IBM Group: Software Group
Modified date: Jun 26, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.