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

Restore JBEAP-2830 fix

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Blocker
    • 7.1.0.DR6
    • 7.1.0.DR5
    • Logging
    • None

    Description

      The initial fix for JBEAP-2830 included a change to wildfly-core-eap that was never forward ported to upstream. As a result when work on 7.1 required moving to the latest releases of WildFly Core, the necessary bits were not available and the full EAP part of the change needed to be reverted.[1]

      This task is to restore the EAP full behavior once a core release with WFCORE-1658 in it is integrated.

      [1] https://github.com/jbossas/jboss-eap7/commit/50f32c651bae00b183424d51762a646d08ebbf51

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-6155 CLI script fails to set up EAP properly in messaging-clustering quickstart

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1658 JBEAP-2830 enhancements were not forward ported to upstream

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-5310 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha4

          • 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 duplicated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5412 standalone-full-ha profile has enabled logging to console by default

          • 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-2830 Disable console logging for standalone-full-ha.xml

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              dtikhomi@redhat.com Dmitrii Tikhomirov
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: