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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.3.CR1, 7.1.3.GA
    • 7.1.0.DR18
    • EJB, Naming
    • None
    • EAP 7.1.3

    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

      Attachments

        Issue Links

          Activity

            People

              jondruse@redhat.com Jiri Ondrusek
              rhn-support-bmaxwell Brad Maxwell
              Petr Adamec Petr Adamec
              Petr Adamec Petr Adamec
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: