Hey Dan!
Regarding to CDI Extension - yes, that's possible.
We can set it to "DefaultCDIManager" or something similar. On the other
hand it will cause the same exception if user deploys 2 applications and
each will use a Default CDI Producer (unfortunately CDI does not expose
any deployment inf
Dear Infinispan community,
Infinispan 7.1.0.CR1^H2 is available (well, problems can happen ;)
Read more at:
http://blog.infinispan.org/2015/01/infinispan-710cr2-released.html
--
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat
___
infinis
Indeed, I wouldn't consider it a problem if the warning appears with two
applications deployed. I would suggest also changing the warning message to
point to cacheManagerName, not just allowDuplicateDomains.
Cheers
Dan
On Fri, Jan 23, 2015 at 12:02 PM, Sebastian Łaskawiec
wrote:
> Hey Dan!
>
>
That's a good point. I'll include that in my Pull Request.
Thanks for the hint!
Sebastian
On 01/23/2015 02:57 PM, Dan Berindei wrote:
> Indeed, I wouldn't consider it a problem if the warning appears with
> two applications deployed. I would suggest also changing the warning
> message to point
Hey Manik, I think I remember some JIRA to have a state transfer manually, upon
management operation or similar, in order to avoid state transfer mayhem when
bringing a lot of nodes at the same time. I don’t know what’s happened to that,
but would it work?
Cheers,
On 17 Jan 2015, at 02:43, Man
Galder, Manik, the jira you mention is ISPN-3140 JMX operation to
suppress state transfer [1], implemented quite a long time ago. This
should solve the problem of many simultaneous joiners. Does this fit
your needs?
[1] https://issues.jboss.org/browse/ISPN-3140
On 01/23/2015 06:10 PM, Galder Z
No it doesn't. That's quite a different problem. I don't want manual
intervention.
On 23 January 2015 at 08:35, Adrian Nistor wrote:
> Galder, Manik, the jira you mention is ISPN-3140 JMX operation to
> suppress state transfer [1], implemented quite a long time ago. This
> should solve the pro
