| WTP calls default app on Tomcat startup [message #165165] |
Tue, 28 March 2006 14:08  |
Eclipse User |
|
|
|
Originally posted by: dkrukovsky.yahoo.com
I have web application set up as default Tomcat app under WTP ( removed
path variable under .settings/.component ). My application have some
logging tuned to put message on the console when it is called.
I start Tomcat from Servers window. I can control Tomcat startup on the
console. It starts well and I see request to default web app ("/")
immediately after Tomcat startup.
Is it how WTP is supposed to work? If yes then there is a problem that
seems like WTP won't read from connection it opens to default web app.
This results in my app's SocketOutputStream hangs waiting for read.
Thanks for investigation.
|
|
|
|
| Re: WTP calls default app on Tomcat startup [message #165188 is a reply to message #165173] |
Tue, 28 March 2006 14:35  |
| Eclipse User |
|
|
|
Originally posted by: dkrukovsky.yahoo.com
Marc,
Thanks for investigation. The thing that I do simply start the server
without any requests from the browser. Immediately after Tomcat reports
"startup ok" I see my default web app starts processing GET request to
"/". If it is unexpected WTP behavior then how to stop it?
I tested my app with standalone Tomcat. No requests on startup.
Marc Adams wrote:
> I'm missing a piece here that maybe you can fill in. Are you simply
|
|
|
| Re: WTP calls default app on Tomcat startup [message #165212 is a reply to message #165165] |
Tue, 28 March 2006 19:38 |
| Eclipse User |
|
|
|
Originally posted by: ifedorenko.rogers.com
WTP ("default tomcat plugin provided with WTP" to be precise) "pings"
tomcat server to make sure it has started. It is not possible to turn
this off as far as I can tell and I suggest you open enhancement request
if you feel it is important to be able to do so.
If you feel like hacking around WTP sources, look at
TomcatServerBehaviour and PingThread classes in
org.eclipse.jst.server.tomcat.core plugin.
Denis Krukovsky wrote:
> I have web application set up as default Tomcat app under WTP ( removed
> path variable under .settings/.component ). My application have some
> logging tuned to put message on the console when it is called.
>
> I start Tomcat from Servers window. I can control Tomcat startup on the
> console. It starts well and I see request to default web app ("/")
> immediately after Tomcat startup.
>
> Is it how WTP is supposed to work? If yes then there is a problem that
> seems like WTP won't read from connection it opens to default web app.
> This results in my app's SocketOutputStream hangs waiting for read.
>
> Thanks for investigation.
|
|
|
| Re: WTP calls default app on Tomcat startup [message #165342 is a reply to message #165212] |
Thu, 30 March 2006 13:37 |
| Eclipse User |
|
|
|
Originally posted by: dkrukovsky.yahoo.com
Igor Fedorenko wrote:
> WTP ("default tomcat plugin provided with WTP" to be precise) "pings"
> tomcat server to make sure it has started. It is not possible to turn
Then there is a problem with ping that "ping" won't read data from
connection it opens so serverside SocketOutputStream hangs waiting for
bytes to be read, as I described before.
Actually I haven't tested if WTP's "ping" reads data or no, all I see is
my SocketOutputStream.write() hangs after over 40K of data sent. So I
suppose the reason for it is no data read by other party.
|
|
|
| Re: WTP calls default app on Tomcat startup [message #165350 is a reply to message #165212] |
Thu, 30 March 2006 13:38 |
| Eclipse User |
|
|
|
Originally posted by: dkrukovsky.yahoo.com
Igor Fedorenko wrote:
> WTP ("default tomcat plugin provided with WTP" to be precise) "pings"
> tomcat server to make sure it has started. It is not possible to turn
Then there is a problem with ping that "ping" won't read data from
connection it opens so serverside SocketOutputStream hangs waiting for
bytes to be read, as I described before.
Actually I haven't tested if WTP's "ping" reads data or no, all I see is
my SocketOutputStream.write() hangs after over 40K of data sent. So I
suppose the reason for it is no data read by other party.
|
|
|
| Re: WTP calls default app on Tomcat startup [message #165394 is a reply to message #165342] |
Thu, 30 March 2006 16:29 |
| Eclipse User |
|
|
|
Originally posted by: ifedorenko.rogers.com
Denis Krukovsky wrote:
> Igor Fedorenko wrote:
>> WTP ("default tomcat plugin provided with WTP" to be precise) "pings"
>> tomcat server to make sure it has started. It is not possible to turn
>
> Then there is a problem with ping that "ping" won't read data from
> connection it opens so serverside SocketOutputStream hangs waiting for
> bytes to be read, as I described before.
>
> Actually I haven't tested if WTP's "ping" reads data or no, all I see is
> my SocketOutputStream.write() hangs after over 40K of data sent. So I
> suppose the reason for it is no data read by other party.
This is the code snippet from PingThread
URL pingUrl = new URL(url);
URLConnection conn = pingUrl.openConnection();
((HttpURLConnection)conn).getResponseCode();
It does not read anything, it does not even close/disconnect
HttpURLConnection. I suggest you open a bug report.
--
Regards,
Igor Fedorenko
|
|
|
Powered by
FUDForum. Page generated in 0.04274 seconds
] 
Search
Help
Register
Login
Home
