java.rmi.server.ExportException: Port already in use when enabling JMX

up vote
0
down vote

favorite

I am trying to start a java process with JMX like below

java -XX:MaxPermSize=256m 

    -XX:OnOutOfMemoryError=kill -9 %p 

    -Xss256K 

    -Dorg.xerial.snappy.tempdir=/home/ubuntu/tmp 

    -Dlog4j.debug 

    -Dlog4j.defaultInitOverride=true 

    -Dlogdir=/home/ubuntu/logs/flow-processor 

    -DvneraLog4jConfigurationFile=/home/ubuntu/build-target/nfdump/flow-processor.log4j.xml 

    -Dcom.sun.management.jmxremote 

    -Dcom.sun.management.jmxremote.password.file=/home/ubuntu/build-target/nfdump/jmxremote.password 

    -Dcom.sun.management.jmxremote.access.file=/home/ubuntu/build-target/nfdump/jmxremote.access 

    -Djava.rmi.server.hostname=10.xxx.xxx.xx 

    -Dcom.sun.management.jmxremote.ssl=false 

    -Dcom.sun.management.jmxremote.port=11103 

    -Xmx3604m 

    -Ddeployment.info=IPGQRFG 

    -Ddeployment.id=DPGQGXI 

    -Dsku.info=proxy 

    -DuiAccessUrlPath= 

    -Dreporters.configuration=/home/ubuntu/build-target/nfdump/reporters.configuration 

    -Dreporters.application.name=vRNI 

    -cp /home/ubuntu/build-target/nfdump/flow-processor-0.001-SNAPSHOT.jar 

    com.vnera.ipfix.IpfixProcessor 

    /home/ubuntu/build-target/nfdump/ipfix.configuration

But on start I am getting an exception like below occassionally:

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

sun.management.AgentConfigurationError: java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

        at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(ConnectorBootstrap.java:480)

        at sun.management.Agent.startAgent(Agent.java:262)

        at sun.management.Agent.startAgent(Agent.java:452)

Caused by: java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:346)

        at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:254)

        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)

        at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)

        at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:236)

        at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213)

        at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:173)

        at sun.management.jmxremote.SingleEntryRegistry.<init>(SingleEntryRegistry.java:49)

        at sun.management.jmxremote.ConnectorBootstrap.exportMBeanServer(ConnectorBootstrap.java:816)

        at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(ConnectorBootstrap.java:468)

        ... 2 more

Caused by: java.net.BindException: Address already in use (Bind failed)

        at java.net.PlainSocketImpl.socketBind(Native Method)

        at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)

        at java.net.ServerSocket.bind(ServerSocket.java:375)

        at java.net.ServerSocket.<init>(ServerSocket.java:237)

        at java.net.ServerSocket.<init>(ServerSocket.java:128)

        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45)

        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:345)

        at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)

        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:335)

        ... 11 more

I am seeing that the java process in question is owning the jmx port 11103:

support@vrni-proxy-release:~$ sudo lsof -i :11103

COMMAND  PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME

java    8011 ubuntu   14u  IPv4  32077      0t0  TCP *:11103 (LISTEN)

Output of ps -ef | grep flow-processor

support@vrni-proxy-release:~$ ps -ef | grep flow-processor

ubuntu    8011  7903  1 Oct17 ?        12:11:07 java -XX:MaxPermSize=256m -XX:OnOutOfMemoryError=kill -9 %p -Xss256K -Dorg.xerial.snappy.tempdir=/home/ubuntu/tmp -Dlog4j.debug -Dlog4j.defaultInitOverride=true -Dlogdir=/home/ubuntu/logs/flow-processor -DvneraLog4jConfigurationFile=/home/ubuntu/build-target/nfdump/flow-processor.log4j.xml -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.password.file=/home/ubuntu/build-target/nfdump/jmxremote.password -Dcom.sun.management.jmxremote.access.file=/home/ubuntu/build-target/nfdump/jmxremote.access -Djava.rmi.server.hostname=10.196.173.49 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=11103 -Xmx3604m -Ddeployment.info=IPGQRFG -Ddeployment.id=DPGQGXI -Dsku.info=proxy -DuiAccessUrlPath= -Dreporters.configuration=/home/ubuntu/build-target/nfdump/reporters.configuration -Dreporters.application.name=vRNI  -cp /home/ubuntu/build-target/nfdump/flow-processor-0.001-SNAPSHOT.jar com.vnera.ipfix.IpfixProcessor /home/ubuntu/build-target/nfdump/ipfix.configuration

Can someone let me know what is going wrong?

edited Nov 22 at 15:22

Per Lundberg

1,60812030

asked Nov 22 at 12:51

tuk

1,49512151

1

What happens if you specify an alternative port in the -Dcom.sun.management.jmxremote.port= setting? Does it then complain also, about the new port?
– Per Lundberg
Nov 22 at 13:00

Even with the port mentioned here 11103 this issue does not come always. It comes occasionally.
– tuk
Nov 22 at 13:16

1

@PerLundberg - I have read this stackoverflow.com/questions/20884353/…. But I am not sure why should we be setting both com.sun.management.jmxremote.port and com.sun.management.jmxremote.rmi.port to the same value ?
– tuk
Nov 22 at 13:17

Good link, thanks. But a silly question: when this happens, could it be that you have an old instance of flow-processor still running? (I mean: you try to start it, but an old process still exists and that's why it fails.) Could this be the problem?
– Per Lundberg
Nov 22 at 22:25

add a comment |

up vote
0
down vote

favorite

I am trying to start a java process with JMX like below

java -XX:MaxPermSize=256m 

    -XX:OnOutOfMemoryError=kill -9 %p 

    -Xss256K 

    -Dorg.xerial.snappy.tempdir=/home/ubuntu/tmp 

    -Dlog4j.debug 

    -Dlog4j.defaultInitOverride=true 

    -Dlogdir=/home/ubuntu/logs/flow-processor 

    -DvneraLog4jConfigurationFile=/home/ubuntu/build-target/nfdump/flow-processor.log4j.xml 

    -Dcom.sun.management.jmxremote 

    -Dcom.sun.management.jmxremote.password.file=/home/ubuntu/build-target/nfdump/jmxremote.password 

    -Dcom.sun.management.jmxremote.access.file=/home/ubuntu/build-target/nfdump/jmxremote.access 

    -Djava.rmi.server.hostname=10.xxx.xxx.xx 

    -Dcom.sun.management.jmxremote.ssl=false 

    -Dcom.sun.management.jmxremote.port=11103 

    -Xmx3604m 

    -Ddeployment.info=IPGQRFG 

    -Ddeployment.id=DPGQGXI 

    -Dsku.info=proxy 

    -DuiAccessUrlPath= 

    -Dreporters.configuration=/home/ubuntu/build-target/nfdump/reporters.configuration 

    -Dreporters.application.name=vRNI 

    -cp /home/ubuntu/build-target/nfdump/flow-processor-0.001-SNAPSHOT.jar 

    com.vnera.ipfix.IpfixProcessor 

    /home/ubuntu/build-target/nfdump/ipfix.configuration

But on start I am getting an exception like below occassionally:

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

sun.management.AgentConfigurationError: java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

        at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(ConnectorBootstrap.java:480)

        at sun.management.Agent.startAgent(Agent.java:262)

        at sun.management.Agent.startAgent(Agent.java:452)

Caused by: java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:346)

        at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:254)

        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)

        at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)

        at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:236)

        at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213)

        at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:173)

        at sun.management.jmxremote.SingleEntryRegistry.<init>(SingleEntryRegistry.java:49)

        at sun.management.jmxremote.ConnectorBootstrap.exportMBeanServer(ConnectorBootstrap.java:816)

        at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(ConnectorBootstrap.java:468)

        ... 2 more

Caused by: java.net.BindException: Address already in use (Bind failed)

        at java.net.PlainSocketImpl.socketBind(Native Method)

        at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)

        at java.net.ServerSocket.bind(ServerSocket.java:375)

        at java.net.ServerSocket.<init>(ServerSocket.java:237)

        at java.net.ServerSocket.<init>(ServerSocket.java:128)

        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45)

        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:345)

        at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)

        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:335)

        ... 11 more

I am seeing that the java process in question is owning the jmx port 11103:

support@vrni-proxy-release:~$ sudo lsof -i :11103

COMMAND  PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME

java    8011 ubuntu   14u  IPv4  32077      0t0  TCP *:11103 (LISTEN)

Output of ps -ef | grep flow-processor

support@vrni-proxy-release:~$ ps -ef | grep flow-processor

ubuntu    8011  7903  1 Oct17 ?        12:11:07 java -XX:MaxPermSize=256m -XX:OnOutOfMemoryError=kill -9 %p -Xss256K -Dorg.xerial.snappy.tempdir=/home/ubuntu/tmp -Dlog4j.debug -Dlog4j.defaultInitOverride=true -Dlogdir=/home/ubuntu/logs/flow-processor -DvneraLog4jConfigurationFile=/home/ubuntu/build-target/nfdump/flow-processor.log4j.xml -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.password.file=/home/ubuntu/build-target/nfdump/jmxremote.password -Dcom.sun.management.jmxremote.access.file=/home/ubuntu/build-target/nfdump/jmxremote.access -Djava.rmi.server.hostname=10.196.173.49 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=11103 -Xmx3604m -Ddeployment.info=IPGQRFG -Ddeployment.id=DPGQGXI -Dsku.info=proxy -DuiAccessUrlPath= -Dreporters.configuration=/home/ubuntu/build-target/nfdump/reporters.configuration -Dreporters.application.name=vRNI  -cp /home/ubuntu/build-target/nfdump/flow-processor-0.001-SNAPSHOT.jar com.vnera.ipfix.IpfixProcessor /home/ubuntu/build-target/nfdump/ipfix.configuration

Can someone let me know what is going wrong?

edited Nov 22 at 15:22

Per Lundberg

1,60812030

asked Nov 22 at 12:51

tuk

1,49512151

1

What happens if you specify an alternative port in the -Dcom.sun.management.jmxremote.port= setting? Does it then complain also, about the new port?
– Per Lundberg
Nov 22 at 13:00

Even with the port mentioned here 11103 this issue does not come always. It comes occasionally.
– tuk
Nov 22 at 13:16

1

@PerLundberg - I have read this stackoverflow.com/questions/20884353/…. But I am not sure why should we be setting both com.sun.management.jmxremote.port and com.sun.management.jmxremote.rmi.port to the same value ?
– tuk
Nov 22 at 13:17

