IBM Support

When translating large files receiving error 170 Extended Rule Failure where User Exits that perform SQL queries are called.

Troubleshooting


Problem

Using same map and smaller input file they process without the Extended Rule Failure error. 
The Database Usage is indicating that the  JDBC Pool connection, which the map is using, reached maximum number of connections when processing the large input file. 

Symptom

Oracle DB, which is the source of the SQL in user exit, is at max capacity (found in Database Usage)
system.log showing

ERROR 000110010846 WORKFLOW.WORKFLOW.ERR_Document_setUserLifeSpan [Document].setUserLifeSpan() Unable to insert/update document user lifespan
ERROR <LWUtility.JdbcService--972570377> LWUtility.JdbcService - Error connecting to database  Exception: Failed to get a JDBC connection

ERROR [LightweightJDBCAdapter] Error executing sql query "UPDATE dbo.tblHHShipConfirmInbound SET ASNProcessed = 0 WHERE ReferenceNumber = ?".
ERROR [1677152040991] Transaction (Process ID 87) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
ERROR 000000000000 GLOBAL_SCOPE [LightweightJDBCAdapter] Error executing sql query "UPDATE dbo.tblHHShip SET ASNProcessed = 0 WHERE ReferenceNumber = ?".
SQL Error Code: 1205
SQL State: 40001
com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 87) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
ERROR 000310160003 UTIL.FRAME_POOL.ERR_Pool_getItem1 [Pool].getItem(boolean): Could not create a new item.

tx.log showing:
ERROR 000610100006 TRANSLATION.TRANSLATION_RULES.ERR_ExtendedRuleExecuter_str1 Translator extended rule InvocationTargetException - see appserver log for stack trace
TRANSLATION.TRANSLATION_RULES.null
TRANSLATION.TRANSLATION_RULES.java.lang.reflect.InvocationTargetException
Caused by: java.lang.NullPointerException
    at com.sterlingcommerce.woodstock.translator.rules.UserExitOpcodes.callObjectMethod_JP_(UserExitOpcodes.java:200)
futher down we see:
Caused by: java.lang.RuntimeException: com.sterlingcommerce.woodstock.util.frame.jdbc.JDBCConnectionException: Failed to get a JDBC connection

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"ARM Category":[{"code":"a8m50000000CjtJAAS","label":"Translation-\u003EUnclear Error Message-\u003ETranslation Errors"},{"code":"a8m50000000CjtxAAC","label":"Translation-\u003EUser Exit-\u003EUE Ext Rule Function"}],"ARM Case Number":"TS012242876","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
15 May 2023

UID

ibm16958530