Re: Plz help! at wits end! tomcat/mod_jk hangs when calling itself

2001-06-24 Thread Dmitri Colebatch

Not sure if this is going to be of _any_ assistance whatsoever, but anyway... 
 I've seen a situation where someone was using the java.net.URL package to 
open a connection and request a page where the connection was opened but it 
appears the buffer wasn't being flushed, and the request hence wasn't being 
transmitted to the destination, hence the appearance of hanging.  Have you 
tried sniffing the traffic between the calling servlet and its target?  

Again, not sure if this will help, but a suggestion nonetheless.

cheers
dim

On Mon, 25 Jun 2001 11:43, you wrote:
> I had sent an email about this problem on friday, and
> had some more info to add.
>
> My environment:
>   Solaris 8
>   jdk 1.3.1, with hotspot enabled
>   tomcat 3.2.2
>   apache 1.3.19
>
> The problem:
>   I have a servlet that opens a URL connection to the
>   servlet container. So if I call http://blah/blinky,
>   where blinky is my servlet, it is possible under some
>   situations for this servlet to open a URL such as
>   http://blah/lumpy, where lumpy is some other servlet.
>
>   This is part of a largish site publishing framework
>   I built on top of JServ. Now, things worked great with
>   JServ, but I am having a devil of a time getting this
>   to work in Tomcat.
>
> Observations:
>   When the blinky servlet opens a URL to the same tomcat
>   instance, the log entries for mod_jk go as far as making
>   the call to marshal stuff before calling tomcat - as seen
>   by the mod_jk.log entry:
> [jk_ajp13.c (480)]: ajp13_marshal_into_msgb - Done
>   At this point, nothing happens. I *should* be seeing entries
>   for the jk_open_socket function, but they never appear.
>
> What I have tried:
>   - I have disabled the default 8080 listener, thinking it
> may be interfering.
> No luck
>   - I changed the cachesize of the ajp12 and ajp13 workers
> to 8 from the default of 1.
> No luck
>   - I added the "min_spare_threads" parameter to the entries
> for the ajp12 and ajp13 connectors in server.xml
> No luck
>   - switched between tomcat 3.2.1 and 3.2.2
> No luck
>   - upgraded apache to 1.3.19
> No luck
>   - Torn my hair out from the roots
> No luck
>
> I am at my wits end. Any help will be gratefully received.
>
> TIA,
> naeem



Plz help! at wits end! tomcat/mod_jk hangs when calling itself

2001-06-24 Thread Bari, Naeem

 
I had sent an email about this problem on friday, and
had some more info to add.
 
My environment:
  Solaris 8
  jdk 1.3.1, with hotspot enabled
  tomcat 3.2.2
  apache 1.3.19
 
The problem:
  I have a servlet that opens a URL connection to the
  servlet container. So if I call http://blah/blinky,
  where blinky is my servlet, it is possible under some
  situations for this servlet to open a URL such as
  http://blah/lumpy, where lumpy is some other servlet.
 
  This is part of a largish site publishing framework
  I built on top of JServ. Now, things worked great with
  JServ, but I am having a devil of a time getting this
  to work in Tomcat.
 
Observations:
  When the blinky servlet opens a URL to the same tomcat
  instance, the log entries for mod_jk go as far as making
  the call to marshal stuff before calling tomcat - as seen
  by the mod_jk.log entry:
[jk_ajp13.c (480)]: ajp13_marshal_into_msgb - Done
  At this point, nothing happens. I *should* be seeing entries
  for the jk_open_socket function, but they never appear.
 
What I have tried:
  - I have disabled the default 8080 listener, thinking it
may be interfering.
No luck
  - I changed the cachesize of the ajp12 and ajp13 workers
to 8 from the default of 1.
No luck
  - I added the "min_spare_threads" parameter to the entries
for the ajp12 and ajp13 connectors in server.xml
No luck
  - switched between tomcat 3.2.1 and 3.2.2
No luck
  - upgraded apache to 1.3.19
No luck
  - Torn my hair out from the roots
No luck
 
I am at my wits end. Any help will be gratefully received.
 
TIA,
naeem