Retail Predictive Application Server (MOSC)

MOSC Banner

Is there an option to modify commit timeout setting in RPASv19?

in Retail Predictive Application Server (MOSC) 1 commentAnswered ✓

Hi,

We are currently exploring RPAC as a means of test automation for A&IP. During our testing, we encountered commit timeouts due to "TestCase got UserDoesNotExist" error. We have added the correct user but the same error persists.

While we are doing user changes, each RPAC execution runs around 8 hours. I believe this is a setting within RPASv19. Our goal is to reduce the timeout to a shorter time temporarily until we fix the UserDoesNotExist error.

We have tried OAT tasks such as list/set/unset domain variables, manage domain properties, etc but we can't find the option to shorten this timeout setting.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center