Error handle request; Root exception is: java.lang.NoSuchMethodError

Hello Guys,
I am running EBS 11i, rdbms 10g on OEL4. After applying a bunch of patches to resolve some IE issues I ran into an error:
"FRM-41072: Cannot create group ACTION_REC_GROUP" when trying to cancel a PO.
An SR directed me to apply patch 8286920 which indeed fixed the FRM-41072 error. After this patch "Logon to Oracle Applications Manager" is not possible as the page gives me :
Error handle request; Root exception is: java.lang.NoSuchMethodError: oracle.apps.fnd.security.AolSecurity.userPwdHash(Ljava/lang/String;)Ljava/lang/String;
MOS thinks that patch 8286920 didn't break OAM but I don't think so since this is only happening on my DEV and TEST systems on which I have applied the patch. PROD, wihtout the patch, is accessible through OAM just as usual?
Any thouths?
Thank you
Mathias

Did you apply all patches mentioned in the following docs?
FRM-41072 - Unable to Cancel Purchase Order or Purchase Order Line or Release [ID 947402.1]
Change Tax Code in the Purchase Order Gets Error - Could not reserve record (2 tries) Keep trying [ID 956047.1]
Autocreate Process Does Not Default Purchase Order Form As The Active Window After PO Is Created - Does Not Come To The Front [ID 1055623.1]
Did you bounce all the services and see if you ca reproduce the issue?
What about clearing the server cache files? -- How To Clear Caches (Apache/iAS, Cabo, Modplsql, Browser, Jinitiator, Java, Portal, WebADI) for E-Business Suite? [ID 742107.1]
Can you find any errors in the database/apache log files? Any invalid objects?
If you have verified all the above please update the SR with the error you have after applying that patch.
Thanks,
Hussein

