Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3151

Failure to start jboss-cli.sh due to space in the startup path

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.1.0.CR1, 8.1.0.Final
    • None
    • None
    • None

    Description

      The CLI startup script needs to be modified to process arguments like standalone.sh and friends to, to be tolerant of spaces in the original arg list.

      Original report:

      Sent email to wildfly-dev:

      Java EE 7 CI job on WildFly trunk is failing:
      
      https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20WildFly-cb/155/console
      
      Here is the error message:
      
      Started 45 of 56 services (22 services are lazy, passive or on-demand)
       [0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect
      '--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)'
      Error: Could not find or load main class EE
      Process leaked file descriptors. See
      http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
      for more information
      Build step 'Execute shell' marked build as failure
      

      David responded:

      Looks like a possible regression in standalone.sh due to there being a
      space in the startup path.
      
      As a workaround you could change your workspace name from "Java EE 7
      Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or
      similar (with no spaces).
      

      Attachments

        Activity

          People

            jperkins-rhn James Perkins
            arungupta_jira Arun Gupta (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: