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

(7.0.z) Use JBOSS_NAME variable in the JBOSS_LOCKFILE in the init script for RHEL

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 7.0.6.CR1, 7.0.6.GA
    • None
    • Scripts
    • None
    • EAP 7.0.6

    Description

      This enhancement is a follow up on JBEAP-3444 - having something like :

      JBOSS_LOCKFILE=/var/lock/subsys/${JBOSS_NAME}

      will make setting up several services on one host a tidbit more easier.

      Attachments

        Issue Links

          clones

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-7461 (7.1.x) Use JBOSS_NAME variable in the JBOSS_LOCKFILE in the init script for RHEL

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-8461 [GSS](7.0.z) Upgrade WildFly Core from 2.1.13 to 2.1.14

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3444 (7.0.z) Use script name for file related to Wildfly to allow multiple instances easily

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Activity

            People

              rpelisse@redhat.com Romain Pelisse
              rpelisse@redhat.com Romain Pelisse
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 4 hours
                  4h
                  Remaining:
                  Remaining Estimate - 4 hours
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified