Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Gopesh Saha (GOPESH SAHA)
Merkle
Lead Decisioning Architect
Merkle
GB
GOPESH SAHA Member since 2011 26 posts
Merkle
Posted: Sep 18, 2019
Last activity: Sep 23, 2019
Posted: 18 Sep 2019 6:00 EDT
Last activity: 23 Sep 2019 11:02 EDT
Closed

Campaign failed with Exception in stage: Offer Flow Suspend and Update the campaign to resolve this issue

Hi,

We are running a campaign and getting error as below. Would you kindly help us to understand the root cause or what action we could take to resolve this?

Thank you!

Exception in stage: Offer Flow
Suspend and Update the campaign to resolve this issue. After updating, you can Restart or Skip this run

Checked in the log and below is the log message:

Show More

Hi,

We are running a campaign and getting error as below. Would you kindly help us to understand the root cause or what action we could take to resolve this?

Thank you!

Exception in stage: Offer Flow
Suspend and Update the campaign to resolve this issue. After updating, you can Restart or Skip this run

Checked in the log and below is the log message:

  api.dataflow.DataFlow) ERROR   - Supressing an exception from status subscriber onNext 
com.pega.dsm.dnode.api.DNodeException: Unable to release lock on [Data_Flow_Lock_For_ASSIGN-DDF PR-2938!DIST72STATUS_CHANGE] 
	at com.pega.dsm.dnode.impl.dataflow.manager.DataFlowLockManager.unlock(DataFlowLockManager.java:58) 
	at com.pega.dsm.dnode.impl.dataflow.manager.WorkPersistenceManager.saveWithStatusChange(WorkPersistenceManager.java:156) 
	at com.pega.dsm.dnode.impl.dataflow.manager.WorkPersistenceManager.save(WorkPersistenceManager.java:130) 
	at com.pega.dsm.dnode.impl.dataflow.manager.DataFlowMetricsSubscriber$AssignmentUpdater.updateWith(DataFlowMetricsSubscriber.java:156) 
	at com.pega.dsm.dnode.impl.dataflow.manager.DataFlowMetricsSubscriber.onNext(DataFlowMetricsSubscriber.java:55) 
	at com.pega.dsm.dnode.impl.dataflow.manager.DataFlowMetricsSubscriber.onNext(DataFlowMetricsSubscriber.java:25) 
	at com.pega.dsm.dnode.api.dataflow.DataFlow$1$2.onNext(DataFlow.java:234) 
	at com.pega.dsm.dnode.api.dataflow.DataFlow$1$2.onNext(DataFlow.java:228) 
	at com.pega.dsm.dnode.api.dataflow.DataFlow$1.emit(DataFlow.java:156) 
	at com.pega.dsm.dnode.impl.stream.DataObservableImpl.subscribe(DataObservableImpl.java:56) 
	at com.pega.dsm.dnode.impl.dataflow.manager.LocalRun.execute(LocalRun.java:149) 
	at com.pega.dsm.dnode.impl.dataflow.manager.LocalRun.lockAndRun(LocalRun.java:87) 
	at com.pega.dsm.dnode.impl.dataflow.manager.LocalRun.run(LocalRun.java:63) 
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
	at com.pega.dsm.dnode.impl.prpc.PrpcThreadFactory$PrpcThread.run(PrpcThreadFactory.java:81) 
Caused by: com.pega.pegarules.pub.database.LockGoneException: Database-LockFailure-LockLost	Data_Flow_Lock_For_ASSIGN-DDF PR-2938!DIST72STATUS_CHANGE 
From: (B17ABCCCF0E0040267BA0ECFB7F59B2CF)  
	SQL: select pxOwnerId as "pxOwnerId", pxUpdateOperator as "pxUpdateOperator", pxUpdateOpName as "pxUpdateOpName", pxExpireDateTime as "pxExpireDateTime", pxUpdateDateTime as "pxUpdateDateTime", pxLockHandle as "pxLockHandle", pxCreateDateTime as "pxCreateDateTime", pxUserHost as "pxUserHost" from PEGA_DATA.pr_sys_locks where pzInsKey = ? 
	SQL Inserts: <Data_Flow_Lock_For_ASSIGN-DDF PR-2938!DIST72STATUS_CHANGE>	 
 
	at com.pega.pegarules.data.internal.access.DBLockProviderImpl.releaseLock(DBLockProviderImpl.java:834) 
	at com.pega.dsm.dnode.impl.dataflow.manager.DataFlowLockManager.unlockWithLockProvider(DataFlowLockManager.java:82) 
	at com.pega.dsm.dnode.impl.dataflow.manager.DataFlowLockManager.unlock(DataFlowLockManager.java:56) 
	... 15 more 
2019-09-18 09:53:54,855 [-threads-1000418060)] [  STANDARD] [                    ] [      AAMKT:01.21.01] (PegaMKT_Work_ProgramRun.Action) ERROR   - Failure in ExecuteProgramRun: Exception in stage: Offer Flow


Show Less
To see attachments, please log in.
Pega Marketing
System Administration

  • Rishi Sinha
Posted: 5 years ago
Posted: 19 Sep 2019 14:14 EDT
Sriram Coimbatore Krishnan (Sriram Krishnan)
PEGA
Fellow, Software Architect, Outbound Runtime
Pegasystems Inc.
US

Hi,

Does this exception happen for every campaign run or this particular item PR-2938 is continuously throwing the same exception ? are other campaign running in this system fine ?

Can you open the data flow work object item - PR-2938 (instance of Pega-DM-DDF-Work) in the designer portal and see what sort of errors are reported there ? there would also be a component level error reported and that would be useful to click on the link and get the status message of the failure.

Are there any campaign custom extension activities being called by taking over any Pega Marketing rules ?

To see attachments, please log in.
Posted: 5 years ago
Posted: 23 Sep 2019 10:59 EDT
Gopesh Saha (GOPESH SAHA)
Merkle
Lead Decisioning Architect
Merkle
GB

Hi,

This error was for every reschedule(i.e. multiple PR runs). After trying few times, gradually records processed, and after that no error reported. But, while we pick a new set of data, this happened again.

Regards,

Gopesh

To see attachments, please log in.
Posted: 5 years ago
Posted: 23 Sep 2019 11:02 EDT
Gopesh Saha (GOPESH SAHA)
Merkle
Lead Decisioning Architect
Merkle
GB

Hi All,

Just to confirm on this issue, I didn't find the exact root cause for this issue, but while we run campaign same as live configuration this works. So, we requested testing team to proceed with some more test based on Live configuration and see.

Thanks for your response!

Regards,

Gopesh

To see attachments, please log in.

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

Pega Collaboration Center 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