From the TRACE logs, I can see that
org.hibernate.cache.infinispan.access.TransactionalAccessDelegate.remove(Object)
invoked the writeCache.remove(key) with
key=org.jboss.as.test.clustering.cluster.ejb3.xpc.bean.Employee#1 but
the other node isn't notified of this change (as far as I can tel
I'm now on the path of trying to clean the test up to make fewer
assumptions about whether loading an entity locally will share the
loaded value across the cluster with other nodes 2lc. Perhaps we have
optimized the cache to only load locally and still invalidate across the
cluster.
Scott
On
Hi,
Emmanuel said he wanted to contact Max, not sure what came out of this.
--Gunnar
Am 14.12.2012 18:56 schrieb "Steve Ebersole" :
> Nope, but I'll look into it.
>
> On Fri 14 Dec 2012 10:53:27 AM CST, Gunnar Morling wrote:
>
>>
>> Hi all,
>>
>> As it seems, there is a problem with the IRC tran
Nope, but I'll look into it.
On Fri 14 Dec 2012 10:53:27 AM CST, Gunnar Morling wrote:
>
> Hi all,
>
> As it seems, there is a problem with the IRC transcripts from
> #hibernate-dev [1]. There are no logs after December 12th. Does anyone
> happen to know whats the problem and how it could be fixed
Hi all,
As it seems, there is a problem with the IRC transcripts from
#hibernate-dev [1]. There are no logs after December 12th. Does anyone
happen to know whats the problem and how it could be fixed?
Thanks,
--Gunnar
[1]
http://transcripts.jboss.org/channel/irc.freenode.org/%23hibernate-dev/20
I'll add TRACE logging to
org.hibernate.cache.infinispan.access.TransactionalAccessDelegate to
show more information about what is going on in there when we fail to
invalidate the 2lc on the other node.
Any other ideas?
On 12/14/2012 10:13 AM, Scott Marlow wrote:
> On 12/14/2012 09:46 AM, Sco
On 12/14/2012 09:46 AM, Scott Marlow wrote:
> I enabled org.jboss.as.jpa TRACE logging as well as org.infinispan TRACE
> (I know overly verbose) logging. Output is here
> http://dl.dropbox.com/u/35343318/jboss/serverlogs.zip
>
> In the node1 log, I see that we delete the entity and then try to
> p
I enabled org.jboss.as.jpa TRACE logging as well as org.infinispan TRACE
(I know overly verbose) logging. Output is here
http://dl.dropbox.com/u/35343318/jboss/serverlogs.zip
In the node1 log, I see that we delete the entity and then try to
perform the remove command. I don't seem to see this
