Oracle10g AppSer..Lookup error: javax.naming.AuthenticationException

Please help ..
I have a working EAR on weblogic app server and deployed it on oracle 10g app server release 2 .. the application is developed in struts .. the following error is shown on the console ..
06/09/22 10:34:28 Start process
06/09/22 10:34:37 log4j:WARN No appenders could be found for logger (org.apache.struts.util.PropertyMessageResources).
06/09/22 10:34:37 log4j:WARN Please initialize the log4j system properly.
06/09/22 10:34:43 INSIDE GET PROPERTY METHOD value for property= org.jnp.interfaces.NamingContextFactory
06/09/22 10:34:43 INSIDE GET PROPERTY METHOD value for property= localhost:1099
06/09/22 10:34:43 Oracle Application Server Containers for J2EE 10g (10.1.2.0.2) initialized
06/09/22 11:04:57 ************Inside eCreditSessionListenerClass Session Created: 0
22 Sep 2006 11:04:57,352 INFO com.ecredit.login.struts.LoginAction - inside getBeanObjec
22 Sep 2006 11:04:57,384 INFO com.ecredit.login.struts.LoginAction - inside getBeanObjec------>Login
22 Sep 2006 11:04:57,399 INFO com.ecredit.login.struts.LoginAction - Exception occured in Throwable Action Classjavax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Invalid username/password for default (); nested exception is:
     javax.naming.AuthenticationException: Invalid username/password for default () [Root exception is javax.naming.AuthenticationException: Invalid username/password for default ()]
22 Sep 2006 11:04:57,399 INFO com.ecredit.login.struts.LoginAction - after getBeanObjec
22 Sep 2006 11:04:57,399 INFO com.ecredit.login.struts.LoginAction - after home
22 Sep 2006 11:04:57,399 INFO com.ecredit.login.struts.LoginAction - Exception occured in Throwable Action Classjava.lang.NullPointerException
22 Sep 2006 11:04:57,415 DEBUG org.apache.struts.action.RequestProcessor - processForwardConfig(ForwardConfig[name=null,path=null,redirect=false,contextRelative=false,module=null])
The code snippet where this error probably occurred is >>>>
     private Object getBeanObject(String beanName)
          Object objref = null;
          try
               System.out.println("inside getBeanObjec");
               Properties props= new Properties();
               props.put(Context.INITIAL_CONTEXT_FACTORY, initial_context_factory);
               props.put(Context.PROVIDER_URL,provider_url);
               Context initCtx=new InitialContext(props);
               System.out.println("inside getBeanObjec------>" +beanName);
               objref=initCtx.lookup(beanName);
          catch(Exception e)
               e.printStackTrace();
          return objref;
At the line >>>>>>>>
objref=initCtx.lookup(beanName);
Please help me to get rid of this ......
Thanks in advance
Gurpreet Singh

Hi
private Object getBeanObject(String beanName)
Object objref = null;
try
System.out.println("inside getBeanObjec");
Context initCtx=new InitialContext();
System.out.println("inside getBeanObjec------>" +beanName);
objref=initCtx.lookup(beanName);
catch(Exception e)
e.printStackTrace();
return objref;
try this pleace
Asanka Priyanjith

