activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arthur Naseef (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5566) Karaf test fails when standard ports already in-use on the system
Date Wed, 04 Feb 2015 16:25:35 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305437#comment-14305437
] 

Arthur Naseef commented on AMQ-5566:
------------------------------------

*Port 1099 Failure Exception*
{noformat}
karaf@root> Exception in thread "JMX Connector Thread [service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root]"
java.lang.RuntimeException: Could not start JMX connector server
	at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:248)
Caused by: java.io.IOException: Cannot bind to URL [rmi://0.0.0.0:1099/karaf-root]: javax.naming.NoPermissionException
[Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested
exception is: 
	java.rmi.AccessException: Cannot modify this registry]
	at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:826)
	at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
	at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:235)
Caused by: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException:
RemoteException occurred in server thread; nested exception is: 
	java.rmi.AccessException: Cannot modify this registry]
	at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:143)
	at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:226)
	at javax.naming.InitialContext.bind(InitialContext.java:419)
	at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643)
	at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
	... 1 more
Caused by: java.rmi.ServerException: RemoteException occurred in server thread; nested exception
is: 
	java.rmi.AccessException: Cannot modify this registry
	at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:419)
	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:267)
	at sun.rmi.transport.Transport$1.run(Transport.java:177)
	at sun.rmi.transport.Transport$1.run(Transport.java:174)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:556)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
	at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:275)
	at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:252)
	at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:378)
	at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
	at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:137)
	... 5 more
Caused by: java.rmi.AccessException: Cannot modify this registry
	at sun.management.jmxremote.SingleEntryRegistry.bind(SingleEntryRegistry.java:76)
	at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
	at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:409)
	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:267)
	at sun.rmi.transport.Transport$1.run(Transport.java:177)
	at sun.rmi.transport.Transport$1.run(Transport.java:174)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:556)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
{noformat}

> Karaf test fails when standard ports already in-use on the system
> -----------------------------------------------------------------
>
>                 Key: AMQ-5566
>                 URL: https://issues.apache.org/jira/browse/AMQ-5566
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 5.11.0
>            Reporter: Arthur Naseef
>
> Test {{org.apache.activemq.karaf.itest.ActiveMQAMQPBrokerFeatureTest}} fails when either
port 61616 or port 1099 is already in-use on the server.
> Preferably this test would use dynamically allocated port numbers.
> Freeing ports 61616 and 1099 allows the test to pass normally.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message