[ https://issues.apache.org/jira/browse/CLOUDSTACK-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009513#comment-14009513 ]
ASF subversion and git services commented on CLOUDSTACK-6328: ------------------------------------------------------------- Commit c535b894840e1a625186f7c62796e80950293221 in cloudstack's branch refs/heads/4.4-forward from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c535b89 ] CLOUDSTACK-6328: added license header and removed white space > 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 > > 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.2#6252)