PQ99888: DEFAULT VALUE FOR WEBSPHERE MQ TOPIC CONNECTION FACTORY "BROKER VERSION" IN THE WEBSPHERE ADMINISTRATIVE CONSOLE IS INCORRECT. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When using the WebSphere Administrative Console to create a WebSphere MQ JMS Topic Connection Factory, the default value for the Broker Version property is set to "Advanced". However, if customers don't change the value for this property, the application server will in fact use a Broker Version of "Basic".Local fix Problem summary **************************************************************** * USERS AFFECTED: This problem affects customers who use the * * Java Message Service (JMS) functionality * * provided with WebSphere Application Server * * Version 5.1.x. * **************************************************************** * PROBLEM DESCRIPTION: When defining a WebSphere MQ (WMQ) * * Topic Connection Factory (TCF) using * * the WebSphere Administrative Console, * * one of the properties that you can set * * is Broker Version. This property should * * be set to "Basic" if the TCF will be * * used to connect to the WMQ Broker * * (sometimes known as the MA0C Broker), * * or "Advanced" if you are using * * WebSphere MQ Integrator (WMQI) or * * WebSphere MQ Event Broker (WMQEB). * * * * The default value for this property * * (as shown in the Administrative * * Console) is "Advanced". If you do not * * change this property, and subsequently * * try to use this TCF to connect to * * either WMQI or WMQEB, errors * * occur indicating that the Broker * * Version for this TCF is incompatiable * * with the actual broker being used. * **************************************************************** * RECOMMENDATION: * **************************************************************** In certain situations, the JMS Resource Binders (used to create JNDI objects in the application server's JNDI namespace) would not get the value of the Broker Version property from the application server's configuration. Instead, it would just use a default value. However, the default value used by the Binders was different than the value shown in the application server Administrative Console.Problem conclusion The JMS Resource Binders have been changed to always obtain the value of the Broker Version property from the application server's configuration, rather than assuming a default. The fix for this APAR is currently targeted for inclusion in Cumulative Fix 4 for WebSphere Application Server Version 5.1.1. Please refer to the Recommended Updates page for delivery dates: http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP &uid=swg27004980Temporary fix Comments
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: 10W
Software edition:
Reference #: PQ99888
IBM Group: Software Group
Modified date: Mar 9, 2005
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.