OpenSSO : high count of session updates against /opensso/sessionservice - MQ max session reached (Doc ID 1432304.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle OpenSSO - Version: 8.0 and later   [Release: 8.0 and later ]
Information in this document applies to any platform.

Goal

High count of session update could let run the Message Queue (MQ) out of message ids and so OpenSSO are going slow, because no session where longer handled.

This error message will be produced:

Storing of JMS message from IMQConn[AUTHENTICATED,openssomqusr@<ip>null] failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: [B4120]: Can not store message 254436-<ip>-1329398065771 on destination AM_DBREQUEST [Topic]. The destination message count limit (maxNumMsgs) of 100000 has been reached.


How to solve this ?

Solution

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