https://issues.apache.org/bugzilla/show_bug.cgi?id=55931
--- Comment #4 from Konstantin Kolinko <knst.koli...@gmail.com> ---
(In reply to Michael from comment #2)
There are two cases in OP's report
"Case A": without JmxRemoteLifecycleListener
"Case B": with JmxRemoteLifecycleListener
> What is 3-d port opened by Java?
Take a thread dump. You will see what threads actually listen on network ports.
>From there you may guess why.
My result on Fedora 19 with OpenJDK "1.7.0_45" (OpenJDK Client VM (build
24.45-b08, mixed mode, sharing)) running without JmxRemoteLifecycleListener
("Case A") is that I also see 3 open IPv6 ports.
The thread dumps shows that there is one thread named "RMI TCP Accept-9123" and
two threads named "RMI TCP Accept-0" and all three of them have the following
stack trace:
at java.net.ServerSocket.accept(ServerSocket.java:498)
at
sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:388)
at
sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:360)
at java.lang.Thread.run(Thread.java:744)
If I add the following to the setenv.sh, it turns on debug logging [1]
CATALINA_OPTS="${CATALINA_OPTS} -Dsun.rmi.transport.tcp.logLevel=VERBOSE"
[1]
http://docs.oracle.com/javase/7/docs/technotes/guides/rmi/sunrmiproperties.html
With the logging I see how those three ports are being opened, but I do not
know why.
I suspect that the cause for the additional port is some bug in initialization
of RMI Registry. As such, it should be fixed in the JRE.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
