Re: [jboss-as7-dev] EAR Deployed, but doesn't work

----- Original Message ----- > From: "Jason T. Greene"<jason.greene(a)redhat.com> > To: "Andrig Miller"<anmiller(a)redhat.com> > Cc: jboss-as7-dev(a)lists.jboss.org > Sent: Tuesday, March 22, 2011 2:32:20 PM > Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work > On 3/22/11 3:28 PM, Andrig Miller wrote: >> >> ----- Original Message ----- >>> From: "Jason T. Greene"<jason.greene(a)redhat.com> >>> To: jboss-as7-dev(a)lists.jboss.org >>> Sent: Tuesday, March 22, 2011 2:21:31 PM >>> Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work >>> On 3/22/11 3:16 PM, Andrig Miller wrote: >>>> Okay, everyone. Now that I have my EAR deployed successfully, I >>>> tried to >>>> execute the application from my browser. It doesn't do anything >>>> and >>>> there is no error in the log. >>> That's no good! >>> >>>> I'm hitting the application across the network with >>>> http://192.168.1.22:8080/Order, were the IP is the address of my >>>> server >>>> where I'm running the app, and the /Order is the root context >>>> defined >>>> for the war in application.xml. It should return an HTML form. >>>> >>>> I changed in standalone.xml the IP address from 127.0.0.1 to >>>> 192.168.1.22, thinking that would do the same thing as -b >>>> 192.168.1.22 >>>> did on the old stuff. Curiously, I also don't really see anything >>>> that >>>> looks like JBoss Web in the file. I was expecting to see the stuff >>>> that >>>> used to be in server.xml, and META-INF/*beans.xml file for >>>> configuring >>>> it, but I don't really see anything. >>> The IP address shouldn't matter right now because jbossweb is >>> binding >>> to >>> 0.0.0.0 no matter what atm (yes that totally needs to be fixed, the >>> http >>> connector should be referring to the socket bindings section to get >>> the ip) >>> >>>> I'm not really sure what to look at next, so any pointers in the >>>> right >>>> direction is greatly appreciated. >>> So you just see a blank white page? >> Yes. >> >> I just found in the log that after the war is deployed it is on a >> different web context than I configured through the application.xml: >> >> 13:59:16,027 INFO [org.jboss.web] (MSC service thread 1-13) >> registering web context: /OrderManagerWeb >> 13:59:16,028 INFO [org.jboss.as.server.deployment] (MSC service >> thread 1-11) Completed deployment of "OrderManagerWeb.war" in 402 ms >> >> I defined it to be /Order. >> >> So, I just tried /OrderManagerWeb >> >> With that I get a 404, and resource /OrderManagerWeb/ not available. >> >> Is this because of the binding to address 0.0.0.0? >> > I think that log message must be wrong, since the blank white page > suggests you are getting a 200 back. Is there a way you can send us a > copy of this deployment? We may need to debug what exactly is going on > here. > I turned on DEBUG logging and when I hit http://192.168.1.22:8080/OrderManagerWeb/ I get the following: 15:01:18,498 DEBUG [org.apache.coyote.http11.Http11Protocol] (http-8080-1) Register jboss.web:type=RequestProcessor,worker=http-8080,name=HttpRequest1 It definitely was processed by the server. Andy