> BTW we should redirect this to the tomcat-users list as I don't think
> its a development issue.
Sorry about that.
> I don't see anything wrong, and the only drastic difference from my
> previous setup was that I had used the default 8007 and 8009. Now
> This is purely a guess, but I seem to remember reading that ports
> >10000 were special somehow and required root access for some
> functions. What I would suggest is put those to the default, see
> if they work, then (I'm assuming you had a reason for ding this)
> find an acceptable port between 8000-9999.
I think you get that backwards. Programs listening on port<1024
will require root access. Anything larger than that, it doesn't
require special priviledge.
> If that doesn't work then we have a couple more "generic"
> possiblities (such as running out of file handles which is
> very common with tomcat on solaris). I wish I still had access to a
> solaris box to try
> this.. The
> only other difference was that I was using Jdk 1.3 (Sun). Which I'd
> recommend for
> server side stuff unless you have a compelling reason not to.
> Its more
> stable, has
> less glitches and is faster. Jdk 1.2.x was suns "wowee" and
> jdk 1.3.x is a
> performance
> and stability release (IMHO)..
>
> If you haven't tweaked your file handles at any point then
> there is a good
> chance that
> is in the way, unfortunately I do not remember what the
> strings were to fix
> this, but
> I'm sure their documented somewhere (and they're not intuitive)..
Thanks for the tips. We can't switch JDK for this release we're
having. But next release, we are hoping to use JDK 1.3
shinta