Similar Messages

  • Javax.naming.AuthenticationException: RMIConnection Disconnected

    Hi,
    I'm having a problem deploying one application in the Enterprise Manager (10g). When i deploy the application, everything works fine, i can enter on the instance, see stadistics of my application, etc
    But when i stop the instance, and start again, it throws an error javax.naming.AuthenticationException: RMIConnection Disconnected. And when i try to access to the configuration of my instance, it said me that there's a problem in the authentication, and the admin password must be the same that the oc4j administrator password... and i'm using the same account...
    The full trace of the error is the following:
    10/06/30 16:46:19 SEVERE: CoreRemoteMBeanServer.fetchMBeanServerEjbRemote Error reading application-client descriptor: Error communicating with server: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected] for URL: ormis://servidor:12718/defaultjavax.naming.NamingException: Error reading application-client descriptor: Error communicating with server: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected] [Root exception is java.lang.InstantiationException: Error communicating with server: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
            javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
            javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
            javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected]]
    at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:127)
    at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:117)
    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 oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:468)
    at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:161)
    at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.<init>(RemoteMBeanServer.java:128)
    at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.getMBeanServer(RemoteMBeanServer.java:158)
    at oracle.oc4j.admin.jmx.client.ClientMBeanServerProxyFactory.getMBeanServer(ClientMBeanServerProxyFactory.java:68)
    at oracle.oc4j.admin.jmx.remote.rmi.RMIJMXConnectorImpl.getConnector(RMIJMXConnectorImpl.java:190)
    at oracle.oc4j.admin.jmx.remote.JMXConnectorImpl.connect(JMXConnectorImpl.java:400)
    at oracle.oc4j.admin.topology.ConnectionRefImpl.getConnector(ConnectionRefImpl.java:241)
    at oracle.oc4j.admin.management.farm.mbeans.JVMAgr.getAttribute(JVMAgr.java:1378)
    at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:36)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:239)
    at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1071)
    at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:953)
    at oracle.oc4j.admin.jmx.server.mbeans.model.DefaultModelMBeanImpl.invoke(DefaultModelMBeanImpl.java:700)
    at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
    at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
    at oracle.oc4j.admin.jmx.server.state.LocalizationFilterMBeanServer.invoke(LocalizationFilterMBeanServer.java:579)
    at oracle.oc4j.admin.jmx.distributed.MBeanServerDelegate.invoke(MBeanServerDelegate.java:495)
    at oracle.oc4j.admin.management.farm.mbeans.J2EEServerAgr.getAttribute(J2EEServerAgr.java:1599)
    at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:36)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:239)
    at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1071)
    at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:953)
    at oracle.oc4j.admin.jmx.server.mbeans.model.DefaultModelMBeanImpl.invoke(DefaultModelMBeanImpl.java:700)
    at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
    at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
    at oracle.oc4j.admin.jmx.server.state.LocalizationFilterMBeanServer.invoke(LocalizationFilterMBeanServer.java:579)
    at oracle.sysman.ias.studio.jmx.spi.JMXConnectorImpl.invoke(JMXConnectorImpl.java:389)
    at oracle.sysman.ias.studio.j2ee.shared.jmx.oc4j.ClusterIASJMXUtil.getAttribute(ClusterIASJMXUtil.java:370)
    at oracle.sysman.ias.studio.setup.javasso.JMXJavaSSOConfAdminBean.isJssoConfigured(JMXJavaSSOConfAdminBean.java:1041)
    at oracle.sysman.ias.studio.setup.javasso.JavaSSOConfHelper.isJssoConfigured(JavaSSOConfHelper.java:802)
    at oracle.sysman.ias.studio.cluster.TopologyHelper.prepareData(TopologyHelper.java:1300)
    at oracle.sysman.ias.studio.sdk.AbstractController.prepareData(AbstractController.java:875)
    at oracle.sysman.emSDK.svlt.PageHandler.handleRequest(PageHandler.java:391)
    at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:765)
    at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:283)
    at oracle.sysman.ias.studio.app.StudioConsole.doGet(StudioConsole.java:297)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    at oracle.sysman.ias.studio.app.BrowserVersionFilter.doFilter(BrowserVersionFilter.java:75)
    at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
    at oracle.sysman.ias.studio.app.MultipleJVMFilter.doFilter(MultipleJVMFilter.java:85)
    at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
    at oracle.sysman.ias.studio.app.PostLogonFilter.doFilter(PostLogonFilter.java:80)
    at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
    at oracle.sysman.ias.studio.app.ShortHostnameRedirectFilter.doFilter(ShortHostnameRedirectFilter.java:68)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:619)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: java.lang.InstantiationException: Error communicating with server: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected]
    at com.oracle.naming.J2EEContext.create(J2EEContext.java:104)
    at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:124)
    ... 77 more
    Caused by: oracle.oc4j.rmi.OracleRemoteException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected]
    at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:110)
    at oracle.oc4j.deployment.ApplicationClientResourceFinder.getFinder(ApplicationClientResourceFinder.java:123)
    at oracle.oc4j.deployment.ApplicationClientResourceFinder.getLocation(ApplicationClientResourceFinder.java:75)
    at oracle.oc4j.deployment.ApplicationClientResourceFinder.getEjbBinding(ApplicationClientResourceFinder.java:38)
    at com.oracle.naming.J2EEContext.addEJBReferenceEntries(J2EEContext.java:515)
    at com.oracle.naming.J2EEContext.create(J2EEContext.java:97)
    ... 78 more
    Caused by: javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
    javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected]
    at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:64)
    at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:101)
    ... 83 more
    Caused by: javax.naming.AuthenticationException: RMIConnection Disconnected
    at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:99)
    at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
    at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:646)
    at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:190)
    at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:174)
    at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
    at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
    ... 84 more
    In bold, there is a clue that can help, but i can't understand :P
    Any help would be appreciated
    Bye!

    gday WhiteSox --
    You don't say how you are creating the new container -- is this standalone where you've extracted it to another directory and munged the ports, or in an OracleAS instalallation where you created a new instance?
    What are you using to perform the deployment operation?
    If you post some more details, we can try and help.
    cheers
    -steve-

  • Root exception is javax.naming.AuthenticationException: Not authorized

    Hi :
    I am trying to access an EJB (OC4j Container ) thru a thick client which is running on the same machine but outside the container.
    My code to access the ejb is as follows:
    Properties props = new Properties();
         props.put(Context.INITIAL_CONTEXT_FACTORY
         , "com.evermind.server.rmi.RMIInitialContextFactory");
         props.put(Context.PROVIDER_URL, "ormi://localhost:23791/Sample");
         props.put(Context.SECURITY_PRINCIPAL, "sample");
         props.put(Context.SECURITY_CREDENTIALS, "demo");     
              InitialContext initialContext = new InitialContext(props);
              System.out.println("Initial Context"+initialContext);
              System.out.println("EjbNames.USER_HOME.getJndiName()"+EjbNames.USER_HOME.getJndiName());//EjbNames is an enum.Which returns jndi name of the specific ejb.)
    I have also modified to system-jazn-data.xml as follows:
    <application>
              <name>Sample</name>
              <login-modules>
                   <login-module>
                        <class>com.sample.abc.web.security.SampleLoginModule</class>
                        <control-flag>required</control-flag>
                        <options>
                             <option>
                                  <name>Password</name>
                                  <value>demo</value>
                             </option>
                             <option>
                                  <name>Username</name>
                                  <value>sample</value>
                             </option>
                        </options>
                   </login-module>
              </login-modules>
         </application>
    Still I am getting following Exception while trying to connect thru thick client to the server. Stack trace is as follows:
    SEVERE: ConnectionImpl:ilogin javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is:
         javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized]
    Aug 18, 2006 12:03:44 PM com.sample.abc.api.exceptions.SampleException <init>
    SEVERE: java.io.PrintStream@145f0e3
    java.lang.Exception: Home not found.
         Also below is the error which is printed on OC4j Console:
    NOTIFICATION J2EE RMI0004 Invalid username or password for Sample(sample). Authentication failed.
    Please help,also let me know If I am missing on configuration side or whatever is required.I am using OC4j 10.1.3.
    Thanks & Regards

    Add the following in system-jazn-data.xml
    <grant>
              <grantee>
                   <principals>
                        <principal>
                             <type>user</type>
                             <class>Your Principal Class</class>
                             <name>UserName to which you want to give permission</name>
                        </principal>
                   </principals>
              </grantee>
              <permissions>
                   <permission>
                        <class>com.evermind.server.rmi.RMIPermission</class>
                        <name>login</name>
                   </permission>
              </permissions>
         </grant>

  • Javax.naming.AuthenticationException [Root exception is com.tarantella.tta

    Dear all,
    i am trying to integrate active directory i am getting LDAP connection error
    LDAP Connection Error
    javax.naming.AuthenticationException [Root exception is com.tarantella.tta.webservices.TTAException]
    and cannot proceed.
    i selected on the previous screen as domain controller plus LDAP/Active directory
    right
    but it is not working
    any idea?

    Hi,
    Please try using the User Pricipal Name (UPN) as the username:
    username@domein
    Also make sure you ldap server url are correct:
    ldap://server.domain
    not:
    ldap://domain
    Best Regards,
    Arno Staal
    Divider B.V.

  • Javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Cre...

    Sir/Madam,
    i am working on Windows Platform and I am getting this error when i want ot configure the LDAP.
    Please suggest
    javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
         at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3005)
         at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2951)
         at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2753)
         at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2667)
         at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
         at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
         at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
         at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
         at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)
         at TestClient.main(TestClient.java:33)
    Thanks in advance.
    Regards
    Neelamadhab

    javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]LDAP is rejecting your credentials (username / password). Make sure your credentials are coorectly given, otherwise get help from LDAP admin.
    regards,
    Sekar

  • Javax.naming.AuthenticationException [LDAP: error code 49 - 80090308

    i am getting a problem in connection.
    javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece
    plz suggest                                                                                                                                                                                                                                                                                                                                                                                                           

    satish_dhn wrote:
    plz suggesterr code 49 means problem with login credentials.
    "525" (between "data" and "vece" ) means user not found.

  • Javax.naming.AuthenticationException: No such domain/application:

    I'm trying on JDeveloper 11g tutorial on "Build a Web Application with JDeveloper 11g Using EJB, JPA, and JavaServer Faces. I encounter this problem when try to run the simple java client created by Jdeveloper.
    javax.naming.AuthenticationException: No such domain/application: "current-workspace-app"
         at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:120)
         at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:70)
         at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:720)
         at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:252)
         at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:235)
         at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:302)
         at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:64)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at mssql.HRFacadeClient.main(HRFacadeClient.java:13)
    Anyone knows what's the cause of this error? I follow exactly the steps in Jdeveloper 11g tutorial. The only difference is that my database is MS SQL database.

    Same error.
    The real application (web and ejb's) are running on the same OC4J instance. The Web client are accessing the ejb's on port 3101, so i think this is the correct rmi port.
    The server is a part of an infrastructure that are running on the same server, the server is one of two ApplicationServers that the infrastructure (farm) is controlling.
    each server has an instance name, the server i was deplying to has name instance2. Maybe i have to give a reference to to the instance?

  • Javax.naming.AuthenticationException.  Root exception is java.lang.SecurityException: Authentication for user system denied in realm weblogic

    We have started getting the above error message in a system that has worked happily
    for the past 6 months or so (and continues to work happily from our disaster recovery
    environment). I should probably add that this occurs when we are attempting to
    write to the database via the connection pool.
    Anyone have any ideas?
    Thanks
    Andrew
    The full stack trace is
    javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
    Authentication for user system denied in realm weblogic
         <<no stack trace available>>
    31-Jan-02 00:04:41 GMT Warning Adapter RuntimeException
    thrown by rmi server(class com.esure.ibis.a
    ccesslayer.sb.useraccess.UserAccessBeanEOImpl)
    [265127279722
    6064825S:hfxesure17:[7005,7005,7002,7002,7005,7002,-1]:esure
    prdwls/296]: [BaseEJBObject]
    home: com.esure.ibis.accesslaye
    r.sb.useraccess.UserAccessBeanHomeImpl@4b741e
    com.esure.ibis.util.IbisException: NamingException occurred in UserAccess Session
    Bean::validateUser()
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBean.validateUser(UserAccessBean.java:192)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanImpl.validateUser(UserAccessBeanImpl.java:110)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl.validateUser(UserAccessBeanEOImpl.java:31)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl_WLSkel.invoke(UserAccessBeanEOImpl_WLSkel.java:202)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    We have started getting the above error message in a system that has worked happily
    for the past 6 months or so (and continues to work happily from our disaster recovery
    environment). I should probably add that this occurs when we are attempting to
    write to the database via the connection pool.
    Anyone have any ideas?
    Thanks
    Andrew
    The full stack trace is
    javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
    Authentication for user system denied in realm weblogic
         <<no stack trace available>>
    31-Jan-02 00:04:41 GMT Warning Adapter RuntimeException
    thrown by rmi server(class com.esure.ibis.a
    ccesslayer.sb.useraccess.UserAccessBeanEOImpl)
    [265127279722
    6064825S:hfxesure17:[7005,7005,7002,7002,7005,7002,-1]:esure
    prdwls/296]: [BaseEJBObject]
    home: com.esure.ibis.accesslaye
    r.sb.useraccess.UserAccessBeanHomeImpl@4b741e
    com.esure.ibis.util.IbisException: NamingException occurred in UserAccess Session
    Bean::validateUser()
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBean.validateUser(UserAccessBean.java:192)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanImpl.validateUser(UserAccessBeanImpl.java:110)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl.validateUser(UserAccessBeanEOImpl.java:31)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl_WLSkel.invoke(UserAccessBeanEOImpl_WLSkel.java:202)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • Naming error: javax.naming.NoInitialContextException

    I get the below error message when I try to run the testing class below that. I googled the exception and read:
    This exception is thrown when no initial context implementation can be created. The policy of how an initial context implementation is selected is described in the documentation of the InitialContext class.
    // then I read this: http://publib.boulder.ibm.com/infocenter/adiehelp/index.jsp?topic=/com.sun.api.doc/javax/naming/NoInitialContextException.html
    This exception can be thrown during any interaction with the InitialContext, not only when the InitialContext is constructed. For example, the implementation of the initial context might lazily retrieve the context only when actual methods are invoked on it.
    I really dont understand what I read. Could someone please explain what my issue is and why it is occurring and how I could fix it.
    Thank you in advance,
    Crystal
    Naming error: javax.naming.NoInitialContextException: Need to specify class name
    in environment or system property, or as an applet parameter, or in an applicat
    ion resource file:  java.naming.factory.initial
    Exception in thread "main" java.lang.NullPointerException
            at notifier.notifierMethod.SiteManager(notifierMethod.java:230)
            at notifier.testing.main(testing.java:22)
    testing.java
    class testing {
        public static void main(String[] args) {
            //Display "Hello World!"
            System.out.println("Hello World!");
            notifier notifierInformation = new notifier();
            //session.setAttribute("notifier", notifierInformation);
            //get db connection
            database.DataFactory dbf = database.DataFactory.getDataFactory(database.DataFactory.sybase);
            notifierInterface notifierDB = dbf.getNotifierInterface();
            notifier sitemanager = notifierDB.SiteManager(newID, notifierInformation);  // LINE 22
    notifierMethod
    public notifier SiteManager(String newID, notifier notifierInformation) {
            try {
                ArrayList sitemgrList = new ArrayList();
                this.conn = database.SybaseDAO.grabConnection();
                cs = conn.prepareCall("{call mt."+newID+"_Notifier_SiteManager()}"); // LINE 230
                rs = cs.executeQuery();
                while(rs.next()) {
                    String owner = rs.getString(1);
                        sitemgrList.add(owner);
                notifierInformation.setSitemgrList(sitemgrList);
    }

    Aleen - Thank you for your help but I just dont get what you are saying at all! I am reading through all the links and its just not clicking with me. Is it possible for you to show me a vague example of what you mean?
    What do you mean by system properties/enviroment parameters? Do you mean what is in my web.xml/server.xml, like so?
    public static Connection grabConnection() {
            Connection conn = null;
            try {
                Context ctx = (Context)new InitialContext().lookup("java:comp/env");
                DataSource ds = (DataSource)ctx.lookup("jdbc/connectDB");
                conn = ds.getConnection();
            } catch(SQLException e) { System.err.println("SQL error: " + e);
            } catch(NamingException n) { System.err.println("Naming error: " + n);
            return conn;
    web.xml
    <description>MySQL Test App</description>
    <resource-ref>
          <description>DB Connection</description>
          <res-ref-name>jdbc/connectDB</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
    </resource-ref>
    server.xml
    <Context path="/appName" docBase="/appName"
            debug="5" reloadable="true" crossContext="true">
      <Logger className="org.apache.catalina.logger.FileLogger"
                 prefix="localhost_DBPool_log" suffix=".log"
                 timestamp="true"/>
    <Resource name="jdbc/connectDB" auth="Container" type="javax.sql.DataSource"
                   maxActive="5" maxIdle="1" maxWait="10000" removeAbandoned="true"
                removeAbandonedTimeout="60" logAbandoned="true"
                   username="myName" password="myPass" driverClassName="sun.jdbc.odbc.JdbcOdbcDriver"
                   url="jdbc:odbc:webdev"/>
    </Context>I just dont understand why if I have this code in a servlet it works fine but when I try to put it in a java class it doesnt work. And I am sorry in advance, I am not trying to be a pain in the a55 to you.. and I will keep reading
    Thanks - Crystal

  • Solution to: javax.naming.AuthenticationException.  Root exception is java.lang.SecurityException: attempting to add an object which is not an instance of java.security.Principal to a Subject's Principal Set

    Hello world,
    To anybody who receives this irritating error in a Java client
    application attempting to access Weblogic Server 6.1 (and possibly
    weblogic server 6):
    javax.naming.AuthenticationException. Root exception is
    java.lang.SecurityException: attempting to add an object which is not
    an instance of java.security.Principal to a Subject's Principal Set
    The cause of your problem is having JAAS explicitly in your classpath.
    It somehow messes up authentication to WebLogic. Remove it and your
    problem will disappear.
    The complete exception was:
    javax.naming.AuthenticationException. Root exception is
    java.lang.SecurityException: attempting to add an object which is not
    an instance of java.security.Principal to a Subject's Principal Set
         at javax.security.auth.Subject$SecureSet.add(Subject.java:1098)
         at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(BootServicesStub.java:72)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:80)
         at weblogic.security.acl.internal.Security.authenticate(Security.java:108)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:509)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:364)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:336)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:208)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:668)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
         at javax.naming.InitialContext.init(InitialContext.java:222)
         at javax.naming.InitialContext.<init>(InitialContext.java:198)
         at au.com.orrcon.orrconcentral.Application.<init>(Application.java:87)
         at au.com.orrcon.orrconcentral.Application.getApp(Application.java:52)
         at au.com.orrcon.orrconcentral.orrconCentral.<init>(orrconCentral.java:130)
         at au.com.orrcon.orrconcentral.orrconCentral.main(orrconCentral.java:219)

    Steve Wesemeyer <[email protected]> wrote:
    I have encountered the same problem and I do not have JAAS on my classpath
    at all (unless it's there by default). Are there any other possible
    causes for this?
    Cheers,
    SteveA note to all who read this thread:
    I also had to remove Sun's j2ee (version 1.2) from my client's classpath before
    the same problem went away. 1 programmer day down the drain....
    Regards,
    MG

  • JNDI lookup failed:javax.naming.NameNotFoundException

    Hello:
    I have a application (not web) that publish messages to a specific topic, i want to receive these messages in a Web Service, but when the web service make the call to a class that is the JMS Client it can't find the Connection factory Name that i create in the aplication.
    I want to know what i have to do,
    I work with J2EE1.3.1 and JMS1.0.2 for the application that publish the messages
    and Jwsdp1.1, tomcat 4 and j2sdk 1.4.0 for the web service.
    I create the connection factory with this command:
    j2eeadmin -addJmsFactory jms/DurableTopicB topic -props clientID=IdTopicB
    Then in the class that the web service invoke i trying to join with this:
    try {
    jndiContext =new InitialContext();
    }catch (NamingException e){
    System.err.println("Could not create JNDI API "+
    "context:"+e.toString());
    return;
    *Look up connection factory and topic.If either  
    *does not exist,exit.                            
    try {
    topicConnectionFactory =(TopicConnectionFactory)
    jndiContext.lookup(conFacName);
    }catch (NamingException e){                      
    System.err.println("JNDI API lookup failed:"+
    e.toString());
    return;
    //System.exit(1);
    But i receive a error message in the log of Tomcat:
    JNDI API lookup failed:javax.naming.NameNotFoundException: El nombre DurableTopicB no este asociado a este contexto
    Thanks

    Hello:
    I display the full context of the connection factory in the application that publish the message:
    Full context is :
    Enviroment is : {java.naming.corba.orb=com.sun.enterprise.iiop.POAEJBORB@ec4a87}
    And in the web service when i create the initial context the full context is:
    Full context is : java:
    Enviroment is : {java.naming.factory.initial=org.apache.naming.java.javaURLContextFactory, java.naming.factory.url.pkgs=org.apache.naming}
    How can i see the connection factory in the Web Service, because the connection factory was created in other Application?

  • Javax.naming.AuthenticationException

    Hi :
    I am getting the following exception when I am trying to lookup
    a MBeanHome
    java.lang.IllegalArgumentException: Invalid user name or password, javax.naming.AuthenticationException
    [Root exception is java.lang.SecurityException: attempting to add an object which
    is not an instance of java.security.Principal to a Subject's Principal Set]
    at weblogic.management.Helper.getMBH(Helper.java:62)
    at weblogic.management.Helper.getAdminMBeanHome(Helper.java:28)
    at TestMBeanHome.main(TestMBeanHome.java:9)
    I am doing a simple lookup, like so...
    MBeanHome home = (MBeanHome)Helper.getAdminMBeanHome("system", "password", "t3://localhost:7001"
    The login/password work through the console.
    Any help is appreciated
    --krish

    You should be able to get the MBeanHome with the Helper class if the system
    username, pwd are correct.
    unless you have put some ACLs on MBeans and restricted the access for some
    specific users....
    Are you sure that your system user's password is: "password" ?
    I wrote a small prog to check the method and it returns the mbeanHome
    correctly ....
    I have attached it below ....
    hope it helps,
    Mihir
    import weblogic.management.Helper;
    import weblogic.management.*;
    import javax.management.*;
    public class useHelper {
    public static String SERVER_NAME="myserver";
    public static weblogic.management.MBeanHome localHome = null;
    public static weblogic.management.MBeanHome adminHome = null;
    public static void main(String[] args) {
    useHelper.find("172.17.26.33", 7001, "mihirk00");
    public static void find(String host, int port, String password) {
    String url = "t3://" + host + ":" + port;
    try {
    localHome = (MBeanHome)Helper.getMBeanHome("system", password,
    url, SERVER_NAME);
    adminHome = (MBeanHome)Helper.getAdminMBeanHome("system",
    password, url);
    System.out.println("Local and Admin Homes " + "found using the
    Helper class: " + localHome + " " + adminHome);
    } catch (IllegalArgumentException iae) {
    System.out.println("Illegal Argument Exception: " + iae);
    "Krish Garimella" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi :
    I am getting the following exception when I am trying to lookup
    a MBeanHome
    java.lang.IllegalArgumentException: Invalid user name or password,javax.naming.AuthenticationException
    [Root exception is java.lang.SecurityException: attempting to add an
    object which> is not an instance of java.security.Principal to a Subject's PrincipalSet
    at weblogic.management.Helper.getMBH(Helper.java:62)
    at weblogic.management.Helper.getAdminMBeanHome(Helper.java:28)
    at TestMBeanHome.main(TestMBeanHome.java:9)
    I am doing a simple lookup, like so...
    MBeanHome home = (MBeanHome)Helper.getAdminMBeanHome("system", "password","t3://localhost:7001"
    The login/password work through the console.
    Any help is appreciated
    --krish

  • Error while running Client Program of Entity Bean (BMP) : javax.naming.Name

    Hi,
    I have tried an entity bean application. I am able to deploy my entity bean in WebLogic 7.0 server. But when I ran the client program I am getting the following error.
    javax.naming.NameNotFoundException : Unable to resolve 'java:comp.env/ejb/AccountBean' Resolved: ' ' unresolved : 'java:comp': remaining name 'java:comp.env/ejb/AccountBean'
    My ejb-jar.xml is as follows:
    <ejb-jar>
    <enterprise-beans>
    <entity>
    <ejb-name>AccountBean</ejb-name>
    <home>AccountHome</home>
    <remote>Account</remote>
    <ejb-class>AccountBean<ejb-class>
    <persistance-type>Bean</persistance-type>
    <prim-key-class>AccountPK</prim-key-class>
    <reentrant>False</reentrant>
    <primkey-field>AccountID</primkey-field>
    <env-entry>
    <env-entry-name>jdbc.drivers</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>oracle.jdbc.driver.OracleDriver</env-entry-value>
         </env-entry>
    <env-entry>
    <env-entry-name>JDBC-URL</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>jdbc:oracle:thin:@erp:1521:Oracle9i</env-entry-value>
         </env-entry>
         <ejb-ref>
                   <ejb-ref-name>ejb/AccountBean</ejb-ref-name>
                   <ejb-ref-type>Entity</ejb-ref-type>
                   <home>AccountHome</home>
                   <remote>Account</Account>
                   <ejb-link>AccountBean</ejb-link>
              <ejb-ref>
              <resource-ref>
                   <resource-ref-name>jdbc/bmp-account</resource-ref-name>
                   <resouce-ref-type>javax.sql.DataSource</resource-ref-type>
                   <res-auth>Container</res-auth>
                   <res-sharing-scope>sharable</res-sharing-sope>
              <resource-ref>
         </entity>
    </enterprise-beans>
    <assembly-descriptor>
    </assembly-descriptor>
    <ejb-jar>
    My weblogic-ejb-jar.xml is as follows:
    <weblogic-ejb-jar>
         <weblogic-enterprise-bean>
              <ejb-name>AccountBean</ejb-name>
              <entity-descriptor>
                   <pool>
                   </pool>
                   <entity-cache>
                        <cache-between-transaction>false</cache-between-transcation>
                   </entity-cache>
                   <persistance>
                   </persistance>
                   <entity-clustering>
                   </entity-clustering>
              </entity-descripto>
              <transaction-descriptor>
              </transaction-descriptor>     
              <reference-descriptor>
                   <resource-descriptor>
                        <res-ref-name>jdbc/bmp-accoun</res-ref-name>
                        <jndi-name>MariJNDI</jndi-name>
                   </resource-descriptor>
                   <ejb-reference-descriptor>
                        <ejb-ref-name>ejb/AccountBean</ejb-ref-name>
                        <jndi-name>AccountBean</jndi-name>
                   </ejb-reference-descriptor>
              </reference-descriptor>
              </weblogic-enterprise-bean>
         </weblogic-ejb-jar>
    My Client Program is as follows:
    import javax.ejb.*;
    public class Client{
    public static void main(String[] args){
    Account account = null;
         try{
         Context = new InitialContext(System.getProperties());
         AccountHome home = (AccountHome) ctx.lookup("java:comp/env/ejb/AccountBean");
         home.create("123-456-7890","John");
         }catch(...){
    Any help is appreciated.
    Thanks in advance.
    Regards,
    Mari.

    Hi,
    My Client Program is as follows:
    import javax.ejb.*;
    public class Client{
    public static void main(String[] args){
    Account account = null;
         try{
    Context = new
    Context = new
    InitialContext(System.getProperties());
    AccountHome home = (AccountHome)
    AccountHome)
    ctx.lookup("java:comp/env/ejb/AccountBean");
         home.create("123-456-7890","John");
         }catch(...){
    }What are the System Properties? Are you running the client remotely? Are you running the client as a stand alone Java app or using the Weblogic's Client Runner? 'java:comp' as the jndi name is usually used when the client runs inside the container... But it doesn't seem to be the case.
    Kexkey

  • Error in EJB client program (javax.naming.NoInitialContextException)

    Hi folks ,
    I'm new to j2ee programming and using Netbeans 5.5 , i created a session bean program and deployed successfully in JOnAS application server but i'm not able to run the client program which invokes session bean (EJB module ).
    when i run client program i'm getting the following error .
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
            at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
            at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
            at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at SimpleSessionClient.Main.main(Main.java:33)
    BUILD SUCCESSFUL (total time: 21 seconds)
    but the same program runnig perfectly when i deploy in Java System Application Server(8.2(JSAS))
    I included j2ee.jar and appserv-rt jar in classpath of client program for JSAS i don't know what are the jar files (which does the same function as j2ee.ar,appserv-rt.jar ) which is to be included for JOnAS .
    i'm struggling with this for the past two weeks . please tell me the solution .
    Thanks in advance

    Thanks for the suggestion artntek.
    I located the jndi.properties file in the %J2EE_HOME%\lib\classes folder, and I copied it to the %J2EE_HOME%\bin directory, but nothing seems to have changed.
    does anyone know what value should be associated with Context.INITIAL_CONTEXT_FACTORY in the properties for the InitialContext object? More specifically, what value should be used for the reference install of the 1.3 j2ee release from sun?
    This error suggests to me that a class name must be specified for the initial naming context factory - but I don't know what to use.

  • JNDI lookup from OC4J to weblogic throws javax.naming.NameNotFoundException

    Hi All,
    We have the below setup in our production environment.
    EJB application is deployed in the Weblogic 10.3.4.0 Server on Sun Solaris. The EJB version is 3.0
    OC4J 10.2.0 is running on another Sun Solaris machine.
    There are 2 webservice applications WEBSERV1 & TestSoapEJB running on this OC4J container.
    We need to do lookup the EJBs deployed on the Weblogic server. For this we used the below logic in the web service's Stateless session bean:
    String weblogicURL = "";
    Properties props = new Properties();
    try
    props.load(Thread.currentThread().getContextClassLoader().getResourceAsStream("wl.properties"));
    weblogicURL     = props.getProperty("weblogicURL");     
    catch (FileNotFoundException e)
    e.printStackTrace();
    catch (IOException e)
    e.printStackTrace();
    Context ctx = null;
    Hashtable ht = new Hashtable();
    ht.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    ht.put(Context.SECURITY_PRINCIPAL,"weblogic");
    ht.put(Context.SECURITY_CREDENTIALS,"weblogic654");
    ht.put(Context.PROVIDER_URL, weblogicURL);
    ctx = NamingManager.getInitialContext(ht) ;
    // tried using //ctx = new InitialContext(ht); same behavior.
    TestEJB.AdministratorEJB ejb = (TestEJB.AdministratorEJB) ctx.lookup("TestEJB#TestEJB.AdministratorEJB");
    ctx.close();
    When we first test first WEBSER1, the lookup is fine.
    But when we test the second webservice WEBSER2, the webservice name itself not able to lookup: It gives the below error:
    javax.naming.NameNotFoundException: remaining name: env/TestSoapEJB
    Below is the stack throws thrown on browser:
    500 Internal Server Error
    javax.naming.NameNotFoundException: remaining name: env/TestSoapEJB     
    at weblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:35)     
    at weblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:39)     
    at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:59)     
    at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:59)     
    at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:64)     
    at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)     
    at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)     
    at javax.naming.InitialContext.lookup(InitialContext.java:392)     
    at oracle.j2ee.ws.SessionBeanRpcWebService.init(SessionBeanRpcWebService.java:65)     
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)     
    at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpApplication.loadServlet(HttpApplication.java:2354)     
    at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpApplication.findServlet(HttpApplication.java:4795)     
    at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2821)     
    at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:680)     
    at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)     
    at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)     
    at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)     
    at java.lang.Thread.run(Thread.java:662)
    It seems that, the OC4J is looking in Weblogic context. But it should be looking in its own context. How to resolve this issue.
    The same case happens if i restart the OC4J and first test the TestSoapEJB the lookup is fine . But if i test the WEBSERV1 , it throws the same error as above. In short, if one of the webservices lookup is working fine, the other webservice is not working. At the same time only one webservice's lookup is working.
    Kindly help me to resolve this issue.
    regards,
    Zia
    Edited by: PT Expert on Sep 9, 2012 3:16 AM

    I work now more that two days on this error!!!
    -> I remade my complete jdev project, it did not work!
    -> I deleted the jdev/system/j2ee/oc4j/workspace dir
    -> I search for some .lock files
    -> and many more tries!!! But without success...
    Is there a way to reset the Embedded OC4J?

Maybe you are looking for