AFX Requests fails to process as the Usage Store Manager is full in RSA Governance & Lifecycle
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.2.x, 7.5.x
Issue
The following error is being logged in /home/{afxuser}/AFX/esb/logs/esb.AFX-MAIN.log:
2022-10-11 11:09:14.294 [ERROR] org.mule.exception.DefaultMessagingExceptionStrategy:337 -
********************************************************************************
Message : Failed to route event via endpoint: DefaultOutboundEndpoint{endpointUri=jms://AFX.INBOUND?connector=jmsConnector, connector=ActiveMQJmsConnector
{
name=jmsConnector
lifecycle=start
this=34281e5b
numberOfConcurrentTransactedReceivers=1
createMultipleTransactedReceivers=true
connected=true
supportedProtocols=[jms]
serviceOverrides=<none>
}
, name='endpoint.jms.AFX.INBOUND', mep=ONE_WAY, properties={connector=jmsConnector}, transactionConfig=Transaction{factory=null, action=INDIFFERENT, timeout=0}, deleteUnacceptedMessages=false, initialState=started, responseTimeout=10000, endpointEncoding=UTF-8, disableTransportTransformer=false}. Message payload is of type: ActiveMQTextMessageCode : MULE_ERROR--2
--------------------------------------------------------------------------------
Exception stack is:
1. Usage Manager Store is Full, 100% of 1073741824. Stopping producer (ID:clrv0000234346.ic.ing.net-45827-1664872697929-0:1:729507:1) to prevent flooding queue://AFX.INBOUND. See http://activemq.apache.org/producer-flow-control.html for more info(JMS Code: null) (javax.jms.ResourceAllocationException) org.apache.activemq.broker.region.BaseDestination:581 (http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/ResourceAllocationException.html)
2. Failed to route event via endpoint: DefaultOutboundEndpoint{endpointUri=jms://AFX.INBOUND?connector=jmsConnector, connector=ActiveMQJmsConnector
{
name=jmsConnector
lifecycle=start
this=34281e5b
numberOfConcurrentTransactedReceivers=1
createMultipleTransactedReceivers=true
connected=true supportedProtocols=[jms]
serviceOverrides=<none>
},
name='endpoint.jms.AFX.INBOUND', mep=ONE_WAY, properties={connector=jmsConnector}, transactionConfig=Transaction{factory=null, action=INDIFFERENT, timeout=0}, deleteUnacceptedMessages=false, initialState=started, responseTimeout=10000, endpointEncoding=UTF-8, disableTransportTransformer=false}. Message payload is of type: ActiveMQTextMessage (org.mule.api.transport.DispatchException) org.mule.transport.AbstractMessageDispatcher:117 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/transport/DispatchException.html)
--------------------------------------------------------------------------------
Root Exception stack trace:
javax.jms.ResourceAllocationException: Usage Manager Store is Full, 100% of 1073741824. Stopping producer (ID:clrv0000234346.ic.ing.net-45827-1664872697929-0:1:729507:1) to prevent flooding queue://AFX.INBOUND. See http://activemq.apache.org/producer-flow-control.html for more info
at org.apache.activemq.broker.region.BaseDestination.waitForSpace(BaseDestination.java:581)
at org.apache.activemq.broker.region.Queue.checkUsage(Queue.java:735)
at org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:665)
+ 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
********************************************************************************
Cause
Workaround
- Log in as the AFX user
- Stop AFX
- Create a new KahaDB following this article: How to create a new ActiveMQ KahaDB for use with AFX in RSA Identity Governance & Lifecycle
- Edit /home/{afxuser}/AFX/activemq/conf/log4j.properties to add the rollover settings:
log4j.appender.kahadb=org.apache.log4j.RollingFileAppender
log4j.appender.kahadb.file=${activemq.base}/data/kahadb.log
log4j.appender.kahadb.maxFileSize=100MB
log4j.appender.kahadb.maxBackupIndex=5
log4j.appender.kahadb.append=true
log4j.appender.kahadb.layout=org.apache.log4j.PatternLayout
log4j.appender.kahadb.layout.ConversionPattern=%d [%-}}\{{15}}{{.15t] %5p %30.30c{1} - %m%n
log4j.logger.org.apache.activemq.store.kahadb.MessageDatabase=TRACE, kahadb
- Start AFX
Related Articles
How to resolve ORA-22285 error thrown in the Data Archiving process of RSA Identity Governance & Lifecycle 29Number of Views Office365 Collector fails to process 'Is Disabled' and 'Is Locked' flags and Admin Error 'ORA-01722: invalid number' in RS… 68Number of Views Full Refresh Deactivates Manual User Account Mappings in RSA Identity Governance & Lifecycle 167Number of Views RSA MFA Agent 2.0 for Epic Hyperdrive Installation and Administration Guide 142Number of Views JVM crash during verification process of upgrade 23Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x
Don't see what you're looking for?