You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "xiezhi (JIRA)" <ji...@apache.org> on 2012/10/15 11:22:03 UTC
[jira] [Updated] (GERONIMO-6390) A port used by geronimo server but
is not controlled in the config-subsititution.properties
[ https://issues.apache.org/jira/browse/GERONIMO-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
xiezhi updated GERONIMO-6390:
-----------------------------
Attachment: system.properties.patch
update the system.properties for better usage
> A port used by geronimo server but is not controlled in the config-subsititution.properties
> -------------------------------------------------------------------------------------------
>
> Key: GERONIMO-6390
> URL: https://issues.apache.org/jira/browse/GERONIMO-6390
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CORBA
> Affects Versions: 3.0-beta-1
> Reporter: xiezhi
> Assignee: xiezhi
> Priority: Minor
> Attachments: system.properties.patch
>
>
> I find there is a port(65430) used by geronimo server but is not controlled in the config-subsititution.properties. The port is a random high value.
> It is related with the module j2ee-corba-yoko.
> Proto Local Address Foreign Address State PID
> TCP 0.0.0.0:1050 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:1099 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:1527 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:2001 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:4201 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:6882 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:8443 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:9999 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:10359 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:10360 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:10361 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:61616 0.0.0.0:0 LISTENING 5036
> TCP 0.0.0.0:65430 0.0.0.0:0 LISTENING 5036
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira