Hi Dan, MS-Outlook usually blocks this port, you might also consider to tell windows to not use ports in a certain range. Unfortunately I didn't find the required registry right now.
greetings, Achim 2011/3/3 Andreas Pieber <[email protected]>: > np, good to hear, that this solved your problem. > > kind regards, Andreas > > On Mar 3, 2011 5:31 AM, "Dan Tran" <[email protected]> wrote: >> forgot to mention port 1099 is problem port. >> >> -D >> >> On Wed, Mar 2, 2011 at 8:25 PM, Dan Tran <[email protected]> wrote: >>> You are absolutely right, ( hit my head for not able to translate >>> 'bind' issue provided by the log ) >>> >>> Big Thanks >>> >>> -Dan >>> >>> On Wed, Mar 2, 2011 at 7:42 PM, Andreas Pieber <[email protected]> >>> wrote: >>>> I know this problem. It seams that this port is already used by some >>>> other Windows-Service. Please try to reconfigure the jmx port in >>>> etc/org.apache.karaf.management.cfg >>>> >>>> Kind regards, >>>> Andreas >>>> >>>> On Thu, Mar 3, 2011 at 1:06 AM, Dan Tran <[email protected]> wrote: >>>>> Hello, >>>>> >>>>> I am a Karaf newbie trying to get Karaf to run on my windows 7 >>>>> professional ( got it working on Linux, and windows vista ) and run >>>>> into some >>>>> exception when starting karaf with bin/karaf.bat >>>>> >>>>> The issue has something to do with JMX permission, and I could not >>>>> find any similar issue on user group ). >>>>> Can someone help? Here is the log >>>>> >>>>> __ __ ____ >>>>> / //_/____ __________ _/ __/ >>>>> / ,< / __ `/ ___/ __ `/ /_ >>>>> / /| |/ /_/ / / / /_/ / __/ >>>>> /_/ |_|\__,_/_/ \__,_/_/ >>>>> >>>>> Apache Karaf (2.2.0) >>>>> >>>>> Hit '' for a list of available commands >>>>> and '[cmd] --help' for help on a specific command. >>>>> Hit 'Exception in thread "JMX Connector Thread >>>>> >>>>> [service:jmx:rmi://localhost:44444/jndi/rmi://localhost:1099/karaf-root]" >>>>> java.lang.RuntimeException: Could not start JMX connector server >>>>> at >>>>> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:104) >>>>> Caused by: java.io.IOException: Cannot bind to URL >>>>> [rmi://localhost: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:804) >>>>> at >>>>> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:417) >>>>> at >>>>> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:102) >>>>> 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:126) >>>>> at >>>>> com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208) >>>>> at javax.naming.InitialContext.bind(InitialContext.java:400) >>>>> at >>>>> javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:625) >>>>> at >>>>> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412) >>>>> ... 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:396) >>>>> at >>>>> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:250) >>>>> at sun.rmi.transport.Transport$1.run(Transport.java:159) >>>>> at java.security.AccessController.doPrivileged(Native Method) >>>>> at sun.rmi.transport.Transport.serviceCall(Transport.java:155) >>>>> at >>>>> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) >>>>> at >>>>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) >>>>> at >>>>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>>>> at java.lang.Thread.run(Thread.java:619) >>>>> ' or ' at >>>>> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255) >>>>> at >>>>> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233) >>>>> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:359) >>>>> at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source) >>>>> at >>>>> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:120) >>>>> osgi:shutdown ... 5 more >>>>> Caused by: java.rmi.AccessException: Cannot modify this registry >>>>> ' to shutdown Karaf. >>>>> at >>>>> sun.management.jmxremote.SingleEntryRegistry.bind(SingleEntryRegistry.java:61) >>>>> >>>>> at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source) >>>>> at >>>>> sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:386) >>>>> at >>>>> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:250) >>>>> at sun.rmi.transport.Transport$1.run(Transport.java:159) >>>>> at java.security.AccessController.doPrivileged(Native Method) >>>>> at sun.rmi.transport.Transport.serviceCall(Transport.java:155) >>>>> at >>>>> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) >>>>> at >>>>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) >>>>> at >>>>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>>>> at java.lang.Thread.run(Thread.java:619) >>>>> >>>>> >>>>> Big thanks >>>>> >>>>> -Dan >>>>> >>>>> PS. This is a resend from my gmail account. The last one thru nabble >>>>> which has not been accepted since 4 days ago >>>>> >>>> >>> >
