| This table lists the enhancements and fixes in fix pack version 7.5.0.2. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | RTC-6293 | | Minimum and maximum properties under "Number of connections for event deilivery" are not seen in EMD screen |
| Symptom: When UNORDERED delivery is selected, Minimum and maximum properties under "Number of connections for event deilivery" are not seen in EMD screen. |
| Resolution: Removed support for UNORDERED delivery. |
|
| 2 | RTC-6503 | | User name and password fields are empty in "deployment properties screen" for outbound scenario |
| Symptom: User name and password fields are empty in "deployment properties screen" for outbound scenario. The values entered in discovery properties screen are not carried to deployment properties screen. |
| Resolution: Fixed by AFC RTC-6694. See AFC Readme. |
|
| 3 | RTC-6774 | | JDE Adapter failing to validate the timeout property properly in deployment properties screen |
| Symptom: JDE Adapter failing to validate the timeout property properly in deployment properties screen. A positive long value higher than MAX_INT can get cast to a negative integer and result in execptions at runtime. |
| Resolution: Updated JDEOutboundConnectionConfiguration and JDEMetadataSelection classes to allow values in the range 0 to MAX_INT only in the timeout properties during EMD. |
|
| 4 | RTC-6860 | | JDE adapter is polling for all the events in JDE server irrespective of BO mapped during the EMD step |
| Symptom: When JDE adapter receives an event which is not configured through EMD, it throws a NullPointerException since the BO definition for that event could not be found. |
| Resolution: Updated the adapter to throw ResourceException when BO definition could not be found. |
|
| 5 | RTC-6881 | | NullPointerException seen in .log after Discovery |
| Symptom: NullPointerException seen in .log after Discovery |
| Resolution: Added null check and corrected the property name used to lookup XMLLists property element in JDEFilterPG. |
|
| 6 | RTC-7033 | | JDE adapter is not deleting the events which are 1 with XID entry which may lead to performance issue |
| Symptom: If the server is terminated while event processing is in progress, any entries with status 1 are left undeleted from the event table. When event processing resumes after server is restarted, the event entries remain in the event table. |
| Resolution: Updated JDEEventStoreWithXid to include events already existing in event table (but received from EIS once again as the events were not acknowledged when they were processed in the previous run) for deletion. |
|
| 7 | RTC-7038 | | JDE server connection leak in JDEInboundHandlerWithXid |
| Symptom: When an instance of JDEInboundHandlerWithXid is created, a failure to create a sync event session can result in connection to JDE server not logged off. The connection is logged off only when close() is called on the instance. But then an exception thrown by the constructor leaves no chance to call close() thus leading to connection leaks. |
| Resolution: Updated JDEInboundHandlerWithXid to logoff connection when SyncEventSession creation fails. |
|
| This table lists the enhancements and fixes in fix pack version 7.5.0.1. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 103499 | JR40937 | Password getting displayed for Connection_Id parameter in the trace logs |
| Symptom: Password getting displayed for Connection_Id parameter in the trace logs |
| Resolution: Removed password from the Connection_Id |
|
| 2 | 103593 | JR40938 | JDE Adapter inbound scenario failing with WMB |
| Symptom: JDE Adapter inbound scenario failing with WMB due to exceptions Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.sca.sdo.DataFactory. JDE code is checking whether it is SDOV1 or SDOV2 while creating the data object. |
| Resolution: Checking of SDO version is delegated to AFC code while creating the data object. |
|
| 3 | 103499 | JR40939 | For Wrong credentials "AUTHENTICATION" Failure is not getting captured in trace log |
| Symptom: When wrong credentials are provided AUTHENTICATION Failure is not getting captured in trace logs. Also, CONNECTION closed should not be reported as there is no connectoion is established. |
| Resolution: Changed JDEResourceAdapter.isAuthenticationFailure() to recognize com.jdedwards.system.connector.dynamic.InvalidLoginException as authentication failed exception. Changed the connection retry behaviour not to attempt retries in case of authentication failure. |
|
| 4 | 103593 | JR40940 | Not reporting any event status in trace logs for authentication failure,connection lost and connection failure for inbound scenario. |
| Symptom: Not reporting any event status in trace logs for authentication failure,connection lost and connection failure for inbound scenario. |
| Resolution: Changed JDEInboundHandlerWithXid.createSyncEventSession() to catch ApplicationExceptions and log authentication failures |
|
| 5 | 103593 | JR40943 | Message flow is getting deployed successfully in to the broker when provided wrong crendentials for inbound scenario |
| Symptom: Message flow deployment in to the broker is successful when we provided wrong crendentials for inbound scenario. |
| Resolution: In case of authentication failure in inbound scenario, wrapping of JDE ApplicationException in AuthenticationFailException results in deployment to succeed. Throwing the original exception as is after logging fails the deploymentm which is the expected behavior. |
|
| 6 | 103593 | JR40944 | Reporting wrong event status when provided wrong credentials for inbound scenario. |
| Symptom: Reporting wrong event status when provided wrong credentials for inbound scenario. It should report authentication failure and connection failure as event status not authentication failure and connection lost as event status. |
| Resolution: Throw the original JDE ApplicationException as is to prevent connection lost getting logged incorrectly. |
|
| 7 | 103593 | JR40945 | Not Reporting any connection related event status for "connection failure" and "connection Lost" in inbound scenario |
| Symptom: Not Reporting any connection related event status for connection failure and connection Lost in inbound scenario. |
| Resolution: Updated JDEInboundHandlerWithXid and JDEEventStoreWithXid to emit a connection event in case of connection loss. |
|
| 8 | 103593 | JR40946 | Message flow is getting deployed successfully in to the broker when there is connection failure and Lost for inbound scenario |
| Symptom: Message flow deployment in to the broker is successful when there is connection failure and connection Lost for inbound scenario. |
| Resolution: Changed the default value of the property retryConnectionOnStartup to false. |
|
| 9 | | JR40947 | Errors are caused when building the project after running EMD for inbound scenario. |
| Symptom: Errors are caused when building the project after running EMD for inbound scenario. |
| Resolution: Changed JDERTEDataDescription.getCardinality() to return "1" instead of "RTE". |
|
| 10 | | JR40974 | Runtime errors occured for JDE inbound and SAP outbound mediation flow scenario in WPS7.5 |
| Symptom: Runtime errors occured for JDE inbound and SAP outbound mediation flow scenario in WPS7.5. Throws "org.xml.sax.SAXNotRecognizedException: Feature 'http://apache.org/xml/features/xinclude' is not recognized" due to xerces dependency jar required by the adapter. |
| Resolution: Setting the property "org.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeAwareParserConfiguration" in jre/lib/xerces.properties in the WPS' java runtime directory removes the SAXNotRecognizedException exception. |
|