cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-6328) Prevent console proxy support scripts from spawning multiple java processes
Date Tue, 25 Nov 2014 19:05:13 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225021#comment-14225021
] 

ASF subversion and git services commented on CLOUDSTACK-6328:
-------------------------------------------------------------

Commit 650464eda05d9e392ef7f99a6e08a6576de41ce7 in cloudstack's branch refs/heads/4.3 from
[~saurav.lahiri]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=650464e ]

CLOUDSTACK-6328: run.sh check if an existing java process is running, before spawining new
ones

Signed-off-by: Jayapal <jayapal@apache.org>
(cherry picked from commit 96b1c6bf3cae3c03a872770ceb420c5daef21713)
Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>


> Prevent console proxy support scripts from spawning multiple java processes
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6328
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6328
>             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
>             Fix For: 4.4.0
>
>
> From the mail on dev list 
> ===========================================================
> Hi,
> The console proxy supporting scripts run.sh restarts the java process if it determines
that  for some reason the _run.sh 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 _run.sh 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
file
> is causing issues. A way to fix this could be to change the code in run.sh 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
logged
> for this.
> ====================================================



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message