[
https://issues.apache.org/jira/browse/KARAF-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424527#comment-13424527
]
Hendy Irawan commented on KARAF-1683:
-------------------------------------
Hmm... it only detects JDK, not JRE. I think this is better, detects JDK first,
then JRE as fallback :
{code}
if [ -x readlink ]; then
[ -z $JAVA_HOME ] && export JAVA_HOME="$(readlink -f /usr/bin/javac | sed
's:/bin/javac::')"
[ -z $JAVA_HOME ] && export JAVA_HOME="$(readlink -f /usr/bin/java | sed
's:/bin/java::')"
fi
{code}
Also added double quotes to make it safe in case the returned pathname has
fancy characters (exotic config?).
> "no matching cipher found" error connecting via SSH to wrapper Karaf service
> - on Ubuntu
> ----------------------------------------------------------------------------------------
>
> Key: KARAF-1683
> URL: https://issues.apache.org/jira/browse/KARAF-1683
> Project: Karaf
> Issue Type: Bug
> Components: karaf-os-integration
> Affects Versions: 2.2.8, 2.3.0
> Environment: Ubuntu 12.04 64-bit. OpenJDK 7
> Reporter: Hendy Irawan
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.9, 2.3.0, 3.0.0
>
>
> When wrapper is used to install service in Ubuntu 12.04 (or any Ubuntu for
> that matter, probably Debian too), SSH is not possible.
> {code}
> no matching cipher found: client
> aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected]
> server
> {code}
> The reason is Debian doesn't set JAVA_HOME due to policy
> (https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/364794)
> Workaround is to put this in the bin/<name>-service script :
> {code}
> export JAVA_HOME=$(readlink -f /usr/bin/javac | sed "s:/bin/javac::")
> {code}
> It should be default, or probably like this :
> {code}
> [ -z $JAVA_HOME ] && export JAVA_HOME=$(readlink -f /usr/bin/javac | sed
> "s:/bin/javac::")
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
