Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5459

Fix java:/jaas not bound during services startup

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.1
    • EAP_EWP 5.1.0
    • Security
    • None
    • Hide
      Due to an error in the order of services starting up, JNDIContextEstablishment could potentially start later than expected, causing NamingExceptions because the context java:/jaas was not bound in JNDI. This binding is now handled in JaasSecurityManagerService, which starts before any service in the <code>deploy/</code> directory.
      Show
      Due to an error in the order of services starting up, JNDIContextEstablishment could potentially start later than expected, causing NamingExceptions because the context java:/jaas was not bound in JNDI. This binding is now handled in JaasSecurityManagerService, which starts before any service in the <code>deploy/</code> directory.
    • Documented as Resolved Issue

    Description

      Due to the order of services starting up, JNDIContextEstablishment may start later than expected thus causing NamingExceptions because the context jaas is not bound in JNDI.

      Attachments

        Activity

          People

            mmoyses Marcus Moyses (Inactive)
            mmoyses Marcus Moyses (Inactive)
            Misty Stanley-Jones Misty Stanley-Jones (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: