You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2008/11/07 14:54:46 UTC

[jira] Reopened: (QPID-961) qpid.stopall script no longer runs correctly under Solaris

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

Marnie McCormack reopened QPID-961:
-----------------------------------

      Assignee: Marnie McCormack  (was: Rob Godfrey)

Not force quitting processes thus re-opened

> qpid.stopall script no longer runs correctly under Solaris
> ----------------------------------------------------------
>
>                 Key: QPID-961
>                 URL: https://issues.apache.org/jira/browse/QPID-961
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M2.1
>            Reporter: Martin Ritchie
>            Assignee: Marnie McCormack
>             Fix For: M4
>
>         Attachments: qpid-run.patch, qpid_scripts.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Summary:
> The problem we have is this command line:
> pids=`ps -ef |grep $USER | grep $PROGRAM | grep -v grep | awk '{print $2}'`
> Which now as a result in adding XX values to our startup script shows:
> ritchiem 10188  7608  0 14:44:40 pts/34   0:08 java -server -XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m 
> Which doesn't exactly allow us to identify it as Qpid.
> We should if possible move the -DQPID_HOME option to be at the start or there may be a better set of options to ps for Solaris.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.