000030929 - Offline task issues with JBOSS application server in RSA Adaptive Authentication (OnPrem)

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000030929
Applies ToRSA Product Set: Adaptive Authentication (OnPrem)
RSA Version/Condition: 7.1 P2
Platform: UNIX
Platform (Other): JBOSS Appliacation Server
O/S Version: Solaris 10
IssueOffline tasks fail with the following errors in the log (aa_re.offline.log)
ERROR [com.rsa.re.offlinetasks.tasks.normalization.ScoreNormalizationOnEventBuckets] org.jboss.util.threadpool.ThreadPoolFullException: Error scheduling work: org.jboss.util.threadpool.RunnableTaskWrapper@1e302d9
java.lang.RuntimeException: org.jboss.util.threadpool.ThreadPoolFullException: Error scheduling work: org.jboss.util.threadpool.RunnableTaskWrapper@1e302d9
    at com.rsa.tools.external.jboss.workmanager.connector.ReJBossWorkManager.schedule(ReJBossWorkManager.java:87)
    at com.rsa.tools.external.jboss.workmanager.connector.ReJBossWorkManager.schedule(ReJBossWorkManager.java:105)
CauseFailing to configure a separate work manager for RSA Risk Engine Offline tasks causes thread pool exceptions
 
ResolutionFor JBoss, you must define a new thread pool “OfflineTaskThreadPool” with default settings dedicated to offline tasks.
For example, the JBOSS_HOME\server\default\deploy\jca-jboss-beans.xml file is as follows:

<!-- AA Risk Engine Offline Tasks Thread Pool -->
<bean name="OfflineTaskThreadPool" class="org.jboss.util.threadpool.BasicThreadPool">
<!-- Expose via JMX -->
<annotation>@org.jboss.aop.microcontainer.aspects.jmx.
JMX(name="jboss.system:service=OfflineTaskThreadPool",exposedInterface=org.jboss.util.threadpool.BasicThreadPoolMBean.class)
</annotation>
<!-- The name that appears in thread names -->
<property name="name">OfflineTaskThreadPool</property>
<!-- The maximum amount of work in the queue -->
<property name="maximumQueueSize">1024</property>
<!-- The maximum number of active threads -->
<property name="maximumPoolSize">100</property>
<!-- The minimum number of active threads -->
<property name="minimumPoolSize">10</property>
<!-- The behaviour when the queue is full
(default abort) -->
<property name="blockingMode">wait</property>
<!-- How long to keep threads alive after their last work
(default one minute) -->
<property name="keepAliveTime">60000</property>
</bean>

Attachments

    Outcomes