Identity Management (MOSC)

MOSC Banner

What is causing "oracle.security.am.asdk.AccessClient$ConfigUpdateTimerTask run"?

edited Jul 14, 2016 11:23AM in Identity Management (MOSC) 4 commentsAnswered ✓

Hi,

I am working with a relatively simple test application to test working with the OAM ASDK.  My app seemed to work fine at home, but when I test at work, the app runs through ONCE, but then, after a few minutes, it appears to start executing AGAIN, and then I get something like this:

Jul 13, 2016 2:20:10 PM oracle.security.am.asdk.AccessClient$ConfigUpdateTimerTask run

WARNING: Failed to read/write configuration in file {0}.

I'm guessing that there's some kind of internal timer/looping, maybe so that SOMETHING is causing my app to re-read the configuration file every 'x' minutes, and then re-runs my app, but I have NO idea what the "SOMETHING" might be?  That looping/re-running is definitely not something that I configured, not on purpose, at least.

Tagged:

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