Unfortunately, I don't seem to have the necessary rights to create JIRA issues
:-(
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257545#4257545
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257545
___
Not sure whether there are any further developments on this, but would it be
worthwhile modifying EvictionTimerTask.handleRegion(...) so that at least if an
unforseen problem occurs which causes the eviction to stop then at least the
exception is logged:
private void handleRegion(Region reg
It's 3.0.3.GA
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243992#4243992
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243992
___
jboss-user mailing list
jboss-user@lists.
We have a problem whereby we have seen the following message logged
continuously on a customer's installation of our software that uses JBoss Cache
with Hibernate:
Warning putNodeEvent(): eviction node event queue size is at 98% threshold
value of capacity: 20 Region: /query/entity/by_name
When we start up our JBoss application we sometimes get the exception shown
below. It occurs on roughly 1/4 of startups. We are running JBossAS 4.2.0.GA
with JBoss Messaging 1.4.0.SP3 (also saw problem with SP2). We are running with
clustered destinations (but with just one cluster node at prese
When using SQLServer for the persistence back-end for JBoss Messaging we have
been experiencing a large number of deadlocks when consumer thread transactions
are committed:
| 2007-11-12 10:26:29,088 431718 WARN
[org.jboss.messaging.core.impl.JDBCSupport] (Thread-42:) SQLException caught,
S
We have a two-node clustered JBoss AS (4.2.0GA) installation with JBoss
Messaging 1.4.0.CR2. We have a topic (configured as Clustered) and a remote
client with subscriptions to that topic using a number of selectors.
The PostOffice is also configured as Clustered.
The remote client sometimes re
