RequestDispatcher.forward() Taking 30 Seconds Each

[Will Handley]

Have a really odd one: In a web app, using RequestDispatcher.forward()
to pass request along to next servlet/jsp. No problem when using
Tomcat in development, but as soon as moved to iPlanet, each trans
taking a very, very long time. By writing time info to iPlant log, see
that first handoff is instantanious, but each one after that takes
almost exactly 30 seconds. The pattern is too consistent to be
coincidence, it must be waiting for some resource, then timing out.
Only difference I see between first handoff and all subsequent ones is
that the first is from a front controller servlet with no database
access, subsequent ones access an Oracle database. But I'm using
connection pooling, don't think that's really a factor. I get the RD
from the servlet context, if that's relevant. Same behavior when fwd
to servlet or JSP.
Anybody have any ideas?

 

[Nigel Wade]

Have a really odd one: In a web app, using RequestDispatcher.forward()
to pass request along to next servlet/jsp. No problem when using
Tomcat in development, but as soon as moved to iPlanet, each trans
taking a very, very long time. By writing time info to iPlant log, see
that first handoff is instantanious, but each one after that takes
almost exactly 30 seconds. The pattern is too consistent to be
coincidence, it must be waiting for some resource, then timing out.
Only difference I see between first handoff and all subsequent ones is
that the first is from a front controller servlet with no database
access, subsequent ones access an Oracle database. But I'm using
connection pooling, don't think that's really a factor. I get the RD
from the servlet context, if that's relevant. Same behavior when fwd
to servlet or JSP.
Anybody have any ideas?

Whenever I see "30 seconds delay" I immediately think "DNS timeout".

Given your situation I've no idea if this is the case, but 30 sec. delays
are so synonymous with DNS that it's got to be worth investigating.