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

Failed to create security context for subsystem=naming/service=*

    XMLWordPrintable

Details

    • Hide

      1. Configuration tab -> Subsystems -> Naming - View
      2. Select service in the left orientation pane
      3. Select remote-naming in the Singleton Child Resources table
      4. Click Remove button
      5. Click service -> * in the left orientation pane

      Show
      1. Configuration tab -> Subsystems -> Naming - View 2. Select service in the left orientation pane 3. Select remote-naming in the Singleton Child Resources table 4. Click Remove button 5. Click service -> * in the left orientation pane

    Description

      After removing the remote-naming service in naming subsystem, a service -> * will appear in the left orientation pane. After clicking it, the following error message is produced:

      Failed to create security context for subsystem=naming/service=*

Unexpected response format at address: subsystem=naming/service=*

      Is there any point to showing the service -> * in the left orientation pane? It seems rather pointless and confusing at this point.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. HAL-1180 Failed to create security context for subsystem=naming/service=*

          • 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.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-6032 (7.1.0) Upgrade HAL to 2.9.0.Alpha2

          • 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

          Activity

            People

              mpetrov@redhat.com Michal Petrov
              mjurc@redhat.com Michal Jurc
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2 hours Original Estimate - 2 hours
                  2h
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h