RPM Conflict Checking Process Not Completing - StuckThreadMaxTime Timeout (Doc ID 2191941.1)

Last updated on OCTOBER 17, 2016

Applies to:

Oracle Retail Price Management - Version 14.1 and later
Information in this document applies to any platform.

Symptoms

  If Promotion is stuck in conflict checking and its taking long time to complete  or its not completing,verify the RPM.log and if  there is below error in the RPM server log,the data base operation will not proceed since "Stuck Thread Max Time" exceeds more then the configured time in the Weblogic Server.

This error occurs because the WebLogic Server has exceeded its “Stuck Thread Max Time:” default value of 600 seconds.

 

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms