Yeah, I reached the same conclusion.
Hence why I got started though with https://issues.jboss.org/browse/ISPN-1404
and https://issues.jboss.org/browse/ISPN-1408 that need to be fixed both at
same time.
It still requires some config modification, but a lot less drastic that the two
jiras
Hi,
one of our efforts around EDG testing is to test whether all XML
elements/attributes being set in standalone.xml take effect, i.e.
whether org.infinispan.config.Configuration, which in turn is used to
create caches, is populated properly based on the xml config file.
(this test goal is
On 12 Oct 2011, at 22:21, Vladimir Blagojevic wrote:
Hey guys,
After endless hours of super interesting hacking I think this one is
close to integration now. While you guys review it I'll tidy up javadoc
and amend the pull.
I've added my comments to the pull request.
A few notes. I kept
Hi all,
since we're mentioning ispncon
I had this idea of adding simple server instance management that would
allow me to
do simple test scenarios that involve starting, stopping, killing servers
the shape of the addon to the interface is briefly described here:
Brilliant! and as you suggested yourself, we could reuse the same
channel that jconsole and other agents use so it wouldn't be an extra
port but one which syadmins have to think about anyway (especially
when locking down the system)
Sanne
On 13 October 2011 20:30, Dan Berindei
Hey all,
I'm a bit stuck with the Infinispan 5.1 upgrade in AS 7.1.
I've tried both with BETA1 and a SNAPSHOT build from today.
When a deployment forces a cache to start, I see the following
stacktrace:
14:06:07,584 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8)
MSC1: Failed
