Registry.rebind disallowed; origin /11.0.10.31 is non-local host.

Hello everyone.
I have a problem.
I have a server that I register in the RMI registry. Client from a remote machine get the server (as a remote object) and calls his method for the generation of another object on the parameters passed. The server creates this object and tries to register it in the RMI registry, and this raises an exception Registry.Registry.rebind disallowed; origin /11.0.10.31 is non-local host.
What could be the problem and how to solve it?
Thanks.

Ah, this is the problem. It's a bit difficult to explain but if you create an in-JVM Registry and then call rebind() on the result while executing a remote method on behalf of a client, your are doing a local method invocation on the Registry instance so the client host appears to be the calling client rather than yourself. Change the rebind() call to use Naming.rebind() and the problem will go away.

Similar Messages

Java.rmi.AccessException: Registry.Registry.rebind disallowed

I am getting the following error while creating a client socket. I am not exactly sure what is causing the problem.
This is happening on windows 2k3 sp2 French dual stack machine.
java.rmi.AccessException: Registry.Registry.rebind disallowed; origin /fe80:0:0:0:219:b9ff:fe00:d81d is non-local host:java.rmi.AccessException: Registry.Registry.rebind disallowed; origin /fe80:0:0:0:219:b9ff:fe00:d81d is non-local host
And also I observed the server socket is something different to the normal one ..
ServerSocket[addr=::/0:0:0:0:0:0:0:0,port=0,localport=11501
Normally it will be 0.0.0.0/0.0.0.0. I don't know why it is different....
Any pointers why I am getting that exception and the server socket is =::/0:0:0:0:0:0:0:0?
Edited by: shash10 on Jun 9, 2008 12:07 AM
Edited by: shash10 on Jun 9, 2008 12:36 AM

I am getting the following error while creating a client socket.No, you're getting it while calling Registry.rebind(), because you're doing that from a client that isn't on the same host as the Registry, and that's illegal, as the exception text says. Nothing to do with IPv6 actually.

Rebind invoked from non-local host (AccessException)

Hi all,
I have a simple RMI setup where a client class asks for a new object from a server class, however, I use this call to create the new object on the server and then attempt to register it with the rmiregistry before passing the remote reference back (ie UnicastRemoteObject). This is because I want the client to access a new remote object on the server (the new object may not be serializable).
The problem is after I tried it with a remote machine, I got an AccessException, Registry.rebind disallowed. This seems to be because you can't get a client (non-local) to affect the registry for security. Fair enough. Although I thought becuase it is a method on the server which does the actual object creation and registration that it IS local and it would work...
any comments...?
is there a way around this...?
Thanks in advance,
Toby

Hi...You can rebind a object only from the local machine...RMI does not allow remote binding of the objects because of security reasons and whenever you try to do so you get an Access Exception.
Hope this Helps.

Rmi Registry rebind problem

hi
I have used the Registry.rebind method in my program. The problem I am facing is like this;
when I use the rebind method as 'registry.rebind("Server",this);' it is working fine; but when I use
String name="Server";
'registry.rebind(name,this);' it is giving the following error: java.rmi.NotBoundException: Server.
Any suggestions?
thnx
Som

have you try
final static String name = "Server";

Get the original loading bar in Safari 4 (non beta) ?

I am trying to get the original loading bar from Safari 3 into the official release of Safari 4. Is there any way to do this?
Thanks,
F.N.H.

Greetings,
Sorry, but there's no way to do that.

Simple question about java.rmi.registry.Registry

Hi,
where the object java.rmi.registry.Registry takes a URL to rmiregistry when perform bind method.
thanks.

Ok, will try to explain.
I have a server that I register in the RMI registry. Client from a remote machine get the server (as a remote object) and calls his method for the generation of another object on the parameters passed. The server creates this object and tries to register it in the RMI registry, and this raises an exception Registry.Registry.rebind disallowed; origin /11.0.10.31 is non-local host.
11.0.10.31 is a IP - address of the client

Startup Problems Application Server on Fedora Core 5

Greetings All;
Little background information
router ip address: 192.168.1.1
web server ip address: 192.168.1.101 (outside: dcrumb.homeip.net)
installed from ip address: 192.168.1.100
using jdk-1.5.0_07
here are my applicable firewall rules:
-A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 4848 -j ACCEPT
-A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 8080 -j ACCEPT
-A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 8181 -j ACCEPT
-A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 8686 -j ACCEPT
I've also forwarded these ports in my Linksys router
Here are my error messages:
[#|2006-06-14T22:30:13.251-0400|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
/usr/share/jdk1.5.0_07/bin/java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=/opt/SUNWappserver/domains/domain1/logs/server.log
-Djava.endorsed.dirs=/opt/SUNWappserver/lib/endorsed
-Djava.security.policy=/opt/SUNWappserver/domains/domain1/config/server.policy
-Djava.security.auth.login.config=/opt/SUNWappserver/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=/opt/SUNWappserver/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=/opt/SUNWappserver/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=/usr/share/jdk1.5.0_07/jre/lib/ext:/opt/SUNWappserver/domains/domain1/lib/ext:/opt/SUNWappserver/derby/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=/opt/SUNWappserver/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=/opt/SUNWappserver/config
-Djava.library.path=/usr/share/jdk1.5.0_07/jre/lib/i386/client:/usr/share/jdk1.5.0_07/jre/lib/i386/client:/usr/share/jdk1.5.0_07/jre/lib/i386:/usr/share/jdk1.5.0_07/jre/../lib/i386:/opt/SUNWappserver/lib:/usr/lib/lwp:/opt/SUNWappserver/lib:/usr/lib/lwp:/usr/share/jdk1.5.0_07/jre/lib/i386/client:/usr/share/jdk1.5.0_07/jre/lib/i386:/usr/share/jdk1.5.0_07/jre/../lib/i386:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib:
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
/usr/share/jdk1.5.0_07/lib/tools.jar:/opt/SUNWappserver/lib/appserv-rt.jar:/opt/SUNWappserver/lib/admin-cli.jar:/opt/SUNWappserver/lib/jax-qname.jar:/opt/SUNWappserver/lib/appserv-cmp.jar:/opt/SUNWappserver/lib/jaxrpc-impl.jar:/opt/SUNWappserver/lib/commons-launcher.jar:/opt/SUNWappserver/lib/jmxremote_optional.jar:/opt/SUNWappserver/lib/j2ee-svc.jar:/opt/SUNWappserver/lib/commons-logging.jar:/opt/SUNWappserver/lib/mail.jar:/opt/SUNWappserver/lib/dom.jar:/opt/SUNWappserver/lib/appserv-jstl.jar:/opt/SUNWappserver/lib/jaxr-impl.jar:/opt/SUNWappserver/lib/j2ee.jar:/opt/SUNWappserver/lib/jsf-api.jar:/opt/SUNWappserver/lib/jsf-impl.jar:/opt/SUNWappserver/lib/saaj-api.jar:/opt/SUNWappserver/lib/appserv-upgrade.jar:/opt/SUNWappserver/lib/jaxr-api.jar:/opt/SUNWappserver/lib/xsdlib.jar:/opt/SUNWappserver/lib/saaj-impl.jar:/opt/SUNWappserver/lib/rmissl.jar:/opt/SUNWappserver/lib/relaxngDatatype.jar:/opt/SUNWappserver/lib/xercesImpl.jar:/opt/SUNWappserver/lib/xalan.jar:/opt/SUNWappserver/lib/appserv-admin.jar:/opt/SUNWappserver/lib/appserv-ext.jar:/opt/SUNWappserver/lib/jaxrpc-api.jar:/opt/SUNWappserver/lib/activation.jar:/opt/SUNWappserver/lib/jmxremote.jar:/opt/SUNWappserver/lib/install/applications/jmsra/imqjmsra.jar:/opt/SUNWappserver/imq/lib/jaxm-api.jar:/opt/SUNWappserver/imq/lib/fscontext.jar:/opt/SUNWappserver/lib/ant/lib/ant.jar
com.sun.enterprise.server.PEMain
start
display|#]
[#|2006-06-14T22:30:29.526-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [/opt/SUNWappserver/imq/bin].|#]
[#|2006-06-14T22:30:29.537-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2006-06-14T22:30:33.433-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0046:The Platform MBeanServer is available. It will be used to register Application Server MBeans. Platform MBeans will also be available for browsing while using standard JMX Console.|#]
[#|2006-06-14T22:30:33.461-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-06-14T22:30:34.381-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-06-14T22:30:37.708-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2006-06-14T22:30:37.769-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2006-06-14T22:30:41.921-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
[#|2006-06-14T22:30:44.285-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
[#|2006-06-14T22:30:44.322-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
[#|2006-06-14T22:30:49.383-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2006-06-14T22:31:15.145-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2006-06-14T22:31:17.679-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 75388332422004736|#]
[#|2006-06-14T22:31:19.824-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2006-06-14T22:31:19.826-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2006-06-14T22:31:20.540-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 75388332902776832|#]
[#|2006-06-14T22:31:21.303-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2006-06-14T22:31:21.542-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
[#|2006-06-14T22:31:21.995-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
[#|2006-06-14T22:31:22.758-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2006-06-14T22:31:23.256-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
[#|2006-06-14T22:31:23.306-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
[#|2006-06-14T22:31:23.320-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2006-06-14T22:31:23.350-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
[#|2006-06-14T22:31:23.931-0400|INFO|sun-appserver-pe8.2|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
[#|2006-06-14T22:31:33.650-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
[#|2006-06-14T22:31:33.651-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2006-06-14T22:31:33.720-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2006-06-14T22:31:34.266-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]
[#|2006-06-14T22:31:34.268-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2006-06-14T22:31:34.290-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2006-06-14T22:31:34.523-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
[#|2006-06-14T22:31:34.524-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2006-06-14T22:31:34.546-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2006-06-14T22:31:35.616-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]3 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://dcrumb.homeip.net:8686/management/rmi-jmx-connector]: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]|#]
[#|2006-06-14T22:31:35.619-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://dcrumb.homeip.net:8686/management/rmi-jmx-connector]: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:104)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.io.IOException: Cannot bind to URL [rmi://dcrumb.homeip.net:8686/management/rmi-jmx-connector]: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]
at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
at com.sun.enterprise.admin.jmx.remote.server.JmxConnectorServerDriver.startConnectorServer(JmxConnectorServerDriver.java:177)
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:95)
... 3 more
Caused by: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
... 5 more
Caused by: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:385)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
... 9 more
Caused by: java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host
at sun.rmi.registry.RegistryImpl.checkAccess(RegistryImpl.java:223)
at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:119)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
|#]
[#|2006-06-14T22:31:35.629-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2006-06-14T22:31:35.630-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2006-06-14T22:31:35.639-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:122)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:414)
at com.sun.enterprise.server.PEMain.run(PEMain.java:317)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
|#]
[#|2006-06-14T22:31:35.642-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2006-06-14T22:31:35.665-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2006-06-14T22:31:35.708-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2006-06-14T22:31:35.728-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2006-06-14T22:31:36.657-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2006-06-14T22:31:36.675-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2006/06/14 22:31:36]|#]
[#|2006-06-14T22:31:36.676-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2006-06-14T22:31:36.686-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
[#|2006-06-14T22:31:36.687-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2006-06-14T22:31:36.688-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2006-06-14T22:31:38.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2006-06-14T22:31:39.375-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
[#|2006-06-14T22:31:39.376-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
[#|2006-06-14T22:31:39.452-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2006-06-14T22:31:39.482-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
Does anybody have any suggestions?
Many thanks,
Best,
--Dave
Message was edited by CrumbDav
I did some more research and looked in my domain.xml file and came across this. Not sure if it helps any:
- <configs>
- <config dynamic-reconfiguration-enabled="true" name="server-config">
- <http-service>
<http-listener acceptor-threads="5" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-1" port="8080" security-enabled="false" server-name="" xpowered-by="true" />
<http-listener acceptor-threads="5" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-2" port="8181" security-enabled="true" server-name="" xpowered-by="true" />
<http-listener acceptor-threads="5" address="0.0.0.0" blocking-enabled="false" default-virtual-server="__asadmin" enabled="true" family="inet" id="admin-listener" port="4848" security-enabled="false" server-name="" xpowered-by="true" />
- <virtual-server hosts="${com.sun.aas.hostName}" http-listeners="http-listener-1,http-listener-2" id="server" log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
<property name="docroot" value="${com.sun.aas.instanceRoot}/docroot" />
<property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access" />
</virtual-server>
- <virtual-server default-web-module="admingui" hosts="${com.sun.aas.hostName}" http-listeners="admin-listener" id="__asadmin" log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
<property name="docroot" value="${com.sun.aas.instanceRoot}/docroot" />
<property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access" />
</virtual-server>
</http-service>
- <iiop-service client-authentication-required="false">
<orb max-connections="1024" message-fragment-size="1024" use-thread-pool-ids="thread-pool-1" />
<iiop-listener address="0.0.0.0" enabled="true" id="orb-listener-1" port="3700" security-enabled="false" />
- <iiop-listener address="0.0.0.0" enabled="true" id="SSL" port="3820" security-enabled="true">
<ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true" />
</iiop-listener>
- <iiop-listener address="0.0.0.0" enabled="true" id="SSL_MUTUALAUTH" port="3920" security-enabled="true">
<ssl cert-nickname="s1as" client-auth-enabled="true" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true" />
</iiop-listener>
</iiop-service>

Nope - it's not supported. It is useable though ...
The problem is that the Fedora series uses cutting edge technology. The Fedora technology cycles every 6-9 months.
Oracle likes things very stable. So Oracle builds a clean copy using a specific set of APIs at a specific release of the kernel, the glibc and so on. They chose the commercial releases which cycle every 18-24 months - in part so they can get people trained to provide support.
Due to the nature of Linux, you CAN install the correct APIs and get it to work and many of the free distros. Just don't expect Oracle to provide assistance or support. (After all, where do they stop - there are hundreds of free distros, and even more when you count the 'objsolete but still running' ones.)
If you really want to proceed, then you need to read up the cookbook sites from experts such as Ivan Kartik (http://ivan.kartik.sk/) or Werner Puschitz (http://www.puschitz.com) As long as you realize that the install is NOT recommended for production.

JMXConnectorServer.start() causes java.rmi.AccessException

Hi all,
I've already posted this message to the tomcat mailing list as well as to the jmx forum, but without any result.
I've a web service running inside tomcat which
creates the jmx stuff needed to manage resources:
LocateRegistry.createRegistry(port);
String localhost = InetAddress.getLocalHost().getCanonicalHostName();
MBeanServer mbs = MBeanServerFactory.createMBeanServer();
// it is the same with getPlatformMBean
JMXServiceURL url = new JMXServiceURL("service:jmx:rmi:///jndi/rmi://" + localhost + ":"
+ port + "/qosp");
JMXConnectorServer cs =
JMXConnectorServerFactory.newJMXConnectorServer(url, null, mbs);
cs.start();The problem is that I get a java.rmi.AcessException -- see below -- when the cs.start() call is executed (on linux machines only -- it works fine on Windows)
The problem seems to be the following:
Caused by: java.rmi.ServerException: RemoteException occurred in
server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /
128.240.229.70 is non-local host
However my machine does not have that address, and actually I have no idea what it is.
Any clue?
Michele
Nov 6, 2006 11:55:01 AM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path: .:/Library/Java/Extensions:/System/Library/Java/
Extensions:/usr/lib/java
Nov 6, 2006 11:55:01 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Nov 6, 2006 11:55:01 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 666 ms
Nov 6, 2006 11:55:02 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Nov 6, 2006 11:55:02 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.15
Nov 6, 2006 11:55:02 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Nov 6, 2006 11:55:02 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive axis2.war
2006-11-06 11:55:03,668 INFO
org.apache.axis2.deployment.DeploymentEngine - Deploying module :
addressing-1.1
2006-11-06 11:55:03,682 INFO
org.apache.axis2.deployment.DeploymentEngine - Deploying module :
managerInterceptor
2006-11-06 11:55:03,690 INFO
org.apache.axis2.deployment.DeploymentEngine - Deploying module :
soapmonitor-1.1
2006-11-06 11:55:03,890 INFO ncl.qosp.controller.LifecycleSupport -
Qosp jmx is starting up...
org.apache.axis2.deployment.DeploymentException: Processing
Operations Modules Unable to start the connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Unable to start the
connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Processing
Operations Modules Unable to start the connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Unable to start the
connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:124)
at org.apache.axis2.deployment.DeploymentEngine.doDeploy
(DeploymentEngine.java:528)
at org.apache.axis2.deployment.repository.util.WSInfoList.update
(WSInfoList.java:196)
at org.apache.axis2.deployment.RepositoryListener.update
(RepositoryListener.java:227)
at org.apache.axis2.deployment.RepositoryListener.checkServices
(RepositoryListener.java:174)
at org.apache.axis2.deployment.DeploymentEngine.loadServices
(DeploymentEngine.java:88)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices
(WarBasedAxisConfigurator.java:252)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfiguration
Context(ConfigurationContextFactory.java:72)
at org.apache.axis2.transport.http.AxisServlet.initConfigContext
(AxisServlet.java:373)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:
317)
at org.apache.catalina.core.StandardWrapper.loadServlet
(StandardWrapper.java:1105)
at org.apache.catalina.core.StandardWrapper.load
(StandardWrapper.java:932)
at org.apache.catalina.core.StandardContext.loadOnStartup
(StandardContext.java:3915)
at org.apache.catalina.core.StandardContext.start
(StandardContext.java:4176)
at org.apache.catalina.core.ContainerBase.addChildInternal
(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild
(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:
524)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:
804)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:
693)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:
472)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118)
at org.apache.catalina.startup.HostConfig.lifecycleEvent
(HostConfig.java:310)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
1020)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
1012)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:
442)
at org.apache.catalina.core.StandardService.start
(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:
700)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules Unable to start the connector; nested
exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Unable to start the
connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector
at org.apache.axis2.deployment.ServiceBuilder.populateService
(ServiceBuilder.java:320)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGr
oup(ArchiveReader.java:76)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:118)
... 35 more
Caused by: org.apache.axis2.deployment.DeploymentException: Unable to
start the connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector
at
org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass
(ServiceBuilder.java:349)
at org.apache.axis2.deployment.ServiceBuilder.populateService
(ServiceBuilder.java:127)
... 37 more
Caused by: java.lang.RuntimeException: Unable to start the connector
at ncl.qosp.controller.LifecycleSupport.initRemoteJmx
(LifecycleSupport.java:192)
at ncl.qosp.controller.LifecycleSupport.startUp
(LifecycleSupport.java:132)
at
org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass
(ServiceBuilder.java:345)
... 38 more
Caused by: java.io.IOException: Cannot bind to URL [rmi://
sealbook.ncl.ac.uk:10099/qosp]: javax.naming.NoPermissionException
[Root exception is java.rmi.ServerException: RemoteException occurred
in server thread; nested exception is:
       java.rmi.AccessException: Registry.Registry.bind disallowed; origin /
128.240.229.70 is non-local host]
at javax.management.remote.rmi.RMIConnectorServer.newIOException
(RMIConnectorServer.java:814)
at javax.management.remote.rmi.RMIConnectorServer.start
(RMIConnectorServer.java:431)
at ncl.qosp.controller.LifecycleSupport.initRemoteJmx
(LifecycleSupport.java:190)
... 40 more
Caused by: javax.naming.NoPermissionException [Root exception is
java.rmi.ServerException: RemoteException occurred in server thread;
nested exception is:
       java.rmi.AccessException: Registry.Registry.bind disallowed; origin /
128.240.229.70 is non-local host]
at com.sun.jndi.rmi.registry.RegistryContext.bind
(RegistryContext.java:122)
at com.sun.jndi.toolkit.url.GenericURLContext.bind
(GenericURLContext.java:208)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at javax.management.remote.rmi.RMIConnectorServer.bind
(RMIConnectorServer.java:635)
at javax.management.remote.rmi.RMIConnectorServer.start
(RMIConnectorServer.java:427)
... 41 more
Caused by: java.rmi.ServerException: RemoteException occurred in
server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /
128.240.229.70 is non-local host
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:
385)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run
(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:613)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer
(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall
(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at com.sun.jndi.rmi.registry.RegistryContext.bind
(RegistryContext.java:116)
... 45 more
Caused by: java.rmi.AccessException: Registry.Registry.bind
disallowed; origin /128.240.229.70 is non-local host
at sun.rmi.registry.RegistryImpl.checkAccess(RegistryImpl.java:223)
at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:119)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:
375)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run
(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:613)
2006-11-06 11:55:04,041 ERROR
org.apache.axis2.deployment.DeploymentEngine - Invalid service
RoutingService.aar due to Processing Operations Modules Unable to
start the connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Unable to start the
connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Processing
Operations Modules Unable to start the connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Unable to start the
connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector
org.apache.axis2.deployment.DeploymentException: Processing
Operations Modules Unable to start the connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Unable to start the
connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Processing
Operations Modules Unable to start the connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Unable to start the
connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:124)
at org.apache.axis2.deployment.DeploymentEngine.doDeploy
(DeploymentEngine.java:528)
at org.apache.axis2.deployment.repository.util.WSInfoList.update
(WSInfoList.java:196)
at org.apache.axis2.deployment.RepositoryListener.update
(RepositoryListener.java:227)
at org.apache.axis2.deployment.RepositoryListener.checkServices
(RepositoryListener.java:174)
at org.apache.axis2.deployment.DeploymentEngine.loadServices
(DeploymentEngine.java:88)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices
(WarBasedAxisConfigurator.java:252)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfiguration
Context(ConfigurationContextFactory.java:72)
at org.apache.axis2.transport.http.AxisServlet.initConfigContext
(AxisServlet.java:373)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:
317)
at org.apache.catalina.core.StandardWrapper.loadServlet
(StandardWrapper.java:1105)
at org.apache.catalina.core.StandardWrapper.load
(StandardWrapper.java:932)
at org.apache.catalina.core.StandardContext.loadOnStartup
(StandardContext.java:3915)
at org.apache.catalina.core.StandardContext.start
(StandardContext.java:4176)
at org.apache.catalina.core.ContainerBase.addChildInternal
(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild
(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:
524)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:
804)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:
693)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:
472)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118)
at org.apache.catalina.startup.HostConfig.lifecycleEvent
(HostConfig.java:310)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
1020)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
1012)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:
442)
at org.apache.catalina.core.StandardService.start
(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:
700)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules Unable to start the connector; nested
exception is:
java.lang.RuntimeException: Unable to start the connector; nested
exception is:
org.apache.axis2.deployment.DeploymentException: Unable to start the
connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector
at org.apache.axis2.deployment.ServiceBuilder.populateService
(ServiceBuilder.java:320)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGr
oup(ArchiveReader.java:76)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:118)
... 35 more
Caused by: org.apache.axis2.deployment.DeploymentException: Unable to
start the connector; nested exception is:
java.lang.RuntimeException: Unable to start the connector
at
org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass
(ServiceBuilder.java:349)
at org.apache.axis2.deployment.ServiceBuilder.populateService
(ServiceBuilder.java:127)
... 37 more
Caused by: java.lang.RuntimeException: Unable to start the connector
at ncl.qosp.controller.LifecycleSupport.initRemoteJmx
(LifecycleSupport.java:192)
at ncl.qosp.controller.LifecycleSupport.startUp
(LifecycleSupport.java:132)
at
org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass
(ServiceBuilder.java:345)
... 38 more
Caused by: java.io.IOException: Cannot bind to URL [rmi://
sealbook.ncl.ac.uk:10099/qosp]: javax.naming.NoPermissionException
[Root exception is java.rmi.ServerException: RemoteException occurred
in server thread; nested exception is:
       java.rmi.AccessException: Registry.Registry.bind disallowed; origin /
128.240.229.70 is non-local host]
at javax.management.remote.rmi.RMIConnectorServer.newIOException
(RMIConnectorServer.java:814)
at javax.management.remote.rmi.RMIConnectorServer.start
(RMIConnectorServer.java:431)
at ncl.qosp.controller.LifecycleSupport.initRemoteJmx
(LifecycleSupport.java:190)
... 40 more
Caused by: javax.naming.NoPermissionException [Root exception is
java.rmi.ServerException: RemoteException occurred in server thread;
nested exception is:
       java.rmi.AccessException: Registry.Registry.bind disallowed; origin /
128.240.229.70 is non-local host]
at com.sun.jndi.rmi.registry.RegistryContext.bind
(RegistryContext.java:122)
at com.sun.jndi.toolkit.url.GenericURLContext.bind
(GenericURLContext.java:208)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at javax.management.remote.rmi.RMIConnectorServer.bind
(RMIConnectorServer.java:635)
at javax.management.remote.rmi.RMIConnectorServer.start
(RMIConnectorServer.java:427)
... 41 more
Caused by: java.rmi.ServerException: RemoteException occurred in
server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /
128.240.229.70 is non-local host
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:
385)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run
(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:613)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer
(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall
(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at com.sun.jndi.rmi.registry.RegistryContext.bind
(RegistryContext.java:116)
... 45 more
Caused by: java.rmi.AccessException: Registry.Registry.bind
disallowed; origin /128.240.229.70 is non-local host
at sun.rmi.registry.RegistryImpl.checkAccess(RegistryImpl.java:223)
at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:119)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:
375)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run
(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:613)
2006-11-06 11:55:04,180 INFO
org.apache.axis2.deployment.DeploymentEngine - Deploying Web service
version.aar
Nov 6, 2006 11:55:04 AM org.apache.coyote.http11.Http11BaseProtocol
start
INFO: Starting Coyote HTTP/1.1 on http-8080
Nov 6, 2006 11:55:04 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Nov 6, 2006 11:55:04 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/26 config=null
Nov 6, 2006 11:55:04 AM org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Nov 6, 2006 11:55:04 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 2979 ms

Is it possible that
InetAddress.getLocalHost().getCanonicalHostName() is
returning a bogus name? Could you replace it with
.getHostName()?Yes, I did it, but nothing changed, so I tried to hardcode the 'localhost' when I create the JMXServiceURL instead of using the value returned by InetAddress.getLocalHost().get* and it worked.
Could it be because of network settings (I'm running behind a proxy)?
Thanks,
Michele

Multihomed Machine and RMI

I am attempting to start rmid on a multihomed Win2k Server running J2SE 1.4.1. It seems that rmid is selecting one of the interfaces and deciding that it is non-local, then it exits with an error.
Can somebody tell me how to work around this problem?
See below for the traceback.
Thanks,
Neil
====================================================
C:\jini1_2_1_001\example\lookup>rmid -J-Djava.security.policy=policy.all
Tue Nov 26 12:17:28 GMT 2002:ExecGroup-0:err:Exception in starting ActivationGroupInit:
Tue Nov 26 12:17:28 GMT 2002:ExecGroup-0:err:java.rmi.activation.ActivationException: exception creating group; nested exception is:
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.ActivationSystem.activeGroup disallowed; origin /47.109.119.1 is non-local host
Tue Nov 26 12:17:28 GMT 2002:ExecGroup-0:err: at java.rmi.activation.ActivationGroup.createGroup(ActivationGroup.java:345)
...........[ SNIP ]..........
C:\Jini and JavaSpaces\Jini Download\jini1_2_1_001\example\lookup>java -version
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)

This happens if Java can't create a ServerSocket bound to that IP address, which is the test it uses to ensure the IP address is local. This could be a permissions problem.

RemoteException LOCALHOST is non-local host

Hello RMI gurus,
I am trying to run an example RMI application to get a better understanding of how RMI works, but I have encountered this problem. The error I am getting is this:
Error: RemoteException occured in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.rebind disallowed;
origin
LOCALHOST/127.0.0.1 is non-local host
I have the rmiregistry running on the default port on the same system that I am trying to run the server part of the program, and am using Java 1.3. Here is how I start the program:
java -Djava.rmi.server.codebase=file:///java/verify/ -cp /java/verify FibonacciServerAlso, I bind my object to rmi with this call in the FibonacciServer class:
Naming.bind("fibonacci", f);
I am guessing it is choking on this.
Any way...thanks in advance for any help with this!
C.M.

Naming.bind("fibonacci", f);
Naming.bind("//localhost/fibonacci",f);You can add rmi: in front of localhost but it is not essential.

Rmi bind and register

I tried to bind an object onto a remote registry which is running on remote site, but I got an error saying that binding was denied. I use sun package. Do u have any idea about this?

per the API docs, The Naming.bind method throws an AccessException "if this operation is not permitted (if originating from a non-local host, for example)"
Lee

RMIRegistry and Server on different Machines

Is it possible to run rmiregistry on one machine and then bind an object from a different machine to this registry. I can't find any documentation to say that you can't.
If i try to, i get a hostname is a non-local host Exception.

What im actually doing is this :
I have a client program that wishes to transport some C code to a server for execution on that server. This would be simple enough but the client should not be concerned with where the server is, but only needs to know a name server that holds all object and server names so as they can then query this one registry for a server name and then connect to this server.
I was hoping that you could run rmiregistry on one machine, a server on another, bind that server object to the registry and then connect to the server from the client via the registry.
I have written my own registry object that implements this fine but i wanted to know whether this was a long winded way. Surely RMI is a java developers alternative to CORBA (according to sun web site !), in which this would be possible with the ORB running on a remote machine to client and server?

Can anybody help me to understand this RMI registry service code?

RMI is so difficult to me. please let me know following code what it means.
If this class is instantiated with 50000 port number,
Does RMI Registry Service get started with 50000 port number in place of rmiregistry commands?
And I don't have to execute rmiregistry command?
thanks in advance.
import java.rmi.AccessException;
import java.rmi.AlreadyBoundException;
import java.rmi.NotBoundException;
import java.rmi.Remote;
import java.rmi.RemoteException;
import java.rmi.registry.Registry;
import java.rmi.server.ObjID;
import java.rmi.server.RemoteServer;
import java.util.Enumeration;
import java.util.Hashtable;
import sun.rmi.server.UnicastServerRef;
import sun.rmi.transport.LiveRef;
* Registry implementation.
* @version 1.0
public class RegistryImpl extends RemoteServer implements Registry {
     private static final long serialVersionUID = -7162736590129110751;
     private Hashtable bindings;
    private static ObjID id = new ObjID(0);
     * @param i port number
     * @throws RemoteException
    public RegistryImpl(int i) throws RemoteException {
        bindings = new Hashtable(101);
        LiveRef liveref = new LiveRef(id, i);
        setup(new UnicastServerRef(liveref));
    private void setup(UnicastServerRef unicastserverref) throws RemoteException {
        super.ref = unicastserverref;
        unicastserverref.exportObject(this, null, true);
     * Lookup a remote object.
     * @param name Name of the remote object.
     * @return Remote object of the specified name.
    public Remote lookup(String name) throws RemoteException, NotBoundException {
//        Logger.debug("NamingService", "lookup: " + name);
        Remote obj;
        synchronized(bindings) {
            obj = (Remote)bindings.get(name);
            if(obj == null)
                throw new NotBoundException(name);
        return obj;
     * Binds the specified name to a remote object.
     * @param name A URL-formatted name for the remote object.
     * @param obj A reference for the remote object (usually a stub).
    public void bind(String name, Remote obj) throws RemoteException, AlreadyBoundException, AccessException {
//        Logger.debug("NamingService", "bind: " + name);
        checkAccess("Registry.bind");
        synchronized(bindings) {
            if(bindings.containsKey(name))
                throw new AlreadyBoundException(name);
            bindings.put(name, obj);
     * Destroys the binding for the specified name that is associated with a remote object.
     * @param name A URL-formatted name for the remote object.
    public void unbind(String name) throws RemoteException, NotBoundException, AccessException {
//        Logger.debug("NamingService", "unbind: " + name);
        checkAccess("Registry.unbind");
        synchronized(bindings) {
            if(!bindings.containsKey(name))
                throw new NotBoundException(name);
            bindings.remove(name);
     * Rebinds the specified name to a new remote object. Any existing binding
     * for the name is replaced.
     * @param name A URL-formatted name for the remote object.
     * @param obj A reference for the remote object (usually a stub).
    public void rebind(String name, Remote obj) throws RemoteException, AccessException {
//        Logger.debug("NamingService", "rebind: " + name);
        checkAccess("Registry.rebind");
        bindings.put(name, obj);
     * Returns an array of the names bound in the registry.
     * @return An array of the names bound in the registry.
    public String[] list() throws RemoteException {
        String[] names;
        synchronized(bindings) {
            int i = bindings.size();
            names = new String;
Enumeration e = bindings.keys();
while(--i >= 0)
names[i] = (String)e.nextElement();
return names;
* TO-DO
public static void checkAccess(String s) throws AccessException {
// check if s is in the list of agents.
if(true)
else
throw new AccessException("");
public static ObjID getID() {
return id;

You don't have any need to understand this code. The complication is due to the registry needing a fixed objectID.
You just need to know the methods of java.rmi.registry.LocateRegistry class. This allows you to start an RMI Registry inside your JVM and give it any TCP port number you like.

RMI registry inside tomcat

Hello,
I'm wondering if any of you have previous experiences in the following situation.
I have a linux server with tomcat 5.0.28 that is supposed to act as an RMI end point for clients connecting with the aforementioned RMI to do some persisting stuff. Now I figured that the easiest way is to create a servlet that creates the RMI registry and binds my server objects (so that's in the servlet's init(), with 1 load-on-startup, the servlet doesn't do anything else, at least yet).
Now problems arise: my linux server is logging "context is read-only" when trying to bind the objects to RMI. Testing on my windows laptop doesn't show the same error for some reason (although it doesn't work properly either). This is apparently normal, as the contexts are supposed to be read-only.
Thing is, I wouldn't want to run a separate rmiregistry on the server, if possible to do it with a simple servlet. But is this the easiest way?
Thank you in advance,
yours truly, in sickness and in health,
Jussi

'Context is read-only' is not a Registry error
message. You are trying to bind to something else.
Show us some code.Well, I'm not doing a lot of binding, so I'm assuming it's this part:
               DDBServer stub = (DDBServer)UnicastRemoteObject.exportObject(this, 0);
               Registry registry = LocateRegistry.getRegistry();
               registry.rebind("DDBServer", stub);The error message is:
2007-04-18 14:06:40 NamingContextListener[Catalina/localhost/DDBServer]: Creation of the naming context failed: javax.naming.NamingException: Context is read only

RMI Registry leaves thread running

I've searched the postings about this topic and none of them have been helpful. I create an RMI registry at port 1099 in my app, use it, and then try to shut it down, but it leaves a thread running.
The following sample code shows what my code does (in a condensed form):
Registry registry = LocateRegistry.createRegistry(1099);
Communicator c = new CommunicatorImpl();
registry.rebind("//localhost/remoteserver", c );
Naming.rebind("rmi://localhost:1099/TriggerService", c);
registry.unbind("//localhost/remoteserver");
Naming.unbind("rmi://localhost:1099/TriggerService");
boolean b = UnicastRemoteObject.unexportObject(registry, true);
System.err.println( "unexported: "+b );When I run this code in Eclipse and the code exits, I still have a process running that was spawned by "LocateRegistry.createRegistry(1099)", but I can't figure out how to get a handle for it within my program, so that I can kill it. I've read that it will end when the JVM ends, but the RMI portion of my app is only a small part and I need the rest of it to keep running. Is there a way to stop this thread?
Thanks,
Tony

Well I only see 'createRegistry' and 'getRegistry' I don't see any 'destroyRegistry' methods. So I don't know.
What I used to do back in the day was to use Runtime to start an external process for processes that I needed to kill later on. So perhaps you can use the runtime to start the registry from the command line so to speak. Then hold a reference to the returned process. Then you can kill that process when you want the registry to die. In this case you will for sure be creating a new 'jvm' for the registry to run within. (if the registry is a java program)
Otherwise I have no idea why you would be seeing an extra java process. If you run the eclipse debugger, the debugger should not exit until the whole process is done. Even when the program is done, the debugger will still be 'live' and you can push the stop button to stop the whole launched process.

Registry.rebind disallowed; origin /11.0.10.31 is non-local host.

Similar Messages

Maybe you are looking for