Error Opening Connection to DriverID
Scenario:
We are processing an inbound XML file (source) into a database table (target). During the ruleset transformation we call a SQL Action.
Issue:
When executing the ruleset we error'd when calling the SQL Action.
EXTOL error message:
[INFO] - Starting Transform
[INFO] - Starting Transformation Engine
[INFO] - Executing "MG Processing"
[ERROR] - A communication error has been detected. Communication protocol being used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error was detected: Software caused connection abort: recv failed. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS
[ERROR] - CacheConnection.prepareStatement() SQLException: A communication error has been detected. Communication protocol being used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error was detected: Software caused connection abort: recv failed. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS
[ERROR] - GMAID lookup from PRODV/F0901: Error opening connection to DriverID: 402d6c58a34a4111a735b9c86110d609 DatabaseURL: jdbc:as400://192.168.10.12/prodvdta Error is: null
[ERROR] - GMAID lookup from PRODV/F0901: The connection to DriverID: 402d6c58a34a4111a735b9c86110d609 DatabaseURL: jdbc:as400://192.168.10.12/prodvdta is null.
[ERROR] - Transformation ended in error, please refer to the information on the Translation Messages Tab.
[INFO] - Ending Transformation Engine
[INFO] - Completed Task.
Resolution:
Reprocess inbound XML file. Error was intermittant.
By: Sean Hoppe on