9 Replies Latest reply on Nov 7, 2014 10:16 AM by Justin Bertram

    Wildfly 8.1 - configure and try remoting JNDI lookup

    Andrea Fantappiè Newbie

      I'm trying to make a remote lookup to the jms connection factory as explained here:

       

      http://www.mastertheboss.com/jboss-server/jboss-jms/how-to-code-a-remote-jms-client-for-wildfly-8

       

      and here:

       

      Remote EJB invocations via JNDI - EJB client API or remote-naming project - WildFly 8 - Project Documentation Editor

       

      my code is exactly the same as the one on the first link.

       

      I've startup Wildfly with the default standalone-full configuration after added the ApplicationRealm user but at first lookup line (jms/RemoteConnectionFactory) I've got this exception:

       

      Exception in thread "main" javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [http-remoting://localhost:8080 (Operation failed with status WAITING after 5000 MILLISECONDS)] [Root exception is java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS]

        at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:240)

        at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)

        at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)

        at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)

        at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)

        at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)

        at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)

        at javax.naming.InitialContext.lookup(InitialContext.java:417)

        at it.infogroup.remote.Test.main(Test.java:48)

      Caused by: java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS

        at org.jboss.naming.remote.protocol.IoFutureHelper.get(IoFutureHelper.java:97)

        at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:198)

        ... 8 more

       

      I'm assuming that the code is correct, verified a lot of time and tried different users, but always same error, so I think I miss some config on server side, someone can help me?

        • 1. Re: Wildfly 8.1 - configure and try remoting JNDI lookup
          Justin Bertram Master

          Can you attach:

          • The log from the server including the server start-up process.
          • The server config.
          • The client code.
          • 2. Re: Wildfly 8.1 - configure and try remoting JNDI lookup
            Wolf-Dieter Fink Master

            Maybe this quickstart helps quickstart/ejb-multi-server see the app-main application.

            1 of 1 people found this helpful
            • 3. Re: Wildfly 8.1 - configure and try remoting JNDI lookup
              Andrea Fantappiè Newbie

              The config is the default standalone-full, the code is the one posted on first link, here the log:

               

              2014-11-05 16:55:06,850 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
              2014-11-05 16:55:07,240 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
              2014-11-05 16:55:07,365 INFO  [org.jboss.as] (MSC service thread 1-3) JBAS015899: WildFly 8.1.0.Final "Kenny" starting
              2014-11-05 16:55:07,381 DEBUG [org.jboss.as.config] (MSC service thread 1-3) Configured system properties:
                awt.toolkit = sun.awt.windows.WToolkit
                file.encoding = Cp1252
                file.encoding.pkg = sun.io
                file.separator = \
                java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
                java.awt.printerjob = sun.awt.windows.WPrinterJob
                java.class.path = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\jboss-modules.jar
                java.class.version = 52.0
                java.endorsed.dirs = C:\Sviluppo\Java\jdk1.8.0_05\jre\lib\endorsed
                java.ext.dirs = C:\Sviluppo\Java\jdk1.8.0_05\jre\lib\ext;C:\Windows\Sun\Java\lib\ext
                java.home = C:\Sviluppo\Java\jdk1.8.0_05\jre
                java.io.tmpdir = C:\Users\IG07988\AppData\Local\Temp\
                java.library.path = C:\Sviluppo\Java\jdk1.8.0_05\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;E:\Sviluppo\Java\sonar-runner-2.3\bin;C:\Program Files (x86)\Inno Setup 5;E:\app\ORAUSER\product\12.1.0\dbhome_1\bin;E:\app\Oracle\product\12.1.0\dbhome_1\bin;c:\Program Files (x86)\AMD APP\bin\x86_64;c:\Program Files (x86)\AMD APP\bin\x86;C:\app\prova\product\11.1.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\OpenVPN\bin;C:\Program Files (x86)\Bitvise SSH Client;C:\Program Files\nodejs\;E:\Sviluppo\Java\Libraries\apache-ant-1.9.2\bin;C:\Program Files\TortoiseSVN\bin;DERBY_HOME\bin;C:\Sviluppo\Java\jdk1.8.0_05\bin;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Users\IG07988\AppData\Roaming\npm;C:\Program Files\Apache Software Foundation\apache-maven-3.2.3\bin;C:\Program Files (x86)\Inno Setup 5;C:\Program Files\Apache Software Foundation\Apache-Subversion-1.8.9\bin;.
                java.net.preferIPv4Stack = true
                java.runtime.name = Java(TM) SE Runtime Environment
                java.runtime.version = 1.8.0_05-b13
                java.specification.name = Java Platform API Specification
                java.specification.vendor = Oracle Corporation
                java.specification.version = 1.8
                java.util.logging.manager = org.jboss.logmanager.LogManager
                java.vendor = Oracle Corporation
                java.vendor.url = http://java.oracle.com/
                java.vendor.url.bug = http://bugreport.sun.com/bugreport/
                java.version = 1.8.0_05
                java.vm.info = mixed mode
                java.vm.name = Java HotSpot(TM) 64-Bit Server VM
                java.vm.specification.name = Java Virtual Machine Specification
                java.vm.specification.vendor = Oracle Corporation
                java.vm.specification.version = 1.8
                java.vm.vendor = Oracle Corporation
                java.vm.version = 25.5-b02
                javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
                javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
                javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
                javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
                javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
                javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
                javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
                javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
                javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
                javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
                jboss.home.dir = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final
                jboss.host.name = d01319
                jboss.modules.dir = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\modules
                jboss.modules.system.pkgs = org.jboss.byteman
                jboss.node.name = d01319
                jboss.qualified.host.name = d01319
                jboss.server.base.dir = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone
                jboss.server.config.dir = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\configuration
                jboss.server.data.dir = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\data
                jboss.server.deploy.dir = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\data\content
                jboss.server.log.dir = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\log
                jboss.server.name = d01319
                jboss.server.persist.config = true
                jboss.server.temp.dir = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\tmp
                line.separator =

              logging.configuration = file:E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\configuration/logging.properties
                module.path = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\modules
                org.jboss.boot.log.file = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\log\server.log
                org.jboss.resolver.warning = true
                org.xml.sax.driver = __redirected.__XMLReaderFactory
                os.arch = amd64
                os.name = Windows 7
                os.version = 6.
              1

                path.separator = ;

                program.name = standalone.bat

                sun.arch.data.model = 64

                sun.boot.class.path = C:\Sviluppo\Java\jdk1.8.0_05\

              jre\lib\resources.jar;C:\Sviluppo\Java\jdk1.8.0_05\jre\lib\rt.jar;C:\Sviluppo\Java\jdk1.8.0_05\jre\lib\sunrsasign.jar;C:\Sviluppo\Java\jdk1.8.0_05\jre\lib\jsse.jar;C:\Sviluppo\Java\jdk1.8.0_05\jre\lib\jce.jar;C:\Sviluppo\Java\jdk1.8.0_05\jre\lib\charsets.jar;C:\Sviluppo\Java\jdk1.8.0_05\jre\lib\jfr.jar;C:\Sviluppo\Java\jdk1.8.0_05\jre\classes
                sun.boot.library.path = C:\Sviluppo\Java\jdk1.8.0_05\jre\bin
                sun.cpu.endian = little
                sun.cpu.isalist = amd64
                sun.desktop = windows
                sun.io.unicode.encoding = UnicodeLittle
                sun.java.command = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\jboss-modules.jar -mp E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final --server-config=standalone-full.xml
                sun.java.launcher = SUN_STANDARD
                sun.jnu.encoding = Cp1252
                sun.management.compiler = HotSpot 64-Bit Tiered Compilers
                sun.os.patch.level = Service Pack 1
                sun.stderr.encoding = cp850
                sun.stdout.encoding = cp850
                user.country = IT
                user.dir = E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\bin
                user.home = C:\Users\IG07988
                user.language = it
                user.name = IG07988
                user.script =
                user.timezone = Europe/Berlin
                user.variant =
              2014-11-05 16:55:07,381 DEBUG [org.jboss.as.config] (MSC service thread 1-3) VM Arguments: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.boot.log.file=E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\log\server.log -Dlogging.configuration=file:E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\configuration/logging.properties
              2014-11-05 16:55:10,750 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
              2014-11-05 16:55:10,797 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.2.2.Final
              2014-11-05 16:55:10,828 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.2.2.Final
              2014-11-05 16:55:11,015 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.
              2014-11-05 16:55:10,969 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 51) JBAS013171: Activating Security Subsystem
              2014-11-05 16:55:11,156 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017502: Undertow 1.0.15.Final starting
              2014-11-05 16:55:11,234 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017502: Undertow 1.0.15.Final starting
              2014-11-05 16:55:11,249 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 34) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
              2014-11-05 16:55:11,296 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 42) JBAS012615: Activated the following JSF Implementations: [main]
              2014-11-05 16:55:11,312 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 46) JBAS011800: Activating Naming Subsystem
              2014-11-05 16:55:11,327 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 52) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
              2014-11-05 16:55:11,327 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension
              2014-11-05 16:55:11,468 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017527: Creating file handler for path E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final/welcome-content
              2014-11-05 16:55:11,483 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem
              2014-11-05 16:55:11,515 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.3.Final
              2014-11-05 16:55:11,764 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
              2014-11-05 16:55:11,889 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.5.Final)
              2014-11-05 16:55:11,889 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
              2014-11-05 16:55:12,217 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
              2014-11-05 16:55:12,451 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.21.Beta1
              2014-11-05 16:55:12,607 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = h2
              2014-11-05 16:55:12,669 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server default-server.
              2014-11-05 16:55:12,685 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting
              2014-11-05 16:55:12,825 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\deployments
              2014-11-05 16:55:13,199 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
              2014-11-05 16:55:13,496 WARN  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
              2014-11-05 16:55:13,589 WARN  [jacorb.codeset] (MSC service thread 1-2) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1
              2014-11-05 16:55:13,792 INFO  [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started
              2014-11-05 16:55:13,870 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\data\messagingjournal,bindingsDirectory=E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\data\messagingbindings,largeMessagesDirectory=E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\data\messaginglargemessages,pagingDirectory=E:\Sviluppo\Workspaces\servers\jboss\wildfly-8.1.0.Final\standalone\data\messagingpaging)
              2014-11-05 16:55:13,886 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221006: Waiting to obtain live lock
              2014-11-05 16:55:14,011 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
              2014-11-05 16:55:14,104 INFO  [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.4.Final
              2014-11-05 16:55:14,120 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221013: Using NIO Journal
              2014-11-05 16:55:14,182 INFO  [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 56) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
              2014-11-05 16:55:14,245 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support CORE
              2014-11-05 16:55:14,338 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support AMQP
              2014-11-05 16:55:14,338 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016328: CORBA Naming Service started
              2014-11-05 16:55:14,354 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support STOMP
              2014-11-05 16:55:14,480 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221034: Waiting to obtain live lock
              2014-11-05 16:55:14,480 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221035: Live Server Obtained live lock
              2014-11-05 16:55:14,807 INFO  [org.jboss.messaging] (MSC service thread 1-4) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor
              2014-11-05 16:55:14,807 INFO  [org.jboss.messaging] (MSC service thread 1-3) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor
              2014-11-05 16:55:14,948 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live
              2014-11-05 16:55:14,948 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [04bb3920-162f-11e4-911f-5f98ecf7b64d]
              2014-11-05 16:55:14,979 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
              2014-11-05 16:55:14,994 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 59) HQ221003: trying to deploy queue jms.queue.ExpiryQueue
              2014-11-05 16:55:15,010 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue
              2014-11-05 16:55:15,026 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 57) HQ221003: trying to deploy queue jms.queue.DLQ
              2014-11-05 16:55:15,026 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ
              2014-11-05 16:55:15,041 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
              2014-11-05 16:55:15,088 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) JBAS010406: Registered connection factory java:/JmsXA
              2014-11-05 16:55:15,150 INFO  [org.hornetq.ra] (MSC service thread 1-3) HornetQ resource adaptor started
              2014-11-05 16:55:15,150 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatorhornetq-ra
              2014-11-05 16:55:15,150 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
              2014-11-05 16:55:15,150 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
              2014-11-05 16:55:15,306 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
              2014-11-05 16:55:15,322 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
              2014-11-05 16:55:15,322 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final "Kenny" started in 8924ms - Started 218 of 266 services (92 services are lazy, passive or on-demand)

              • 4. Re: Wildfly 8.1 - configure and try remoting JNDI lookup
                Justin Bertram Master

                My only thought here is that either you aren't running the client on the same machine as the server (which means that "localhost" won't work) or that you don't have an alias for "localhost" that resolves it to 127.0.0.1.

                • 5. Re: Wildfly 8.1 - configure and try remoting JNDI lookup
                  Andrea Fantappiè Newbie

                  I'm running all on same develop machine, localhost resolve correctly on all other java code.

                   

                  I've also tried the github quickstart at quickstart/helloworld-jms at master · wildfly/quickstart · GitHub but same issue...

                   

                  Note: I'm currently using the wildfly-maven-plugin to deploy my apps, and it use the jboss remoting too, so I don't think is a network issue.

                  • 6. Re: Wildfly 8.1 - configure and try remoting JNDI lookup
                    Wolf-Dieter Fink Master

                    A bit more basics

                    If you unzip/install a new WildFly instance and start it, are you able to access localhost:8080 and localhost:9990 via browser and use the bin/jboss-cli.bat script and connect to the management?

                    • 7. Re: Wildfly 8.1 - configure and try remoting JNDI lookup
                      Justin Bertram Master

                      At this point I'm not sure what the problem could be.  I've run the HelloWorld-JMS quickstart a number of times on my box without issue, and I've used local Wildfly servers for simple JMS clients more times than I can remember.  Everything always just works.

                      • 8. Re: Wildfly 8.1 - configure and try remoting JNDI lookup
                        Andrea Fantappiè Newbie

                        I've tried again with a new server binaries and now it perform the lookup, but throw this errore trying to send the message:

                         

                        HQ119031: Unable to validate user: quickstart

                         

                        If I add <security-enabled>false</security-enabled> to the configuration it work. Hornetq need a special configuration to validate users?

                        • 9. Re: Wildfly 8.1 - configure and try remoting JNDI lookup
                          Justin Bertram Master

                          Security is enabled and there are no default users so if you want to access HornetQ you either have to disable security (as you have done) or add a user.  I believe the quickstart instructions cover how to create the appropriate user(s).