Article Original Creation Date: 2011-04-04
flag = "required">
guest
java:/DefaultDS
SELECT PASSWD FROM JMS_USERS WHERE USERID=?
SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?
flag = "required">
guest
jboss.mq:service=StateManager
Problem
The SG4 does not start policy when events are sent.
This is tried on Bootstrap and Boot events
The appl log says:
Because all event types have exceeded their queue limits.
Environment
Solaris 10,
Oracle 10,
JBoss 4.0.4.GA
Tomcat 5.5.25
Cause
In first instance a check of the sprt_sg_policy_device_hold table showd 3 policies with 500 up to 1750 devices queued.
The sprt_nc_inform_event table also hold 8500 entries.
This all happened because of some performance issue in the application mainly happening regarding the DB connections.
Configured are 250 connections per application server and it turned out that connections were not freed up quick enough.
In that case the Encore.log shows: 'Managed connection errors' Causing all kinds of policy related performance problems.
Check resolution for the final problem cause.
Solution
The final resolution was to Install JBoss and SG4.1.3 from scratch on both servers.
After that we investigated the main cause and it turned out to be the Null Persistence configuration setting in the
JBoss_home_dir/server//conf/login-config.xml file.
Both Security domain for JBossMQ and Security domain for JBossMQ when using file-state-service.xml need to be uncommented!