[
https://issues.apache.org/jira/browse/KAFKA-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290445#comment-14290445
]
jaikiran pai commented on KAFKA-1869:
-------------------------------------
[~huqian] As [~omkreddy] noted, that ephemeral port that's being used for the
JMX communication is more of an implementation detail of the JRMP protocol. It
appears to be a well known problem and there seem to be some workaround to it
(like usage of Java agent), but I think that's something that you'll have to
write up as a custom application specific thing.
On a different note, I think if you have questions related to this, it might be
a good idea to open a discussion in the Kafka user mailing list, details of
which are here http://kafka.apache.org/contact.html
> Openning some random ports while running kafka service
> -------------------------------------------------------
>
> Key: KAFKA-1869
> URL: https://issues.apache.org/jira/browse/KAFKA-1869
> Project: Kafka
> Issue Type: Bug
> Environment: kafka_2.9.2-0.8.1.1
> Reporter: QianHu
> Assignee: Manikumar Reddy
> Fix For: 0.8.2
>
>
> while running kafka service , four random ports have been opened . In which
> , 8888 and 9092 are setted by myself , but 28538 and 16650 are opened
> randomly . Can you help me that why this random ports will be opened , and
> how can we give them constant values ? Thank you very much .
> [work@02 kafka]$ jps
> 8400 Jps
> 727 Kafka
> [work@02 kafka]$ netstat -tpln|grep 727
> (Not all processes could be identified, non-owned process info
> will not be shown, you would have to be root to see it all.)
> tcp 0 0 0.0.0.0:8888 0.0.0.0:*
> LISTEN 727/./bin/../jdk1.7
> tcp 0 0 0.0.0.0:28538 0.0.0.0:*
> LISTEN 727/./bin/../jdk1.7
> tcp 0 0 0.0.0.0:9092 0.0.0.0:*
> LISTEN 727/./bin/../jdk1.7
> tcp 0 0 0.0.0.0:16650 0.0.0.0:*
> LISTEN 727/./bin/../jdk1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
