| Version | CR Number | Problem | Fix Description |
|---|---|---|---|
| 2.2.1 | CR 58458 |
During request processing, when an error occurred, the eMatrix adapter did not set a flag informing the adapter framework of the status of a request. When a request failed the collaboration or message flow was not notified of the failure.
Note: this error will only occur when the adapter is used with certain versions of adapter framework. The error was noticed with adapter framework version 4.2.1.15 |
The eMatrix adapter has been updated to set the return code whenever an exception is thrown during request processing. |
| 2.2.1 | CR 35736 |
If a MatrixException is thrown by a method in the eMatrix ADK
any transaction that encloses the java statement which caused
the exception will be cancelled without notifying the ADK user.
The tranaction will appear to commit successfully, however it
will have no effect on the state of the eMatrix application. Our adapter wraps all request processing logic in an eMatrix transaction. Therefore, customers who develop JPOs which capture and recover from MatrixException exceptions and attempt to execute these JPOs using our WBI command business objects will not effect the state of the eMatrix application nor will they be notified of any failure. The problem was originally described in MatrixOne incident 248120. More information regarding the problem is captured in MatrixOne incident 287785. MatrixOne has no plans to fix this behavior. Therefore, we have patched our adapter to allow customers to workaround it. |
Version 2.2.1 of the adapter fixes this problem by allowing
users to disable the transaction used when the adapter processes
WBI command objects during requests. In order to shut of transactions the user must add the name/value pair "disable_transactions=true" to the business object level application specific information of the top level command object sent to a request. Note: disabling transactions is only necessary when the user attempts to execute a JPO that may throw a MatrixException exception. There is no other known scenario where disabling transactions positively impacts the execution of an MQL command. |
Perform the steps described in the table below.
| Version | Platform | Add/Remove/Replace | File (path relative to $CROSSWORLDS directory) |
|---|---|---|---|
| 2.2.1 | All | Replace | connectors\eMatrix\CWeMatrix.jar |
| 2.2.1 | All | Replace | connectors\messages\eMatrixConnector.txt |
15 July 2004
Copyright 2004 IBM Corporation. Proprietary and Confidential. All Rights Reserved.