Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-28402

ShellExecutor must be able to trace the executed command

    XMLWordPrintable

    Details

      Description

      The org.nuxeo.ecm.platform.commandline.executor.service.executors.ShellExecutor is used for all convertion and more.
      Today we can have the template command used by activating the debug log:

          <Logger name="org.nuxeo.ecm.platform.commandline.executor.service.executors" level="debug" />
      

      This trace thing like:

      ... Running system command: convert -define registry:temporary-path=#{nuxeo.tmp.dir} -quiet -strip -thumbnail #{size} -background transparent -gravity center -format png -quality 75 #{inputFilePath}[0] #{outputFilePath}
      

      Which is not very interesting in case of hang processing, because a thread dump could give you the code path and the contribution with the same information:

         <command name="resizer" enabled="true">
            <commandLine>convert</commandLine>
            <parameterString>-define registry:temporary-path=#{nuxeo.tmp.dir} -quiet -depth #{targetDepth} #{inputFilePath}[0] jpg:- | convert - -resize #{targetWidth}x#{targetHeight} #{outputFilePath}</parameterString> ...
      

      What is needed is the exact executed command.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              bdelbosc Benoit Delbosc
              Participants:
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.