harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov (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 09:40:03 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-2135?page=comments#action_12452400 ] 
Alexey Varlamov commented on HARMONY-2135:

Unfortunately there is no specification per se on this stuff, only descriptive guides of how
this is done in RI (e.g. [1]).
I doubt there is something wrong with other impls, this is an application misbehaviour in
my POV. That is, if you'd forced overriden "java.home" via cmd-line, other Java impls should
fail as well (I didn't tried this though). Seems that in other implementation j.s.Security
class has better chance to be initialized earlier than "java.home" is changed, so the difference.

[1] http://java.sun.com/j2se/1.5.0/docs/guide/security/PolicyFiles.html

> 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
>            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