| This table lists the enhancements and fixes in fix pack version 7.0.0.5. |
| Enhancements |
| There are no enhancements in this interim fix. |
| Fixes |
| 1 | 6821(AFC) | | Create EventStore to ActivationSpec mapping for ConnectionLeak
issue in recovery. |
| Symptom:Connection Leak during XARecovery. |
| Resolution: AFC recovery implementation modified to handle the connection
leak issue. |
|
| 2 | 6818(AFC) | | EventStoreBackedXAResource throws unhandled NullPointerException in
Commit and Rollback calls for when event is null |
| Symptom: NullPointerExceptions seen in the logs during Inbound processing
of events |
| Resolution: With the fix when an event for a requested Xid is not found in
the EventStore, an XA exception will be thrown, which will be sent to the
container. Depending on the error code set on the XAException based on one
phase or two phase commit, the container will send an appropriate call.
Example in case of two phase commit the container will reissue a commit
call.
|
|
| 3 | 6816(AFC) | | Error while formatting the Xid |
| Symptom: Format check for pending xids from adapter was failing, because of
which recovery of pending transactions not taking place |
| Resolution: Xid format check in XidImpl fixed to verify the correctness of
the xid format.
|
|
| 4 | 6815(AFC) | | Forget and Rollback calls are not setting xid to null, post
recovery |
| Symptom: Events that have been rolled back during recovery are not picked
up for future processing |
| Resolution: Events that have been rolled back during recovery needs to be
made eligible for future poll cycles to fetch them, this is done by
updating these events in the event store such that they qualify as new
events, that can be fetched by future poll cycles
|
|
| 5 | 6744(AFC) | | CheckIllegalXMLCharacter is using String instead of StringBuffer
which will eventually lead to a high heap usage |
| Symptom: Use of String in CheckIllegalXMLCharacter leads to creation of
large number of String objects as String is immutable, heap profiling
showed increasing number of String objects that are not getting cleaned up,
this has a potential to cause a problem when the input size is large. |
| Resolution: Changed the implementation to use StringBuffer instead of
String..
|
|
| 6 | 6322(AFC) | | JCA
timer was not getting cancelled |
| Symptom: If an exception occurs while trying to shutdown the EventManager,
EventManager is tried to be shutdown infinitely. This is because the JCA
timer was not getting cancelled |
| Resolution: Even if an exception occurs while EventManager is being tried
to shutdown, the JCA timer is cancelled so as to make sure their life
cycles are in sync
|
|
| 7 | 6928(AFC) | JR42026 | WorkRejectedException in logs, followed by adapter stopping to
poll |
| Symptom: WorkRejectedException in logs, followed by adapter stopping to
poll |
| Resolution: Work that was rejected was not getting removed from the
workInPorgress list which was resulting in no new work to be added for
submission, as a result of which adapter could not poll once a poll work
was rejected.
|
|
| 8 | 103778 | JR40681 | The messageendpoint.release() method in CallbackEventSender for non-transacted delivery is not called. |
| Symptom: When the
messageendpoint.release() method is not called for non-transacted
delivery, the messageendpoint object won't be released back to the pool
and the runtime easily run of memory over the a period of time. |
| Resolution: Call the messageendpoint.release method for non-transacted delivery. |
|
| 9 | 103806 | | Connection retry limit is not working as expected |
| Symptom: During adapter polling cycle,
if the adapter is not able to establish the connection to the EIS, it
does not retry specified times |
| Resolution: Catch and log the CommException in the run method of PollEventManagerWorker
|
|
| 10 | RTC 6218 | | Failed event retry is not working as expected |
| Symptom: During adapter polling cycle,
if the adapter is not able to deliver the event sucessfully to the
endpoint, it retries for more than the specified times |
| Resolution: Cancel the JCA timer task in the PollEventManagerWorker, when the event manager is shutdown.
|
|
|
11
|
103618
|
|
Message flow hangs when the message flow is stopped during polling
|
|
Symptom: During Inbound
polling on WebSphere Message Broker, there is a thread deadlock
situation encountered if the message flow is stopped during the
processing of an event.
|
|
Resolution: The timer
mechanism used to schedule the polling thread leads to deadlock
situation. The polling mechanism on WMB is now handled by using the work
manager to manage and execute the polling thread.
|
|
|
12
|
103619
|
|
Detect Illegal XML character property
should not be visible during discovery in WebSphere Message Broker
toolkit and Rational Application Developer
|
|
Symptom: Detect Illegal
XML character feature does not applie to WebSphere Message Broker and
WebSphere Application server runtimes. This property should not be
visible in the external service wizard during Inbound and Outbound on
WMB and RAD.
|
|
Resolution: The property
is removed from the external service wizard when the tooling is Message
Broker toolkit or Rational Application Developer.
|
|
|
13
|
101812
|
|
Detecting illegal XML characters in SDO DESPI of Adapters
|
|
Symptom: We are facing an
issue in which a runtime exception is being thrown when the BO generated
by the Adapter is being serialized down the line to be transferred over
the wire during the BOXML serialization because of invalid xml
characters in the BO.
|
|
Resolution: Provide
options to let the user to make choices and add validation in SDO DESPI
of Adapters. Currently we have 4 choices: (a) Do not validate BO content
for illegal XML characters (default); (b) Throw exceptions if BO
content contains illegal XML charaters;(c) Discard illegal XML
characters in BO content and log; (d) Escape sequence illegal XML
characters and log.
|
|