harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Ellison (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-2135) DaCapo eclipse fails with java.security.NoSuchAlgorithmException for an algorithm known to exist
Date Fri, 24 Nov 2006 12:30:09 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-2135?page=comments#action_12452435 ] 
Tim Ellison commented on HARMONY-2135:

I believe that this will be fixed by HARMONY-2163 resolution in repository revision r478857.

Please see if that fix resolves this problem for you.

> DaCapo eclipse fails with java.security.NoSuchAlgorithmException for an algorithm known
to exist
> ------------------------------------------------------------------------------------------------
>                 Key: HARMONY-2135
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2135
>             Project: Harmony
>          Issue Type: Bug
>          Components: App-Oriented Bug Reports
>         Environment: Linux
>            Reporter: Robin Garner
>         Assigned To: Tim Ellison
>            Priority: Minor
> The DaCapo benchmark suite relies heavily on SHA-1 digests of log files to validate its
output.  This code works for all benchmarks that work on drlvm, except eclipse.  Eclipse fails
> java.security.NoSuchAlgorithmException: MessageDigest SHA-1 implementation not found
>         at org.apache.harmony.security.fortress.Engine.getInstance(Engine.java:98)
>         at java.security.MessageDigest.getInstance(MessageDigest.java:68)
>         at dacapo.Digest.create(Digest.java:26)
>         at dacapo.FileDigest.getText(FileDigest.java:87)
>         at dacapo.FileDigest.get(FileDigest.java:43)
>         at dacapo.Benchmark.validate(Benchmark.java:250)
>         at dacapo.Benchmark.run(Benchmark.java:127)
>         at dacapo.TestHarness.runBenchmark(TestHarness.java:298)
>         at dacapo.TestHarness.main(TestHarness.java:239)
>         at Harness.main(Harness.java:7)
>         at java.lang.reflect.VMReflection.invokeMethod(Native Method)
>         at java.lang.reflect.Method.invoke(Unknown Source)
>         at org.apache.harmony.vm.JarRunner.main(Unknown Source)
> The error message is clearly bogus because other benchmarks happily find the same message
digest implementation.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message