Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-1998

Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly

XMLWordPrintable

    • Hide

      Run the test.sh which is a standalone module application.

      $ unzip nameserviceProviderTest.zip;
$ cd nameserviceProviderTest
$ JBOSS_HOME=~/java/wildfly-10.1.0.Final ./test.sh
17:53:58,131 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
*** MyNameService.lookupAllHostAddr called

      "*** MyNameService.lookupAllHostAddr called" is printed in stdout if the custom NameService has been enabled.

      On WildFly, define a system property in standalone.conf:

         JAVA_OPTS="$JAVA_OPTS -Dsun.net.spi.nameservice.provider.1=dns,MyNameService"

      And prepend the new module path in standalone.sh:

          JBOSS_MODULEPATH="/path/to/nameserviceProviderTest/modules:$JBOSS_HOME/modules"

      Then deploy the testweb.war in the archive and access http://localhost:8080/testweb/test.jsp. The message is not printed in stdout.

      Show
      Run the test.sh which is a standalone module application. $ unzip nameserviceProviderTest.zip; $ cd nameserviceProviderTest $ JBOSS_HOME=~/java/wildfly-10.1.0.Final ./test.sh 17:53:58,131 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final *** MyNameService.lookupAllHostAddr called " *** MyNameService.lookupAllHostAddr called " is printed in stdout if the custom NameService has been enabled. On WildFly, define a system property in standalone.conf: JAVA_OPTS= "$JAVA_OPTS -Dsun.net.spi.nameservice.provider.1=dns,MyNameService" And prepend the new module path in standalone.sh: JBOSS_MODULEPATH= "/path/to/nameserviceProviderTest/modules:$JBOSS_HOME/modules" Then deploy the testweb.war in the archive and access http://localhost:8080/testweb/test.jsp . The message is not printed in stdout.

      System property sun.net.spi.nameservice.provider.<n> allows a user to customize a NameService. It works on a standalone java, which is using JBoss Modules, if services="import" is added on sun.jdk module dependency and the sun.jdk module has the following additional dependencies.

                      <path name="sun/net/spi/nameservice"/>
                <path name="sun/net/spi/nameservice/dns"/>

      Though it doesn't work as a web application which has the same module path and the same dependency in jboss-deployment-structure.xml.

        1. nameserviceProviderTest.zip
          14 kB

              rhn-support-onagano Osamu Nagano
              rhn-support-onagano Osamu Nagano
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: