On 1.9.2014 09:56, Galder Zamarreño wrote:
Hi guys,
Thanks a lot for your feedback on this.
Having looked closer, the log message says:
[echo] Killing Infinispan server with PID - 3658 29739
And the pattern of how that log message gets computed is:
echo message=Killing Infinispan server
Galder, I think kill is working properly, but the server socket cannot be
bound because a client connection has not finished closing:
http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t
On Tue, Sep 2, 2014 at 9:09 AM,
Hi,
So, according to that, ${pid} is “3658 29739” which looks wrong.
Not sure what that means, whether there are two processes running and both
should be killed, or the way the PID is computed is buggy.
IMHO it means that there are 2 processes running, both need to be killed. If
the PID
Hi,
I looked at it and I don't think using InfinispanServerKillProcessor would be
any better,
since it still just calls 'kill -9'. The only difference is that it doesn't
kill all
java processes starting from jboss-modules.jar, but just the one configured for
the test.
Is it maybe possible
Hi,
Dan has reported [1]. It appears as if the last server started in
infinispan-as-module-client-integrationtests did not really get killed. From
what I see, this kill was done via the specific Ant target present in that
Maven module.
I also remembered recently [2] was added. Maybe we need
