Problem

The JMaster was no longer able to process the edislave request, edislave entered in Emergency state. The JMaster only tried to process the result corresponding to the failed configuration.

Cause

Adding a long parameter, that exceeds the maximum character allowed length in the DB which is 32 will cause the master to go in a loop and only try to process the result of the workflow with the faulty configuration. Issue is caused by adding double quotes in the pop.cfg configuration, ACTUAL_PARAM:

pop.cfg

ACTUAL_PARAM="SUBJECT=asdf.asdfgh@email.com,

asdf.asdfgh@email.com,asdf.asdfghjk@email.com,asdf.asdfghjk@email.com"

"asdf.asdfghjk@email.com,asdf.asdfghjk@email.com,asdf.asdfghjk@email.com,asdf.asdfghjk@email.com"
ACTUAL_PARAM="NOTIFY="company_name 824 - Application Advice"

Cannot handle event: java.sql.SQLException: ORA-12899: value too large for column

madeb errors:

ERROR 09:08:13,198 master.WorkerThread [LogProtHandler-44764562 /

/10.3.35.129:48758] [LogProtMsgDaemon.java 1653] - error in handleEvent

java.sql.SQLException: ORA-12899: value too large for column "ACTISVTB_RUN"."CTRL_CFGJOBPAR"."NAME" (actual: 40, maximum: 32)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)

at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1017)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:655)

at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:249)

at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:566)

at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:215)

at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:58)

at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:943)

at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1075)

at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3820)

at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3897)

at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1361)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105)

at de.axway.aim.controller.master.DebPrepStmt.executeUpdate(DebPrepStmt.java:171)

at de.axway.aim.controller.master.cfg.CfgJSelectEntry.save(CfgJSelectEntry.java:407)

at de.axway.aim.controller.master.LogProtMsgDaemon$LogProtHandler.handleEvent(LogProtMsgDaemon.java:1592)

at de.axway.aim.controller.master.LogProtMsgDaemon$LogProtHandler.inject(LogProtMsgDaemon.java:741)

at de.axway.lib.logprot.LogProtRecvPort.inject(LogProtRecvPort.java:1637)

at de.axway.lib.logprot.LogProtRecvPort.inject(LogProtRecvPort.java:1629)

at de.axway.lib.logprot.LogProtRecvPort.receiveAnEvent(LogProtRecvPort.java:1533)

at de.axway.lib.logprot.LogProtRecvPort.doRun(LogProtRecvPort.java:1380)

at de.axway.aim.controller.master.LogProtMsgDaemon$LogProtHandler.doRun(LogProtMsgDaemon.java:572)

at de.axway.aim.controller.master.WorkerThread.run(WorkerThread.java:388)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)

at java.lang.Thread.run(Thread.java:795)

Master Log Errors:

Error*******|11.10.2018 09:06:45.058|MyPID=4327092 |Cannot handle

event: java.sql.SQLException: ORA-12899: value too large for column

"ACTISVTB_RUN"."CTRL_CFGJOBPAR"."NAME" (actual: 40, maximum: 32)

Error*******|11.10.2018 09:07:12.992|MyPID=4327092 |Cannot handle

event: java.sql.SQLException: ORA-12899: value too large for column

"ACTISVTB_RUN"."CTRL_CFGJOBPAR"."NAME" (actual: 40, maximum: 32)

Error*******|11.10.2018 09:08:13.198|MyPID=4327092 |Cannot handle

event: java.sql.SQLException: ORA-12899: value too large for column

"ACTISVTB_RUN"."CTRL_CFGJOBPAR"."NAME" (actual: 40, maximum: 32)

Resolution

The workaround: Avoid adding doulbe quotes in the ACTUAL_PARAMER section in pop.cfg

Solution implemented by RD in SP15:

1.Added parameter to define whether double quotes should be allowed in wf parameter values.

2. added validation against double quotes.