Similar Messages

  • Javax.naming.NamingException.  Root exception is java.lang.NoSuchMethodError

    I am using WLS5.1 inside visualage environment. I am trying to run
    a Simple EJB which connects to the database and executes two simple
    queries. The client code is as shown below:
    try{
    Context ic = getInitialContext();
    System.out.println("Initial Context created......"); java.lang.Object
    objref = ic.lookup("simpleBean.AtmHome"); System.out.println("objref
    created......");
    AtmHome home = (AtmHome) PortableRemoteObject.narrow(objref, AtmHome.class);
    System.out.println("home created......");
    Atm atm = home.create();
    System.out.println("atm created......");
    atm.transfer(8, 9, 100000);
    catch (NamingException ne)
    ne.printStackTrace(System.out);
    finally {
         try {
              ic.close();
              System.out.println("Closed the connection");
         catch (Exception e) {
              System.out.println("Exception while closing context....." );
    The above code executes fine for the first time but second time
    it throws an exception "javax.naming.NamingException.
    Root exception is java.lang.NoSuchMethodError"
    javax.naming.NamingException. Root exception is java.lang.NoSuchMethodError
         java.lang.Throwable()
         java.lang.Error()
         java.lang.LinkageError()
         java.lang.IncompatibleClassChangeError()
         java.lang.NoSuchMethodError()
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         javax.naming.NameImpl(java.util.Properties)
         javax.naming.CompositeName()
         weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
         weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
         weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
    int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
         java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
    weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
         void weblogic.kernel.ExecuteThread.run()
    --------------- nested within: ------------------
    weblogic.rmi.ServerError: A RemoteException occurred in the server
    method
    - with nested exception:
    [java.lang.NoSuchMethodError:
    Start server side stack trace:
    java.lang.NoSuchMethodError
         java.lang.Throwable()
         java.lang.Error()
         java.lang.LinkageError()
         java.lang.IncompatibleClassChangeError()
         java.lang.NoSuchMethodError()
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         javax.naming.NameImpl(java.util.Properties)
         javax.naming.CompositeName()
         weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
         weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
         weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
    int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
         java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
    weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
         void weblogic.kernel.ExecuteThread.run()
    End  server side stack trace
         weblogic.rmi.extensions.WRMIInputStream weblogic.rmi.extensions.AbstractRequest.sendReceive()
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.WLContextStub.lookup(java.lang.String)
         java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
         void simpleBean.AtmClient.main(java.lang.String [])
    NamingException is caught....
    I found out that it hangs at lookup function in the above code.
    Please let me know if I am missing any environment settings.
    Thanks
    Shailaja

    This problem is solved after installing service pack 8 for weblogic
    5.1
    -shailaja
    "shailaja" <[email protected]> wrote:
    >
    I am using WLS5.1 inside visualage environment. I am trying
    to run
    a Simple EJB which connects to the database and executes
    two simple
    queries. The client code is as shown below:
    try{
    Context ic = getInitialContext();
    System.out.println("Initial Context created......"); java.lang.Object
    objref = ic.lookup("simpleBean.AtmHome"); System.out.println("objref
    created......");
    AtmHome home = (AtmHome) PortableRemoteObject.narrow(objref,
    AtmHome.class);
    System.out.println("home created......");
    Atm atm = home.create();
    System.out.println("atm created......");
    atm.transfer(8, 9, 100000);
    catch (NamingException ne)
    ne.printStackTrace(System.out);
    finally {
         try {
              ic.close();
              System.out.println("Closed the connection");
         catch (Exception e) {
              System.out.println("Exception while closing context....."
    The above code executes fine for the first time but second
    time
    it throws an exception "javax.naming.NamingException.
    Root exception is java.lang.NoSuchMethodError"
    javax.naming.NamingException. Root exception is java.lang.NoSuchMethodError
         java.lang.Throwable()
         java.lang.Error()
         java.lang.LinkageError()
         java.lang.IncompatibleClassChangeError()
         java.lang.NoSuchMethodError()
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         javax.naming.NameImpl(java.util.Properties)
         javax.naming.CompositeName()
         weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
         weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
         weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
    int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
         java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
    weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
         void weblogic.kernel.ExecuteThread.run()
    --------------- nested within: ------------------
    weblogic.rmi.ServerError: A RemoteException occurred in
    the server
    method
    - with nested exception:
    [java.lang.NoSuchMethodError:
    Start server side stack trace:
    java.lang.NoSuchMethodError
         java.lang.Throwable()
         java.lang.Error()
         java.lang.LinkageError()
         java.lang.IncompatibleClassChangeError()
         java.lang.NoSuchMethodError()
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         javax.naming.NameImpl(java.util.Properties)
         javax.naming.CompositeName()
         weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
         weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
         weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
    int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
         java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
    weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
         void weblogic.kernel.ExecuteThread.run()
    End  server side stack trace
         weblogic.rmi.extensions.WRMIInputStream weblogic.rmi.extensions.AbstractRequest.sendReceive()
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.WLContextStub.lookup(java.lang.String)
         java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
         void simpleBean.AtmClient.main(java.lang.String [])
    NamingException is caught....
    I found out that it hangs at lookup function in the above
    code.
    Please let me know if I am missing any environment settings.
    Thanks
    Shailaja

  • Failed to get connection-; Root exception is: java.lang.NullPointerExceptio

    Hi:
    When I login Applications, click on any OAM got the following errors. All the forms are good.
    An error has occurred!
    Failed to get connection-; Root exception is: java.lang.NullPointerException
    I don't know when started to be like that but I applied some patches yesterday. Thank you for your help in advance.

    Hi;
    You dont need to check log file. Please check apache log file for error details.
    By the way did you try to
    1. close apps services
    2. run autoconfig on dbtier than
    3. run autoconfig on appstier and be sure you dont have any error message,than recheck issue
    Regard
    Helios

  • 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)

  • 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

  • Error handling notification type=Platform,Domain=java.lang,subType=GC

    I'm seeing this error over and over. Odd that 17 and 18 are not listed as members.
    -Andrew
      MemberId|ServiceVersion|ServiceJoined|MemberState
        2|3.7.1|2012-03-28 08:59:53.744|JOINED,
        4|3.7.1|2012-03-28 04:42:03.799|JOINED,
        6|3.7.1|2012-03-28 05:22:21.955|JOINED,
        7|3.7.1|2012-03-28 05:55:56.571|JOINED,
        8|3.7.1|2012-03-28 05:55:56.584|JOINED,
        9|3.7.1|2012-03-28 06:42:46.461|JOINED,
        10|3.7.1|2012-03-28 06:00:00.698|JOINED,
        11|3.7.1|2012-03-28 08:20:01.535|JOINED,
        12|3.7.1|2012-03-28 08:20:02.32|JOINED,
        13|3.7.1|2012-03-28 08:21:12.046|JOINED,
        14|3.7.1|2012-03-21 09:10:59.991|JOINED,
        16|3.7.1|2012-03-21 09:11:03.034|JOINED,
        20|3.7.1|2012-03-21 09:10:59.236|JOINED,
        22|3.7.1|2012-03-21 09:11:00.273|JOINED,
        23|3.7.1|2012-03-21 09:11:02.329|JOINED
      RecycleMillis=1200000
      RecycleSet=MemberSet(Size=0
    TcpRing{Connections=[23]}
    IpMonitor{AddressListSize=1}
    2012-03-28 09:00:04.395/11.378 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Service Managemen
    t joined the cluster with senior service member 14
    2012-03-28 09:00:04.659/11.642 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
    tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=18
    2012-03-28 09:00:04.677/11.660 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
    tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=17
    2012-03-28 09:00:04.693/11.676 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
    tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=18
    2012-03-28 09:00:04.706/11.689 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
    tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=17
    Map (?):
    2012-03-28 09:00:04.875/11.858 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
    tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=18

    No ideas on a cause or solution for this? I only saw it once and I don't know how to reproduce it.
    -Andrew

  • Getting javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory.  Root exception is java.lang.ClassCastException: weblogic.jndi.WLInitialContextFactory

    We have an Issue in Weblogic6.1/7.0, while accessing a bean through Java Client. In the Code, i am providing the Initial Context factory and provider url to
    InitialContext Constructor. Weblogic.jar WILL NOT be availabe in the classpath.We are Loading the classes through CustomClassLoader which was written by us by extending java.lang.ClassLoader.
    While Constructing the InitialContext, it throws NoInitialContextException, the root exception it says ClassCastException.
    With this i am attaching the code snippet:
    JarAndClassFileLoader customLoader = JarAndClassFileLoader.getLoaderInstance();
    customLoader.pathFileVec.addElement(new ZipFile("c:\\FDRIVE\\bea\\wlserver6.1\\lib\\weblogic.jar"));               
    Thread.currentThread().setContextClassLoader(customLoader);
    Properties prop = new Properties();
    prop.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    prop.put(Context.PROVIDER_URL,"t3://localhost:7001");
    InitialContext itl = new InitialContext(prop) ---> Getting the above said NoInitialContextException..
    Kindly provide the necessary solutions to overcome this.

    I guess you did something wrong implementing your classloader(s).
    This works with 7.0:
         ClassLoader weblogicClassLoader;
         Thread.currentThread().setContextClassLoader(
         weblogicClassLoader = new URLClassLoader(
         new URL[] { new URL("http://localhost:7001/classes/") }
         Hashtable env = new Hashtable();
    env.put("java.naming.factory.initial", "weblogic.jndi.WLInitialContextFactory");
    env.put("java.naming.provider.url", "t3://localhost:7001");
         InitialContext ctx = new InitialContext(env);     
    You may also look at these examples:
    http://dima.dhs.org/misc/ThinClient.jsp
    http://dima.dhs.org/misc/ThinClient2.jsp
    B.Ravikumar <[email protected]> wrote:
    We have an Issue in Weblogic6.1/7.0, while accessing a bean through Java Client. In the Code, i am providing the Initial Context factory and provider url to
    InitialContext Constructor. Weblogic.jar WILL NOT be availabe in the classpath.We are Loading the classes through CustomClassLoader which was written by us by extending java.lang.ClassLoader.
    While Constructing the InitialContext, it throws NoInitialContextException, the root exception it says ClassCastException.
    With this i am attaching the code snippet:
    JarAndClassFileLoader customLoader = JarAndClassFileLoader.getLoaderInstance();
    customLoader.pathFileVec.addElement(new ZipFile("c:\\FDRIVE\\bea\\wlserver6.1\\lib\\weblogic.jar"));               
    Thread.currentThread().setContextClassLoader(customLoader);
    Properties prop = new Properties();
    prop.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    prop.put(Context.PROVIDER_URL,"t3://localhost:7001");
    InitialContext itl = new InitialContext(prop) ---> Getting the above said NoInitialContextException..
    Kindly provide the necessary solutions to overcome this.--
    Dimitri

  • Error watching JMS queues with JMSUtils: java.lang.NoSuchMethodError: main

    Hi. I'm trying to use the command line utility JMSUtils to see if I have configured correctly a new queue in oc4j server but when I try to use execute it following the instructions I have found on the net it doesn't appear to be in the oc4j.jar
    I found that class in oc4jclient.jar but without a main method.
    I use the 10g Release 3 (10.1.3.0.0) for Microsoft Windows
    The instruction I execute is:
    C:\product\10.1.3\OracleAS_1\j2ee\home>java -classpath c:\ora10g\j2ee\home\oc4j.
    jar;c:\ora10g\j2ee\home\lib\jms.jar com.evermind.server.jms.JMSUtils -username admin -password welcome destinations
    Exception in thread "main" java.lang.NoClassDefFoundError: com/evermind/server/j
    ms/JMSUtils
    Mensaje editado por:
    user515269
    Mensaje editado por:
    user515269

    When I try to execute the JMSUtils class that's inside
    oc4j-internal.jar appears the same exception I had
    executing the class that's inside oc4jclient.jar:
    NoSuchMethodError: main
    Anybody knows why this class doesn't have a main method
    or how can I execute it?Jose:
    It seems that the command line utility JMSUtils is removed from oc4j 10.1.3, although the class is still packaged into some oc4j jar. According to the documentation, "In this release, OracleAS JMS Utility functionality is available as attributes and operations on various MBeans, replacing the deprecated command line interface of previous releases.".
    Please see the section "OracleAS JMS Utility" of the book "Oracle® Containers for J2EE
    Services Guide, 10g Release 3 (10.1.3) for Windows or UNIX, B14427-01", which is available on line.
    Hope this helps.

  • Root exception is java.lang.ClassNotFoundException: org.apache.naming.java.

    Hi, All
    From where i can get .jar file which should have org.apache.naming.java.javaURLContextFactory class ..
    Thank You,

    Hi, All
    From where i can get .jar file which should have org.apache.naming.java.javaURLContextFactory class ..
    Thank You,

  • Unmarshalling return; nested exception is: java.lang.ClassNotFoundException

    I think what I'm trying to achieve is probably very simple (or at least should be) but I've been trying for at least 5 hrs now:
    I'm using RMI for a distributed app I'm building for my degree.
    Up until today I got around the need for using a SecurityManager by including all shared classes (those I pass between client and server) in a class library .jar file referenced by both client and server projects.
    This has worked fine, but now I've coded a method that returns an object of a class that I do NOT want to include in the shared library (because I don't want the client to be able to construct these objects); therefore, I've decided to try and get the dynamic class loading working.
    I'm using netbeans and testing on a single computer.
    Here's what I'm trying:
    My main() method has the standard code I've seen: if (System.getSecurityManager() == null) System.setSecurityManager(new RMISecurityManager());
    In the server project's Run properties, I'm specifying VM Options: -Djava.security.policy=c:\security.policy -Djava.rmi.server.codebase="file://C:/"
    I've copied the ellusive class's .java file into C:\ to keep the URL simple, but I've also tried directing it to the netbean project's bin\ folder using '%20' for spaces, both with the same results - about a five second pause (so it's finding something I think) and then the error message from the client's output:
    error unmarshalling return; nested exception is: java.lang.ClassNotFoundException: mypackage.myClass
    My policy file's contents are:
    grant {
    permission java.security.AllPermission;
    I've tried about 20 different ways of formatting the codebase argument's URL.. can anyone help?
    David
    p.s. my OS is Windows 7

    Thanks EJP,
    Yes, after posting I guessed it might want the .class file instead, so I directed it their instead - still no joy, unfortunately!
    I'm carrying out all testing on one computer, so (+if+ I could get it to work) a local codebase address would not be a problem.
    Noted about the server-side security manager. I might want to use callbacks, but the server still won't need to download class files from the client, so I'll still try and set the codebase, but will try without loading a security manager on the server-side.
    For the time being I've put the class in the shared library but have defined it within the same package as the server code. By doing this I've been able to set the class's accessibility back to default, but the client can still access it as Object (from the shared library).
    This solution is good enough, but I still wonder why the client refuses to accept the class file from the C:\ codebase.

  • Caught an unexpected exception! java.lang.ClassCastException at com.sun.cor

    Hi,
    Iam struggling with this problem from last 3days.
    Any body could u help me to solve this problem.
    error:
    Caught an unexpected exception!
    java.lang.ClassCastException at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow (PortableRemoteObject.java:293)
    at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
    at ConverterClient.main(ConverterClient.java:59)
    Client Code is here:
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.rmi.PortableRemoteObject;
    import java.util.Properties;
    import javax.ejb.CreateException;
    import java.util.Hashtable;
    // NOT NECESSARY import Converter;
    // NOT NECESSARY import ConverterHome;
    public class ConverterClient {
    public static void main(String[] args) {
    try {
    Properties env = new Properties();
              env.put("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
              env.put("java.naming.provider.url", "iiop://localhost:3700");
              Context initial = new InitialContext(env);
         ConverterHome home =(ConverterHome)PortableRemoteObject.narrow(initial.lookup("MyConverter"),ConverterHome.class);
    // Create converter session bean
    Converter currencyConverter = home.create();
    // Calculate from dollars to yen
    double amount = currencyConverter.dollarToYen(100.00);
    System.out.println("100 Dollars is " + String.valueOf(amount) + " Yen");
    // Calculate from yen to dollars
    amount = currencyConverter.yenToEuro(100.00);
    System.out.println("100 Yen is " + String.valueOf(amount) + " Dollars");
    } catch (Exception ex) {
    System.err.println("Caught an unexpected exception!");
    ex.printStackTrace();

    Hi,
    I have a stateless bean and accessing it from a jsp page in Orion App Server. There is no problem in the deployment. of the application.
    When I access the bean from the jsp page is throwing
    java.lang.ClassCastException
    at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(Unknown Source)
    The code is :
    Object homeObject = null;
    homeObject = ctx.lookup("LoginHome");
    out.println(homeObject.toString());
    LoginHome ejbHome = (LoginHome)PortableRemoteObject.narrow(homeObject,LoginHome.class);
    Login login = ejbHome.create();
    when I use the statement
    homeOject.toString() to print the object it prints
    LoginHome EJBHome
    I am not able to resolve this for th epast three days.
    Thanks,
    Vivek S

  • Java.lang.NoSuchMethodError but method is found in both java and class file

    Hi All,
      I am working on adding a new component to Trips and Expense but I'm getting an exception and I have no idea why.  Its claiming a java.lang.NoSuchMethodError in class IPrivateVcTraAllMyTrips yet the method is there.
      When I step through the code I can get to the point where it tries to attach the component then before it actually crashes, I hold ctrl and click on the method that it claims does not exist.  The code brings me to the IPrivateVcTraAllMyTrips java code and to the method ... so it is there in my sources.  I then went to my bin directory and decompiled the IPrivateVcTraAllMyTrips class and found the method there as well.  It seems as tho its not actually being deployed.
      Does anyone have any suggestions?
    Exception Stack ##
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NoSuchMethodError: com.sap.xss.tra.vc.allmytrips.wdp.IPrivateVcTraAllMyTrips.wdGetFcObjectSelectionComponentUsage()Lcom/sap/tc/webdynpro/progmodel/api/IWDComponentUsage;
        at com.sap.xss.tra.vc.allmytrips.VcTraAllMyTrips.onInit(VcTraAllMyTrips.java:262)
        at com.sap.xss.tra.vc.allmytrips.wdp.InternalVcTraAllMyTrips.onInit(InternalVcTraAllMyTrips.java:408)
        at com.sap.xss.tra.vc.allmytrips.VcTraAllMyTripsInterface.onInit(VcTraAllMyTripsInterface.java:175)
        at com.sap.xss.tra.vc.allmytrips.wdp.InternalVcTraAllMyTripsInterface.onInit(InternalVcTraAllMyTripsInterface.java:205)
        at com.sap.xss.tra.vc.allmytrips.wdp.InternalVcTraAllMyTripsInterface$External.onInit(InternalVcTraAllMyTripsInterface.java:399)

    I wish it were that simple.  I have restarted but it still threw the same exception.
    I ended up reimporting everything again and starting from scratch (a 4 hour process to get back to where I was).  The issue is no more.
    thx for your reply

  • Java.lang.NoSuchMethodError: javax/persistence/OneToMany.orphanRemoval()Z

    Hi,
    I have a web application that is built using Spring 3.2.1 and Hibernate 4.2.0 (JPA 2). The application deploys and runs well in Weblogic v 12.1.1. Now we have a change in the requirement from the client regarding the server version. The server needs to be downgraded to a lower version i.e., Weblogic v 10.3.2. Now, when I deploy the application onto this version of the server I get the following exception while deployment.
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.filterChains': Cannot resolve reference to bean 'org.springframework.security.web.DefaultSecurityFilterChain#0' while setting bean property 'sourceList' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.web.DefaultSecurityFilterChain#0': Cannot resolve reference to bean 'org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter#0' while setting constructor argument with key [3]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter#0': Cannot resolve reference to bean 'org.springframework.security.authentication.ProviderManager#0' while setting bean property 'authenticationManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.authentication.ProviderManager#0': Cannot resolve reference to bean 'org.springframework.security.config.authentication.AuthenticationManagerFactoryBean#0' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.config.authentication.AuthenticationManagerFactoryBean#0': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.authenticationManager': Cannot resolve reference to bean 'org.springframework.security.authentication.dao.DaoAuthenticationProvider#0' while setting constructor argument with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.authentication.dao.DaoAuthenticationProvider#0': Cannot resolve reference to bean 'cpmaSecurityService' while setting bean property 'userDetailsService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cpmaSecurityService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.ncr.cpa.data.dao.UserDao com.ncr.cpa.service.impl.CPMASecurityService.userDAO; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userDaoImpl': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private org.hibernate.SessionFactory com.ncr.cpa.data.dao.impl.UserDaoImpl.sessionFactory; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in ServletContext resource [/WEB-INF/classes/applicationContextTxManager.xml]: Invocation of init method failed; nested exception is java.lang.NoSuchMethodError: javax/persistence/OneToMany.orphanRemoval()Z
      at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:329)
      at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:107)
      at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
      at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:154)
      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1391)
      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1132)
      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:522)
      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:461)
      at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295)
      at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
      at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292)
      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
      at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:608)
      at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:933)
      at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)
      at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:390)
      at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:294)
      at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:113)
      at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
      at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
      at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1870)
      at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)
      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
      at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
      at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:672)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
      at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:44)
      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
      at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
      at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
      at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
      at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
      at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)
      at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
      at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)
      at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)
      at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
      at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    It looks like a problem with the JPA library. I tried few of the solutions after I did some research but were of no use. Below are the solutions that I had tried
    Solution 1:
    1) Copy hibernate-jpa-2.0-api-1.0.1.Final.jar into your weblogic's %DOMAIN_HOME%/lib directory.
    2) Open up your setDomainEnv.cmd (windows) or setDomainEnv sh (unix) script file and set your PRE_CLASSPATH variable to set PRE_CLASSPATH=%DOMAIN_HOME%\lib\hibernate-jpa-2.0-api-1.0.1.Final.jar
    After trying the above solution the exception is still raised while deployment of the application.
    Solution 2:
    Create "weblogic-application.xml" file into META-INF with something like this:
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-application xmlns="http://xmlns.oracle.com/weblogic/weblogic-application">
    <application-param>
      <param-name>webapp.encoding.default</param-name>
      <param-value>UTF-8</param-value>
    </application-param>
    <prefer-application-packages> 
      <package-name>javax.persistence.*</package-name>
    </prefer-application-packages>
    </weblogic-application>
    After trying the above solution the exception is still raised while deployment of the application
    I really appreciate if anyone can suggest me what is causing this exception and how can I fix this?
    Thanks,
    Srikanth

    Hi,
    if you deplyo to Application Server 10.1.3 make sure you install the ADF runtime libraries 10.1.3.1. Shut down the Application Server and use the runtime installer from the JDeveloper tools menu
    Frank

  • Java.lang.NoSuchMethodError: com.sap.tc.webdynpro.model.webservice.gci.WSTy

    Hello,
      I have SAP EH1 for SAP NWCE 7.1 and NWDS with the recent upgrade pack of WD. When I run my WD application the following exception ocurr,
      java.lang.NoSuchMethodError: com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.(Ljava/lang/String;Ljava/lang/String;Ljavax/xml/namespace/QName;Ljava/lang/String;Ljava/util/Map;Ljava/lang/String;Lcom/sap/tc/webdynpro/model/webservice/gci/IWSTypedModelInfo;Ljava/util/Map;Ljava/util/Map;)V
    at pe.com.minsur.wd_test_esr.wdtestesr_model.Wdtestesr_Model.<init>(Wdtestesr_Model.java:240)
        at pe.com.minsur.wd_test_esr.wdtestesr_app.comp.Wdtestesr_Comp.wdDoInit(Wdtestesr_Comp.java:111)
        at pe.com.minsur.wd_test_esr.wdtestesr_app.comp.wdp.InternalWdtestesr_Comp.wdDoInit(InternalWdtestesr_Comp.java:445)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:160)
        at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
    My DoInit Method only have this code,
    public void wdDoInit()
        Wdtestesr_Model model = new Wdtestesr_Model();
    Any ideas?
    Regards
    MG

    The problem is that the logical destinations are not well configured.

  • Java.lang.NoSuchMethodError: deadChild

    I'm running a unix shell script using Runtime.exec(). This returns a process. However, when I wait for the process to complete, I get the following error messages and the process hangs:
    java.lang.NoSuchMethodError: deadChild
    at java.lang.UNIXProcess.run(Native Method)
    at java.lang.Thread.run(Thread.java.481)The code that I'm using is as follows:
    final Runtime r = Runtime.getRuntime();
    Process p;
    // Execute external script and wait for its termination
    p = r.exec(cmd); 
    // cmd is an array containing the scriptname and parameters
    p.waitFor();Any ideas on what's causing the error?     

    I have not used deadChild anywhere in my code. The message shows the error is occurring a "Native Method" and not in my code. I interpret that to mean java.lang is calling it and not my code.

Maybe you are looking for