| This table lists the enhancements and fixes in interim fix version 7.0.0.1_IF03. |
| Enhancements |
| 1 | 093352 | | Support the broker WMB. |
| Symptom:
To support outbound and inbound interaction on broker WMB.
|
| Resolution:
Support the broker WMB by masking some EMD properties not applicable for WMB.
|
|
| Fixes |
| 1 | 102125 | | "Folder of failed events" will lead some security risk, and mistake. |
| Symptom:
"Folder of failed events",the whole BO schema and data will be put into the folder. This assumes application having privilege to read and write local file of the broker. This has security risks.
|
| Resolution:
Remove the "Folder of failed events", and save the event data to the Event Data column of the persistent event store.
|
|
| 2 | 102075 | | Hide or remove the Timeout and MaxRecord properties when no XML List BO is selected. |
| Symptom:
Timeout and MaxRecord are interaction specification properties only valid for XML List RetrieveAll operations. However they are shown when no XML List BO is selected.
|
| Resolution:
Hide or remove the Timeout and MaxRecord properties when no XML List BO is selected.
|
|
| This table lists the enhancements and fixes in fix pack version 7.0.0.1. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 100356 | | When adapter creates 2 or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. |
| Symptom:
When adapter creates 2 or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException.
|
| Resolution:
Redefined the methods of "hashCode()" and "equals()" in the SDOV1Type class. Then individual adapter can distinguish those BO correctly by "namespace + name" if those BOs name are equal.
|
|
| 2 | 100406 | | For Adapter inbound and outbound operation(standalone deployment), after the application is restarted, the NullPointerException will appear when the adapter tries to query the ASI Infor from cache. |
| Symptom:
For Adapter inbound and outbound operation(standalone deployment), after the application is restarted, the NullPointerException will appear when the adapter tries to query the ASI Infor from cache.
|
| Resolution:
The BO's namespace and name has been preserved as BO instance's fields. After the application is restarted, adapter can still get them from those instance's field rather than the stale data cache.
|
|
| 3 | 100430 | | When adapter caches some BeanTypes that have a great deal of properties, java OutOfMemmory Exception be thrown during performing inbound and outbound operation with some events (persisting 20-50 times in WAS broker). |
| Symptom:
When adapter caches some BeanTypes that have a great deal of properties, java OutOfMemmory Exception be thrown during performing inbound and outbound operation with some events (persisting 20-50 times in WAS broker).
|
| Resolution:
The BeanType's class names are preserved as key of cache, rather than BeanType's instance. When broker is WAS, adapter can get BeanType structure referred to its class name.
|
|
| 4 | 99888 | | When adapter gets ARM transaction factory name to process ARM transaction, a WAS internal private API is used for it, which need to be replaced with public interfaces. |
| Symptom:
When adapter gets ARM transaction factory name to process ARM transaction, a WAS internal private API is used for it, which need to be replaced with public interfaces.
|
| Resolution:
Switched to Invoke PmiRmJmxService MBean, a set of public interfaces exposed by WAS to get ARM transaction fatory name.
|
|
| 5 | 100262 | | Ambiguous semantics of the max connection number in the event delivery config |
| Symptom: Adapter will not use connection pool for event delivery if max connection number is 1 and delivery mode is "UNORDERED". In this situation, multiple thread will share one connection without thread safe mechanism, which will cause exception.
|
| Resolution: The fix makes connection pool be used when max connection number is 1, connection pool keep thread safe and thus is recommended to use under "UNORDERED" and "ORDERED BY KEY" delivery mode; If user preferred not to use connection pool, he/she could set max connection number to 0, while thread safe will not be guaranteed.
|
|
| 6 | 77930 | | Printing out the AdapterFoundationClasses version in the Logs/traces. |
| Symptom: Currently with all the adapters , The AFC version is not printed out in the logs/traces. It would be really helpful to have this information printed out to the logs/traces especially in debugging issues due to conflicting AFC being loaded at runtime.
|
| Resolution: print AFC version in the trace |
|