Unable lookup Datasource from EJB

I am unable to lookup the datasource from my entity bean. I am using BMP in Weblogic
81. The call in the bean is :
ds = (DataSource)jndiContext.lookup("java:comp/env/jdbc/myPool");
I get the following exception:
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundExcept
ion: While trying to lookup 'jdbc.myPool' didn't find subcontext 'jdbc' Re
solved ; remaining name 'jdbc/myPool'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic
NamingNode.java:869)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.jav
In my config.xml file, I have the pool setup as:
<JDBCConnectionPool DriverName="oracle.jdbc.OracleDriver"
Name="myPool" Password="{3DES}PKeN6pXlt/o="
Properties="user=dmluser" Targets="myserver"
TestConnectionsOnCreate="true" TestConnectionsOnReserve="true"
TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:oracle:thin:@localhost:1521:DEV"/>
<JDBCTxDataSource JNDIName="myPool" Name="myPool"
PoolName="myPool" Targets="myserver"/>
Any ideas of what might be wrong?
Thanks
Tom

You have defined the datasource with a global JNDI name, so
jndiContext.lookup("myPool") would work.
java:/comp/env is a JNDI namespace local to your component. So if you
will need to add a mapping in your BMP's ejb-jar.xml and
weblogic-ejb-jar.xml that maps comp/env/jdbc/myPool to the myPool name
in the global JNDI.
-- Rob
Tom Jordan wrote:
I am unable to lookup the datasource from my entity bean. I am using BMP in Weblogic
81. The call in the bean is :
ds = (DataSource)jndiContext.lookup("java:comp/env/jdbc/myPool");
I get the following exception:
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundExcept
ion: While trying to lookup 'jdbc.myPool' didn't find subcontext 'jdbc' Re
solved ; remaining name 'jdbc/myPool'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic
NamingNode.java:869)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.jav
In my config.xml file, I have the pool setup as:
<JDBCConnectionPool DriverName="oracle.jdbc.OracleDriver"
Name="myPool" Password="{3DES}PKeN6pXlt/o="
Properties="user=dmluser" Targets="myserver"
TestConnectionsOnCreate="true" TestConnectionsOnReserve="true"
TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:oracle:thin:@localhost:1521:DEV"/>
<JDBCTxDataSource JNDIName="myPool" Name="myPool"
PoolName="myPool" Targets="myserver"/>
Any ideas of what might be wrong?
Thanks
Tom

