I am working on related activities on a replica of ci.hibernate.org
am playing with Docker and trying to see how well it could fit the the
project build needs.
When running OGM build job on this replica server, I have noticed the same
I think that the problem is related to Axis plugin, like you were pointing
I have also noticed this:
That is the link for the plain text version of the logs.
Not sure if the message you find there:
No such file: /var/lib/jenkins/jobs/hibernate-ogm-master/builds/2014-04-01_07-01-01/log
Is the blocking problem or just a side-effect of something else.
I hope to be able to show soon a Docker based approach to possibly bypass
totally this kind of problems.
On Tue, Apr 1, 2014 at 12:46 PM, <hibernate-dev-request(a)lists.jboss.org>wrote:
Send hibernate-dev mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of hibernate-dev digest..."
1. [OGM] CI jobs hang (Gunnar Morling)
2. Re: Session and carrying 3rd party state (Gunnar Morling)
3. Re: Session and carrying 3rd party state (Gunnar Morling)
---------- Forwarded message ----------
From: Gunnar Morling <gunnar(a)hibernate.org>
To: "hibernate-dev(a)lists.jboss.org" <hibernate-dev(a)lists.jboss.org>
Date: Tue, 1 Apr 2014 09:20:28 +0200
Subject: [hibernate-dev] [OGM] CI jobs hang
For some reason, the CI jobs for OGM can't be executed (all jobs, master,
java8, PR seem affected) . They hang forever in an initial state, i.e.
there is no console output and also the sub-jobs are not dispatched (these
are matrix projects). Worse, they can't even be canceled (trying to do so
has no effect), only a server restart helps.
Have there been any recent changes to the job (or server) config which may
cause this? I found https://issues.jenkins-ci.org/browse/JENKINS-9688which
indicates, that the jobs may be waiting eternally for a resource which they
can't acquire (I don't see any resources requested in the job config, but I
vaguely remember something around JGroups channels).
Does anyone know what's going on here?