3:16 p.m.
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.
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.
I'm not really sure what to look at next, so any pointers in the right direction is
greatly appreciated.
Thanks.
Andy
3:21 p.m.
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?
--
Jason T. Greene
JBoss, a division of Red Hat
3:28 p.m.
----- 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?
Andy
--
Jason T. Greene
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
3:32 p.m.
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.
--
Jason T. Greene
JBoss, a division of Red Hat
3:37 p.m.
----- 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.
Sure thing. I have attached the latest EAR, and what I have in the standalone.xml file,
along with the MySql module stuff in a zip file.
Andy
--
Jason T. Greene
JBoss, a division of Red Hat
5:25 p.m.
On Tue, 2011-03-22 at 16:37 -0400, Andrig Miller wrote:
Sure thing. I have attached the latest EAR, and what I have in the
standalone.xml file, along with the MySql module stuff in a zip file.
Ok, so EAR deployment acts weird [I get a .deploying and a .dodeploy
file, and no .isdeployed, without any error]. application.xml does not
propagate the WAR mapping. And the WAR deployment then acts weird, it's
there (the 404 with error report shows that), but not functional.
Repackaging as a WAR (the JAR goes into /WEB-INF/lib) yields better
results.
--
Remy Maucherat <rmaucher(a)redhat.com>
Red Hat Inc
7:07 p.m.
----- Original Message -----
From: "Remy Maucherat" <rmaucher(a)redhat.com>
To: jboss-as7-dev(a)lists.jboss.org
Sent: Tuesday, March 22, 2011 4:25:53 PM
Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work
On Tue, 2011-03-22 at 16:37 -0400, Andrig Miller wrote:
> Sure thing. I have attached the latest EAR, and what I have in the
> standalone.xml file, along with the MySql module stuff in a zip
> file.
>
Ok, so EAR deployment acts weird [I get a .deploying and a .dodeploy
file, and no .isdeployed, without any error]. application.xml does not
propagate the WAR mapping. And the WAR deployment then acts weird,
it's
there (the 404 with error report shows that), but not functional.
I get an OrderManagerApp.ear.isdeployed file in the deployments directory on my end.
Repackaging as a WAR (the JAR goes into /WEB-INF/lib) yields better
results.
--
Remy Maucherat <rmaucher(a)redhat.com>
Red Hat Inc
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
12:10 p.m.
BTW I am looking into this today.
On 3/22/11 3:37 PM, Andrig Miller wrote:
----- 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.
Sure thing. I have attached the latest EAR, and what I have in the standalone.xml file,
along with the MySql module stuff in a zip file.
Andy
>
> --
> Jason T. Greene
> JBoss, a division of Red Hat
--
Jason T. Greene
JBoss, a division of Red Hat
1:48 p.m.
Okay, thanks. Let me know if you need me to do anything in my test environment.
Andy
----- 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: Wednesday, March 23, 2011 11:10:40 AM
Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work
BTW I am looking into this today.
On 3/22/11 3:37 PM, Andrig Miller wrote:
>
>
> ----- 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.
>
> Sure thing. I have attached the latest EAR, and what I have in the
> standalone.xml file, along with the MySql module stuff in a zip
> file.
>
> Andy
>
>>
>> --
>> Jason T. Greene
>> JBoss, a division of Red Hat
--
Jason T. Greene
JBoss, a division of Red Hat
4:26 p.m.
I have already found a few bugs triggered by this deployment, I ll break
this up into issues you can track soon. I want to see this deployment
working by Beta2.
On 3/23/11 1:48 PM, Andrig Miller wrote:
Okay, thanks. Let me know if you need me to do anything in my test
environment.
Andy
----- 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: Wednesday, March 23, 2011 11:10:40 AM
> Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work
> BTW I am looking into this today.
>
> On 3/22/11 3:37 PM, Andrig Miller wrote:
>>
>>
>> ----- 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.
>>
>> Sure thing. I have attached the latest EAR, and what I have in the
>> standalone.xml file, along with the MySql module stuff in a zip
>> file.
>>
>> Andy
>>
>>>
>>> --
>>> Jason T. Greene
>>> JBoss, a division of Red Hat
>
>
> --
> Jason T. Greene
> JBoss, a division of Red Hat
--
Jason T. Greene
JBoss, a division of Red Hat
4:45 p.m.
That would be great. If we get this working by beta 2, then I can start doing some
preliminary profiling.
Andy
----- 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: Wednesday, March 23, 2011 3:26:55 PM
Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work
I have already found a few bugs triggered by this deployment, I ll
break
this up into issues you can track soon. I want to see this deployment
working by Beta2.
On 3/23/11 1:48 PM, Andrig Miller wrote:
> Okay, thanks. Let me know if you need me to do anything in my test
> environment.
>
> Andy
>
> ----- 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: Wednesday, March 23, 2011 11:10:40 AM
>> Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work
>> BTW I am looking into this today.
>>
>> On 3/22/11 3:37 PM, Andrig Miller wrote:
>>>
>>>
>>> ----- 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.
>>>
>>> Sure thing. I have attached the latest EAR, and what I have in the
>>> standalone.xml file, along with the MySql module stuff in a zip
>>> file.
>>>
>>> Andy
>>>
>>>>
>>>> --
>>>> Jason T. Greene
>>>> JBoss, a division of Red Hat
>>
>>
>> --
>> Jason T. Greene
>> JBoss, a division of Red Hat
--
Jason T. Greene
JBoss, a division of Red Hat
9:44 p.m.
Hi Andy,
Where is the source for this project?
One of the other issues is that it's using the old jboss global (non
portabl) jndi names. I'd like to update it to use the EE6 standard
names, and perhaps @EJB injection, unless you prefer the manual JNDI
lookups.
On 3/23/11 4:45 PM, Andrig Miller wrote:
That would be great. If we get this working by beta 2, then I can
start doing some preliminary profiling.
Andy
----- 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: Wednesday, March 23, 2011 3:26:55 PM
> Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work
> I have already found a few bugs triggered by this deployment, I ll
> break
> this up into issues you can track soon. I want to see this deployment
> working by Beta2.
>
> On 3/23/11 1:48 PM, Andrig Miller wrote:
>> Okay, thanks. Let me know if you need me to do anything in my test
>> environment.
>>
>> Andy
>>
>> ----- 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: Wednesday, March 23, 2011 11:10:40 AM
>>> Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work
>>> BTW I am looking into this today.
>>>
>>> On 3/22/11 3:37 PM, Andrig Miller wrote:
>>>>
>>>>
>>>> ----- 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.
>>>>
>>>> Sure thing. I have attached the latest EAR, and what I have in the
>>>> standalone.xml file, along with the MySql module stuff in a zip
>>>> file.
>>>>
>>>> Andy
>>>>
>>>>>
>>>>> --
>>>>> Jason T. Greene
>>>>> JBoss, a division of Red Hat
>>>
>>>
>>> --
>>> Jason T. Greene
>>> JBoss, a division of Red Hat
>
>
> --
> Jason T. Greene
> JBoss, a division of Red Hat
--
Jason T. Greene
JBoss, a division of Red Hat
3:41 p.m.
----- 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 just did a packet capture on doing the request with /Order and not /OrderManagerWeb and
I get the following:
13 10.938891 192.168.1.22 192.168.1.133 HTTP HTTP/1.1 404 Not Found
So, its getting a 404.
When I do /OrderManagerWeb I get the JBossWeb error page along with the 404, so I think
the log message is correct, which points to some problem with either my application.xml,
or to the deployer for it.
So, probably two problems here.
Andy
--
Jason T. Greene
JBoss, a division of Red Hat
4:04 p.m.
----- 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
--
Jason T. Greene
JBoss, a division of Red Hat
4:07 p.m.
Andy,
RequestDumperValve should trace out your http request. I do not know
how you can configure it in AS7.
Regards,
Anil
On 03/22/2011 04:04 PM, Andrig Miller wrote:
----- 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
3:38 p.m.
Andy,
its not fair that you did not get brocked for asking, without
enabling logs. :)
People still remember my ultra-brock in early AS5 days.
Regards,
Anil
On 03/22/2011 03: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?
Andy
3:40 p.m.
Andy gets a pass :) Plus in this case I'm pretty sure we have a nasty
bug that's not logging a proper error message.
On 3/22/11 3:38 PM, Anil Saldhana wrote:
Andy,
its not fair that you did not get brocked for asking, without
enabling logs. :)
People still remember my ultra-brock in early AS5 days.
Regards,
Anil
On 03/22/2011 03: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?
>
> Andy
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Jason T. Greene
JBoss, a division of Red Hat
3:43 p.m.
I appreciate the pass, but its not necessary ;-).
Andy
----- 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:40:37 PM
Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work
Andy gets a pass :) Plus in this case I'm pretty sure we have a nasty
bug that's not logging a proper error message.
On 3/22/11 3:38 PM, Anil Saldhana wrote:
> Andy,
> its not fair that you did not get brocked for asking, without
> enabling logs. :)
>
> People still remember my ultra-brock in early AS5 days.
>
> Regards,
> Anil
>
> On 03/22/2011 03: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?
>>
>> Andy
>>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Jason T. Greene
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
3:46 p.m.
By the way my message was too big (due to the module definition with the mysql database
driver in there), so its waiting for moderator approval.
Andy
----- 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:40:37 PM
Subject: Re: [jboss-as7-dev] EAR Deployed, but doesn't work
Andy gets a pass :) Plus in this case I'm pretty sure we have a nasty
bug that's not logging a proper error message.
On 3/22/11 3:38 PM, Anil Saldhana wrote:
> Andy,
> its not fair that you did not get brocked for asking, without
> enabling logs. :)
>
> People still remember my ultra-brock in early AS5 days.
>
> Regards,
> Anil
>
> On 03/22/2011 03: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?
>>
>> Andy
>>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Jason T. Greene
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
5021
days inactive
5023
days old
18 comments
4 participants
participants (4)
-
Andrig Miller -
Anil Saldhana -
Jason T. Greene -
Remy Maucherat