cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6328) Prevent console proxy support scripts from spawning multiple java processes
Date Tue, 27 May 2014 09:29:01 GMT


ASF subversion and git services commented on CLOUDSTACK-6328:

Commit c83e90b008900bc15ed5fe6309e49dfaff92f0a8 in cloudstack's branch refs/heads/4.4 from
[;h=c83e90b ]

CLOUDSTACK-6328: added license header and removed white space

> Prevent console proxy support scripts from spawning multiple java processes
> ---------------------------------------------------------------------------
>                 Key: CLOUDSTACK-6328
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: SystemVM
>    Affects Versions: 4.3.0
>            Reporter: Saurav Lahiri
>            Assignee: Saurav Lahiri
> From the mail on dev list 
> ===========================================================
> Hi,
> The console proxy supporting scripts restarts the java process if it determines
that  for some reason the has exited. If the original java process has exited then
that is not an issue. If for some reason the java process is still running, then the while
loop which calls will cause a second instance of a jvm to start, which refers to the
same log file namely cloud.out. It appears that two different jvms referring to the same log
> is causing issues. A way to fix this could be to change the code in to use the
get_pids routine to check  and preempt start of a new java process if an existing process
is running.
> Please let me know if I have read the situation correctly and if a defect needs to be
> for this.
> ====================================================

This message was sent by Atlassian JIRA

View raw message