[kepler-dev] [Bug 5582] New: DataTurbine server crashing the JRE

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Wed Mar 28 20:19:05 PDT 2012


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5582

             Bug #: 5582
           Summary: DataTurbine server crashing the JRE
    Classification: Unclassified
           Product: Kepler
           Version: trunk
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sensor-view
        AssignedTo: barseghian at nceas.ucsb.edu
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


I don't think this is a Kepler bug but I want to record my notes somewhere:

I was able to get the DataTurbine server to crash the JRE around 10 times
today. Sometimes the JRE would leave a log file, I submitted one to Sun. I was
using DT 3.2b5 but moved to 3.2b6, but this didn't seem to help. Likewise I
moved the client (Kepler DT actor) from 3.2b5 to 3.2b6, to no avail. I was able
to crash the server using both Ubuntu w/ java 1.6.0_26-b03 and osX 10.6 w/ java
1.6.0_29-b11-402-10M3527. I'm in the process of doing some cleanup on the DT
actor, but I verified these crashes would occur with none of the new changes.
Generally the procedure was I'd run the growingDegreeDays workflow requesting 1
day of data. After about 6-10 iterations of this workflow in succession the
server would crash.

This hasn't been well vetted but what seems to have "fixed" it is starting the
server with a larger archiveSize -- I bumped from 500000 to 1000000. Recently I
loaded a lot more data to the reap02 channels, so perhaps that's why this has
only recently cropped up. I've now run the GDD workflow requesting *100* days
of data 10 times, and no crash w/ the 3.2b6 DT server on my mac. I'm going to
run a long stress test over night and see what happens.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.


More information about the Kepler-dev mailing list