Similar Messages

  • Jboss & Looking up DataSource from Client (not in Jboss)

    I have a project that will be describered as follows,
    1. Using Jboss server in which a DataSource is deployed
    2. Developing the Java client that looking up the above DataSource.
    My little problem is the java client is not deployed in Jboss, that is the normal java program. So can the client look up the DataSouce?
    Any help is appropriate!

    Actually I was wrong, and it makes sense why. This post is from
    David Jencks, if I recall he is the author of the JCA subsystem on jboss. This was his post on the jboss web-board (Had to look cause I tried it). I hope that you can develop some session facade beans to do whatever you would like. : )
    davidjencks
    Posts: 1,927
    Registered: Jun, 2001
    Re: Lookup DataSource from remote client      Posted: Apr 2, 2003 12:31 AM
    This is impossible and an extremely bad idea for numerous reasons.
    Write a session bean to do the db work, and call it from the remote clients.

  • How can I look up DataSource from one EJB to the other EJB?

    Image that, I have 3 databases:
    DB1
    DB2
    DB3,
    And then, 03 DataSources is deployed in DS EJB, named DataSource1, DataSource2, DataSource3.
    In the other App EJB, I have Connection Management function, as follows:
    public Connection getConnection(databaseKey) {
    if (databaseKey.equals("DB1")){
    connection = remote.lookup("DataSource1");
    }else if (databaseKey.equals("DB2")){
    connection = remote.lookup("DataSource2");
    }else if (databaseKey.equals("DB3")){
    connection = remote.lookup("DataSource3");
    return connection;
    How can I access DataSource 1,2,3 from the other EJB? How to config EJB server for that?
    Thanks in advance!
    Now, I have the other App EJB. Some class will require one of the above DataSource from DS EJB through function getConnection(databaseKey){}

    I strongle suggest you to use a ServiceLocator for this . It will be very easy to identify.Go to the sun home page and look for a servicelocator pattern.You can even directly use that code for you.

  • Unable to invoke a EJB from a BPEL process

    I am unable to invoke a EJB from a BPEL process. Whenever I try to test it from the oracle EM, I get the below exception. I am using WebLogic 10.3.3, SOA suite 11.1.1.3 and JDev 11.1.1.3 .
    This is what I see from the EM....
    Non Recoverable System Fault :
    javaInterface attribute for the binding is missing or the inteface class is not available.
    Below is a part of the stack trace from the soa server log…
    Caused By: oracle.classloader.util.AnnotatedClassNotFoundException:
    Missing class: com.abc.GreetingEJBBean
    Dependent class: oracle.integration.platform.blocks.ejb.SDOEjbReferenceD
    elegateImpl
    Loader: sun.misc.Launcher$AppClassLoader@20929799
    Code-Source: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
    /modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
    Configuration: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
    /modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
    Piece of xml from the composite.xml
    <reference name="GreetingService"
    ui:wsdlLocation="http://123.45.218.140:7001/GreetingEJBBean/GreetingEJBBeanService?wsdl">
    <interface.wsdl interface="http://abc.com/#wsdl.interface(GreetingEJBBean)" />
    <binding.ejb uri="GreetingEJB-GreetingEJB-GreetingEJB"
    javaInterface="com.abc.GreetingEJB"/>
    </reference>
    Looks like its not able to find the javaInterface mentioned above.
    I have a simple EJB with one business method and a very simple BPEL process.
    @Stateless(name = "GreetingEJB", mappedName = "GreetingEJB-GreetingEJB-GreetingEJB")
    @WebService
    public class GreetingEJBBean implements GreetingEJB {
    public GreetingEJBBean() {
    public String greetUser(String name){
    return ("Hello " + name);
    Any help would be greatly appreciated.

    I haven't tried from a BPEL process, but I have had success (as in Lucas's blogs) of using services and references as EJB Java Interface. This is with EJB java interfaces solely of base types (i.e. String foo(String s)).
    At high level here's what I have noted so far:
    1. Per Lucas's blog, @javaInterface is not being added to the ejb.binding automatically but it's not clear to me when this is and is not required given that interface.java is specified for the reference or service. Would interface.java and @javaInterface ever be different? I've been adding @javaInterface manually anyways since Lucas is a smart guy and I'd rather avoid errors. :-)
    2. Dropping an EJB interface jar in SCA-INF/lib works, but I've had the problem that the JDeveloper SOA Plugin doesn't see those classes until I stop and restart JDeveloper. Until then, I'm confronted with the java->wsdl mapping error. I was sort of primed to figure this one out since I ran into similar issues with SOA SpringBean components.
    3. Dropping EJB interface source in SCA-INF/src is more reliable, because then I can build the project (i.e. create SCA-INF/classes) and the JDeveloper SOA Plugin seems to resolve these brand new classes immediately.
    4. I've tried to invoke an EJB java-interface reference with a slightly complicated java interface (a class parameter with some fields, one of which is an array of another class). The auto-generated WSDL doesn't look exactly right to me (but I'm new to JAXB). Mediator maps to it just fine and the project compiles and deploys normally but fails at runtime. I have not researched in depth. It's not clear to me from the documentation and release notes whether I should expect for it to work, or whether I should expect to have to create my own JAXB mapping. If the latter, I really need a good example!

  • Fail to lookup the local EJB by JNDI in Managed Server

    Hi all,
    I currently in a deep problem, and can't figure out the cause of it. It just annoying me for week.
    In my app, I have binded to the local ejb to JNDI (let's say "ejb/CustomerLocal"), then the client lookup the Local EJB by the following code.
    localIc = new InitialContext();
    home = (EJBLocalHome)localIc.lookup("ejb/CustomerLocal");
    It works well as I do development in the Domain Admin Server. However, when I do the System Integration Test and deploy my app to the managed server, the app fail. It just can't do the Local EJB lookup. Following is the exception.
    javax.naming.NameNotFoundException: Unable to resolve 'ejb/CustomerLocal' Resolved ejb[Root exc
    eption is javax.naming.NameNotFoundException: Unable to resolve 'ejb.CustomerLocal' Resolved ejb
    ]; remaining name CustomerLocal'
    Does anybody know the cause of it and have solution?
    Thanks a lot

    Hi,
    Just now I replicated the same problem what you are facing. I created one managed server. When I deployed my ejb to admin server I did not get any problem. But when I deploy the same into my managed server I got Naming Exception. Because I did n/t specify Context.PROVIDER_URL. A provider URL contains bootstrap server information that the initial context factory can use to obtain an initial context. So when you deploy EJB on another server, you have to get the Naming service from that server. Hence provider URL must pointing to that server. So I included following statements before lookup my ejb in managed server.
    Properties p=new Properties ();
    p.put (Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
    p.put (Context.PROVIDER_URL,"t3://localhost: 7003");
    Context ctx=new InitialContext (p);
    FacadeHome home=(FacadeHome) ctx.lookup ("ejb/CustomerLocal");
    In my case managed server port number is 7003. Now onwards managed server (Port number 7003) will provide ‘Naming Service’, not by admin server (port number 7001), which is default.
    Note: Context.PROVIDER_URL— specifies the URL of the WebLogic Server that provides the name service. The default is t3://localhost: 7001. When you are not specified it will assume that POVIDER_URL is t3://localhost: 7001 this is nothing but your admin server in your case. However, a JNDI client may need to access a name space other than the one identified in its environment. In this case, it is necessary to explicitly set the java.naming.provider.url (provider URL) property used by the InitialContext constructor.
    I hope it helps.
    Regards,
    Kuldeep Singh.

  • Access Datasource from Servlet Engine (Tomcat)

    Hi,
    I'm using datasource connections in my beans and event in servlets.. It works fine in JRun 3.1 environment.
    But when I port to J2EE1.3 its throwing this exception...
    I just want to understand whether it is a limitation in J2EE1.3 & Tomcat environment or it is a security problem or do I have to change any configuration file so that I can make the datasource connection available outside the J2EE environment.
    java.lang.IllegalArgumentException: Unknown component type      at com.sun.enterprise.naming.NamingManagerImpl.getComponentType(NamingManagerImpl.java:670)      at com.sun.enterprise.naming.NamingManagerImpl.getMangledIdName(NamingManagerImpl.java:708)      at com.sun.enterprise.naming.NamingManagerImpl.getComponentIdInternal(NamingManagerImpl.java:680)      at com.sun.enterprise.naming.NamingManagerImpl.getComponentId(NamingManagerImpl.java:313)      at com.sun.enterprise.naming.java.javaURLContext.getComponentContext(javaURLContext.java:397)      at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:51)      at javax.naming.InitialContext.lookup(InitialContext.java:350)      at com.camilion.env.ejb.EjbEnvironment.getJDBCConnection(EjbEnvironment.java:105)      at com.camilion.report.servlet.ReportServlet.service(ReportServlet.java:49)      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)      at org.apache.catalina.servlets.InvokerServlet.serveRequest(InvokerServlet.java:428)      at org.apache.catalina.servlets.InvokerServlet.doGet(InvokerServlet.java:180)      at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)      at org.apache.catalina.core.ApplicationFilterChain.access$0(ApplicationFilterChain.java:197)      at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176)      at java.security.AccessController.doPrivileged(Native Method)      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172)      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)      at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)      at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)      at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:215)      at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)      at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)      at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)      at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)      at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)      at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2314)      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)      at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)      at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:368)      at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)      at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)      at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:163)      at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)      at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)      at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)      at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:995)      at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1088)      at java.lang.Thread.run(Thread.java:484)

    I'm getting the same problem trying to lookup a datasource from a JSP with J2EE 1.3 reference implementation.

  • Error while importing EJB model in Web dynpro: Unable to fetch the EJBs.

    Hi,
    We are getting the below error while importing ejb model to Web dynpro.
    Error :
    Unable to fetch the EJBs. Check if the selected Enterprise Application contain the EJBs.
    I have created the public part-> It has a reference to EJB client and the enterprise application also has reference to the EJB project.The EJB is also added in dependency list.
    But still we are getting this error. Could anyone please explain what can i do to solve this issue.
    Best Regards,
    Karthika

    Hi Vishweshwara,
    Thanks for your reply.
    Please find the steps i followed while importing EJB model in webdynpro.
    1. The Entity forwarding permission has been enabled.
    2. public part reference has been created and through the reference entity option the ejbDC->Client public part is selected.
    I followed all the steps mentioned in the document. But still i am getting that error. In EJB DC we have list of JPA entities and stateless session beans are exposed as a webservice(top-down manner).The enterprise application has a reference to the EJB DC.
    I could be able to invoke the ejb service beans from ejb explorer and Webservice navigator.
    I am able to insert,delete and modify the records from there.
    Please let me know what could i do to resolve this error?
    Best Regards,
    Karthika
    Edited by: SAKarthika on Apr 29, 2011 1:43 PM

  • Error while using LiveCycle java APIs with Http servlets:"Remote EJBObject lookup failed for ejb/Inv

    Hi all,
    When i try to run more than one servelt of the Quick Start samples that using Livecycle Java APIs and i get an error of "Remote EJBObject lookup failed for ejb/Invocation provider" from any servelt i run.
    I try some Quick samples which is not servelts (java class) and it works fine, which makes me sure that my connection properties is true.
    Environment:
    The LiveCycle is based on "Websphere v6.1", and i use "Eclipse Platform
    Version: 3.4.1".
    i install "tomcat 5.5.17" to test the servelts in developing time through Eclipse.(only for test in developing time not for deploy on )
    The Jars i added in the classpath:
    adobe-forms-client.jar
    adobe-livecycle-client.jar
    adobe-usermanager-client.jar
    adobe-utilities.jar
    ejb.jar
    j2ee.jar
    ecutlis.jar
    com.ibm.ws.admin.client_6.1.0.jar
    com.ibm.ws.webservices.thinclient_6.1.0.jar
    server.jar
    utlis.jar
    wsexception.jar
    My code is :
    Properties ConnectionProps = new Properties();
    ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_EJB_ENDPOINT, "iiop://localhost:2809");
    ConnectionProps.setProperty ServiceClientFactoryProperties.DSC_TRANSPORT_PROTOCOL,ServiceClientFactoryProperties.DSC_ EJB_PROTOCOL);
    ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE,ServiceClientFa ctoryProperties.DSC_WEBSPHERE_SERVER_TYPE);
    ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_USERNAME, "Administrator");
    ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_PASSWORD, "password");
    ConnectionProps.setProperty("java.naming.factory.initial", "com.ibm.ws.naming.util.WsnInitCtxFactory");
    //Create a ServiceClientFactory object
    ServiceClientFactory myFactory = ServiceClientFactory.createInstance(ConnectionProps);
    //Create a FormsServiceClient object
    FormsServiceClient formsClient = new FormsServiceClient(myFactory);
    //Get Form data to pass to the processFormSubmission method
    Document formData = new Document(req.getInputStream());
    //Set run-time options
    RenderOptionsSpec processSpec = new RenderOptionsSpec();
    processSpec.setLocale("en_US");
    //Invoke the processFormSubmission method
    FormsResult formOut = formsClient.processFormSubmission(formData,"CONTENT_TYPE=application/pdf&CONTENT_TYPE=app lication/vnd.adobe.xdp+xml&CONTENT_TYPE=text/xml", "",processSpec);
    List fileAttachments = formOut.getAttachments();
    Iterator iter = fileAttachments.iterator();
    int i = 0 ;
    while (iter.hasNext()) {
    Document file = (Document)iter.next();
    file.copyToFile(new File("C:\\Adobe\\tempFile"+i+".jp i++;
    short processState = formOut.getAction();
    ...... (To the end of the sample)
    My Error was:
    com.adobe.livecycle.formsservice.exception.ProcessFormSubmissionException: ALC-DSC-031-000: com.adobe.idp.dsc.net.DSCNamingException: Remote EJBObject lookup failed for ejb/Invocation provider
    at com.adobe.livecycle.formsservice.client.FormsServiceClient.processFormSubmission(FormsSer viceClient.java:416)
    at HandleData.doPost(HandleData.java:62)
    at HandleData.doGet(HandleData.java:31)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
    a

    I assume here that your application is deployed on a different physical machine of where LCES is deployed and running.
    Do the following test:
    - Say that LCES is deployed on machine1 and your application is deployed on machine2. Ping machine1 from machine2 and note the ip address.
    - Ping machine1 from machine1 and note the ip address.
    The two pings should match.
    - Ping machine2 from machine1 and note the ip address.
    - Ping machine2 from machine2 and note the ip address.
    The two pings should match.
    Usually this kind of error would happen if your servers have internal and external ip addresses.

  • JCo 3.0  - RFC call from EJB with SSO

    Hello,
    I am trying to call abap using JCo 3.0 from EJB (NW CE 1.0). I have configured destination on server with authentication method to use SAP Logon tickets. But when I call my EJB method that looks like this:
    JCoDestination dest=JCoDestinationManager.getDestination("RFCCallTest");
    JCoRepository repo=dest.getRepository();
    JCoFunction f= repo.getFunction("ZMG_RET_NAME");
    JCoParameterList in=f.getImportParameterList();
    in.setValue(0, "param1");
    f.execute(dest);
    I get an exception when executing the first line of code:
    Message:     Exception occurred during lookup of RFC Destination RFCCallTest: No SAP logon ticket found
    Category:     /System/Security
    Location:com.sap.security.core.server.destinations.provider.DestinationsProviderFrame.getDestinationProperties()
    When I change the destination authentication method to Technical user it works well.
    SSo between the servers works.
    This scenarion also works when I use older JCo implementation (2.x)
    BR
    Viktor

    Hi Bill,
    I too faced the same problem for quite some time on SP9. I thought it was the adapter problem that persisted ...but it was not !!
    After importing the RFC structure into XI, if the name of the imported RFC program is renamed/changed on R/3 side, then you will get the same error "lookup of binding via CPA-cache failed for AdapterType RFC, AdapterN."
    So make sure that RFC program name on the R/3 side was not changed/renamed after you have imported the RFC structure into XI.
    If the RFC program name had changed, make sure you reimport the RFC structure to avoid this problem.
    Regards,
    Sridhar

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

  • S:RSSDK:400 Unable to create javax.ejb.EJBObject

    Hello Guys,
       I'm trying to extract information from xPD in to BW and the error message S:RSSDK:400 Unable to create javax.ejb.EJBObject is raised during the dataload. If you have any suggestion, please let me know.
    Thanks and Regards,
    Iván.

    can anybody help to solve? rwrd pts

  • Stand-alone JNDI lookup of an EJB in an Enterprise Application (EAR) build

    Hi All,
    I am having some difficulty doing JNDI look up an EJB 3.0 Bean that is part of an Enterprise Application (EAR) build. Below are all the related codes:
    package ejb;
    import javax.ejb.Local;
    @Local
    public interface Hello1Local {
        public String getHello1();
    package ejb;
    import javax.ejb.Stateless;
    @Stateless
    public class Hello1Bean implements Hello1Local {
        public String getHello1() {
            return "I am Hello1 Bean!";
    package ejb;
    import javax.ejb.Remote;
    @Remote
    public interface Hello2Remote {
        public String getHello2();
    package ejb;
    import javax.ejb.Stateless;
    import javax.ejb.EJB;
    @Stateless
    @EJB(name="ejb/Hello1",
         beanInterface=Hello1Local.class,
         beanName="Hello1Bean")
    public class Hello2Bean implements Hello2Remote {
        @EJB private Hello1Local hello1bean;
        public String getHello2() {
            return hello1bean.getHello1();
    There is no problem looking up Hello2 Bean using an Application Client such as the following:
    public class LocalHelloApplicationClient {
        @EJB(name="Hello2")
        private static Hello2Remote hello2Bean;
        public static void main(String[] args) {
            System.out.println("hello2Bean.getHello2(): " + hello2Bean.getHello2());
    }There is also no problem doing JNDI lookup (from a Stand-Alone Client the same bean if both Hello1 and Hello2 were created by themselves. ie not part of an Enterprise Application (EAR) build. However, I am wondering whether it is possible to do JNDI lookup of the same bean (Hello2) that is part of an Enterprise Application (EAR) built. Below are the type of JNDI lookup entries that I have tried without success:
    public class StandalonePojoCallHelloWorld {
        public static void main(String [] args)
            try
                InitialContext jndiContext = new InitialContext();
                Hello2Remote hello2Bean =  (Hello2Remote) jndiContext.lookup("ejb.Hello2Remote");
                                                                     or
                Hello2Remote hello2Bean =  (Hello2Remote) jndiContext.lookup("LocalHelloEnterpriseApplication.Hello2.remote");
                                                                     or
                Hello2Remote hello2Bean =  (Hello2Remote) jndiContext.lookup("LocalHelloEnterpriseApplication.ejb.Hello2Remote");
                                                                     or
                Hello2Remote hello2Bean =  (Hello2Remote) jndiContext.lookup("LocalHelloEnterpriseApplication.Hello2Remote");
                                                                     or
                Hello2Remote hello2Bean =  (Hello2Remote) jndiContext.lookup("LocalHelloEnterpriseApplication.LocalHelloEnterpriseApplication-ejb.Hello2Remote");
                System.out.println("hello2Bean.getHello2(): " + hello2Bean.getHello2());
            catch (javax.naming.NamingException ne)
             ne.printStackTrace();
    They all came up with the same error message:
    javax.naming.NameNotFoundException: LocalHelloEnterpriseApplication.LocalHelloEnterpriseApplication-ejb.Hello2Remote not found
            at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)
            at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:188)
            at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:74)
            at com.sun.enterprise.naming.RemoteSerialContextProviderImpl.lookup(RemoteSerialContextProviderImpl.java:129)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)Any suggestion would be appreciated.
    Thanks,
    Jack

    Hello
    I've somme problems to get access to ejb interface from remote stand-alone client.
    Here is my EJB code :
    package stateless;
    import javax.ejb.Stateless;
    @Stateless(name = "TestSB", mappedName = "ejb/stateless/TestSB")
    public class TestEJBBean implements TestEJBRemote {
        public String getMessage() {
           return "Hello EJB World";
    }And the remote interface :
    package stateless;
    import javax.ejb.Remote;
    @Remote
    public interface TestEJBRemote {
        String getMessage();
    } In client side, i just edit main.java like this :
    package testclient;
    import java.io.FileInputStream;
    import java.util.Properties;
    import javax.naming.InitialContext;
    import stateless.TestEJBRemote;
    public class Main {
        public static void main(String[] args) throws Exception {
            Properties props = new Properties();
            props.load(new FileInputStream("jndi.properties"));
            InitialContext ctx = new InitialContext(props);
            TestEJBRemote testEJB = (TestEJBRemote) ctx.lookup("ejb/stateless/TestSB");
            System.out.println(testEJB.getMessage());
    }here is my jndi.properties file (my glassfish server IP is 192.168.0.10) :
    java.naming.factory.initial = com.sun.enterprise.naming.SerialInitContextFactory
    java.naming.factory.url.pkgs = com.sun.enterprise.naming
    java.naming.factory.state = com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl
    org.omg.CORBA.ORBInitialHost = 192.168.0.10
    org.omg.CORBA.ORBInitialPort = 3918when i run client on the same machine than the glassfish app server, it works fine.
    But i run it on the different machine than the glassfish app server (on the same LAN without firewall), it fails with this error message :
    eclan@eclan-laptop:~/NetBeansProjects/TestClient$ java -jar dist/TestClient.jar
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 3918"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 4038"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 4138"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 3918"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 4038"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 4138"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    eclan@eclan-laptop:~/NetBeansProjects/TestClient$ THANKS YOU FOR YOUR HELP
    Justin

  • Best way to access JNDI configured DataSource from outside container

    I'm not sure if this is the right forum category, but it seemed like a good place to start.
    I have a DB2 database on an OS/390 mainframe that is configured as a JNDI datasource in WebSphere (WSAD) 5.1.x. I can get connections and do database transactions within my web-application just fine.
    Part of my project needs a cron managed stand-alone application to do some database clean up work. It essentially needs to query one database, and then based on the results stick some data into the DB2 database. Easy enough right?
    The issue here is that our Security department will not under any circumstances give us the passwords and users for either database. They give these only to the server admins who configure WSAD. We also can't use a properties file. The server admins either won't touch any properties file (it is considered "code" and they don't want to be responsible for problems) or they won't have access to the contents of the ears or jars we give them. This basically leaves us with our JNDI datasource as the only datasource we could access (because the admins will have it configured with a username and password). There is also no way to infer a valid username/password from the owner of the web-app since it will live on an NT box and the NT user won't have mainframe rights.
    There is also no possibility of bending these rules no matter how stupid or cumbersome they are.
    So my question is, what is the best method in which to gain access to this JNDI DataSource or a Connection from this DataSource? Can I even get a DataSource from a JNDI lookup? Is JMS/RMI or some other acronymn that I don't know about the only way to acomplish this?
    We're using Struts MVC -> Spring -> Hibernate in the webapp, if that helps.
    Thanks in advance.

    You seem to be asking: "how can a standalone app get a valid DB2 connection by leveraging the live objects in a WSAD application"?
    While this is pretty far from my area of expertise, I don't think you can. While both JMS and RMI (and other technologies) can export some types of Java objects, they have to be objects that implement the java.io.Serializable interface. Connections cannot be serialized because these objects (normally) encapsulate a live TCP/IP connection. I don't see any fundamental reason a DataSource object couldn't be serialized other than security, but that very reason means that no reasonable implementation is going to be serializable; if it were serializable, you could almost certainly extract the value of the username and password from the serialized object. In other words, what you're really trying to do is get around security and Java's security is probably robust enough to prevent it.
    If the DB credentials only live in the WSAD world, that's where the database work has to be done. However, there's no reason the work can't be driven by a servlet or JSP that is in turn invoked from a cron-driven script or application. Personally, I do such "event notifier" scripts in Perl; Java is a bit heavy for "start up, post to URL, shutdown", but if you have more work going on you could certainly use Java. If actually doing the work in the WSAD application is not acceptable, then you're probably stuck.

  • Is it possible to set Tomcat Manager to lookup roles from DataSourceRealm?

    I know the Realm Configuration docs say that "Tomcat does not provide any built-in capabilities to maintain users and roles", but manager.xml contains the comment "Link to the user database we will get roles from", so that seems to imply that you can link to a different user database.
    I thought I could do this with JDBCRealm, but after using UserDatabaseRealm, I thought I might set up the dbase as a JNDI Datasource and authenticate and lookup roles via UserDatabaseRealm.
    After getting my database configured as a JNDI DataSource, and failing to authenticate against it via JNDIRealm, I realized that DataSourceRealm is a variation on JDBCRealm where you refer to the dbase via a JNDI DataSource. I have DataSourceRealm working, and I changed my Manager ResourceLink to point to the JNDI DataSource, but Tomcat Manager still can't lookup roles from anything other than the tomcat-users.xml demonstration file.
    The Admin Tool has screens where you can create users and roles, but this only seems to work with MemoryRealm and UserDatabaseRealm (xml files).
    Is this all just for demonstration?
    Is there no possibility of configuring TC Manager and Admintool to interface with an alternate user database (relational)?
    Shouldn't the docs clarify this by stating that you shouldn't bother trying to point the Manager ResourceLink at an alternate user database because it can't be done and the functionality is for demonstration of MemoryRealm and UserDatabaseRealm only?

    Its a 'Yes' or 'No' question.

  • Runtime Datasource from Jboss/Weblogic

    I have a application running JBoss, which we uses the datasource in the deploy folder.
    I have the report viewer working it is using the datasource from within the report file itself. At runtime, i would like to change the datasource in the report to use the datasource from Jboss, or pass a open connection. My only want to have one connection pool managed by the applicaiton server(Jboss/Weblogic).
    Thanks. Please let me know if it is unclear.

    I understand that I don't have the ability to pass in a connection. However, it is possible to use  the Jboss/Weblogic datasource in the deploy folder. If so, could you point in the right direction. So I could share the database connection pool.
    I have tried to use the setting JNDI string in the propertyBag for the connectionInfo. However, I am unable to get it to work.
    Thanks in advance for your time.

Maybe you are looking for

  • Check encashment entry  for incoming payment

    Dear Viewers, I would like to know how utillity companies are handling the customer check encashment in FI-CA. Let's say customer is giving the check. The entry is posted as follows: Dr. Incoming Check clearing account Cr. Business partner account. A

  • Difference between Webservice and RFC

    Dear Experts, We have an application to implement where the application will be called from other NON SAP technology. We got two solutions one is developing RFC's and calling it from other NON SAP Technology OR developing Webservice. Could any one pl

  • Response not committed on Tomcat 4.1

    Hello, I have the following application architecture: A button on a JSP is clicked, which sends the request to the Controller servlet. This servlet gets a RequestDispatcher and forwards to another specified JSP. The problem is where I check to see th

  • HT4759 how do i retrieve my contact information that was in my iphone 4s n transfered to 5s

    how do i retrieve my contact infornation after sale of new phone

  • Ipod Photo and Ipod dock

    I have a question:Does the Ipod Dock only work with Mac Computers? I want to get one but not sure if it will work with windows XP SP2. Can somebody help me out.