Good link, thanks. But a silly question: when this happens, could it be that you have an old instance of flow-processor still running? (I mean: you try to start it, but an old process still exists and that's why it fails.) Could this be the problem?
– Per Lundberg
Nov 22 at 22:25

add a comment |

up vote
0
down vote

favorite

I am trying to start a java process with JMX like below

java -XX:MaxPermSize=256m 

    -XX:OnOutOfMemoryError=kill -9 %p 

    -Xss256K 

    -Dorg.xerial.snappy.tempdir=/home/ubuntu/tmp 

    -Dlog4j.debug 

    -Dlog4j.defaultInitOverride=true 

    -Dlogdir=/home/ubuntu/logs/flow-processor 

    -DvneraLog4jConfigurationFile=/home/ubuntu/build-target/nfdump/flow-processor.log4j.xml 

    -Dcom.sun.management.jmxremote 

    -Dcom.sun.management.jmxremote.password.file=/home/ubuntu/build-target/nfdump/jmxremote.password 

    -Dcom.sun.management.jmxremote.access.file=/home/ubuntu/build-target/nfdump/jmxremote.access 

    -Djava.rmi.server.hostname=10.xxx.xxx.xx 

    -Dcom.sun.management.jmxremote.ssl=false 

    -Dcom.sun.management.jmxremote.port=11103 

    -Xmx3604m 

    -Ddeployment.info=IPGQRFG 

    -Ddeployment.id=DPGQGXI 

    -Dsku.info=proxy 

    -DuiAccessUrlPath= 

    -Dreporters.configuration=/home/ubuntu/build-target/nfdump/reporters.configuration 

    -Dreporters.application.name=vRNI 

    -cp /home/ubuntu/build-target/nfdump/flow-processor-0.001-SNAPSHOT.jar 

    com.vnera.ipfix.IpfixProcessor 

    /home/ubuntu/build-target/nfdump/ipfix.configuration

But on start I am getting an exception like below occassionally:

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

sun.management.AgentConfigurationError: java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

        at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(ConnectorBootstrap.java:480)

        at sun.management.Agent.startAgent(Agent.java:262)

        at sun.management.Agent.startAgent(Agent.java:452)

Caused by: java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:346)

        at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:254)

        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)

        at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)

        at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:236)

        at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213)

        at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:173)

        at sun.management.jmxremote.SingleEntryRegistry.<init>(SingleEntryRegistry.java:49)

        at sun.management.jmxremote.ConnectorBootstrap.exportMBeanServer(ConnectorBootstrap.java:816)

        at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(ConnectorBootstrap.java:468)

        ... 2 more

Caused by: java.net.BindException: Address already in use (Bind failed)

        at java.net.PlainSocketImpl.socketBind(Native Method)

        at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)

        at java.net.ServerSocket.bind(ServerSocket.java:375)

        at java.net.ServerSocket.<init>(ServerSocket.java:237)

        at java.net.ServerSocket.<init>(ServerSocket.java:128)

        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45)

        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:345)

        at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)

        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:335)

        ... 11 more

I am seeing that the java process in question is owning the jmx port 11103:

support@vrni-proxy-release:~$ sudo lsof -i :11103

COMMAND  PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME

java    8011 ubuntu   14u  IPv4  32077      0t0  TCP *:11103 (LISTEN)

Output of ps -ef | grep flow-processor

support@vrni-proxy-release:~$ ps -ef | grep flow-processor

ubuntu    8011  7903  1 Oct17 ?        12:11:07 java -XX:MaxPermSize=256m -XX:OnOutOfMemoryError=kill -9 %p -Xss256K -Dorg.xerial.snappy.tempdir=/home/ubuntu/tmp -Dlog4j.debug -Dlog4j.defaultInitOverride=true -Dlogdir=/home/ubuntu/logs/flow-processor -DvneraLog4jConfigurationFile=/home/ubuntu/build-target/nfdump/flow-processor.log4j.xml -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.password.file=/home/ubuntu/build-target/nfdump/jmxremote.password -Dcom.sun.management.jmxremote.access.file=/home/ubuntu/build-target/nfdump/jmxremote.access -Djava.rmi.server.hostname=10.196.173.49 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=11103 -Xmx3604m -Ddeployment.info=IPGQRFG -Ddeployment.id=DPGQGXI -Dsku.info=proxy -DuiAccessUrlPath= -Dreporters.configuration=/home/ubuntu/build-target/nfdump/reporters.configuration -Dreporters.application.name=vRNI  -cp /home/ubuntu/build-target/nfdump/flow-processor-0.001-SNAPSHOT.jar com.vnera.ipfix.IpfixProcessor /home/ubuntu/build-target/nfdump/ipfix.configuration

Can someone let me know what is going wrong?

edited Nov 22 at 15:22

Per Lundberg

1,60812030

asked Nov 22 at 12:51

tuk

1,49512151

I am trying to start a java process with JMX like below

java -XX:MaxPermSize=256m 

    -XX:OnOutOfMemoryError=kill -9 %p 

    -Xss256K 

    -Dorg.xerial.snappy.tempdir=/home/ubuntu/tmp 

    -Dlog4j.debug 

    -Dlog4j.defaultInitOverride=true 

    -Dlogdir=/home/ubuntu/logs/flow-processor 

    -DvneraLog4jConfigurationFile=/home/ubuntu/build-target/nfdump/flow-processor.log4j.xml 

    -Dcom.sun.management.jmxremote 

    -Dcom.sun.management.jmxremote.password.file=/home/ubuntu/build-target/nfdump/jmxremote.password 

    -Dcom.sun.management.jmxremote.access.file=/home/ubuntu/build-target/nfdump/jmxremote.access 

    -Djava.rmi.server.hostname=10.xxx.xxx.xx 

    -Dcom.sun.management.jmxremote.ssl=false 

    -Dcom.sun.management.jmxremote.port=11103 

    -Xmx3604m 

    -Ddeployment.info=IPGQRFG 

    -Ddeployment.id=DPGQGXI 

    -Dsku.info=proxy 

    -DuiAccessUrlPath= 

    -Dreporters.configuration=/home/ubuntu/build-target/nfdump/reporters.configuration 

    -Dreporters.application.name=vRNI 

    -cp /home/ubuntu/build-target/nfdump/flow-processor-0.001-SNAPSHOT.jar 

    com.vnera.ipfix.IpfixProcessor 

    /home/ubuntu/build-target/nfdump/ipfix.configuration

But on start I am getting an exception like below occassionally:

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

sun.management.AgentConfigurationError: java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

        at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(ConnectorBootstrap.java:480)

        at sun.management.Agent.startAgent(Agent.java:262)

        at sun.management.Agent.startAgent(Agent.java:452)

Caused by: java.rmi.server.ExportException: Port already in use: 11103; nested exception is:

        java.net.BindException: Address already in use (Bind failed)

        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:346)

        at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:254)

        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)

        at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)

        at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:236)

        at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213)

        at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:173)

        at sun.management.jmxremote.SingleEntryRegistry.<init>(SingleEntryRegistry.java:49)

        at sun.management.jmxremote.ConnectorBootstrap.exportMBeanServer(ConnectorBootstrap.java:816)

        at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(ConnectorBootstrap.java:468)

        ... 2 more

Caused by: java.net.BindException: Address already in use (Bind failed)

        at java.net.PlainSocketImpl.socketBind(Native Method)

        at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)

        at java.net.ServerSocket.bind(ServerSocket.java:375)

        at java.net.ServerSocket.<init>(ServerSocket.java:237)

        at java.net.ServerSocket.<init>(ServerSocket.java:128)

        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45)

        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:345)

        at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)

        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:335)

        ... 11 more

I am seeing that the java process in question is owning the jmx port 11103:

support@vrni-proxy-release:~$ sudo lsof -i :11103

COMMAND  PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME

java    8011 ubuntu   14u  IPv4  32077      0t0  TCP *:11103 (LISTEN)

Output of ps -ef | grep flow-processor

support@vrni-proxy-release:~$ ps -ef | grep flow-processor

ubuntu    8011  7903  1 Oct17 ?        12:11:07 java -XX:MaxPermSize=256m -XX:OnOutOfMemoryError=kill -9 %p -Xss256K -Dorg.xerial.snappy.tempdir=/home/ubuntu/tmp -Dlog4j.debug -Dlog4j.defaultInitOverride=true -Dlogdir=/home/ubuntu/logs/flow-processor -DvneraLog4jConfigurationFile=/home/ubuntu/build-target/nfdump/flow-processor.log4j.xml -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.password.file=/home/ubuntu/build-target/nfdump/jmxremote.password -Dcom.sun.management.jmxremote.access.file=/home/ubuntu/build-target/nfdump/jmxremote.access -Djava.rmi.server.hostname=10.196.173.49 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=11103 -Xmx3604m -Ddeployment.info=IPGQRFG -Ddeployment.id=DPGQGXI -Dsku.info=proxy -DuiAccessUrlPath= -Dreporters.configuration=/home/ubuntu/build-target/nfdump/reporters.configuration -Dreporters.application.name=vRNI  -cp /home/ubuntu/build-target/nfdump/flow-processor-0.001-SNAPSHOT.jar com.vnera.ipfix.IpfixProcessor /home/ubuntu/build-target/nfdump/ipfix.configuration

Can someone let me know what is going wrong?

java java-8 jmx

edited Nov 22 at 15:22

Per Lundberg

1,60812030

asked Nov 22 at 12:51

tuk

1,49512151

edited Nov 22 at 15:22

Per Lundberg

1,60812030

asked Nov 22 at 12:51

tuk

1,49512151

edited Nov 22 at 15:22

Per Lundberg

1,60812030

edited Nov 22 at 15:22

Per Lundberg

1,60812030

edited Nov 22 at 15:22

Per Lundberg

1,60812030

asked Nov 22 at 12:51

tuk

1,49512151

asked Nov 22 at 12:51

tuk

1,49512151

asked Nov 22 at 12:51

tuk

1,49512151

1

What happens if you specify an alternative port in the -Dcom.sun.management.jmxremote.port= setting? Does it then complain also, about the new port?
– Per Lundberg
Nov 22 at 13:00

Even with the port mentioned here 11103 this issue does not come always. It comes occasionally.
– tuk
Nov 22 at 13:16

1

@PerLundberg - I have read this stackoverflow.com/questions/20884353/…. But I am not sure why should we be setting both com.sun.management.jmxremote.port and com.sun.management.jmxremote.rmi.port to the same value ?
– tuk
Nov 22 at 13:17

Good link, thanks. But a silly question: when this happens, could it be that you have an old instance of flow-processor still running? (I mean: you try to start it, but an old process still exists and that's why it fails.) Could this be the problem?
– Per Lundberg
Nov 22 at 22:25

add a comment |

1

What happens if you specify an alternative port in the -Dcom.sun.management.jmxremote.port= setting? Does it then complain also, about the new port?
– Per Lundberg
Nov 22 at 13:00

Even with the port mentioned here 11103 this issue does not come always. It comes occasionally.
– tuk
Nov 22 at 13:16

1

@PerLundberg - I have read this stackoverflow.com/questions/20884353/…. But I am not sure why should we be setting both com.sun.management.jmxremote.port and com.sun.management.jmxremote.rmi.port to the same value ?
– tuk
Nov 22 at 13:17

Good link, thanks. But a silly question: when this happens, could it be that you have an old instance of flow-processor still running? (I mean: you try to start it, but an old process still exists and that's why it fails.) Could this be the problem?
– Per Lundberg
Nov 22 at 22:25

What happens if you specify an alternative port in the -Dcom.sun.management.jmxremote.port= setting? Does it then complain also, about the new port?
– Per Lundberg
Nov 22 at 13:00

Even with the port mentioned here 11103 this issue does not come always. It comes occasionally.
– tuk
Nov 22 at 13:16

@PerLundberg - I have read this stackoverflow.com/questions/20884353/…. But I am not sure why should we be setting both com.sun.management.jmxremote.port and com.sun.management.jmxremote.rmi.port to the same value ?
– tuk
Nov 22 at 13:17

Good link, thanks. But a silly question: when this happens, could it be that you have an old instance of flow-processor still running? (I mean: you try to start it, but an old process still exists and that's why it fails.) Could this be the problem?
– Per Lundberg
Nov 22 at 22:25

add a comment |

active

oldest

votes

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53431457%2fjava-rmi-server-exportexception-port-already-in-use-when-enabling-jmx%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

active

oldest

votes

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Qfyilyi