NamingException / SocketException during AppMod lookup

Hi,
below there is an Exception i received while try to connect to the AppModule,
deployed as "AppModule Session Bean", to an OC4J 9.0.2. At the End you see my
Sourcecode which produces the Exception.
Does anyone have an Idea whats going wrong with my sourcecode?
Regards Mirko
-- Exception --
Setting up Initial Context...
Diagnostics: (BC4J Bootstrap) Routing diagnostics to standard output (use -Djbo.debugoutput=silent to remove)
[00] Diagnostic Properties: Timing:false Functions:false Linecount:true Threshold:6
[01] CommonMessageBundle (language base) being initialized
[02] Stringmanager using default locale: 'null'
[03] BC4JDeployPlatform: EjbIas
Doing LookUp...de.orb.server.orbServerModule_cm
javax.naming.NamingException: Lookup error: java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read; nested exception is:
java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.remoteLookup()
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.initRemoteHome()
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.<init>(oracle.jbo.JboContext, java.lang.String)
oracle.jbo.common.JboHome oracle.jbo.client.remote.ejb.ias.InitialContextImpl.createJboHome(java.lang.String)
java.lang.Object oracle.jbo.common.JboInitialContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
de.orb.server.common.orbServerModule de.orb.net.CommunicationLayer.getApplicationModuleInstance(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String)
void de.orb.net.CommunicationLayer.connectToApplicationModule()
de.pantarhei.datacarrier.DataCarrier de.orb.net.CommunicationLayer.getPanelData(int)
void de.orb.MainFrame.jbInit()
void de.orb.MainFrame.<init>(java.lang.String)
void de.orb.MainApplication.<init>(java.lang.String[])
void de.orb.MainApplication.main(java.lang.String[])
couldn't connect to AppModule
-- source --
env.put (Context.INITIAL_CONTEXT_FACTORY, JboContext.JBO_CONTEXT_FACTORY);
env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_EJB_IAS);
env.put(JboContext.APPLICATION_PATH, "serverEJB");
env.put(Context.SECURITY_PRINCIPAL, "admin"); // OC4J User
env.put(Context.SECURITY_CREDENTIALS, "admin"); // OC4J Passwd
env.put(JboContext.HOST_NAME, machineNo);
env.put(JboContext.CONNECTION_PORT, portNo);
try {
System.out.println("Setting up Initial Context...");
Context ic = new InitialContext(env);
System.out.println("Doing LookUp..." + amName);
orbServerModuleHome home = (orbServerModuleHome)ic.lookup(amName);
System.out.println("Calling create...");
appMod = (orbServerModule)home.create();
System.out.println("establishing Connection...");
appMod.getTransaction().connect(connStr);
} catch(Exception ex) {
throw ex;

Hi,
below there is an Exception i received while try to connect to the AppModule,
deployed as "AppModule Session Bean", to an OC4J 9.0.2. At the End you see my
Sourcecode which produces the Exception.
Does anyone have an Idea whats going wrong with my sourcecode?
Regards Mirko
-- Exception --
Setting up Initial Context...
Diagnostics: (BC4J Bootstrap) Routing diagnostics to standard output (use -Djbo.debugoutput=silent to remove)
[00] Diagnostic Properties: Timing:false Functions:false Linecount:true Threshold:6
[01] CommonMessageBundle (language base) being initialized
[02] Stringmanager using default locale: 'null'
[03] BC4JDeployPlatform: EjbIas
Doing LookUp...de.orb.server.orbServerModule_cm
javax.naming.NamingException: Lookup error: java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read; nested exception is:
java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.remoteLookup()
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.initRemoteHome()
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.<init>(oracle.jbo.JboContext, java.lang.String)
oracle.jbo.common.JboHome oracle.jbo.client.remote.ejb.ias.InitialContextImpl.createJboHome(java.lang.String)
java.lang.Object oracle.jbo.common.JboInitialContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
de.orb.server.common.orbServerModule de.orb.net.CommunicationLayer.getApplicationModuleInstance(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String)
void de.orb.net.CommunicationLayer.connectToApplicationModule()
de.pantarhei.datacarrier.DataCarrier de.orb.net.CommunicationLayer.getPanelData(int)
void de.orb.MainFrame.jbInit()
void de.orb.MainFrame.<init>(java.lang.String)
void de.orb.MainApplication.<init>(java.lang.String[])
void de.orb.MainApplication.main(java.lang.String[])
couldn't connect to AppModule
-- source --
env.put (Context.INITIAL_CONTEXT_FACTORY, JboContext.JBO_CONTEXT_FACTORY);
env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_EJB_IAS);
env.put(JboContext.APPLICATION_PATH, "serverEJB");
env.put(Context.SECURITY_PRINCIPAL, "admin"); // OC4J User
env.put(Context.SECURITY_CREDENTIALS, "admin"); // OC4J Passwd
env.put(JboContext.HOST_NAME, machineNo);
env.put(JboContext.CONNECTION_PORT, portNo);
try {
System.out.println("Setting up Initial Context...");
Context ic = new InitialContext(env);
System.out.println("Doing LookUp..." + amName);
orbServerModuleHome home = (orbServerModuleHome)ic.lookup(amName);
System.out.println("Calling create...");
appMod = (orbServerModule)home.create();
System.out.println("establishing Connection...");
appMod.getTransaction().connect(connStr);
} catch(Exception ex) {
throw ex;
} Try..
ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(amName);
ApplicationModule appModd = home.create();
If you have exported methods then you should be able to cast the
appmodule returned by home.create() to you're appmodule interface. This is the interface generated in the common subpackage.

