Hi Chris,
I have tested the scenario according to your information and still couldn't
reproduce the issue. I could run wso2server as a background process over
ssh with command;
vagrant ssh -c './wso2carbon-4.2.0/bin/wso2server.sh start'
I can access management console if I ssh vagrant guest
Hi Nipuni,
AFAIK sever process will not terminate once you terminate the ssh
process . You have to kill the server process manually. User ps -ef|grep
carbon to identity the process id and kill it using kill -9 id command.
Thanks
Isura
On Sat, Jul 19, 2014 at 10:10 AM, Nipuni Perera
According to the JIRA, you should use -c not -E , did you test with that
option as well? , BTW wso2servers.sh is working fine with nohup not sure
about stratos.sh . you can update JIRA with your finding.
@Isura , For that you need to start the server as background process , if
not server process
Hi,
I have tried -c option and followed the jira first and got following
results. According to[1] -c option defines the cipher type.
- When running wso2server without -E option I got the following error,
Error: JAVA_HOME is not defined correctly.
CARBON cannot execute java
- When
Hi Nipuni, I've updated the JIRA ticket with some more information...
On Sat, Jul 19, 2014 at 10:28 AM, Nipuni Perera nip...@wso2.com wrote:
Hi,
I have tried -c option and followed the jira first and got following
results. According to[1] -c option defines the cipher type.
When running
Hi,
I am working on jira issue[1]. I have tested this with a remote BAM server
and couldn't reproduce the issue. If wso2server.sh has been executed over
ssh as a nohup process, server does not stop after ssh process terminates.
I have followed the steps below:
1. start ssh and connect to
