I now have a "real" windows pc to test that on - so I'll give it a spin
before reverting/fixing.
Kristian
2013/2/12 Benjamin Bentmann
> Dennis Lundberg wrote:
>
> "ExecuteJava" daemon prio=6 tid=0x06a92790 nid=0x1078 waiting on
>> condition [0x0a63e000..**0x0a63fa10]
>
Dennis Lundberg wrote:
"ExecuteJava" daemon prio=6 tid=0x06a92790 nid=0x1078 waiting on
condition [0x0a63e000..0x0a63fa10]
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
at
java.util.c
An extremely simple solution would be to require JDK 1.6 to build Maven
(but keep Java 5 runtime requirement)...
/Anders
On Thu, Jan 3, 2013 at 7:46 PM, Dennis Lundberg wrote:
> Here's another attempt. It would seem that someone somewhere simply does
> not want people to do this! Here's a rund
Here's another attempt. It would seem that someone somewhere simply does
not want people to do this! Here's a rundown on the hoops I've had to
jump through so far...
* jstack.exe is not available in Sun's Windows 1.5 JDK
* jstack.exe from JDK 1.6 is not allowed to hook into a 1.5 JVM
* SendSigna
That process seems to be just waiting for some other process to complete.
Use something like jps -lv to determine if there's more java processes
around,determine
if any of them seem to be relevant and thread dump them ;)
Kristian
2013/1/2 Dennis Lundberg :
> So, my first ever thread dump. Hope
So, my first ever thread dump. Hope it's the right stuff...
Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.5.0_22-b03 mixed
mode):
"WATCHDOG" daemon prio=6 tid=0x072f1fe0 nid=0x1234 in
Object.wait() [0x0b8df000..0x0b8dfa90]
at java.lang.Object.wait(Native M
Dennis, can you get a thread dump from your windows box?
/Anders
On Wed, Jan 2, 2013 at 5:07 AM, Kristian Rosenvold <
kristian.rosenv...@zenior.no> wrote:
> A thread dump is worth a thousand words ;)
>
> K
>
> Den 2. jan. 2013 kl. 04:28 skrev Dennis Lundberg :
>
> > Hi
> >
> > I've done some mo
A thread dump is worth a thousand words ;)
K
Den 2. jan. 2013 kl. 04:28 skrev Dennis Lundberg :
> Hi
>
> I've done some more digging into this and have come to the following
> conclusions:
>
> 1. It is not the ITs that are the problem - it's the building of core
> itself.
>
> 2. The build hangs
Hi
I've done some more digging into this and have come to the following
conclusions:
1. It is not the ITs that are the problem - it's the building of core
itself.
2. The build hangs when using Java 1.5, but succeeds using Java 1.6.
3. I have only verified this on Windows yet.
Forensic report
Igor and I have successfully run the ITs on 1.5. Igor did it on Linux and I did
it on OS X. So I think it's some interaction on the CI server. I can't get it
to work on Jenkins or Hudson, even with a lot of memory.
On Dec 16, 2012, at 2:43 PM, Anders Hammar wrote:
> The pattern I see is that a
The pattern I see is that all jobs that build with JDK 1.5 hangs. This
includes the windows node.
/Anders
On Sun, Dec 16, 2012 at 7:10 PM, Dennis Lundberg wrote:
> On 2012-12-14 00:29, Brett Porter wrote:
> >
> > On 13/12/2012, at 9:15 PM, Anders Hammar wrote:
> >
> Also, there's some pr
On 2012-12-14 00:29, Brett Porter wrote:
>
> On 13/12/2012, at 9:15 PM, Anders Hammar wrote:
>
Also, there's some problems with Jenkins not finding git installation on
some nodes. But that's a different topic, but possibly related to the
upgrade?
>>>
>>> If you mean the Windows no
/me wants thread dump to put in drink :)
K
Den 16. des. 2012 kl. 04:57 skrev Olivier Lamy :
> 2012/12/14 Anders Hammar :
>> I tried tweaking through:
>> -Xmx512m -Xms512m -XX:MaxPermSize=256m -XX:PermSize=128m
>> but it didn't make any difference.
>
> I did more tests without more success. I ne
2012/12/14 Anders Hammar :
> I tried tweaking through:
> -Xmx512m -Xms512m -XX:MaxPermSize=256m -XX:PermSize=128m
> but it didn't make any difference.
I did more tests without more success. I need to have a look on the
nodes as it's a bit weird.
>
> I don't have much in-depth knowledge about the
I tried tweaking through:
-Xmx512m -Xms512m -XX:MaxPermSize=256m -XX:PermSize=128m
but it didn't make any difference.
I don't have much in-depth knowledge about the darker secrets of Java
memory management so it was just a test. Anyone with a greater brain is
welcome to suggest something to try. O
I have also seen the core it's hang in a quite nasty manner if permgen
is running lowish.
Kristian
2012/12/14 Anders Hammar :
>> I see the hanging too... haven't looked into where it gets stuck any
>> further though. Perhaps it's using an authenticated URL to checkout
>> additional stuff as part
> I see the hanging too... haven't looked into where it gets stuck any
> further though. Perhaps it's using an authenticated URL to checkout
> additional stuff as part of the bootstrap?
>
One theory is that it is related to Jave 5 being used. The JDK 1.6 and 1.7
builds works just fine it seems. Th
On 13/12/2012, at 9:15 PM, Anders Hammar wrote:
>>> Also, there's some problems with Jenkins not finding git installation on
>>> some nodes. But that's a different topic, but possibly related to the
>>> upgrade?
>>
>> If you mean the Windows node, I've already asked about that on
>> builds@a.o
> > Also, there's some problems with Jenkins not finding git installation on
> > some nodes. But that's a different topic, but possibly related to the
> > upgrade?
>
> If you mean the Windows node, I've already asked about that on
> builds@a.o but haven't gotten a reply yet.
>
Git is now found on
> The core-integration-testing-maven-3 jobs has started to hang since
> yesterday morning (whatever timezone the CI is showing). I have no clue how
> to figure out why.
>
I've disabled the "core-integration-testing-maven-3" job for now. We're
just blocking other build jobs as it is now.
As I point
> The Windows node is one, but I believe I saw the same problem on some
> other node as well.
>
The same problem on the solaris node as well.
/Anders
> /Anders (mobile)
> Den 2 dec 2012 22:37 skrev "Dennis Lundberg" :
>
> On 2012-12-02 22:01, Anders Hammar wrote:
>> > It's the core-integration-t
The Windows node is one, but I believe I saw the same problem on some other
node as well.
/Anders (mobile)
Den 2 dec 2012 22:37 skrev "Dennis Lundberg" :
> On 2012-12-02 22:01, Anders Hammar wrote:
> > It's the core-integration-testing-maven-3 job that hangs. I've aborted
> it a
> > few times hop
On 2012-12-02 22:01, Anders Hammar wrote:
> It's the core-integration-testing-maven-3 job that hangs. I've aborted it a
> few times hoping it would fix itself somehow. No luck though.
>
> Also, there's some problems with Jenkins not finding git installation on
> some nodes. But that's a different
It's the core-integration-testing-maven-3 job that hangs. I've aborted it a
few times hoping it would fix itself somehow. No luck though.
Also, there's some problems with Jenkins not finding git installation on
some nodes. But that's a different topic, but possibly related to the
upgrade?
/Anders
Can we have a thread dump of that?
K
Den 2. des. 2012 kl. 21:39 skrev Dennis Lundberg :
> Hi Anders
>
> It looks like ASF Jenkins has been upgraded to 1.492, which should help
> us with the unwanted constant rebuilds in some of our other projects.
>
> Which jobs are hung?
> I can only see one: c
Hi Anders
It looks like ASF Jenkins has been upgraded to 1.492, which should help
us with the unwanted constant rebuilds in some of our other projects.
Which jobs are hung?
I can only see one: core-integration-testing-maven-3-embedded
On 2012-12-02 20:12, Anders Hammar wrote:
> The core-integrat
The core-integration-testing-maven-3 jobs has started to hang since
yesterday morning (whatever timezone the CI is showing). I have no clue how
to figure out why.
/Anders
27 matches
Mail list logo