Similar Messages

  • NamingException and ClassCastException during jndi lookup

    Hi,
    I am trying to access the SAP database(MaxDb)using JNDI lookup in WebDynpro simple java project.
    But, during lookup I am getting the following error
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name : jdbc/VSLOOKUP , can not resolve object reference [Root exception is java.lang.ClassCastException]
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:469)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:558)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.vitalspring.healthbenefits.dbaccess.DBAccessHelper.main(DBAccessHelper.java:51)
    Caused by: java.lang.ClassCastException
         at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:149)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:466)
         ... 3 more
    Can anybody throw some light on it?
    Because, it's urgent for my project.
    I would appreciate any kind of help in this regard.
    Thanks & Regards,
    Rambabu Kancharla

    Hello Anilkumar,
    Sorry for delay in reply as I was on out of work and didn't get chance to check the SDN forums.
    I was able to do it in latest version sneak preview 11.
    I think the problem with the version.
    Thanks,
    Rambabu

  • Error during JNDI lookup Accessing Remote EJB (access to web service restricted using declarative security model)

    Hello everyone,
    I developed a Web Service prototype accessing remote EJB using the EJB
    control with special syntax in the jndi-name attribute: @jws:ejb
    home-jndi-name="t3://10.10.245.70:7131/AccountDelegatorEJB"
    Everything works fine, but I get an error when I restrict access to my web
    service with a declarative security model by implementing steps provided in
    help doc:
    - Define the web resource you wish to protect
    - Define which security role is required to access the web resource
    - Define which users are granted the required security role
    - Configure WebLogic Server security for my web service(Compatibility
    Security/Users)
    I launch the service by entering the address in a web browser. When prompted
    to accept the digital certificate, click Yes, when prompted for network
    authentication information, enter username and password, navigate to the
    Test Form tab of Test View, invoke the method by clicking the button and I
    get the following exception:
    <error>
    <faultcode>JWSError</faultcode>
    <faultstring>Error during JNDI lookup from
    jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed for
    name:t3://10.10.245.70:7131/AccountDelegatorEJB]</faultstring>
    <detail>
    <jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
    lookup from jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed
    for name:t3://10.10.245.70:7131/AccountDelegatorEJB] at
    weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
    8) at
    weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
    .java:220) at
    weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
    ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
    ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64) </jwErrorDetail>
    </detail>
    </error>
    I have a simple Hello method as well in my WebService (which is also
    restricted) and it works fine, but remote EJB access doesn't. I tested my
    prototype on Weblogic 7.2 and 8.1 platforms - same result.
    Is that a bug or I am missing some additional configuration in order to get
    that working. Has anyone seen similar behavior? Is there a known resolution?
    Or a suggested way to work around the problem?
    Thank you.
    Andre

    Andre,
    It would be best if this issue is handled as an Eval Support case. Please
    BEA Customer Support at http://support.beasys.com along with the required
    files, and request that an Eval support case be created for this issue.
    Thanks
    Raj Alagumalai
    WebLogic Workshop Support
    "Andre Shergin" <[email protected]> wrote in message
    news:[email protected]...
    Anurag,
    I removed "t3", still get an error but a different one (Unable to create
    InitialContext:null):
    <error>
    <faultcode>JWSError</faultcode>
    <faultstring>Error during JNDI lookup from
    jndi://secuser1:[email protected]:7131/AccountDelegatorEJB[Unable to
    create InitialContext:null]</faultstring>
    <detail>
    <jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
    lookup from
    jndi://secuser1:[email protected]:7131/AccountDelegatorEJB[Unable to
    create InitialContext:null] at
    weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
    8) at
    weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
    .java:220) at
    weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
    ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
    ibas.GetVisaHistoryTransactions.getVisaHistoryTxn(GetVisaHistoryTransactions
    .jws:67) </jwErrorDetail>
    </detail>
    </error>
    Note: inter-domain communication is configured properly. The Web Service to
    remote EJB works fine without a declarative security.
    Any other ideas?
    Thank you for your help.
    Andre
    "Anurag" <[email protected]> wrote in message
    news:[email protected]...
    Andre,
    It seems you are using the URL
    jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB
    whereas you should not be specifying the "t3:" protocol.
    The URL should be like
    jndi://secuser1:[email protected]:7131/AccountDelegatorEJB
    Please do let me know if you see any issues with this.
    Note that this will only allow you to access remote EJBs in the same WLS
    domain. For accessing EJBs on another domain, you need to configure
    inter-domain communication by
    following a few simple steps as mentioned at
    http://e-docs.bea.com/wls/docs81/ConsoleHelp/jta.html#1106135. This link has
    been provided in the EJB Control Workshop documentation.
    Regards,
    Anurag
    "Andre Shergin" <[email protected]> wrote in message
    news:[email protected]...
    Raj,
    I tried that before, it didn't help. I got similar error message:
    <error>
    <faultcode>JWSError</faultcode>
    <faultstring>Error during JNDI lookup from
    jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB[Lookup
    failed for
    name:t3://secuser1:[email protected]:7131/AccountDelegatorEJB]</faultstr
    ing>
    <detail>
    <jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
    lookup from
    jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB[Lookup
    failed for
    name:t3://secuser1:[email protected]:7131/AccountDelegatorEJB] at
    weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
    8) at
    weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
    .java:220) at
    weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
    ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
    ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64) </jwErrorDetail>
    </detail>
    </error>
    Anything else should I try?
    P.S. AccountDelegatorEJB, the remote EJB my Web Service calls is NOTaccess
    restricted.
    I hope there is a solution.
    Thanks,
    Andre
    "Raj Alagumalai" <[email protected]> wrote in message
    news:[email protected]...
    Andre,
    Can you try using the following url with username and password
    jndi://username:password@host:7001/my.resource.jndi.object ?
    once you add webapp level security, the authenticated is the user who
    invokes the EJB.
    http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/controls/ejb/con
    CreatingANewEJBControl.html?skipReload=true
    has more info on using remote EJB's.
    Hope this helps.
    Thanks
    Raj Alagumalai
    WebLogic Workshop Support
    "Alla Resnik" <[email protected]> wrote in message
    news:[email protected]...
    Hello everyone,
    I developed a Web Service prototype accessing remote EJB using the EJB
    control with special syntax in the jndi-name attribute: @jws:ejb
    home-jndi-name="t3://10.10.245.70:7131/AccountDelegatorEJB"
    Everything works fine, but I get an error when I restrict access to my
    web
    service with a declarative security model by implementing steps
    provided
    in
    help doc:
    - Define the web resource you wish to protect
    - Define which security role is required to access the web resource
    - Define which users are granted the required security role
    - Configure WebLogic Server security for my web service(Compatibility
    Security/Users)
    I launch the service by entering the address in a web browser. Whenprompted
    to accept the digital certificate, click Yes, when prompted for
    network
    authentication information, enter username and password, navigate tothe
    Test Form tab of Test View, invoke the method by clicking the buttonand
    I
    get the following exception:
    <error>
    <faultcode>JWSError</faultcode>
    <faultstring>Error during JNDI lookup from
    jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed for
    name:t3://10.10.245.70:7131/AccountDelegatorEJB]</faultstring>
    <detail>
    <jwErrorDetail> weblogic.jws.control.ControlException: Error during
    JNDI
    lookup from jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookupfailed
    for name:t3://10.10.245.70:7131/AccountDelegatorEJB] at
    weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
    8) at
    weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
    .java:220) at
    weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260)at
    ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
    ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64)</jwErrorDetail>
    </detail>
    </error>
    I have a simple Hello method as well in my WebService (which is also
    restricted) and it works fine, but remote EJB access doesn't. I testedmy
    prototype on Weblogic 7.2 and 8.1 platforms - same result.
    Is that a bug or I am missing some additional configuration in order
    to
    get
    that working. Has anyone seen similar behavior? Is there a knownresolution?
    Or a suggested way to work around the problem?
    Thank you.
    Andre

  • Prob in IR :Internal error during bean lookup for bean RepObjectAccessBean

    Hi,
        I am facing the problem in IR .
    <b>Internal error during bean lookup for bean RepObjectAccessBean</b>
    is the Error window I am getting frequently, After getting this error, It is no allowing to open any of the IR Objects.
    Thanks in advance,
    Dhanabal T

    Hi Dhanabal,
    i got the same error. But it is clear.
    Please chek once ur configuration part. The error is in configuration part only.
    once check all the steps in ur configuration part.
    REgards,
    chandra.

  • Error During SOAP Lookup

    Hi,
    I'm perforing a SOAP Lookup as explained in the Blog: Webservice Calls From a User Defined Function.
    However when i am testing it in Test Tab in message mapping it is showing an error "com.sap.aii.mapping.lookup.LookupException: Exception during processing the payload.Problem when calling an adapter by using communication channel SOAP_RECV (Party: , Service: AA_BS_RECV, Object ID: 4fb8e1fbeb0e3213a3381de6f63d9542) XI AF API call failed. Module exception: 'com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out:could be due to invalid address: java.net.SocketException: Connection timed out:could be due to invalid address'. Cause Exception: 'Connection timed out:could be due to invalid address'."
    When i test it end to end teh Look up is not returning any Value
    Can you please let me know what could be the Error.
    Thanks,
    Bhargav

    Hi Chirag,
    I have checked the Target URL and it is correct.
    There are no proxy settings so i have not given any authentication details
    Thanks,
    Bhargav

  • NamingException on EJB jndi lookup

    I have two applications - deployed under the "default instance".
    When I start up OC4J and deloy app1 and app2, then app1 can do a JNDI lookup on a session bean that resides in App2. It uses the RMIInitialContextFactory.
    Provider is "ormi://localhost/app2"
    My problem is that if I undeploy and redeploy app2, then app1 suddenly can't do a lookup to any sessionBean found in app2 anymore, even though the jndi name still shows up in the browser, and if I try to look it up from an external application running outside of oc4j (with exactly the same code as I'm using in app1), it also works.
    So why is app1 not able to find app2 via jndi after a redeployment?
    D

    Avi - thank you for your response.
    First of all, I run on Suse Linux 10.1. Dunno if that's any help, but hey, more info can't help :)
    Let's answer your questions:
    1.) OCJ4 Version: 10.1.3.0.0 (build 060119.1546.05277)
    2.) JDK Version: 1.5.0_07-b03
    As for your suggestions:
    1.) app1 = parent of app2.
    I'm rather new to Oracle, so maybe I made a mistake during my investigations. Still, I'd like to give a breakdown: I built a framework-type application, and thought about deploying "child modules" (plug-in applications) underneath it, as you proposed.
    This worked fine, but there comes a problem whenever you try to use something like Hibernate in any application that's not deployed in the root (ie any app that's deployed as a child of another). The problem came in 2 flavours:
    A) If you use a jar in the parent and try to do resource loading from the child, the context of the parent is used the whole time. Since the search-policy of the class-loader is loaded->parent->shared->local, and if Hibernate is already used in the parent, it never gets to the child and thus trying to load a resource in the child is futile since parent can't see child context.
    B) Lets say you're not using Hibernate at all in the parent application. When doing resource loading (eg the hibernate.cfg.xml file), Hibernate tries to locate the resource via Thread.currentThread().getContextClassLoader(). OC4J returns the parent-app's thread as the currentThread, NOT that of the child-application that you're actually running the code from, thus it will never be able to pick up resources from within a jar part of the child application. The only way that I managed to get it to work, was to include the Hibernate3.jar as part of the EAR deployment (ie listed it as <library path...> in the orion-application.xml. Putting it in shared-libs or app-libs didn't work...ever. Also, if I happened to use Hibernate in the parent-application, it doesn't matter if I put hibernate3.jar in the EAR of the child - the parent-version gets picked up and used due to the search-policy... NOTE: This is in a JAR - I'm not using WAR's so cannot force local loading as is possible with web-apps...
    I then opted to deploy applications seperately under the root, and using RMI to communicate from the framework-application to its "modules", and vice-versa. The master doesn't know the exact type of the remote interface of whatever child-module it needs to call, so it uses reflection to call the "create" on the EJBHome of whatever child-module it needs to invoke as well as the method on the actual remote-interface.
    Please note, if I deploy both applications (master and child), and perform JNDI lookups from master to child, it works perfectly. As soon as I do a redeploy (or explicity undeploy, deploy), JNDI fails. External clients, though, works all the time. Also, if I redeploy the child before ever calling it from the parent-application, it also works after I did redeployment. It's as if, when you do a JNDI lookup the first time, it caches something and from there on it breaks if you do a redeploy and perform a consequent app-to-app JNDI lookup...
    2.) dedicated.rmicontext=true
    I tried this by setting it as a JNDI property before getting the InitialContext - makes no difference, unfortunately.
    //========CODE============================
    // This is in a SessionBean inside the Master Application. For the time being I've hard-coded the provider-url of the client-application.
    // NOTE: This EXACT same code is used in the external java client - there it works perfect every time, whether I redeploy or not.
    //========================================
    Hashtable<String, String> env = new Hashtable<String, String>();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
    env.put(Context.PROVIDER_URL, "ormi://localhost/client-application");
    env.put(Context.SECURITY_PRINCIPAL, "oc4jadmin");
    env.put(Context.SECURITY_CREDENTIALS, "MyPassword");
    env.put("dedicated.rmicontext","true");
    InitialContext ctx = null;
    try {
         ctx = new InitialContext(env);
         // WHEN I REDEPLOY, CODE CRASHES ON THE NEXT LINE
         Object home = ctx.lookup("ejb/TestWorkerAProxyBean");
         EJBHome obHome = (EJBHome) PortableRemoteObject.narrow(home, EJBHome.class);
         System.out.println("EJBHOME Is [" + obHome + "]");
         final Object invocationTarget = MethodUtils.invokeExactMethod(obHome,"create",new Object[0]);
         System.out.println("invocation target = [" + invocationTarget + "]");
         ClassLoader classLoader = Thread.currentThread().getContextClassLoader();
         IWorkerProxy proxy = (IWorkerProxy)Proxy.newProxyInstance(classLoader, new Class[]{IWorkerProxy.class}, new InvocationHandler() {
              public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
                   try {
                        Method remoteEjbMethod = invocationTarget.getClass().getMethod(method.getName(),method.getParameterTypes());
                        return remoteEjbMethod.invoke(invocationTarget, args);
                   } catch (Exception e) {
                        ExceptionHandler.handle(e);
                   return null;
    } catch (NamingException ne) {
         System.out.println("NamingException");
         ne.printStackTrace();
    } catch (NoSuchMethodException e) {
         System.out.println("NoSuchMethodException");
         e.printStackTrace();
    } catch (Exception e) {
         System.out.println("Other Exception");
         e.printStackTrace();
    ==========================
    ===========EXCEPTION (ONLY IF I REDEPLOY - IT WORKS PERFECT IF I RUN IT FIRST TIME)=================
    ==========================
    06/09/25 17:15:51 NamingException
    06/09/25 17:15:51 javax.naming.NameNotFoundException: ejb/TestWorkerAProxyBean not found
    06/09/25 17:15:51 at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
    06/09/25 17:15:51 at javax.naming.InitialContext.lookup(InitialContext.java:351)
    06/09/25 17:15:51 at com.myapp.master.RequestProcessorBean.processRequest(RequestProcessorBean.java:140)
    06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    06/09/25 17:15:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    06/09/25 17:15:51 at java.lang.reflect.Method.invoke(Method.java:585)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.TxSupportsInterceptor.invoke(TxSupportsInterceptor.java:37)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
    06/09/25 17:15:51 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:86)
    06/09/25 17:15:51 at RequestProcessorLocal_StatelessSessionBeanWrapper4.processRequest(RequestProcessorLocal_StatelessSessionBeanWrapper4.java:37)
    06/09/25 17:15:51 at com.myapp.master.gateway.FrameworkGatewayBean.processObjectRequest(FrameworkGatewayBean.java:172)
    06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    06/09/25 17:15:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    06/09/25 17:15:51 at java.lang.reflect.Method.invoke(Method.java:585)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.TxSupportsInterceptor.invoke(TxSupportsInterceptor.java:37)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
    06/09/25 17:15:51 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:86)
    06/09/25 17:15:51 at FrameworkGatewayRemote_StatelessSessionBeanWrapper10.processObjectRequest(FrameworkGatewayRemote_StatelessSessionBeanWrapper10.java:94)
    06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    06/09/25 17:15:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    06/09/25 17:15:51 at java.lang.reflect.Method.invoke(Method.java:585)
    06/09/25 17:15:51 at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
    06/09/25 17:15:51 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    06/09/25 17:15:51 at java.lang.Thread.run(Thread.java:595)

  • Javax.naming.NameNotFoundException during a lookup() call.

    I am getting this exception when I try to get a reference to my Local Entity bean from within a Remote Session bean.
    ( I did a search in these forums, and found a few topics similar to mine. However, those that were similar were unfortunately still unresolved).
    I have a Session Bean with a Remote interface (ExecutionReportOperator),
    and an Entity Bean with a local interface (ExecutionReport). It is deployed in JBoss, here is output that indicates successful deployment:
    INFO [EjbModule] Deploying ExecutionReport
    INFO [EjbModule] Deploying ExecutionReportOperator
    INFO [BaseLocalProxyFactory] Bound EJB LocalHome 'ExecutionReport' to jndi 'local/ExecutionReport@4199584'
    INFO [ProxyFactory] Bound EJB Home 'ExecutionReportOperator' to jndi 'ExecutionReportOperator'
    INFO [EJBDeployer] Deployed: file:/C:/Program Files/jboss-4.0.3SP1/server/default/deploy/ExecReportingEJBs.jar
    Now, within my Session bean, I'm trying to get a reference to the Home interface of my Entity bean:
    private ExecutionReportHome getExecutionReportHomeObject()
    throws NamingException {
    InitialContext ic = new InitialContext();
    ExecutionReportHome erh = (ExecutionReportHome) ic.lookup("ExecutionReport");
    return erh;
    However this throws a Naming exception. I guess the string I'm sending in to the lookup() method needs to be adjusted/modified. I've tried "local/ExecutionReport" as well as the full package name, no luck. Does anyone know what the string should look like?
    Here are the contents of my ejb-jar.xml file:
    <enterprise-beans>
    <session>
    <ejb-name>ExecutionReportOperator</ejb-name>
    <home>com.fanfare.server.execReporting.beans.session.ExecutionReportOperatorHome</home>
    <remote>com.fanfare.server.execReporting.beans.session.ExecutionReportOperator</remote>
    <ejb-class>com.fanfare.server.execReporting.beans.session.ExecutionReportOperatorBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    <entity>
    <ejb-name>ExecutionReport</ejb-name>
    <local-home>com.fanfare.server.execReporting.beans.entity.ExecutionReportHome</local-home>
    <local>com.fanfare.server.execReporting.beans.entity.ExecutionReport</local>
    <ejb-class>com.fanfare.server.execReporting.beans.entity.ExecutionReportBean</ejb-class>
    <persistence-type>Container</persistence-type>
    <prim-key-class>java.lang.Integer</prim-key-class>
    <reentrant>false</reentrant>
    <cmp-version>2.x</cmp-version>
    <abstract-schema-name>ExecutionReport</abstract-schema-name>
    ...

    Some additional info: Just to test, I created a Remote interface for my Entity bean and deployed it to JBoss. Once I did that, I was able to successfully locate the Local object without any Naming exceptions. (No code changes to my original function, just created the Remote interface and deployed it).
    Hope this extra information is useful.

  • NamingException when trying to lookup DataSource (Oracle)

    I am using Sun 6.1 Web Server with Oracle 9i, and we are evaluating these products (so no support contract).
    I have a connection pool configured as follows:
    <RESOURCES>
    <JDBCCONNECTIONPOOL name="foo_pool" datasourceclassname="oracle.jdbc.pool.OracleDataSource" steadypoolsize="8" maxpoolsize="32" poolresizequantity="2" idletimeout="300" maxwaittime="60000" connectionvalidationrequired="on" connectionvalidationmethod="meta-data" validationtablename="" failallconnections="off" transactionisolationlevel="read-committed" isolationlevelguaranteed="off">
    <PROPERTY name="URL" value="jdbc:oracle:thin:@XX.XX.XX.XXX:1521:oracledv"/>
    <PROPERTY name="User" value=" . . . "/>
    <PROPERTY name="Password" value=" . . . "/>
    </JDBCCONNECTIONPOOL>
    <JDBCRESOURCE jndiname="jdbc/foo_pool" poolname="foo_pool" enabled="on"/>
    </RESOURCES>
    Of course the user and password values are filled in.
    The foo_pool object is there within the JDBC context, and the class of the object as reported by listBindings is javax.sql.DataSource.
    I am trying to lookup the DataSource from a JSP deployed within a web app.
    However, I am getting a NamingException with the explanation "cannot create resource instance". The cause and rootCause Throwable fields of this NamingException are null (big help that is).
    The line that causes the exception is the one that invokes lookup on the "jdbc" sub context, with the parameter "foo_pool".
    I have set up JDBC connection pools to Oracle in the past using WebLogic and JBoss, so I am at least somewhat competent at this. Still somehow I get the feeling that some class is missing, or there is an attempt to instantiate the wrong class or an incompatible class, but since there is no information beyond "cannot instantiate" I have no idea where else to look, after having googled until I am blue in the face.
    Can anyone help?
    Thanks,
    Erik

    Does this help?
    http://swforum.sun.com/jive/thread.jspa?forumID=16&threadID=24492

  • SocketException during reads - JVM_recv in socket input stream read

    I am getting a SocketException when a Java applet talks to our
    WebLogic 7.0 server. The catch is that it only occurs at one site
    (that has very high T1 utilization, although latency is only ~60 ms)
    Our setup is such that the calls hit an Alteon load balancer, which
    then sends the request out to one of 4 IIS clustered servers, where it
    then is sent to one of 2 WL clustered servers. I figured latency
    would be the cause, but on IIS and on WL, the timeouts are set to
    several hundred seconds, so I am not quite seeing where the connection
    is being reset. To be honest, I really don't know if it is WL that is
    killing the connection, as nothing abnormal shows up in the WL log. I
    have seen similar problems in this group, though, although the stack
    traces never follow the same path mine does. I do have the following
    call stack from the Java plug-in console, though. Any ideas would be
    greatly appreciated.
    java.net.SocketException: Connection reset by peer: JVM_recv in socket
    input stream read
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(Unknown Source)
         at java.io.BufferedInputStream.fill(Unknown Source)
         at java.io.BufferedInputStream.read1(Unknown Source)
         at java.io.BufferedInputStream.read(Unknown Source)
         at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
         at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
         at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
    Source)
         at sun.plugin.net.protocol.http.HttpURLConnection.getInputStream(Unknown
    Source)
         at sun.net.www.protocol.http.HttpURLConnection.getHeaderFields(Unknown
    Source)
         at sun.plugin.net.protocol.http.HttpURLConnection.checkCookieHeader(Unknown
    Source)
         at sun.plugin.net.protocol.http.HttpURLConnection.getInputStream(Unknown
    Source)
         at org.xxxx.abstracts.Controller.sendRequest(Controller.java:39)
         at org.xxxx.data.DataMediator.getDataNode(DataMediator.java:46)
         at sun.applet.AppletPanel.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    Also, here is my code, although I can't see anything on the client
    side that seems off:
    public Object sendRequest( Object request, URL receiver ) throws
    Exception{
    Object response = null;
    URLConnection con = null;
    ObjectOutputStream out = null;
    ObjectInputStream in = null;
    try {
    con = receiver.openConnection();
    con.setDoInput(true);
    con.setDoOutput(true);
    con.setUseCaches(false);
    con.setDefaultUseCaches(false);
    con.setAllowUserInteraction(false);
    out = new ObjectOutputStream(con.getOutputStream());
    out.writeObject(request);
    out.flush();
    out.close();
    in = new ObjectInputStream(con.getInputStream());
    response = in.readObject();
    in.close();
    } catch (ClassCastException e) {
    if( out != null ){
    out.close();
    if( in != null ){
    in.close();
    } catch (Exception e) {
    if( out != null ){
    out.close();
    if( in != null ){
    in.close();
    throw e;
    return response;

    There is a known bug on earlier 1.3.1 releases with sockets on Windows 2k
    and XP. I don't remember all the details.
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com/coherence.jsp
    Tangosol Coherence: Clustered Replicated Cache for Weblogic
    "Keith Patrick" <[email protected]> wrote in message
    news:[email protected]...
    I'm getting the exception on the client, which is an XP machine, while
    the server is Win2K. I can't recall which, but either the applet or
    the server runs 1.3x while the other runs 1.4. I discounted that
    factor, though, as the problem only occurs on one site, which on all
    others it works fine.
    "Cameron Purdy" <[email protected]> wrote in message
    news:<[email protected]>...
    Exception is in the applet or on the server?
    Would one of those by any chance be running on W2K with JDK 131_01 orolder?
    >>
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com/coherence.jsp
    Tangosol Coherence: Clustered Replicated Cache for Weblogic
    "Keith Patrick" <[email protected]> wrote in message
    news:[email protected]...
    I am getting a SocketException when a Java applet talks to our
    WebLogic 7.0 server. The catch is that it only occurs at one site
    (that has very high T1 utilization, although latency is only ~60 ms)
    Our setup is such that the calls hit an Alteon load balancer, which
    then sends the request out to one of 4 IIS clustered servers, where it
    then is sent to one of 2 WL clustered servers. I figured latency
    would be the cause, but on IIS and on WL, the timeouts are set to
    several hundred seconds, so I am not quite seeing where the connection
    is being reset. To be honest, I really don't know if it is WL that is
    killing the connection, as nothing abnormal shows up in the WL log. I
    have seen similar problems in this group, though, although the stack
    traces never follow the same path mine does. I do have the following
    call stack from the Java plug-in console, though. Any ideas would be
    greatly appreciated.
    java.net.SocketException: Connection reset by peer: JVM_recv in socket
    input stream read
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(Unknown Source)
    at java.io.BufferedInputStream.fill(Unknown Source)
    at java.io.BufferedInputStream.read1(Unknown Source)
    at java.io.BufferedInputStream.read(Unknown Source)
    at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
    at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
    at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
    Source)
    at
    sun.plugin.net.protocol.http.HttpURLConnection.getInputStream(Unknown
    Source)
    at sun.net.www.protocol.http.HttpURLConnection.getHeaderFields(Unknown
    Source)
    atsun.plugin.net.protocol.http.HttpURLConnection.checkCookieHeader(Unknown
    Source)
    atsun.plugin.net.protocol.http.HttpURLConnection.getInputStream(Unknown
    Source)
    at org.xxxx.abstracts.Controller.sendRequest(Controller.java:39)
    at org.xxxx.data.DataMediator.getDataNode(DataMediator.java:46)
    at sun.applet.AppletPanel.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
    Also, here is my code, although I can't see anything on the client
    side that seems off:
    public Object sendRequest( Object request, URL receiver ) throws
    Exception{
    Object response = null;
    URLConnection con = null;
    ObjectOutputStream out = null;
    ObjectInputStream in = null;
    try {
    con = receiver.openConnection();
    con.setDoInput(true);
    con.setDoOutput(true);
    con.setUseCaches(false);
    con.setDefaultUseCaches(false);
    con.setAllowUserInteraction(false);
    out = new ObjectOutputStream(con.getOutputStream());
    out.writeObject(request);
    out.flush();
    out.close();
    in = new ObjectInputStream(con.getInputStream());
    response = in.readObject();
    in.close();
    } catch (ClassCastException e) {
    if( out != null ){
    out.close();
    if( in != null ){
    in.close();
    } catch (Exception e) {
    if( out != null ){
    out.close();
    if( in != null ){
    in.close();
    throw e;
    return response;

  • Problems during service lookup

    Hello ,
    I have some weird problem using "keystore" service.
    In the normal way I make this call and things look good
    InitialContext ctx =  new InitialContext();
    o = (Object) ctx.lookup("keystore");
    manager = (KeystoreManager) o;
    the result of the lookup is KeyStoreManagerWrapperImpl and the cast works fine.
    But there are cases when the result of the lookup() call is rather different. Then I get
    $Proxy4 object which is useless in the latter approach
    some details of this object may be a bit prompting:
    I see this in the debuger
    RMI_P4: Dynamic Stub:com.sap.engine.services.keystore.KeyStoreManagerImpl
    And it comes from
    com.sap.engine.services.rmi_p4.reflect.LocalInvocationHandler .invokeToString( Object proxy)
    Implemented interfaces are:
    interface java.rmi.Remote
    interface com.sap.engine.services.rmi_p4.RemoteRef
    Available methods are :
    public final int $Proxy4.hashCode()
    public final boolean $Proxy4.equals(java.lang.Object)
    public final java.lang.String $Proxy4.toString()
    public final com.sap.engine.services.rmi_p4.RemoteObjectInfo $Proxy4.getObjectInfo()
    I tried to get the KeystoreManagerImpl which I see in the private members, but no luck
    What to do?
    What does this mean that I get this Proxy4 instance insted of KeyStoreManagerWrapperImpl?
    is there any problem with the service? How should this be fixed?

    Hi Guy,
    could you please explain how and where to add references to the interface and the service?
    Thanks,
    Jacob

  • Firefox freezes during DNS lookup

    On many pages, especially almost any eBay page, firefox gets part way through loading the page and then freezes. Sometimes it eventually finishes loading, but it may be after many minutes. The title of my question is because the firefox status bar always shows a message about looking up some URL during the freeze. I've tried safe mode, and it has no effect on the problem. I've checked for current updates of all plugins, especially Flash. Nothing changes this behavior.
    Some web pages load without this effect. On the same computer, neither IE nor Chrome has any problem with the same pages that freeze Firefox.

    can you try to reproduce this issue on Firefox 10?
    * getfirefox.com

  • ClassCast Exception during EJB lookup

    Context ctx = new InitialContext();
    Object ref = ctx.lookup("MessageSender");
    SenderHome senderHome= (SenderHome)PortableRemoteObject.narrow(ref,SenderHome.class);
    sender = senderHome.createSender();
    where MessageSender is the JNDI name of bean.
    The error is ::
    java.lang.ClassCastException: com.sap.message.sender.SenderHome#
    I have even tried SenderHome senderHome = (SenderHome)ref
    bcos SenderHome is locally deployed. I have also tried with SenderLocalHome ,but it also gives ClassCast Exception.
    Message was edited by:
            Shilpa Bhanot

    Hi,
    Have you tried to find out what the class actually is ?
    <code>
    Context ctx = new InitialContext();
    Object ref = ctx.lookup("MessageSender");
    Object objUnknown= PortableRemoteObject.narrow(ref,SenderHome.class);
    System.out.println ("Class of object is :" +objUnknown.getClass());
    </code>

  • Error during lookup of remote ejb CaseService - Oracle ACM 12C Standalone

    StandAlone Setup:
    CD %ORACLE_HOME%\soa\common\bin
    set QS_TEMPLATES=%ORACLE_HOME%\soa\common\templates\wls\oracle.soa_template_12.1.3.jar, %ORACLE_HOME%\osb\common\templates\wls\oracle.osb_template_12.1.3.jar
    qs_config.cmd
    Then ran config.cmd from WLS and extended BPM domain, then was able to see composer app in deployment.
    AdminServer Args:
    set USER_MEM_ARGS=-Xms512m -Xmx3096m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=1024m
    Error
    ====
    Error during ejb lookup from bpm services client.
    Error during lookup of remote ejb CaseService .
    Contact Oracle support if exception can not be fixed.
            at oracle.bpm.client.impl.casemgmt.CaseManagementServiceRemoteClient.get
    CaseService(CaseManagementServiceRemoteClient.java:86)
            at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
    til.getCaseService(NotificationCallbackUtil.java:158)
            at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
    til.isActivityRegistered(NotificationCallbackUtil.java:167)
            at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
    til.registerEmailActivity(NotificationCallbackUtil.java:83)
            at oracle.bpm.casemgmt.fabric.CaseManagementServiceEngine.stateChanged(C
    aseManagementServiceEngine.java:1340)
            at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListene
    rs(FabricLifecycle.java:54)
            at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(Fabr
    icLifecycle.java:41)
            at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshI
    mpl.java:204)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:606)
            at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
    on(AopUtils.java:318)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
    inpoint(ReflectiveMethodInvocation.java:183)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
    ReflectiveMethodInvocation.java:150)
            at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEven
    tAspect.java:71)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
    ReflectiveMethodInvocation.java:172)
            at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
    cAopProxy.java:202)
            at com.sun.proxy.$Proxy324.postDeployInit(Unknown Source)
            at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.r
    un(FabricKernelInitializerServlet.java:1008)
            at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
    (WorkManagerExecutor.java:184)
            at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
    er.java:184)
            at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused By: javax.naming.NameNotFoundException: While trying to lookup 'ejb.bpm.c
    ase.CaseService' didn't find subcontext 'bpm'. Resolved 'ejb'; remaining name 'b
    pm/case/CaseService'
            at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic
    NamingNode.java:1180)
            at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.jav
    a:265)
            at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.j
    ava:187)
            at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:21
    0)
            at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:22
    4)
            at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.j
    ava:253)
            at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
            at javax.naming.InitialContext.lookup(InitialContext.java:411)
            at oracle.bpm.client.impl.casemgmt.CaseManagementServiceRemoteClient.get
    CaseService(CaseManagementServiceRemoteClient.java:80)
            at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
    til.getCaseService(NotificationCallbackUtil.java:158)
            at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
    til.isActivityRegistered(NotificationCallbackUtil.java:167)
            at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
    til.registerEmailActivity(NotificationCallbackUtil.java:83)
            at oracle.bpm.casemgmt.fabric.CaseManagementServiceEngine.stateChanged(C
    aseManagementServiceEngine.java:1340)
            at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListene
    rs(FabricLifecycle.java:54)
            at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(Fabr
    icLifecycle.java:41)
            at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshI
    mpl.java:204)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:606)
            at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
    on(AopUtils.java:318)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
    inpoint(ReflectiveMethodInvocation.java:183)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
    ReflectiveMethodInvocation.java:150)
            at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEven
    tAspect.java:71)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
    ReflectiveMethodInvocation.java:172)
            at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
    cAopProxy.java:202)
            at com.sun.proxy.$Proxy324.postDeployInit(Unknown Source)
            at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.r
    un(FabricKernelInitializerServlet.java:1008)
            at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
    (WorkManagerExecutor.java:184)
            at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
    er.java:184)
            at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    >
    Please help. The problem does not occur with Integrated WLS. I think the config scripts are correctly running from JDev.

    Hi,
    It's not easy to tell what's wrong with your example.
    Maybe you could send me a zip and I'll check when I have some time.
    By the way, you're asking a question about the lookup of an EJB3, I wrote an article that covers that topic.
    It should give you some interesting input.
    http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html
    Regards.

  • Problem with IIOP/JAAS during lookup

    Hello,
    For the application that we are supporting, Weblogic 8.1 SP3 is used for development. We get a strange error when using JAAS and IIOP for Authentication in our application which has a web interface(JSP) which I have explained below.
    Basically we followed the procedure mentioned on the URL http://edocs.bea.com/wls/docs81/security/fat_client.html. I guess the procedure is same for both Swing client and Web client. Eventhough on the production set-up we run the application with classpath on the manifest file, we use only system classpath for development.
    First we got the error below when we started the application with classpath referring the weblogic.jar.
    javax.security.auth.login.LoginException: java.net.ConnectException: iiop://localhost:7001: Destination not reachable using: 'iiop'; No available router to destination
    After going thru the forum we understood that referring wlclient.jar will solve this problem. So we referred wlclient.jar before referring weblogic.jar on the classpath setting.
    However on starting the server we got the following error
    javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassCastException]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    52)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:175)
    at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
    at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
    at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
    We investigated this further and found that the class "weblogic.jndi.WLInitialContextFactory " in wlclient.jar is creating the problem. So to proceed further on this, we copied wlclient.jar as tempwlclient.jar and removed this class from the "weblogic.jndi.WLInitialContextFactory" from the tempwlclient.jar . We then referred tempwlclient.jar in the classpath (instead of wlclient) before referring weblogic.jar.
    Now the server started and the JAAS authentication was successful and "loginContext.login()" got executed without any error. Now to propagate this subject to EJB call, we used
    Security.runAs( <<loggedInSubject>> , <<inner class>> );
    On doing this we get the following error which is our main problem. We are not able to solve this. Is this because we have both tempwlclient.jar and weblogic.jar on the classpath ? Any ideas on how to solve this. Since we have to close this issue immediately, could you please help us to solve this issue.
    javax.naming.NamingException: Unhandled exception in lookup [Root exception is java.lang.ClassCastException]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:237)
    at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at com.su.tl.explorer.controller.ControllerConnectionManager.getTreeModelServerReference(ControllerConnectionManager.java:100)
    at com.su.tl.abstractui.TreeModelServerConnectionManager.getTreeModelServer(TreeModelServerConnectionManager.java:56)
    at com.su.tl.explorer.webpresentation.taglib.ExplorerRootNodesTag$1.run(ExplorerRootNodesTag.java:55)
    at weblogic.security.subject.SubjectProxy.doAs(SubjectProxy.java:89)
    at weblogic.security.subject.SubjectManager.runAs(SubjectManager.java:258)
    at weblogic.security.Security.runAs(Security.java:67)
    at com.su.tl.explorer.webpresentation.taglib.ExplorerRootNodesTag.doStartTag(ExplorerRootNodesTag.java:49)
    at jsp_servlet._jsp.__nav_index._jspService(__nav_index.java:200)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:463)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6456)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: java.lang.ClassCastException
    at weblogic.security.service.SecurityManager.getCurrentSubject(SecurityManager.java:43)
    at weblogic.iiop.OutboundRequestImpl.<init>(OutboundRequestImpl.java:54)
    at weblogic.iiop.IIOPRemoteRef.getOutboundRequestInternal(IIOPRemoteRef.java:106)
    at weblogic.iiop.IIOPRemoteRef.getOutboundRequest(IIOPRemoteRef.java:127)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:276)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
    at weblogic.corba.cos.naming.NamingContextAny_IIOP_WLStub.resolve_any(Unknown Source)
    at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
    ... 22 more
    Thanks in advance..
    RB

    Here is variation on the topic:
    weblogic.corba.j2ee.naming.ContextImpl$UnsupportedOperationException: naming operation using Name
    at weblogic.corba.j2ee.naming.ContextImpl.getNameInNamespace(ContextImpl.java:508)
    at javax.naming.InitialContext.getNameInNamespace(InitialContext.java:485)
    comes when t3 pure java client uses wljmsclient.jar + wlclient.jar without weblogic.jar
    The moment i use weblogic.jar in place of both client jars client has no problem finding resources and communicating via jms. Client is a stand-alone Swing app that needs to drop and receive msgs. For deployment i only compile java app. What do i miss?

  • Message bean does not start automatically during application server startup

    I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
    Thanks,
    Bill
    #1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
    #1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
    #1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
    #1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
    #1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
    #1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
    #1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
    #1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
    #1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    ... 12 more
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
    Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
    #1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
    #1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
    java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                    at java.lang.Class.getDeclaredConstructors0(Native Method)
                    at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                    at java.lang.Class.getConstructor0(Class.java:1930)
                    at java.lang.Class.newInstance0(Class.java:278)
                    at java.lang.Class.newInstance(Class.java:261)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                    at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                    at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at javax.security.auth.Subject.doAs(Subject.java:379)
                    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
    I've could change that yes, but the startup script doesn't seemed to have this mind.
    Regards,
    Sve

Maybe you are looking for

  • Can you convert a PDF to Word in Arabic?

    Hello, Can you convert a pdf to word in Arabic? When I want to convert a file, adobe does not offer me Arabic. Can you help me please? Thank's

  • Captivate 2 Quiz Problem 2

    We have our quizzes set to place users who do not score a certain percentage on the quiz back to the beginning to retake the quiz. Several people who have "failed" quizzes and been put back at the start to retake the quizzes have then been "Frozen" a

  • Cover flow glitches

    i added custom album art with iTunes, and it's acting all glitchy. i don't really know how to explain. Here's some screenshots http://s225.photobucket.com/albums/dd283/legoboy1234/Cover%20Flow%20Glitches/

  • Gps gone crazy after 7.1 update

    Hi everyone. I ran my daily routine on a standart route. But after last ios update (7.1) my iphone 5's gps receiver gone crazy. I'm using Runkeeper for keeping data. But I've tried runtastic and moves too. Its all same. I attached a screenshot, so yo

  • Blocking Firefighter IDs login

    Hi Gurus, The Firefighter IDs are user type Service, is there anyway we can limit the direct login under these IDs other than withholding passwords? Thanks