Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Batch Programs fail when setting response in Interaction Service

SA-8566
 

Summary



User has observed that multiple Batch Programs failed while trying to set response in Interaction Service (IS).

Error Messages



409 [ PegaRULES-Batch-3] [ STANDARD] [ PegaNBAM:06.03] (seInBatch.System_Queue_.Action) ERROR - ProcessBatch - Error while batch set response.
com.pega.decision.is.ISException: unexpected error when rollbacking
at com.pega.decision.is.ISException.raise(ISException.java:45)
at com.pega.decision.is.impl.ISCoreServiceImpl.serviceCall(ISCoreServiceImpl.java:966)
at com.pega.decision.is.impl.ISCoreServiceImpl.setResponse(ISCoreServiceImpl.java:221)
at sun.reflect.GeneratedMethodAccessor237.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at org.springframework.remoting.support.RemoteInvocationTraceInterceptor.invoke(RemoteInvocationTraceInterceptor.java:70)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)


Steps to Reproduce



Run Programs.

Root Cause



The root cause of this problem is defect/misconfiguration in user's environment from the Oracle database perspective.

Resolution



Recomended to engage Oracle Support team.
Oracle advised user to maintain the connections alive from JDBC perspective. This can be done by setting  ENABLE=BROKEN parameter in the DESCRIPTION clause in the JDBC connection descriptor.


For example: 
jdbc:oracle:thin:@(DESCRIPTION=(ENABLE=BROKEN)(ADDRESS=(PROTOCOL=tcp)(PORT=1521)(HOST=myhost))(CONNECT_DATA=(SERVIVE_NAME=orcl))) 

Also suggested user to set SQLNET.EXPIRE_TIME=1 in the database sqlnet.ora. This will enable Dead Connection Detection (DCD). 

Reference: java.sql.SQLRecoverableException: Closed Connection When Running Application
 (Doc ID 1642867.1).

Published April 20, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us