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

[GSS](7.1.z) use of WildFlyInitialContext with wildfly-config.xml throws javax.naming.NoInitialContextException

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.1.0.DR18
    • Fix Version/s: 7.1.3.CR1, 7.1.3.GA
    • Component/s: EJB, Naming
    • Labels:
      None
    • Environment:

      7.1.0.Beta and 7.1.0.ER2

      Description

      If a client use WildFlyInitialContext without properties the following Exception is thrown:
      Exception in thread "main" javax.naming.NoInitialContextException
      at org.wildfly.naming.client.WildFlyInitialContext.getDefaultInitCtx(WildFlyInitialContext.java:65)
      at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:350)
      at javax.naming.InitialContext.lookup(InitialContext.java:417)
      at org.jboss.wfink.eap71.playground.wildfly.client.WildFlyICConfigClient.main(WildFlyICConfigClient.java:33)

      It is expected that this works according to https://github.com/wildfly/wildfly-naming-client#usage.
      The reproducer can be found here
      https://github.com/wfink/jboss-eap7.1-playground/blob/master/clients/WildFlyConfig/src/main/java/org/jboss/wfink/eap71/playground/wildfly/client/WildFlyICConfigClient.java

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jondruse Jiri Ondrusek
                  Reporter:
                  bmaxwell Brad Maxwell
                  Tester:
                  Petr Adamec
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: