[jira] Commented: (KARAF-230) 2.1.0 Wrapper doesn't work and if hacked no SSH

["Achim Nierbeck (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927828#action_12927828 ] 

Achim Nierbeck commented on KARAF-230:
--------------------------------------

On a Ubuntu machine I had a similar problem. 
If there is an external configuration for JAVA_HOME it will not be overwritten by the configuration within the wrapper configuration. 
Might this be the issue here?

> 2.1.0 Wrapper doesn't work and if hacked no SSH
> -----------------------------------------------
>
>                 Key: KARAF-230
>                 URL: https://issues.apache.org/jira/browse/KARAF-230
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>         Environment: Ubuntu x86_64
>            Reporter: Caspar MacRae
>             Fix For: 2.1.1, 2.2.0
>
>
> I had the same issue in 2.0.0.
> wget http://www.mirrorservice.org/sites/ftp.apache.org//karaf/2.1.0/apache-karaf-2.1.0.tar.gz
> tar -xvzf apache-karaf-2.1.0.tar.gz 
> cd apache-karaf-2.1.0/
> JAVA_HOME=/usr/lib/jvm/java-6-sun/ && export JAVA_HOME
> ./bin/karaf 
> karaf> features:install wrapper
> karaf> wrapper:install 
> karaf> shutdown
> ./bin/karaf-service start    ## Note, no variation of paths works
> Error message:  "542: /srv/gather/karaf/bin/karaf-wrapper: not found"
> The workaround isn't hard (download and replace relevant files from http://wrapper.tanukisoftware.com), but it is a somewhat pointless endeavour as I cannot then access it via SSH (but can access via SSH when just running the bin/karaf script)
> I followed these links for adding and bootstapping bouncycastle:
> http://fusesource.com/forums/thread.jspa?messageID=7395
> http://felix.apache.org/site/65-deploying-security-providers.html
> But still no joy wrt wrapper and SSH.
> I'm using the karaf instance as an ActiveMQ (blueprint) broker host, with camel-quartz and it is setup with a failover instance using simple file lock (all working fine without exception)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.