This is likely because you enabled <management> or the jmx management
port through your -D system property.
Just remove the -D system property from your server config and you
should see those additional port go away.
-Dcom.sun.management.jmxremote
-Chris
On Mar 6, 2008, at 8:28 AM, Scott Ferguson wrote:
On Mar 6, 2008, at 8:07 AM, Tomi Po wrote:
Hello,
I am running Resin Pro 3.1.5 and I see it is listening 4 ports in
total.
TCP 127.0.0.1:6600
TCP 127.0.0.1:6800
TCP *:37140
TCP *:59408
First two are clear; Resin Watchdog port listens 6600, and server
at 6800,
but these other two that listen foreign ports. I have not found
explanation
for those ports - maybe I am missing something?
Are you sure that's Resin? Try getting a thread dump (see /resin-
admin). The thread dump would show what's listening to the sockets.
-- Scott
Somewhere in the Resin documentation there was mentioned that Resin
shows all ports that it is listening when it boots up. Those ports
are not
mentioned in the startup messages. (And before anyone suggests the
obvious:
those ports really belong to resin java process).
What are they? How to disable them? Or modify them to listen
localhost only?
Thanks in advance!
Tomi
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
