Thanks for your response.
I made the change to swimlanes; but it doesn't seem to affect the behavior of
creating records in the JBPM_POOLEDACTOR table for every task instance.
I guess this is just how it works. Perhaps I'll repost on the JBPM-DEV list for
comment.
Thanks,
David
View the ori
Hi,
Could someone let me know if this is normal behavior ? We have a series of
tasks where we are doing a simple assignment to a pooled-actor.
|
|
|
|
I am noticing that for every task-instance that is created, a new pooledactor
is cre
Moving to Jboss-Cache 1.4.1 SP4 and Jgroups 2.4.1SP3 seems to resolve this
issue.
There is an interesting memory usage pattern occuring though: After the server
starts up we see a gradual increase in memory usage on one node in the cluster.
It approaches the Maximum allocated to the instance,
Thank-you for the prompt reply.
I will try upgrading jgroups.
Would it be advisable to upgrade jboss-cache to SP4 as well?
[EMAIL PROTECTED] lib]$ java -cp jgroups.jar org.jgroups.Version
Version:2.4.1
CVS:$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $
His
Hi,
We are using Jboss 4.0.5 in a cluster. We are experiencing deadlock within the
Jboss Cache, which is causing out of memory problems on the server. The Jboss
Cache Version is 1.4.1SP3 (bundled Cache for jboss 4.0.5). We only expirience
this issue when BUDDY replication is enabled.
The thr
