[ 
https://issues.apache.org/jira/browse/IGNITE-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Korotkov updated IGNITE-18014:
-------------------------------------
    Description: 
In ducktest the {{jcmd}} utility is used to get list of the active java 
processes to check 
if the ignite-aware service is started and for service stop as well.

If the {{-XX:+PerfDisableSharedMem}} JVM option is used for java application 
the {{jps}} and 
{{jcmd}} utilities do not work for it - the corresponding process is not 
visible for them. 

To work around the problem the alternative approach may be used. Say use the 
{{pgrep -ax java}} instead of {{jcms}} to get list of pids of java processes.

  was:
In ducktest the `jcmd` utility is used to get list of the active java processes 
to check 
if the ignite-aware service is started and for service stop as well.

If the -XX:+PerfDisableSharedMem JVM options is used for java application the 
`jps` and 
`jcmd` utilities do not work for it - the corresponding process is not visible 
for them.  

To work around the problem the alternative approach may be used. Say use the 
`pgrep -ax java` instead of 'jcms' to get list of pids of java processes.




> [ducktests] Allow run tests with the -XX:+PerfDisableSharedMem JVM option
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-18014
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18014
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Sergey Korotkov
>            Assignee: Sergey Korotkov
>            Priority: Trivial
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In ducktest the {{jcmd}} utility is used to get list of the active java 
> processes to check 
> if the ignite-aware service is started and for service stop as well.
> If the {{-XX:+PerfDisableSharedMem}} JVM option is used for java application 
> the {{jps}} and 
> {{jcmd}} utilities do not work for it - the corresponding process is not 
> visible for them. 
> To work around the problem the alternative approach may be used. Say use the 
> {{pgrep -ax java}} instead of {{jcms}} to get list of pids of java processes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to