Last updated on SEPTEMBER 21, 2016
Applies to:Oracle OpenSSO - Version 8.0.2 and later
Information in this document applies to any platform.
We are seeing message count limit reached errors in sessiondb logs while doing performance testing. Once this error shows up OpenSSO becomes unresponsive and needs a restart of sessiondb and OpenSSO servers. In the beginning of performance test we see the same error with "100000" number instead of 300000. Changing the value from 100000 to 300000 delayed error but did not help.
Oracle OpenSSO 8.0 Update 2 Patch5 Build 6.1(2012-December-3 04:25)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms