[ 
https://wso2.org/jira/browse/WSAS-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Afkham Azeez resolved WSAS-733.
-------------------------------

    Resolution: Fixed

This is because the JAVA_HOME env variable has not been set when the init 
script starts to run. 

Please see the end of this article: http://wso2.org/library/2769

> Problem with JAVA_HOME when starting WSAS as a deamon 
> ------------------------------------------------------
>
>                 Key: WSAS-733
>                 URL: https://wso2.org/jira/browse/WSAS-733
>             Project: WSO2 WSAS
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 2.2
>         Environment: Ubuntu Jeos 7.10
> Java 1.5.0_update13
> VMware WorkStation 6.0.3
>            Reporter: Peter Brennan
>            Assignee: Afkham Azeez
>            Priority: Minor
>
> I've followed the install instructions to make WSAS available under Ubuntu 
> JeOS 7.10.. Starting and Stopping WSAS as a terminal user works fine. 
> However, when I try and start it as a service  ( using the instructions from 
> the FAQ ) it fails at startup with the following errors. 
> STATUS | wrapper  | 2008/03/23 19:31:35 | --> Wrapper Started as Daemon
> STATUS | wrapper  | 2008/03/23 19:31:35 | Launching a JVM...
> ERROR  | wrapper  | 2008/03/23 19:31:35 | Unable to start JVM: No such file 
> or directory (2)
> ERROR  | wrapper  | 2008/03/23 19:31:35 | Unable to start a JVM
> STATUS | wrapper  | 2008/03/23 19:31:35 | <-- Wrapper Stopped
> STATUS | wrapper  | 2008/03/23 20:54:57 | --> Wrapper Started as Daemon
> I've verified that the environment variables in /etc/profile an ~/.profile 
> are set correctly..   After some trial and error ( and looking at the ESB 
> configuration ) I isolated the problem to the wrapper.conf used for WSAS.
> Changing the following line in the wrapper.conf from :
> wrapper.java.command=%JAVA_HOME%/bin/java
> To
> wrapper.java.command=java
> resolves the service startup issue..   The change appears to have no impact 
> when running WSAS in non-service mode as well.
> Cheers
>   Peter

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

        

_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev

Reply via email to