Good news. I fully updated my Ubuntu box, and it subsequently did a completely clean

I just need to do the signature checks, and I'll be ready to vote in favor of River 3.0.

On 09/17/2016 09:57 PM, Peter wrote:
Looks like a problem with the IcedTea jdk when retrieving the 
AccessControlContext.  River appears to have handled the socket closure 

The stress test doesn't stress River much, it uses TaskManager which causes 
contention within  the test code.  TaskManager is only retained for backward 
compatibility and some tests that still use it.

Perhaps try installing Oracle's jdk.

Alternatively, there's a file here:

qa/src/org/apache/river/test/resources (I think from memory).  It called 
qa_defaults (I think again from memory).  Will confirm later.

In this file, you can enable core dumps, then a back trace might reveal the 
actual problem.

Thanks & regards,


Sent from my Samsung device.
Include original message
---- Original message ----
From: Patricia Shanahan <>
Sent: 18/09/2016 08:47:43 am
Subject: QA test failure River 3.0

Is this an actual problem with River 3.0, or just an indication that my
Linux box is not tough enough for this stress test?

       [java] Running
       [java] Time is Sat Sep 17 12:36:29 PDT 2016
       [java] Starting test in separate process with command:
       [java] /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
http://pats-acer1:9082/qa1-share-dl.jar' -cp
-ea -esa

       [java] TIME: 12:36:30 PM
       [java] MasterTest.doTest INFO:
       [java] ============================== CALLING CONSTRUCT()
       [java] MasterTest.doTest INFO:
       [java] =============================== CALLING RUN()
       [java] NonActGrp-out: #
       [java] NonActGrp-out: # A fatal error has been detected by the
Java Runtime Environment:
       [java] NonActGrp-out: #
       [java] NonActGrp-out: #  SIGSEGV (0xb) at pc=0x00007f6f16b24fdc,
pid=934, tid=140113942001408
       [java] NonActGrp-out: #
       [java] NonActGrp-out: # JRE version: OpenJDK Runtime Environment
(7.0_95) (build 1.7.0_95-b00)
       [java] NonActGrp-out: # Java VM: OpenJDK 64-Bit Server VM
(24.95-b01 mixed mode linux-amd64 compressed oops)
       [java] NonActGrp-out: # Derivative: IcedTea 2.6.4
       [java] NonActGrp-out: # Distribution: Ubuntu 14.04.3 LTS, package
       [java] NonActGrp-out: # Problematic frame:
       [java] NonActGrp-out: # V  []
       [java] NonActGrp-out: #
       [java] NonActGrp-out: # Failed to write core dump. Core dumps have
been disabled. To enable core dumping, try "ulimit -c unlimited" before
starting Java again
       [java] NonActGrp-out: #
       [java] NonActGrp-out: # An error report file with more information
is saved as:
       [java] NonActGrp-out: #
       [java] NonActGrp-out: [thread 140113841469184 also had an error]
       [java] NonActGrp-out: Compiled method (nm)  128380  486 n (native)
       [java] NonActGrp-out:  total in heap
[0x00007f6f0d12c810,0x00007f6f0d12cb98] = 904
       [java] NonActGrp-out:  relocation
[0x00007f6f0d12c930,0x00007f6f0d12c990] = 96
       [java] NonActGrp-out:  main code
[0x00007f6f0d12c9a0,0x00007f6f0d12cb98] = 504
       [java] NonActGrp-out: #
       [java] NonActGrp-out: # If you would like to submit a bug report,
please include
       [java] NonActGrp-out: # instructions on how to reproduce the bug
and visit:
       [java] NonActGrp-out: #
       [java] NonActGrp-out: #
       [java] java.rmi.UnmarshalException: exception unmarshalling
response; nested exception is:
       [java] I/O error reading from mux
connection: java.netSocketException: Connection reset
       [java]     at

Reply via email to