[
http://issues.apache.org/jira/browse/GERONIMO-2532?page=comments#action_12445611
]
Kevan Miller commented on GERONIMO-2532:
----------------------------------------
Either 1) your JAVA_HOME/JRE_HOME is incorrect, or 2) the layout of your JRE is
not matching the expectations of geronimo.sh. Can you let us know if you're
setting JAVA_HOME or JRE_HOME and the contents of either $JRE_HOME/lib/ext or
$JAVA_HOME/jre/iib/ext or $JAVA_HOME/lib/ext (I think those are the possible
permutations).
I ran into this problem because my $JRE_HOME/bin directory contained a symbolic
link to the java executable. $JRE_HOME/lib/ext did not exist... Setting
JRE_HOME properly fixes my problem...
The reason why the exception is occurring is that an implementation of HmacSHA1
can not be loaded. The failure to load HmacSHA1 is the root cause of the
problem. You aren't seeing this because an exception is being caught. The
exception processing is calling assert. However, assertions are not enabled. We
should consider adding -enableassertions to geronimo.sh. If you "export
JAVA_OPTS=-enableassertions" before running geronimo.sh, you should see the
actual problem...
Hmm. Actually, this is not a great use of "assert"... from
org.apache.geronimo.security.ContextManager
public static void setAlgorithm(String algorithm) {
...
try {
Mac mac = Mac.getInstance(algorithm);
mac.init(key);
} catch (NoSuchAlgorithmException e) {
assert false : "Should never have reached here";
} catch (InvalidKeyException e) {
assert false : "Should never have reached here";
}
}
> Unable to start the server using the startup scripts
> ----------------------------------------------------
>
> Key: GERONIMO-2532
> URL: http://issues.apache.org/jira/browse/GERONIMO-2532
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: startup/shutdown
> Affects Versions: 1.2
> Environment: Linux an MacOS
> Reporter: Jay D. McHugh
>
> If you try to start the server using the startup scripts, then the server
> gets to the webconsole startup and fails on an NPE error.
> I have tried to track down what is going on and it seems that something about
> the "extended dirs" lines in the startup script causes the problem.
> If I remove those lines, then I am able to start the server successfully.
--
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
