+1

On Oct 14, 2010, at 9:58 PM, Vladimir Blagojevic wrote:

Yes, absolutely I think! Anytime threads go into client code callbacks we should protected ourselves. There is a very easy way to do this with Proxies#newCatchThrowableProxy

Have a look!

Cheers,

Vladimir

On 2010-10-14, at 3:01 PM, Mircea Markus wrote:

${SUBJECT} ?

This doesn't seem to be specified in the javadoc at the moment. Looking at CacheNotifierImpl it doesn't expect such a thing to happen.

IMO we should handle these exceptions and log them as warn.

One way or the other we should expect this to happen, and document it.

wdyt?

Cheers,

Mircea

_______________________________________________

infinispan-dev mailing list

infinispan-dev@lists.jboss.org

https://lists.jboss.org/mailman/listinfo/infinispan-dev

--

Vladimir Blagojevic

JBoss Clustering Team

JBoss, by Red Hat

_______________________________________________

infinispan-dev mailing list

infinispan-dev@lists.jboss.org

https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Galder Zamarreņo
Sr. Software Engineer
Infinispan, JBoss Cache


_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev