Hello.
Investigated a little bit, got some information but dont know how to
trace more.
I've made a Thread trace before and after i call my webapp, this was the
difference:
trace diff begin ###
"RMI Reaper" prio=5 tid=0x002b07f7f3f0 nid=6339 in Object.
> From: Torsten Krah [mailto:[EMAIL PROTECTED]
> Subject: RE: Bootstrap class - Interface bind - Problem there again.
>
> After the call i get additionally this:
> tcp6 0 0 :::54109:::*
> LISTEN 3495/java
Is the port number always the same? Doe
heres no cron job or similiar, i
> have to start it manually.
>
> The fork parameter isnt set, so its left at its default.
>
> kind regards
>
> Torsten
>
>
> Am Mittwoch, den 01.03.2006, 11:46 -0600 schrieb Caldarale, Charles R:
> > > From: Torsten Krah [
> > Subject: RE: Bootstrap class - Interface bind - Problem there again.
> >
> > Problem is there again - after few minutes in working state, a new
> > process shows up with following call:
>
> What Tomcat level? What OS? If Linux, do you have an LD_ASSUME_KERNEL
> set
> From: Torsten Krah [mailto:[EMAIL PROTECTED]
> Subject: RE: Bootstrap class - Interface bind - Problem there again.
>
> Problem is there again - after few minutes in working state, a new
> process shows up with following call:
What Tomcat level? What OS? If Linux,
Problem is there again - after few minutes in working state, a new
process shows up with following call:
/opt/java/bin/java -server -showversion -Xms640M -Xmx640M -verbose:gc
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC
-Xloggc:/var/logs/gc.log -Djava.awt.headless=true
-Djava.endo
Like i said, i configured the connectors to listen on
address="127.0.0.1", so its not the default one.
But i got the problem.
I've stopped and started tomcat after changing the connectors - but not
all java instances were closed when stopping tomcat.
After Stopping Tomcat again, killing all rema
> From: Torsten Krah [mailto:[EMAIL PROTECTED]
> Subject: Bootstrap class - Interface bind
>
> tomcats connectors are configured to listen on localhost only, which
> works fine.
If you're talking about the default Tomcat configuration, that's not
true. In the absence of an IP address specificat
