12 Replies Latest reply on Jun 8, 2015 9:44 PM by jaikiran pai

    Configure Eclipse Luna to start WildFly with standalone-full.xml

    George Berish Novice

      I am switching from Glassfish to WildFly.  Not fun yet!

       

      But today I'd be happy if someone could just offer pointers on how to reconfigure Eclipse Luna to start WildFly with standalone-full.xml.  Right now it starts in with standalone.xml.

       

      Suggestions and insight would be welcome.  I'm still struggling with getting a picture of how to rid the WildFly ... I mean maybe I need to be looking into WildFly configuaration, not Eclipse to do what I want.

       

      Heck .. I'm almost frustrated enough to just rename standalone-full.xml as standalone.xml.  Then rename standalone.xml to Old-standalone.xml.

        • 1. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
          George Berish Novice

          oops.  s/b "ride", not "rid" above but couldn't find a way to edit it.

           

          But I did find an answer.  I'm sure there is a more elegant one, but his one works.

          In the Servers Tab (at the bottom of the JavaEE view)

          Expand the WildFly  icon to find the WildFly/Filesets/Configuration File folder

          Right Click on the Folder

          Click on Edit the File

          Then just type in standalone-full.xml on the Includes Line.

           

          It seems there should be a macro like ... ${jboss_config_ .... something} ... that would add the name, but for now my solution seems to work.

          • 2. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
            jaikiran pai Master

            George Berish wrote:

             

            oops.  s/b "ride", not "rid" above but couldn't find a way to edit it.

            To edit the first post in a topic, there's a "Edit" link on the right hand side menu of the page.

             

            As for the question on how to get WildFly use standalone-full.xml from Eclipse, I'm pretty sure there's a way to do that, but I don't use IDE integration with servers. I'll move this thread to our JBoss Tools forum which is the right place for this and I'm sure someone there will help you out.

            • 4. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
              Rob Stryker Master

              It would be nice to have a few more details here, but, I'll take my shot.

               

              I'm assuming you're using JBoss Tools or JBDS.  I'll also be assuming that you already have a server adapter defined in your Servers view. If either of these are untrue, then please tell me

               

              First, you'll want to double-click on your server in the Servers view.  This will open the server editor.  In the top-left section of the editor, you'll see some details listed, like server name, host, etc.  One of these elements will be labeled "Runtime:".  That label should have a combo-box next to it, and the label itself should be a hyperlink.

               

              If you click on the hyperlink, you'll see the "Edit Runtime" wizard appear. It should look similar to this:  http://docs.jboss.org/tools/3.3.0.Final/en/as/html/images/runtimes_servers/runtimes_servers_3.png

               

              Though there might be small changes or additions to that, since the screenshot is a bit old. But you can clearly see there that the configuration file is listed as "standalone.xml".  You can either type in a new value, or, you can click "Browse..." to browse to your new choice.

               

              Once that's done, you should click "Finish", and then save the editor.

               

              Hope that helps!

              • 5. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
                George Berish Novice

                Hi Jirkiran,

                Thank you.

                This is  dumb, but it may help other newbies.

                When I went back to edit the error

                ... I forgot to log

                ... so the "EDIT" option was nowhere to be seen.

                glb

                • 6. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
                  George Berish Novice

                  Hi Rob,

                   

                  I'm beginning to think WildFly is the least intuitive  software ever.

                  None the less ...  thank you for your help.

                   

                  To answer your question:  This is what I followed to install WildFly and Luna:

                  Tutorials » Installing and Configuring WildFly and JBoss Tools

                   

                  However ... this is WEIRD.

                  The steps I originally showed above as the correct solution did seem to work.  I.e.  if I went to the SERVERS TAB, and expanded the tree there, it did show standalone-full.xml as being loaded. 

                   

                  BUT ... when I followed your instructions, and went to Runtime ... it still showed standalone.xml.

                   

                  Regardless ... Now it says standalone-full.xml in both places, so I hope that makes the Fly happy.

                   

                  And I changed the Correct star to your comment, because that seems the best bet.  glb

                  • 7. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
                    George Berish Novice

                    Hi Rob,

                     

                    In case you are still there and willing  to help

                     

                    Thanks to your help, Luna now gives every indication that it is starting Wildfly with standalone-full.xml.

                     

                    BUT a simple JNDI lookup of "jms/RemoteConnectionFactory" fails miserably.

                     

                    HOWEVER ...

                    If I use the cmd window to start Wildfly, instead of allowing Luna to start it, the JNDI lookup works fine.

                     

                    %JBOSS_HOME%/bin/standalone.bat -c standalone-full.xml

                     

                    In case it helps, the Wildfly "Launch Configuration" has these "program arguments".

                     

                    -mp "D:/Bulletproof/bpWildFly/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone-full.xml -Djboss.server.base.dir=D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\standalone

                     

                    I  tried just adding a " -c " to that list but then Wildfire threw a fit (exception) when Luna tried to start it.

                     

                    Thank you for  any pointers. 

                     

                    Wildfly my be the future ... but it is the least intuitive ... absolutely worst documented software I've ever seen.

                     

                    Most of the time it seems more like a club for the open source insiders.  Hope it matures.

                    glb

                    • 8. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
                      Rob Stryker Master

                      It's kinda hard to respond intelligently without some more information.  The first thing you should include is a stacktrace of how the JNDI call fails, as well as your code that is attempting the lookup.

                       

                      Regarding adding the -c flag,  if you look here (Command line parameters - WildFly 8 - Project Documentation Editor)  you'd see that -c and --server-config are equivilent flags. One is the long-form option, one is the short form, but they are both essentially the same flag. Your launch config is using the long-form flag, so there shouldn't really be a difference here at all.

                       

                      Also, something that'd be useful for us is if you launch via cmd line and then tell us the full java command that was launched,  either through a ps -ax on linux, or whatever mechanism is used to get the full command in windows.   Then do the same when launched from jbosstools / eclipse, and send both to us.  If there's some critical difference between the two, a missing option or an option with an incorrect value, it should become obvious. However, I suspect there isn't any such drastic difference.

                       

                      For example, in linux, when I run ps -ax, I see the following on an WF-8.2  launched via command-line standalone.sh:

                       

                      java -D[Standalone] -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/log/server.log -Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/configuration/logging.properties -jar /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/jboss-modules.jar -mp /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/modules org.jboss.as.standalone -Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded -Djboss.server.base.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone

                       

                      And when launched from eclipse / jbt, I see:

                       

                      /usr/java/jdk1.8.0_31/bin/java -Dprogram.name=JBossTools: WildFly 8.x -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/log/boot.log -Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/configuration/logging.properties -Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=UTF-8 -classpath /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/jboss-modules.jar org.jboss.modules.Main -mp /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone

                       

                       

                      We can see here that on linux at least, there's small differences.  The standalone.sh script uses the java -jar form running jboss-modules.jar, while we add jboss-modules.jar and run the main class org.jboss.modules.Main.  There are other small differences, but nothing that should be causing what you're seeing.

                      • 9. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
                        George Berish Novice

                        Hi Rob, I believe the following is what you requested.  I tried sending  it last night by using "ReplyTo" like the email notifying me of your response said was possible.  But it didn't seem to work.(Note: the reference to a failed tapp2.ear is an app that currently auto-deployes on Glassfish.  But that's a problem for tomorrow.) Thanks for any help.

                        glb

                         

                        HERE IS AN INDEX OF THE FIVE  SECTIONS BELOW I THINK RESPOND TO YOUR REQUEST:

                        1. Relevant Java Code (I left out the overwhelming amount of print code and try/catch code  I added to try to track what was happening.  There really are only three lines. 

                            a. Setting Properties.

                             b. Getting the Context.

                             c. JNDI lookup of the factory.

                        2. Successful Program Run Console Output

                        3. Failed Program Run Console Output

                        4. Luna Wildfly Start Output

                        5. CMD Window Start Console Output

                         

                        1. RELEVANT JAVA CODE

                         

                        a. Setting Properties:

                        private Properties getjndiProperties () {

                            try {

                              Properties output = new Properties();

                              output.setProperty (Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");

                              output.setProperty (Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");

                              output.setProperty (Context.PROVIDER_URL, "http-remoting://localhost:8080/");

                              //This property is important for remote resolving

                              output.setProperty ("jboss.naming.client.ejb.context", "true");

                              //This property is not important for remote resolving

                              output.setProperty ("org.jboss.ejb.client.scoped.context", "true");

                              System.out.println("Local Connection Properties:");

                              for (Object key:output.keySet()) {

                                System.out.println("Key: " + (String) key + "  Value: " + output.getProperty((String) key) );

                              }

                         

                        b. Getting Context

                        Context ctx = (Context) new InitialContext(jndiProps);

                         

                        c. JNDI lookup of the factory

                        String factoryLookupName = "jms/RemoteConnectionFactory";

                        ConnectionFactory factory = (ConnectionFactory) ctx.lookup(factoryLookupName);

                         

                        2. Successful Program Run Console Output

                        Local Connection Properties:

                        Key: java.naming.provider.url  Value: http-remoting://localhost:8080/

                        Key: java.naming.factory.initial  Value: org.jboss.naming.remote.client.InitialContextFactory

                        Key: jboss.naming.client.ejb.context  Value: true

                        Key: java.naming.factory.url.pkgs  Value: org.jboss.ejb.client.naming

                        Key: org.jboss.ejb.client.scoped.context Value: true

                        Jun 06, 2015 3:26:12 PM org.xnio.Xnio <clinit>

                        INFO: XNIO version 3.3.0.Final

                        Jun 06, 2015 3:26:12 PM org.xnio.nio.NioXnio <clinit>

                        INFO: XNIO NIO Implementation Version 3.3.0.Final

                        Jun 06, 2015 3:26:12 PM org.jboss.remoting3.EndpointImpl <clinit>

                        INFO: JBoss Remoting version 4.0.6.Final

                         

                        Successfully obtained a Local WildFly server context

                        javax.naming.InitialContext@17f6480

                         

                        Attempting to lookup: jms/RemoteConnectionFactory

                        Jun 06, 2015 3:26:12 PM org.jboss.ejb.client.remoting.VersionReceiver handleMessage

                        INFO: EJBCLIENT000017: Received server version 2 and marshalling strategies [river]

                        Jun 06, 2015 3:26:12 PM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate

                        INFO: EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@31ef45e3, receiver=Remoting connection EJB receiver [connection=Remoting connection <e22f0e3>,channel=jboss.ejb,nodename=ace]} on channel Channel ID 8d577267 (outbound) of Remoting connection 21f8a58c to localhost/127.0.0.1:8080

                        Jun 06, 2015 3:26:12 PM org.jboss.ejb.client.EJBClient <clinit>

                        INFO: JBoss EJB Client version 2.0.1.Final

                         

                        Successfully obtained ConnectionFactory from local WildFly server

                        HornetQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8080&host=127-0-0-1&http-upgrade-enabled=true&http-upgrade-endpoint=http-acceptor], discoveryGroupConfiguration=null], clientID=null, consumerWindowSize = 1048576, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]

                         

                        3. Failed Program Run Console Output

                        Local Connection Properties:

                        Key: java.naming.provider.url  Value: http-remoting://localhost:8080/

                        Key: java.naming.factory.initial  Value: org.jboss.naming.remote.client.InitialContextFactory

                        Key: jboss.naming.client.ejb.context Value: true

                        Key: java.naming.factory.url.pkgs Value: org.jboss.ejb.client.naming

                        Key: org.jboss.ejb.client.scoped.context  Value: true

                        Jun 06, 2015 3:39:08 PM org.xnio.Xnio <clinit>

                        INFO: XNIO version 3.3.0.Final

                        Jun 06, 2015 3:39:08 PM org.xnio.nio.NioXnio <clinit>

                        INFO: XNIO NIO Implementation Version 3.3.0.Final

                        Jun 06, 2015 3:39:08 PM org.jboss.remoting3.EndpointImpl <clinit>

                        INFO: JBoss Remoting version 4.0.6.Final

                         

                        Successfully obtained a Local WildFly server context

                        javax.naming.InitialContext@17f6480

                         

                        Attempting to lookup: jms/RemoteConnectionFactory

                        Exception Message: Failed to connect to any server. Servers tried: [http-remoting://localhost:8080/ (java.net.ConnectException: Connection refused: no further information)]

                        Exception Cause:   null

                           Source: 

                        Stack Trace:

                        • org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)
                        • org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
                        • org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
                        • org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
                        • org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:87)
                        • org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:129)
                        1. javax.naming.InitialContext.lookup(Unknown Source)
                        • org.america3.testclasses.WildflyJMSTest.getFactory(WildflyJMSTest.java:64)
                        • org.america3.testclasses.WildflyJMSTest.main(WildflyJMSTest.java:23)

                         

                        4. CMD Luna Wildfly Start Output

                        15:19:27,576 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final

                        15:19:27,781 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final

                        15:19:27,852 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.2.0.Final "Tweek" starting

                        15:19:28,984 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment tapp2.ear

                        15:19:29,008 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

                        15:19:29,029 INFO  [org.xnio] (MSC service thread 1-7) XNIO version 3.3.0.Final

                        15:19:29,038 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.3.0.Final

                        15:19:29,070 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.

                        15:19:29,073 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem

                        15:19:29,075 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 51) JBAS013171: Activating Security Subsystem

                        15:19:29,081 INFO  [org.jboss.as.security] (MSC service thread 1-15) JBAS013170: Current PicketBox version=4.0.21.Final

                        15:19:29,085 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.

                        15:19:29,090 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 34) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors

                        15:19:29,097 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 46) JBAS011800: Activating Naming Subsystem

                        15:19:29,116 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017502: Undertow 1.1.0.Final starting

                        15:19:29,119 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 42) JBAS012615: Activated the following JSF Implementations: [main]

                        15:19:29,125 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.1.0.Final starting

                        15:19:29,139 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension

                        15:19:29,221 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-10) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)

                        15:19:29,229 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-15) JBAS015400: Bound mail session [java:jboss/mail/Default]

                        15:19:29,229 INFO  [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service

                        15:19:29,238 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

                        15:19:29,242 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = h2

                        15:19:29,248 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017527: Creating file handler for path D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final/welcome-content

                        15:19:29,487 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server default-server.

                        15:19:29,503 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting

                        15:19:29,510 INFO  [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 4.0.6.Final

                        15:19:29,582 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-14) JBAS017519: Undertow HTTP listener default listening on localhost/127.0.0.1:8080

                        15:19:29,644 WARN  [jacorb.codeset] (MSC service thread 1-15) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1

                        15:19:29,656 WARN  [org.jboss.as.messaging] (MSC service thread 1-11) 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

                        15:19:29,689 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-13) JBAS015012: Started FileSystemDeploymentService for directory D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\standalone\deployments

                        15:19:29,692 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "tapp2.ear" (runtime-name: "tapp2.ear")

                        15:19:29,720 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

                        15:19:29,744 INFO  [org.jboss.as.jacorb] (MSC service thread 1-15) JBAS016330: CORBA ORB Service started

                        15:19:29,762 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=D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\standalone\data\messagingjournal,bindingsDirectory=D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\standalone\data\messagingbindings,largeMessagesDirectory=D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\standalone\data\messaginglargemessages,pagingDirectory=D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\standalone\data\messagingpaging)

                        15:19:29,765 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221006: Waiting to obtain live lock

                        15:19:29,856 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."tapp2.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."tapp2.ear".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "tapp2.ear"

                               at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]

                               at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

                               at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

                               at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.8.0_20]

                               at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.8.0_20]

                               at java.lang.Thread.run(Unknown Source) [rt.jar:1.8.0_20]

                        Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011037: Unable to process modules in application.xml for EAR ["/D:/Bulletproof/bpWildFly/wildfly-8.2.0.Final/bin/content/tapp2.ear"], module file tapp.war not found

                               at org.jboss.as.ee.structure.EarStructureProcessor.deploy(EarStructureProcessor.java:187)

                               at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]

                               ... 5 more

                         

                        15:19:29,862 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221013: Using NIO Journal

                        15:19:29,955 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.

                        15:19:30,002 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support CORE

                        15:19:30,016 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support AMQP

                        15:19:30,021 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support STOMP

                        15:19:30,094 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221034: Waiting to obtain live lock

                        15:19:30,094 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221035: Live Server Obtained live lock

                        15:19:30,197 INFO  [org.jboss.ws.common.management] (MSC service thread 1-14) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final

                        15:19:30,267 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016328: CORBA Naming Service started

                        15:19:30,356 INFO  [org.jboss.messaging] (MSC service thread 1-8) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor

                        15:19:30,357 INFO  [org.jboss.messaging] (MSC service thread 1-7) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor

                        15:19:30,516 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live

                        15:19:30,517 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.4.5.FINAL (Wild Hornet, 124) [54649417-0c9b-11e5-9050-ab28c985ba0b]

                        15:19:30,551 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

                        15:19:30,637 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 57) HQ221003: trying to deploy queue jms.queue.DLQ

                        15:19:30,644 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ

                        15:19:30,647 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

                        15:19:30,648 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 59) HQ221003: trying to deploy queue jms.queue.ExpiryQueue

                        15:19:30,649 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue

                        15:19:30,664 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA

                        15:19:30,722 INFO  [org.hornetq.ra] (MSC service thread 1-2) HornetQ resource adaptor started

                        15:19:30,722 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra

                        15:19:30,724 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-6) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

                        15:19:30,724 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory

                        15:19:30,725 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "tapp2.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"tapp2.ear\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"tapp2.ear\".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment \"tapp2.ear\"

                            Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011037: Unable to process modules in application.xml for EAR [\"/D:/Bulletproof/bpWildFly/wildfly-8.2.0.Final/bin/content/tapp2.ear\"], module file tapp.war not found"}}

                        15:19:30,780 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "tapp2.ear" (runtime-name : "tapp2.ear")

                        15:19:30,782 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

                        JBAS014777:   Services which failed to start:      service jboss.deployment.unit."tapp2.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."tapp2.ear".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "tapp2.ear"

                         

                        15:19:30,844 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

                        15:19:30,845 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

                        15:19:30,845 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.2.0.Final "Tweek" started (with errors) in 3529ms - Started 220 of 270 services (1 services failed or missing dependencies, 93 services are lazy, passive or on-demand)

                        15:19:31,050 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment tapp2.ear (runtime-name: tapp2.ear) in 3ms

                        15:19:31,092 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "tapp2.ear" (runtime-name: "tapp2.ear")

                        15:19:31,092 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

                        JBAS014777:   Services which failed to start:      service jboss.deployment.unit."tapp2.ear".STRUCTURE

                         

                        5. CMD Window Wildfly Start Console Output

                        Microsoft Windows [Version 6.1.7601]

                        Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

                         

                        D:\>%JBOSS_HOME%/bin/standalone.bat -c standalone-full.xml

                         

                        Calling "D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\bin\standalone.conf.bat"

                        Setting JAVA property to "C:\Program Files\Java\jdk1.8.0_05\bin\java"

                        ===============================================================================

                         

                          JBoss Bootstrap Environment

                         

                          JBOSS_HOME: "D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final"

                         

                          JAVA: "C:\Program Files\Java\jdk1.8.0_05\bin\java"

                         

                          JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djbos

                        1. s.modules.system.pkgs=org.jboss.byteman"

                         

                        ===============================================================================

                         

                        Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0

                        15:21:57,212 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final

                        15:21:57,407 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final

                        15:21:57,480 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.2.0.Final "Tweek" starting

                        15:21:58,674 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting fa

                        iled deployment tapp2.ear

                        15:21:58,700 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using soc

                        ket-binding (management-http)

                        15:21:58,723 INFO  [org.xnio] (MSC service thread 1-12) XNIO version 3.3.0.Final

                        15:21:58,736 INFO  [org.xnio.nio] (MSC service thread 1-12) XNIO NIO Implementation Version 3.3.0.Final

                        15:21:58,751 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem

                        15:21:58,760 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinis

                        pan subsystem.

                        15:21:58,765 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 52) JBAS010153: Node identifier property is set to t

                        he default value. Please make sure it is unique.

                        15:21:58,771 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 51) JBAS013171: Activating Security Subsystem

                        15:21:58,788 INFO  [org.jboss.as.security] (MSC service thread 1-15) JBAS013170: Current PicketBox version=4.0.21.Final

                        15:21:58,789 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Exten

                        sion

                        15:21:58,806 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 46) JBAS011800: Activating Naming Subsystem

                        15:21:58,807 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017502: Undertow 1.1.0.Final s

                        tarting

                        15:21:58,807 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017502: Undertow 1.1.0.Final starting

                        15:21:58,823 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 34) WFLYIO001: Worker 'default' has auto-con

                        figured to 16 core threads with 128 task threads based on your 8 available processors

                        15:21:58,848 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 42) JBAS012615: Activated the following JSF Implemen

                        tations: [main]

                        15:21:58,873 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJac

                        amar 1.1.9.Final)

                        15:21:58,879 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deployi

                        ng JDBC-compliant driver class org.h2.Driver (version 1.3)

                        15:21:58,897 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service w

                        ith driver-name = h2

                        15:21:58,901 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service

                        15:21:58,907 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-5) JBAS015400: Bound mail session [java:jboss/mai

                        l/Default]

                        15:21:59,212 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017527: Creating file handler

                        for path D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final/welcome-content

                        15:21:59,274 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-14) JBAS017525: Started server default-server.

                         

                        15:21:59,290 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-13) JBAS017531: Host default-host starting

                        15:21:59,295 INFO  [org.jboss.remoting] (MSC service thread 1-12) JBoss Remoting version 4.0.6.Final

                        15:21:59,368 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTP listener default

                        listening on /127.0.0.1:8080

                        15:21:59,443 WARN  [org.jboss.as.messaging] (MSC service thread 1-16) JBAS011600: AIO wasn't located on this platform, i

                        t will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

                        15:21:59,473 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-14) JBAS015012: Started FileSystemDepl

                        oymentService for directory D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\standalone\deployments

                        15:21:59,479 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "tapp2.e

                        ar" (runtime-name: "tapp2.ear")

                        15:21:59,481 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data sourc

                        e [java:jboss/datasources/ExampleDS]

                        15:21:59,517 WARN  [jacorb.codeset] (MSC service thread 1-12) Warning - unknown codeset (Cp1252) - defaulting to ISO-885

                        9-1

                        15:21:59,528 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221000: live server is starting with co

                        nfiguration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=D:\Bulletproof\bpWildF

                        ly\wildfly-8.2.0.Final\standalone\data\messagingjournal,bindingsDirectory=D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\s

                        tandalone\data\messagingbindings,largeMessagesDirectory=D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\standalone\data\mes

                        saginglargemessages,pagingDirectory=D:\Bulletproof\bpWildFly\wildfly-8.2.0.Final\standalone\data\messagingpaging)

                        15:21:59,536 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221006: Waiting to obtain live lock

                        15:21:59,549 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deploy

                        1. ment.unit."tapp2.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."tapp2.ear".STRUC

                        TURE: JBAS018733: Failed to process phase STRUCTURE of deployment "tapp2.ear"

                                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly

                        -server-8.2.0.Final.jar:8.2.0.Final]

                                at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-ms

                        c-1.2.2.Final.jar:1.2.2.Final]

                                at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.F

                        1. inal.jar:1.2.2.Final]

                                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_05]

                                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_05]

                                at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_05]

                        Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011037: Unable to process modules in ap

                        1. plication.xml for EAR ["/D:/content/tapp2.ear"], module file tapp.war not found

                                at org.jboss.as.ee.structure.EarStructureProcessor.deploy(EarStructureProcessor.java:187)

                                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly

                        -server-8.2.0.Final.jar:8.2.0.Final]

                                ... 5 more

                         

                        15:21:59,560 INFO  [org.jboss.as.jacorb] (MSC service thread 1-12) JBAS016330: CORBA ORB Service started

                        15:21:59,575 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221013: Using NIO Journal

                        15:21:59,619 INFO  [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 56) Your platform does not p

                        rovide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will alway

                        s be preferred to avoid potential system unstability.

                        15:21:59,650 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support CORE

                        15:21:59,658 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support AMQP

                        15:21:59,663 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support STOMP

                        15:21:59,672 INFO  [org.jboss.as.jacorb] (MSC service thread 1-16) JBAS016328: CORBA Naming Service started

                        15:21:59,701 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221034: Waiting to obtain live lock

                        15:21:59,702 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221035: Live Server Obtained live lock

                        15:21:59,772 INFO  [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - S

                        tack CXF Server 4.3.2.Final

                        15:21:59,881 INFO  [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoti

                        ng protocol handled by http-acceptor-throughput acceptor

                        15:21:59,881 INFO  [org.jboss.messaging] (MSC service thread 1-13) JBAS011615: Registered HTTP upgrade for hornetq-remot

                        ing protocol handled by http-acceptor acceptor

                        15:21:59,981 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live

                        15:21:59,981 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.4.5.FI

                        NAL (Wild Hornet, 124) [54649417-0c9b-11e5-9050-ab28c985ba0b]

                        15:21:59,986 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221003: trying to deploy queue jms.queu

                        1. e.ExpiryQueue

                        15:21:59,993 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi

                        name java:/jms/queue/ExpiryQueue

                        15:22:00,003 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221003: trying to deploy queue jms.queu

                        1. e.DLQ

                        15:22:00,005 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi

                        name java:/jms/queue/DLQ

                        15:22:00,020 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi

                        name java:jboss/exported/jms/RemoteConnectionFactory

                        15:22:00,023 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi

                        name java:/ConnectionFactory

                        15:22:00,054 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-6) JBAS010406: Registered connection factor

                        y java:/JmsXA

                        15:22:00,087 INFO  [org.hornetq.ra] (MSC service thread 1-6) HornetQ resource adaptor started

                        15:22:00,088 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActi

                        vator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatorhornetq-ra

                        15:22:00,091 INFO  [org.jboss.as.messaging] (MSC service thread 1-13) JBAS011601: Bound messaging object to jndi name ja

                        va:jboss/DefaultJMSConnectionFactory

                        15:22:00,091 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-7) JBAS010401: Bound JCA ConnectionFactory

                        [java:/JmsXA]

                        15:22:00,095 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deplo

                        y") failed - address: ([("deployment" => "tapp2.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss

                        .deployment.unit.\"tapp2.ear\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ta

                        pp2.ear\".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment \"tapp2.ear\"

                            Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011037: Unable to process modules i

                        n application.xml for EAR [\"/D:/content/tapp2.ear\"], module file tapp.war not found"}}

                        15:22:00,141 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "tapp2.ear" (runtime-nam

                        e : "tapp2.ear")

                        15:22:00,144 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

                        JBAS014777:   Services which failed to start:      service jboss.deployment.unit."tapp2.ear".STRUCTURE: org.jboss.msc.se

                        1. rvice.StartException in service jboss.deployment.unit."tapp2.ear".STRUCTURE: JBAS018733: Failed to process phase STRUCTU

                        RE of deployment "tapp2.ear"

                         

                        15:22:00,167 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127

                        .0.0.1:9990/management

                        15:22:00,168 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

                        15:22:00,169 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.2.0.Final "Tweek" started (with errors)

                        in 3221ms - Started 220 of 270 services (1 services failed or missing dependencies, 93 services are lazy, passive or on

                        -demand)

                        15:22:00,370 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment tapp2.ear (

                        runtime-name: tapp2.ear) in 2ms

                        15:22:00,411 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "tapp2.ear" (runtime-nam

                        e: "tapp2.ear")

                        15:22:00,413 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

                          JBAS014777: Services which failed to start: service jboss.deployment.unit."tapp2.ear".STRUCTURE

                        • 10. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
                          Rob Stryker Master

                          I see you also opened Cannot obtain JMS ConnectionFactory  as a topic for discussion.  Let's hope the core devs respond

                           

                          As for the discrepency between inside jbt and from externally-launched wildfly, what I really need to see is the *process*, not the command output. I need to see what the full command that is running is.  The full command is  basically the full java command, including all system properties being passed in, command line args, flags, vm args, flags, etc.  I gave some examples above.

                           

                          http://superuser.com/questions/403423/get-the-complete-command-line-of-a-process

                          • 11. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
                            George Berish Novice

                            Hi Rob,

                             

                            I truly appreciate your help, but I'm afraid we are out of my depth. 

                             

                            I was only switching to wildfly, because glassfish v3 had a bug I couldn't workaround, and they weren't going to fix it.  So my server host (eApps) recommended that since I was switching, I move to Wildfly instead of glassfish v4 at the same time. 

                             

                            Short Story:  I code 100% Java ... and know only as much about servers and deployment issues as I need to test things. Which for glassfish never required me to go beyond fiddling through the console.

                             

                            My guess so far is that my problem begins with the fact the Wildfly community assumes that almost Everything is done via the command line or CLI, and that is not a place with which I have much facility.

                             

                            If you are still interested in the problem, I'd be happy to do as much work as needed to answer your questions, but I don't know where else to look for anything more than I already copied above.  Unless maybe in the server log?  Or some command I could run from the Command window or CLI.

                             

                            If we can solve this mystery I assume it will help others, since it would be nice if Luna could start Wildfly and still have JMS work, and this is such a simple test class I assume the problem is systemic, not just me.  But if not, I can live with what I have ... and I guess I'm going to have to do more with the Command Window with less help from Eclipse.

                             

                            I don 't know if this helps, but here's the way I see where I am now:

                             

                            When I use the Command Window to start Wildfly JMS in a class whose main method is run by Luna works fine.

                               (so for my other post, the problem is  sort of answered -- just start Wildfly with the Command Window).

                               Otherwise, Item 5 above is a complete cut an paste from the Command Window start up.

                               Item 2 above is a complete cut and past from Luna's Console Output from that successful test.

                               The only other place from which I know how to get output is the server log.  Would that help?

                             

                            When I allow Luna to start Wildfly JMS in a class whose main method is run by Luna throws an exception.

                                Item 4 above is a complete cut and paste of Luna's console output when it starts Wildfly.

                                Item 3 above is a complete cut and past of Luna's console output when the run fails.

                             

                            Thank  you again for your interest and time. 

                             

                            glb

                            • 12. Re: Configure Eclipse Luna to start WildFly with standalone-full.xml
                              jaikiran pai Master

                              Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011037: Unable to process modules in application.xml for EAR ["/D:/Bulletproof/bpWildFly/wildfly-8.2.0.Final/bin/content/tapp2.ear"], module file tapp.war not found -

                              It looks like your application.xml notes that there's a tapp.war within the tapp2.ear. But in reality that tapp.war is missing from the tapp2.ear. Have you checked  that the ear indeed contains the war by that specific name?