Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-8360

[GSS](7.4.z) Escape Windows service.bat arguments

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.4.3.CR1, 7.4.3.GA
    • 7.0.3.GA, 7.1.0.DR10
    • Scripts
    • None
    • +
    • Workaround Exists
    • Hide

      Don't use # or ; in your username or password.
      In some scenarios escaping them with \ also helps.

      Show
      Don't use # or ; in your username or password. In some scenarios escaping them with \ also helps.
    • Hide
      1. Install EAP 7 on Windows Server using ZIP install.
      2. Create an admin user with the following credentials: Username: admin, password: 12#45
      3. As documented, download the jsvc download and setup a windows service with EAP_HOME/bin/service.bat, specifying the jboss user and password. e.g
        service.bat install /jbossuser admin /jbosspass 12#45 /loglevel info
      4. Start the service.
      5. Attempt to stop the service. The service will not stop.
      Show
      Install EAP 7 on Windows Server using ZIP install. Create an admin user with the following credentials: Username: admin , password: 12#45 As documented , download the jsvc download and setup a windows service with EAP_HOME/bin/service.bat, specifying the jboss user and password. e.g service.bat install /jbossuser admin /jbosspass 12#45 /loglevel info Start the service. Attempt to stop the service. The service will not stop.

      This was identified in Customer Case 01772273

      Using some special characters in a JBoss user's password (in this case a hash (#)), and then using that password to setup a windows service will result in the service not being able to stop. The service will start ok, but attempting to stop the service will not work.

      The # in the password is causing the issue. If a simpler password is used (e.g. abc12345), the service works ok.

      I haven't tried too many other special characters, but I assume that the problem is that the service script is not escaping some special characters properly...

              lvydra Lukas Vydra
              lcosti.redhat Lucas Costi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: