APAR status
Closed as program error.
Error description
The MDB Listener JMS Wrappers use a different transactional
behaviour for MQSeries JMS as to other "Generic" JMS providers.
AMBI is a wrappering of MQSeries JMS, and thus their
transactionalbehaviour should the same as MQ. However, because
the JMS wrappers do not recognise the AMBI JMS classes as MQ
the wrong transaction behaviour is used and thus results in
OUT_OF_SYNCPOINT (rc=2035)errors.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: This proble affects all users of the *
* Access Manager for Business Integration *
* product. *
****************************************************************
* PROBLEM DESCRIPTION: The MDB Listener JMS Wrappers use a *
* different transactional behaviour for *
* MQSeries JMS as to other "Generic" JMS *
* providers. AMBI is a wrappering of *
* MQSeries JMS, and thus their *
* transactional behaviour should the *
* same as MQ. However, because the JMS *
* wrappers do not recognise the AMBI JMS *
* classes as MQ the wrong transaction *
* behaviour is used and thus results in *
* OUT_OF_SYNCPOINT (rc=2035) errors. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This is essentialy a piece of new function. Access Manager for
Business Intergration (AMBI) is a new product being developed
in Austin that provides a wrapper for the WebSphere MQ JMS
classes. If a customer wishes to use AMBI as their JMS provider
when using WebSphere Application Server Verson 5.0.x, they must
define AMBI as a "Generic JMS Provider".
The WebSphere Application Server Messaging component also
provides a wrapper for the WMQ JMS classes. When a customer
uses WMQ as it's JMS provider, the wrapper classes force a
particular transactional behaviour. However, when the customer
uses AMBI (which is a "Generic JMS Provider"), a different
transactional behaviour is used.
The WebSphere Messaging component needs to be modified
to check for the existance of the AMBI classes. If these classes
are found, JMS Sessions should be created that have the same
transactional behaviour as those sessions uses to talk to WMQ.
Problem conclusion
The Messaging component has been updated to include the
required checks for Access Manager for Business Integration.
Temporary fix Comments
APAR information |
APAR number |
PQ80078 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-10-27 |
Closed date |
2003-11-11 |
Last modified date |
2003-11-11 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSN |
UP |
R00A PSY |
UP |
R00H PSN |
UP |
R00I PSN |
UP |
R00P PSN |
UP |
R00S PSN |
UP |
R00W PSN |
UP |
|