RMI AccessException
I am using RMI, and every time that I run my server application, I have this Exception
java.rmi.ServerException: Server RemoteException; nested exception is:
java.rmi.AccessException: Registry.rebind 673.89.65.000/673.89.65.000 !=localhost/127.0.0.1
I am using Solaris, can anybody tell me what to do with this exception
Your security manager (probably an RMISecurityManager) is not letting your rebind. What does your policy file say?
Similar Messages
-
Must redeploy app or get java.rmi.AccessException: CORBA NO_PERMISSION 9998
Hello. I'm hoping someone can give me a clue to the source of this problem.
I have a very simple test application which consists of one EJB which is just a stateless session bean that has a method which return the String "Hello". This method can only be run by a user in the "test" role.
I have a simple commandline client packaged in the application. I use deploytool to extract the Client.jar and I can run it with appclient - client myClient.jar. This little class connects to the bean in the server (via jndi lookup as per all tutorial example) and calls the sayHello() method. A login dialog appears in order to authenticate the user as it should and everything works perfectly ... BUT ...
If I stop the server and start it again and try to run the client exactly the same way (appclient - client myClient.jar), I get the error message below. The application is running and I confirm that its there using deploytool and asadmin to list components, etc. The only way I can get it work again is by redeploying the application.
I've looked around and found nothing about this regarding Sun Java System Application Server Platform Edition 8 2004Q4 Beta (which is what I'm using). I found some vague references to a similar sounding problem from people using Application Server 7, but the work around in those posts references switches and settings in deploytool that dont seem to be there in my version.
Can anyone suggest a fix? I'd like the application to work upon starting up the server each morning for example without having to redeploy it. I'm glad to provide my test application archives and sources to anyone who would find them useful for solving this problem.
Thanks!
Error:
java.rmi.AccessException: CORBA NO_PERMISSION 9998 Maybe; nested exception is:
org.omg.CORBA.NO_PERMISSION: ----------BEGIN server-side stack trace----------
org.omg.CORBA.NO_PERMISSION: vmcid: 0x2000 minor code: 1806 completed: Maybe
at com.sun.enterprise.iiop.POAProtocolMgr.mapException(POAProtocolMgr.java:179)
at com.sun.ejb.containers.BaseContainer.authorizeRemoteMethod(BaseContainer.java:908)
at com.sun.ejb.containers.StatelessSessionContainer.createEJBObjectImpl(StatelessSessionContainer.java:274)
at com.sun.ejb.containers.EJBHomeImpl.createEJBObjectImpl(EJBHomeImpl.java:89)
at com.sun.ejb.containers.EJBHomeInvocationHandler.invoke(EJBHomeInvocationHandler.java:140)
at $Proxy15.create(Unknown Source)
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:324)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:123)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:648)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:192)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1683)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1543)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:925)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:181)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:697)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:454)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1188)
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:398)
Caused by: java.rmi.AccessException: Client is not authorized for this invocation.
at com.sun.ejb.containers.BaseContainer.authorizeRemoteMethod(BaseContainer.java:906)
... 19 more
----------END server-side stack trace---------- vmcid: 0x2000 minor code: 1806 completed: Maybe
at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:195)
at javax.rmi.CORBA.Util.mapSystemException(Util.java:65)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:142)
at com.sun.corba.ee.impl.presentation.rmi.bcel.BCELStubBase.invoke(Unknown Source)
at com.dcit.bmj.bmo.interfaces._HelloWorldHome_DynamicStub.create(_HelloWorldHome_DynamicStub.java)
at com.dcit.bmj.client.WasUpClient.main(WasUpClient.java:35)
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:324)
at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:237)
at com.sun.enterprise.appclient.Main.<init>(Main.java:423)
at com.sun.enterprise.appclient.Main.main(Main.java:96)
Caused by: org.omg.CORBA.NO_PERMISSION: ----------BEGIN server-side stack trace----------
org.omg.CORBA.NO_PERMISSION: vmcid: 0x2000 minor code: 1806 completed: Maybe
at com.sun.enterprise.iiop.POAProtocolMgr.mapException(POAProtocolMgr.java:179)
at com.sun.ejb.containers.BaseContainer.authorizeRemoteMethod(BaseContainer.java:908)
at com.sun.ejb.containers.StatelessSessionContainer.createEJBObjectImpl(StatelessSessionContainer.java:274)
at com.sun.ejb.containers.EJBHomeImpl.createEJBObjectImpl(EJBHomeImpl.java:89)
at com.sun.ejb.containers.EJBHomeInvocationHandler.invoke(EJBHomeInvocationHandler.java:140)
at $Proxy15.create(Unknown Source)
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:324)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:123)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:648)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:192)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1683)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1543)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:925)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:181)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:697)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:454)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1188)
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:398)
Caused by: java.rmi.AccessException: Client is not authorized for this invocation.
at com.sun.ejb.containers.BaseContainer.authorizeRemoteMethod(BaseContainer.java:906)
... 19 more
----------END server-side stack trace---------- vmcid: 0x2000 minor code: 1806 completed: Maybe
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.MessageBase.getSystemException(MessageBase.java:902)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSystemException(ReplyMessage_1_2.java:99)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(CorbaMessageMediatorImpl.java:575)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(CorbaClientRequestDispatcherImpl.java:430)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:326)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:132)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:129)
... 10 moreHi Raja.
So Sorry for the delay. Anyway, I've come back to try to do this now and just cant make the problem happen! I'm tearing my hair out to figure out what has changed. In the meantime, I'm going to just move past this. If it shows up again, I'll be sure to post all related files back in this forum.
Thanks! -
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 msIs 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 -
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 AMI 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.
-
Java.rmi.AccessException: CORBA NO_PERMISSION 0 No
i m new to j2ee...deployed "AdviceApp" application successfully given in Head First EJB book to sun RI server...when i run the client which is a simple java application on the same m/c as RI server, i get following error
D:\technical\java\projects\advice>java -cp c:\j2sdkee1.3\lib\j2ee.jar;AdviceAppC
lient.jar;d:\technical\java\projects\advice\ AdviceClient
java.rmi.AccessException: CORBA NO_PERMISSION 0 No; nested exception is:
org.omg.CORBA.NO_PERMISSION: minor code: 0 completed: No
org.omg.CORBA.NO_PERMISSION: minor code: 0 completed: No
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Unknown Source)
at com.sun.corba.ee.internal.iiop.messages.ReplyMessage_1_2.getSystemExc
eption(ReplyMessage_1_2.java:93)
at com.sun.corba.ee.internal.iiop.ClientResponseImpl.getSystemException(
ClientResponseImpl.java:108)
at com.sun.corba.ee.internal.POA.GenericPOAClientSC.invoke(GenericPOACli
entSC.java:136)
at org.omg.CORBA.portable.ObjectImpl._invoke(Unknown Source)
at headfirst._AdviceHome_Stub.create(Unknown Source)
at AdviceClient.go(AdviceClient.java:23)
at AdviceClient.main(AdviceClient.java:11)ne leads will be appreciated.
thnks in advanceNever mind...found the solution
http://java.sun.com/j2ee/sdk_1.3/faq.html#access
had to redeploy the application after security changes. -
Java.rmi.AccessException: CORBA NO_PERMISSION 9998
Hi, Friends,
I am using SUN RI and getting:
java.rmi.AccessException: CORBA NO_PERMISSION 9998
The bean was successfully deployed and the look up for the reference
was successful too and returned an instance:
Object objref = ctx.lookup("ejb/TestConnection");
home =(TestConnectionHome)PortableRemoteObject.narrow(objref,
TestConnectionHome.class);
But when I try to create a bean:
bean = home.create();
I am getting an exception:
Can't create new bean for TestConnection .
java.rmi.AccessException: CORBA NO_PERMISSION 9998 Maybe; nested
exception is:
org.omg.CORBA.NO_PERMISSION: minor code: 9998 completed:
Maybe
java.rmi.AccessException: CORBA NO_PERMISSION 9998 Maybe; nested
exception is:
org.omg.CORBA.NO_PERMISSION: minor code: 9998 completed:
Maybe
org.omg.CORBA.NO_PERMISSION: minor code: 9998 completed: Maybe
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at com.sun.corba.ee.internal.iiop.messages.ReplyMessage_1_2.getSystemExc
eption(ReplyMessage_1_2.java:93)
at com.sun.corba.ee.internal.iiop.ClientResponseImpl.getSystemException(
ClientResponseImpl.java:108)
at com.sun.corba.ee.internal.POA.GenericPOAClientSC.invoke(GenericPOACli
entSC.java:136)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:297)
at com.sap.mw.jco.jra.test._TestConnectionHome_Stub.create(Unknown
Sourc
e)
Does somebody know what is the cause of it?
(All the bean methods like create() are public, so it should not be
the problem.)
I very appreciate any tips,
Regards,
Eugen
PS: I already set Security on "Support Client Choice".I got it finally.
In the Security, I needed to add to the Role Name "Guest" the User Name "guest" -
Exception:java.rmi.AccessException: CORBA NO_PERMISSION 0 No
I was trying to run the Cart example with the J2EE but got the above exception. I was successful with the Converter example but not work with this one.
Please help
TomHere is the exact message:
D:\OnlineBooks\j2eetutorial\examples\ears>runclient -client CartApp.ear -name Ca
rtClient -textauth
Initiating login ...
Enter Username:guest
Enter Password:guest123
Binding name:`java:comp/env/ejb/SimpleCart`
Caught an unexpected exception!
java.rmi.AccessException: CORBA NO_PERMISSION 0 No; nested exception is:
org.omg.CORBA.NO_PERMISSION: minor code: 0 completed: No
org.omg.CORBA.NO_PERMISSION: minor code: 0 completed: No
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at com.sun.corba.ee.internal.iiop.messages.ReplyMessage_1_2.getSystemExc
eption(ReplyMessage_1_2.java:93)
at com.sun.corba.ee.internal.iiop.ClientResponseImpl.getSystemException(
ClientResponseImpl.java:108)
at com.sun.corba.ee.internal.POA.GenericPOAClientSC.invoke(GenericPOACli
entSC.java:132)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:459)
at CartHomeStub.create(Unknown Source)
at CartClient.main(CartClient.java:26)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:22
9)
at com.sun.enterprise.appclient.Main.main(Main.java:155) -
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. -
Cannot connect RMI-IIOP client to standalone OC4J (10.1.3)
[PROBLEM]
I am trying to access an EJB session bean from a simple remote java client.
The EJB is deployed to a standalone OC4J server.
Using the RMI-over-IIOP protocol for client-server communication.
The client and server run in separate JVMs (but on the same machine).
This is a simple java client program, not a J2EE application client.
The InitialContext creation fails with the errors shown below.
I searched around on the web, and found other people with the same issue, but no solution:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4995985
Maybe I'm missing something in my configuration, deployment, client invocation?
Any help will be greatly appreciated!
[SETUP]
I generated the iiop stubs during deployment (-DGenerateIIOP=true) to the server. Added the generated IIOPClient jar file to my client classpath.
Also specified -enableIIOP and remote=true for the EJB deployment.
As per the 10.1.3 documentation, I also specified the following command line arguments:
-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sun.corba.ee.impl.javax.rmi.PortableRemoteObject
-Dcom.oracle.CORBA.OrbManager=com.oracle.corba.ee.impl.orb.ORBManagerImpl
-Dorg.omg.CORBA.ORBInitialHost=testpc1
-Dorg.omg.CORBA.ORBInitialPort=5555
Verified in Oracle Enterprise Manager 10g (Application Server Control) that the application was deployed successfully, and a Stateful Session Bean is visible in the EJB pane.
Also verified that the iiop port (5555) is functioning (netstat).
internal-settings.xml file:
<server-extension-provider name="IIOP" class="com.oracle.iiop.server.IIOPServerExtensionProvider">
<sep-property name="port" value="5555"/>
<sep-property name="host" value="localhost"/>
<sep-property name="ssl" value="false"/>
<sep-property name="ssl-port" value="5556"/>
<sep-property name="ssl-client-server-auth-port" value="5557"/>
<sep-property name="trusted-clients" value="*"/>
</server-extension-provider>
server.xml file contains this entry:
<sep-config path="./internal-settings.xml"/>
[Versions]
Oracle Containers for J2EE 10g (10.1.3.0.0) (build 060119.1546.05277)
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
[ERROR]
com.sun.corba.ee.impl.legacy.connection.SocketFactoryContactInfoImpl <init>
WARNING: ORBUTIL.invalidEndPointInfoType
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 281 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.invalidEndPointInfoType(ORBUtilSystemException.java:5084)
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.invalidEndPointInfoType(ORBUtilSystemException.java:5106)
at com.sun.corba.ee.impl.legacy.connection.SocketFactoryContactInfoImpl.<init>(SocketFactoryContactInfoImpl.java:62)
at com.sun.corba.ee.impl.legacy.connection.SocketFactoryContactInfoListIteratorImpl.next(SocketFactoryContactInfoListIteratorImpl.java:59)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:114)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:214)
at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:345)
at com.sun.jndi.cosnaming.CNCtx.initUsingCorbanameUrl(CNCtx.java:321)
at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:247)
at com.sun.jndi.cosnaming.CNCtx.createUsingURL(CNCtx.java:85)
at com.sun.jndi.url.iiop.iiopURLContextFactory.getUsingURLIgnoreRest(iiopURLContextFactory.java:56)
at com.sun.jndi.url.iiop.iiopURLContextFactory.getUsingURL(iiopURLContextFactory.java:61)
at com.sun.jndi.url.iiop.iiopURLContextFactory.getObjectInstance(iiopURLContextFactory.java:34)
at oracle.j2ee.iiop.IIOPInitialContextFactory.getInitialContext(IIOPInitialContextFactory.java:76)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at ejbremoteclient.Main.getContext(Main.java:80)
at ejbremoteclient.Main.main(Main.java:87)
javax.naming.NamingException
at oracle.j2ee.iiop.IIOPInitialContextFactory.getInitialContext(IIOPInitialContextFactory.java:86)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at ejbremoteclient.Main.getContext(Main.java:80)
at ejbremoteclient.Main.main(Main.java:87)
ClientIIOPSSLSocketFactory.getEndpointInfo: iopprofile is not an instance of IIOPProfileTemplate
[CLIENT CODE]
// get context
Hashtable env = new Hashtable();
env.put("java.naming.provider.url", "corbaname::testpc1:5555#DME3");
env.put("java.naming.factory.initial", "oracle.j2ee.iiop.IIOPInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "oc4jadmin");
env.put(Context.SECURITY_CREDENTIALS, "welcome");
Context ic = new InitialContext(env); <---FAILS HEREHello Deepak
I've been doing some other stuff and then back to RMI/IIOP tests wih my app...
Finally I passed the previous errors, it all ended up being misconfigurations on the server and client side.
Now I'm striving with this one ...
java.rmi.AccessException: CORBA NO_PERMISSION 0 No; nested exception is:
org.omg.CORBA.NO_PERMISSION: ----------BEGIN server-side stack trace----------
org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No
at oracle.oc4j.corba.iiop.security.SecServerRequestInterceptor.receive_request(SecServerRequestInterceptor.java:354)
at com.sun.corba.ee.impl.interceptors.InterceptorInvoker.invokeServerInterceptorIntermediatePoint(InterceptorInvoker.java:509)
at com.sun.corba.ee.impl.interceptors.PIHandlerImpl.invokeServerPIIntermediatePoint(PIHandlerImpl.java:505)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.getServantWithPI(CorbaServerRequestDispatcherImpl.java:429)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:191)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1653)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1513)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:895)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:172)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:668)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:375)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.read(SocketOrChannelConnectionImpl.java:284)
at com.sun.corba.ee.impl.transport.ReaderThreadImpl.doWork(ReaderThreadImpl.java:73)
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:382)
----------END server-side stack trace---------- vmcid: 0x0 minor code: 0 completed: No
at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:204)
at javax.rmi.CORBA.Util.mapSystemException(Util.java:67)
at com.x.tools.login.ejb._LoginHome_Stub.create(Unknown Source)
at com.x.tools.login.clientside.model.Facade.<init>(Facade.java:168)
at com.x.tools.login.clientside.model.Facade.getInstance(Facade.java:122)
at com.x.tools.login.clientside.LoginApp.doLogin(LoginApp.java:169)
at com.x.tools.login.clientside.Login.getInstance(Login.java:83)
at com.x.caracas.AdminApp.clientside.MainAdminApp.<init>(MainAdminApp.java:30)
at com.x.caracas.AdminApp.clientside.MainAdminApp.main(MainAdminApp.java:81)
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 com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.continueLaunch(Unknown Source)
at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.omg.CORBA.NO_PERMISSION: ----------BEGIN server-side stack trace----------
org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No
at oracle.oc4j.corba.iiop.security.SecServerRequestInterceptor.receive_request(SecServerRequestInterceptor.java:354)
at com.sun.corba.ee.impl.interceptors.InterceptorInvoker.invokeServerInterceptorIntermediatePoint(InterceptorInvoker.java:509)
at com.sun.corba.ee.impl.interceptors.PIHandlerImpl.invokeServerPIIntermediatePoint(PIHandlerImpl.java:505)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.getServantWithPI(CorbaServerRequestDispatcherImpl.java:429)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:191)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1653)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1513)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:895)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:172)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:668)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:375)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.read(SocketOrChannelConnectionImpl.java:284)
at com.sun.corba.ee.impl.transport.ReaderThreadImpl.doWork(ReaderThreadImpl.java:73)
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:382)
----------END server-side stack trace---------- vmcid: 0x0 minor code: 0 completed: No
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.MessageBase.getSystemException(MessageBase.java:791)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSystemException(ReplyMessage_1_2.java:97)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(CorbaMessageMediatorImpl.java:546)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(CorbaClientRequestDispatcherImpl.java:430)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:326)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:132)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
... 18 more
Hope it's easy to solve ... I'm not using JAAS .. my jndi.properties looks like this:
java.naming.security.principal=oc4jadmin
java.naming.security.credentials=welcome javax.rmi.CORBA.PortableRemoteObjectClass=com.sun.corba.ee.impl.javax.rmi.PortableRemoteObject
com.oracle.CORBA.OrbManager=com.oracle.corba.ee.impl.orb.ORBManagerImpl
java.naming.factory.initial=oracle.j2ee.iiop.IIOPInitialContextFactory
java.naming.provider.url=corbaname::serverhost:13321#/MyApp -
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.
-
Java.rmi.AccessExeption: CORBA NO_PERMISSION
When I try to connect to my ejb using iiop I have an exception: java.rmi.AccessException: CORBA NO_PERMISSION 0 No; nested exception is:
org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.mapSystemException(ShutdownUtilDelegate.java:93)........
Please help!is you client application a swing app
-
Error in Privileges of OracleSystemUser in OBIEE 11g
Hi,
We are encountering an error with OracleSystemUser.
The policy referenced by URI "oracle/wss_username_token_client_policy" could not be retrieved as connection to Policy Manager cannot be established at "t3://servername:7001,servername:9704" due to invalid configuration or inactive state.
*<Warning> <oracle.wsm.resources.policymanager> <WSM-02310> <Failed to retrieve requested documents due to underlying error "java.rmi.AccessException: [EJB:010160]Security Violation: User: 'OracleSystemUser' has insufficient permission to access EJB: type=<ejb>, application=wsm-pm, module=wsm-pmserver-wls.jar, ejb=DocumentManager, method=retrieveDocuments, methodInterface=Remote, signature={java.lang.String,java.util.Map}.". The operation will be retried.>*
After successfully integrating Active Directory in Weblogic, the error was triggered while implementing privileges to dashboard objects. Currently, we can login to Weblogic and EM but we cannot login to Analytics. All logs in the BI Server and Admin Server logs show the above error.
Please help, thank you
Edited by: 878720 on Sep 27, 2011 8:19 PM
Edited by: 878720 on Sep 27, 2011 8:19 PM
Edited by: 878720 on Sep 27, 2011 8:19 PMHi,
Please Change control flag of default authentication provider (in weblogic domain) from REQUIRED to SUFFICIENT . More on control flag in WebLogic Authentication Provider
Refer :
http://onlineappsdba.com/index.php/2011/06/21/unable-to-login-to-obiee-anylytics-after-oid-integration-user-was-authenticated-but-could-not-be-located-within-the-identity-store/
Thanks
Deva -
Weblogic 10.3.0 - Security Violation when Group Membership Lookup enabled
Dear Admins,
We're running a Weblogic 10.3.0 cluster with our own software deployed.
We're using SQL authentication (JDBC to Oracle DB) to authenticate users.
Recently we've been tuning our WL cluster to improve performance, and have enabled Group Membership Lookup Hierarchy Caching.
Sometimes users log into our application and get inssuficient rights (or some other error). This appears to happen at random. Most of the times they can log in without problems.
We determined it's not something to do with the cluster, although it can happen on one node and the other node will work as normal.
In the Managed server we see this error (with test user):
Managed7Server.out00011:java.rmi.AccessException: [EJB:010160]Security Violation: User: 'test' has insufficient permission to access EJB: type=<ejb>, application=leanapps, module=process_general.jar, ejb=LaLifeProcessController,
method=create, methodInterface=Home, signature={}.
When we disable Group Membership Lookup Hierarchy Caching, this error never occurs.
Our settings (Security Realms -> myrealm -> Providers -> SQL Authenticator -> Performance):
Max Group Hierarchies In Cache: 5000 (we have approx. 2000 groups)
Group Hierarchy Cache TTL: 3600
provider specific settings :
Group Membership Searching: unlimited
Max Group Membership Search Level: 0
Also in Myrealm -> Performance we have set :
Enable WebLogic Principal Validator Cache
Max WebLogic Principals In Cache: 5000
If we put the TTL really low (default 60 seconds), the error hardly ever occurs. But we want to have cache that lasts longer then one minute.
This might be a bug, as we have other clusters running on WL 10.3.5, 12c where we use the same cache settings. This issue does not occur there.
I'm more then willing to provide more info or config files
Edited by: user5974192 on 21-nov-2012 5:17This is fixed now. Someone had defined a Servlet for the web service in web.xml that was preventing the EJB container to kick in.
Edited by: user572625 on Aug 25, 2011 11:54 PM -
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. -
Security-role and security-role-assignment not working in WL7.0
Hello all..
Some EJB components that worked fine in WebLogic 6.1 no longer work in
WL7.0. It has to do with the security-role and security-role-assignment
descriptor elements no longer allowing anonymous users to be included in the
authorization for a bean.
For example, in WL6.1 placing these items in ejb-jar.xml:
<assembly-descriptor>
<security-role>
<role-name>Employees</role-name>
</security-role>
<method-permission>
<role-name>Employees</role-name>
<method>
<ejb-name>CustomerEJB</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
and mapping WebLogic default users to this role in weblogic-ejb-jar.xml:
<security-role-assignment>
<role-name>Employees</role-name>
<principal-name>guest</principal-name>
<principal-name>system</principal-name>
</security-role-assignment>
worked fine for clients creating their context using a simple
InitialContext() constructor without specifying SECURITY_PRINCIPAL or
SECURITY_CREDENTIALS. These users were basically "guest" to WebLogic, and
the security-role-assignment element above told WebLogic that "guest" was in
the Employees role for purposes of this EJB archive.
Worked in WL6.1, no longer works in WL7.0. Client receives typical
permission exception:
java.rmi.AccessException: Security violation: insufficient permission to
access method 'create'
If I explicity connect as "system" things are fine, or I can create a new
user in the default realm in WebLogic, put a matching <principal-name>
element in the section above, and connect as that user. Note that if I leave
off the <security-role> section completely, or set the required role name to
"everyone", the anonymous access works fine. Apparently the anonymous user
is a member of "everyone" behind the scenes even though "everyone" does not
appear in the realm list of groups or roles.
So, my question boils down to this: Is there a "magic" username in WL7 like
"guest" was in WL6.1 that can be mapped to the required role name, or must
every client connection use a true weblogic-created user with appropriate
role assignments used to map it to the required role name.
-Greg
P.S. Note that none of the EJB examples provided with WL used
<security-role>..
Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
www.amazon.com/exec/obidos/ASIN/1931822468 or www.titan-books.comBelow are the screen shots for PFCG:
Maybe you are looking for
-
My wife and I share the same Mac OS 10.6.8 and since downloading Skype on her accout she came not asty connected to any web site for more than a few seconds. I have remove Skype from her account but not mine. I don't have the problem on my accout and
-
HP Pavilion dv6 1328sl, bios says : hard disk not exist !
Good morning, the bios says that the hard disk not exist. Still, if I boot the PC from CD with Linux, the files on the disk c can be seen .. I deleted the partition but the problem remains! does anyone know how to access the advanced menu of the bios
-
The Java Web Service Tutorial - help required
Using Windows 98 platform... I am working through the tutorial example "Hello World". I have got as far as deploying the service definition and starting Tomcat. The tutorial then says to specify the URL http://localhost:8080/jaxrpc-hello/jaxrpc to ve
-
Dv5-1164er no video signal & 3 beeps BIOS
Hello. Sorry for broken English. I disassembled the laptop for cleaning. After I the assembled laptop, lost the video signal and appeared repeated 3 beeps (BIOS). The cables are all connected. Please tell me what I did wrong. And please give error co
-
How to use CL_GUI_ALV_GRID in background run
Hi expert, is possible to use CL_GUI_ALV_GRID in background run? Usually I do a call screen and I put the set_table_for_first_display method in the PBO. How I can use the ALV GRID in a background run? Moderator message: please search for information