Fail to lookup jndi in EJB

Hi,
My application failed to lookup a JMS Object using JNDI lookup in EJB.
The actual application flow is that a Servlet receive a request which
then calls to an EJB
where it loop up the JMS object to establish the message queue
connection.
It works with a simple Servlet which loop up the JMS Object without call
to EJB.
Does anyone known the possible reason causes the application failed to
lookup the JMS Object?
Thanks
Avans
the log is following
The Status is :
MQ java:comp/env/jms/theFactory
MQjava:comp/env/jms/theFactoryjavax.naming.NameNotFoundException: Can't locate jms/theFactory
at com.netscape.server.jndi.CompContext.resolveEnv(Unknown
Source)
at com.netscape.server.jndi.CompContext.lookup(Unknown Source)
at com.netscape.server.jndi.java.javaURLContext.lookup(Unknown
Source)
at javax.naming.InitialContext.lookup(InitialContext.java:357)
at
com.hkex.common.mq.mqwrapper.MQReceiver.<init>(MQReceiver.java:109)
at
com.hkex.common.mq.mqwrapper.MQReceiverGroup.<init>(MQReceiverGroup.j
ava:70)
at
com.hkex.common.mq.mqwrapper.MQContainer.createReceivers(MQContainer.
java:545)
at
com.hkex.common.mq.mqwrapper.MQContainer.createMQObject(MQContainer.j
ava:387)
at
com.hkex.common.mq.mqwrapper.MQContainer.initMQConfig(MQContainer.jav
a:360)
at
com.hkex.common.mq.mqwrapper.MQContainer.<init>(MQContainer.java:93)
at
com.hkex.common.mq.mqwrapper.MQContainer.<clinit>(MQContainer.java:63
at
com.hkex.common.mq.interfacewrapper.FuncParameter.setExpiryTime(FuncP
arameter.java:270)
at
com.hkex.common.mq.interfacewrapper.MQHostAccess.invoke(MQHostAccess.
java:336)
at
com.hkex.common.mq.interfacewrapper.MQHostAccess.syncInvoke(MQHostAcc
ess.java:236)
at
com.hkex.arch.msg.ToHostMessage.sendToMQ(ToHostMessage.java:150)
at
com.hkex.arch.msg.DefaultHostInterface.sendToMQ(DefaultHostInterface.
java:28)
at
com.hkex.arch.msg.MFMModuleBase.sendToMQ(MFMModuleBase.java:26)
at
com.hkex.arch.msg.MFMModuleBase.sendToMQ(MFMModuleBase.java:21)
at
com.hkex.cl.model.dao.mq.MFM_PXCLTL02.processEnquiryDisplayRequest(MF
M_PXCLTL02.java:1676)
at
com.hkex.cl.model.dao.mq.SettlementInstructionDAO.SITLenquiryDisplay(
SettlementInstructionDAO.java:279)
at
com.hkex.cl.model.SIServicesEJB.SITLenquiryDisplay(SIServicesEJB.java
:680)
at java.lang.reflect.Method.invoke(Native Method)
at
com.hkex.cl.model.ejb_skel_com_hkex_cl_model_SIServicesEJB.SITLenquir
yDisplay(ejb_skel_com_hkex_cl_model_SIServicesEJB.java:1176)
at
com.hkex.cl.model.ejb_kcp_skel_SIServices.SITLenquiryDisplay__com_hke
x_cl_SIDetail__com_hkex_arch_base_CCASSUs__43836001(ejb_kcp_skel_SIServices.java
:1094)
at com.kivasoft.ebfp.FPRequest.invokenative(Native Method)
at com.kivasoft.ebfp.FPRequest.invoke(Unknown Source)
at
com.hkex.cl.model.ejb_kcp_stub_SIServices.SITLenquiryDisplay(ejb_kcp_
stub_SIServices.java:1359)
at
com.hkex.cl.model.ejb_stub_SIServices.SITLenquiryDisplay(ejb_stub_SIS
ervices.java:123)
at
com.hkex.cl.controller.SITLEnquiry.processQuery(SITLEnquiry.java:161)
at
com.hkex.arch.controller.base.HttpControllerAdvanced.list(HttpControl
lerAdvanced.java:113)
at java.lang.reflect.Method.invoke(Native Method)
at
com.hkex.arch.controller.base.HttpControllerBasic.invokeActionHandler
(HttpControllerBasic.java:1430)
at
com.hkex.arch.controller.base.HttpControllerBasic.handleBusinessReque
st(HttpControllerBasic.java:1309)
at
com.hkex.arch.controller.base.HttpControllerBasicExtended.handleBusin
essRequest(HttpControllerBasicExtended.java:236)
at
com.hkex.arch.controller.base.HttpControllerBasic.doMagic(HttpControl
lerBasic.java:1168)
at
com.hkex.arch.controller.base.HttpControllerBasic.doPost(HttpControll
erBasic.java:1038)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
at
com.hkex.arch.controller.base.HttpControllerBasic.service(HttpControl
lerBasic.java:1012)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown
Source)
at
com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unkno
wn Source)
at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
MQ Error Msg : Can't locate jms/theFactory
MQ Localized Msg: Can't locate jms/theFactory
Resolved_Name():null
UnResolved_Name():null
Root Cause(): null
Get Explaination():Can't locate jms/theFactory

Similar Messages

Failed to lookup JNDI provider

Hi All,
I'm facing a problem sending Messages to a Queue within an OpenJMS server.
When I send the messages to a OpenJMS server runnin on my LocalHost, It is SUCCESSFUL.
then, I simply change the IP adress of the server (another machine on my local network) ... and here, I obtain the follwing exception :
Failed to lookup JNDI provider for URL: tcp://192.168.4.71:3035/
here is the code I'm using ( and where the exception is raised ):
Hashtable properties = new Hashtable();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.exolab.jms.jndi.InitialContextFactory");
properties.put(Context.PROVIDER_URL, "tcp://192.168.4.71:3035/" );
context = new InitialContext(properties);Any help and suggestion please ?!
It's urgent

for more details :
this is the nested Exception I'm getting :
nested exception is:
java.io.InvalidClassException: org.exolab.jms.net.proxy.Proxy;
local class incompatible: stream classdesc serialVersionUID = -3335702252244367740, local class serialVersionUID = 1
?

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.

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û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û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û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û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û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û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

Failed in WD JNDI lookup in QA Portal

Hello Experts,
I am facing the issue in custom WD application in QA portal system, in dev portal the application is working fine and after transporting the objects into QA portal ,while on preview the iview its giving me error : "Failed in WD JNDI lookup ".
I have tested the WD application from Web dynpro console and its working fine , even i have created iview in QA portal and its working fine but while transporting the iview from DEV to QA Portal is not working . Can any one help me on that .
Your help will highly appreciated ..
Details error :
com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name home~eth_dis
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:357)
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
    at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
    at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:442)
    ... 40 more

Hi Shanti,
Thanks for the quick response.
My portal version is EP 7 with SP21 .As I mention in my thread that I have tested custom application on QA Portal and its working fine. But the problem is only appearing with the transported iview into QA portal.
Regards
Rashi

PortalRuntimeException: Failed in WD JNDI lookup.

Hi Experts
We are getting the following exception when we try to run our WD application in an iView :
com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name xxxxx.com
If we deploy and run our application as such on the server,it works fine.This issue comes only after we have integrated it in the iview.
Please provide some pointers.

Hello Kunal
when you integrate it in an iView, pcd address/location should be there atttributes..i think it's missing
Bhudev

Javax.naming.NamingException: Failed in WD JNDI lookup

Hi,
I have deployed wdj applications,some times its working fine ,but some other times its through the following errors.
javax.naming.NamingException: Failed in WD JNDI lookup
Any one please suggest me
Thanks,
Venu

Hi Friend,
I am not sure what Other Reason can be for this problem mean while check these links. Hope it will help.
/message/6928201#6928201 [original link is broken]
/message/6315352#6315352 [original link is broken]
Regards
Jeetendra

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.

Do i have to use JNDI with EJBS?

Hi
I want to use JNDI to lookup a system which i will send messages to using JMS. I would like to have some java classes on Tomcat to do the job. But...whenever i hear about JNDI it is always in relation to EJBs. Can i only use JNDI with EJBS?
If i can use JNDI is there anything important i need to know about.
Thanks in advance!
San H.

You can definitely use JNDI outside of EJB's - in particular, it's a great interface for dealing with LDAP servers, even securely, and can also be used for DNS interfacing, COS, RMI registries, etc.
While JNDI was chosen as the method by which J2EE components can locate other components in a distributed environment, it's by no means limited to that task :) It's a wonderful API, and in terms of things you need to know, most everything is covered fairly well at the JNDI tutorial in the various trails that are mapped out there.
http://java.sun.com/products/jndi/tutorial/
Good luck!
James
James Manning | Principal Engineer
Porivo Technologies, Inc.
919.806.0566 | [email protected]
http://www.porivo.com/
Measuring end-to-end Web performance.
Register for a FREE Performance appraisal:
http://www.porivo.com/peerReview/eval.html

Problems while performing lookup for Local EJBs

Can anybody tell me how can i perform local ejb lookup in Sun app Server 8.0/8.1 ?
I have following entries in ejb-jar.xml.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar >
<enterprise-beans>
<session >
<ejb-name>TeamLeaderBean</ejb-name>
<local-home>spring.ejb.example.TeamLeaderLocalHome
</local- home>
<local>spring.ejb.example.TeamLeaderLocal</local>
<ejb-class>spring.ejb.example.TeamLeaderBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor></assembly-descriptor>
</ejb-jar>
In sun-ejb-jar.xml I have
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>TeamLeaderBean</ejb-name>
<jndi-name>TeamLeaderBeanLocal</jndi-name>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
In the client EJBs code I have used following ways of performing lookup...
ctx.lookup("java:comp/env//TeamLeaderBeanLocal");
ctx.lookup("java:comp/env/ejb/local/TeamLeaderBeanLocal");
ctx.lookup("ejb/TeamLeaderBeanLocal");
Unfortunately none of these performs a successful lookup...???
Can anybody solve my problem?

In order to look up a local EJB from an EJB client you have to add an <ejb-local-ref> element for client EJB. So:
<session>
<ejb-name>MyClientEJB</ejb-name>
<ejb-local-ref>
<ejb-ref-name>ejb/TeamLeaderBeanLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<ejb-link>TeamLeaderBeanLocal</ejb-link>
</ejb-local-ref>
</session>
fil
Can anybody tell me how can i perform local ejb
lookup in Sun app Server 8.0/8.1 ?
I have following entries in ejb-jar.xml.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems,
Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar >
<enterprise-beans>
<session >
<ejb-name>TeamLeaderBean</ejb-name>
<local-home>spring.ejb.example.TeamLeaderLocalHome
</local- home>
<local>spring.ejb.example.TeamLeaderLocal</local>
<ejb-class>spring.ejb.example.TeamLeaderBean</ejb-clas
s>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor></assembly-descriptor>
</ejb-jar>
In sun-ejb-jar.xml I have
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>TeamLeaderBean</ejb-name>
<jndi-name>TeamLeaderBeanLocal</jndi-name>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
In the client EJBs code I have used following ways of
performing lookup...
ctx.lookup("java:comp/env//TeamLeaderBeanLocal");
ctx.lookup("java:comp/env/ejb/local/TeamLeaderBeanLoca
l");
ctx.lookup("ejb/TeamLeaderBeanLocal");
Unfortunately none of these performs a successful
lookup...???
Can anybody solve my problem?

Lookup jndi in subcontext

Hi,
I change the jvm from hotspot to jrockit in the script of weblogic as it got crashed with HotSpot.
With jrockit, it complains - "lookup jndi.<project name> did not find the subcontext, jndi resolved.
Can anyone throw light on this?
Thanks.

It says for Weblogic 9.0 or higher. But need for 8.1
Also, it(http://edocs.bea.com/wls/docs100/issues/known_resolved.html) <CR299081> says WebLogic Server Administration Console, on the Domain: Configuration: General tab, click Advanced and check Enable Remote Deployer EJB. I dont have EJBs over here.
Thanks.

Failed to lookup connection factory weblogic.jms.XAConnectionFactory

when i deploy any service with jms protocol (write to queue) using sbconsole i face this error
"Failed to lookup connection factory weblogic.jms.XAConnectionFactory"
any suggestion?
Thanks

weblogic.jms.XAConnectionFactory is the default XA connection factory class. You wont see this in any JMS modules in Weblogic server. It should be available by default.
Can you once check the JNDI tree of your servers if this JNDI name exists. (in Weblogic Administration console go to Servers, click on any server and there will be a link for JNDI tree on the server's page)
Also, try creating a new connection factory in Weblogic console and using that in your service. Although it is highly unlikely that a new connection factory will work since all custom XA connection factories are dependent on the default connection factory class you mentioned.

J2EE JNDI-00009 EJB Reference "ejb/SessionEJBCalled" could not be resolved

When load (run) the following EJB (JDev 10.1.3.1.0 embedded server) loads with no problem:
package project2;
import javax.ejb.Stateless;
@Stateless
public class SessionEJBCalledBean implements SessionEJBCalledLocal {
public SessionEJBCalledBean() {    }
public void display() { System.out.println("In called - Project2");   }
When load the following, only difference is name attribute for the @Stateless annotation:
package project2;
import javax.ejb.Stateless;
@Stateless(name="SessionEJBCalled")
public class SessionEJBCalledBean implements SessionEJBCalledLocal {
public SessionEJBCalledBean() {    }
public void display() { System.out.println("In called - Project2");    }
Get the following error message - Why?
2006-08-24 15:48:54.640 WARNING J2EE JNDI-00009 EJB Reference "ejb/SessionEJBCalled" could not be resolved. Allowing J2EEContext creation to continue anyway
Finally - If I specify the name as per the following all is well:
package project2;
import javax.ejb.Stateless;
@Stateless(name="SessionEJBCalledBean")
public class SessionEJBCalledBean implements SessionEJBCalledLocal {
public SessionEJBCalledBean() {    }
public void display() { System.out.println("In called - Project2");   }
Would be appreciated if someone could tell me what is going on?
Thanks - Ken

When load (run) the following EJB (JDev 10.1.3.1.0 embedded server) loads with no problem:
package project2;
import javax.ejb.Stateless;
@Stateless
public class SessionEJBCalledBean implements SessionEJBCalledLocal {
public SessionEJBCalledBean() {    }
public void display() { System.out.println("In called - Project2");   }
When load the following, only difference is name attribute for the @Stateless annotation:
package project2;
import javax.ejb.Stateless;
@Stateless(name="SessionEJBCalled")
public class SessionEJBCalledBean implements SessionEJBCalledLocal {
public SessionEJBCalledBean() {    }
public void display() { System.out.println("In called - Project2");    }
Get the following error message - Why?
2006-08-24 15:48:54.640 WARNING J2EE JNDI-00009 EJB Reference "ejb/SessionEJBCalled" could not be resolved. Allowing J2EEContext creation to continue anyway
Finally - If I specify the name as per the following all is well:
package project2;
import javax.ejb.Stateless;
@Stateless(name="SessionEJBCalledBean")
public class SessionEJBCalledBean implements SessionEJBCalledLocal {
public SessionEJBCalledBean() {    }
public void display() { System.out.println("In called - Project2");   }
Would be appreciated if someone could tell me what is going on?
Thanks - Ken

Failed to lookup External Link

Hi,
I just upgraded to EP7 SP12 and deployed the ESS BP. When I try to preview Content Administration -> Portal Content -> Content Provided by SAP -> Employee Self Service -> iViews -> Benefits and Payment -> Benefits Participation, we see the below error.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed to lookup External Link for: portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.iviews/com.sap.pct.erp.ess.benefits_payment/com.sap.pct.erp.ess.benparticipation
Any one have any ideas?
Your help is greatly appreciated.
Regards,
Rick

I did some more research. It seems like we are having the same problem on another portal server. So I don't think I caused the problem. This is coming from the standard business planning pages like planning wizard, planning modeler, etc.

Failed to lookup port type on Mediator Callback

Hi everyone,
I'm new to SOA Suite and to learn it i've started following the book "Getting Started with Oracle Soa Suite: A Hands On Tutorial". In chapter 7 about BPEL i'm getting the following error message when i try to set a callback on the mediator to a BPEL process:
Nov 6, 2012 9:09:46 PM oracle.tip.tools.ide.fabric.model.WSDLInterface loadOperations
SEVERE: Failed to lookup PortType for {http://xmlns.oracle.com/pcbpel/adapter/file/POProcessing/POProcessing/WriteApprovalResults}Write_ptt in POProcessing/WriteApprovalResults
Nov 6, 2012 9:09:46 PM oracle.tip.tools.ide.fabric.model.WSDLInterface loadOperations
SEVERE: Failed to lookup PortType for {http://oracle.com/sca/soapservice/CreditCardValidation/validationForCC/getStatusByCC}execute_ptt in POProcessing/getCreditCardStatus
I've already acessed the WSDL on browser, tested them on EM and everything seems ok with these two services.
Please, could you help me to solve this error? If you need some code or configuration i can post here.
Best regards,
Hugo

SEVERE: Failed to lookup PortType for...
1. Maybe its just really a different port type and you have it mistyped or something in the calling webservices inside your code (where it makes a call to the WSDL endpoint)
2. It could be that the WSDL basically needs to be local. That is, although its an off the shelf application and all.. you need to download the WSDL on your local computer in a C:\drive or
a location and then use that WSDL file to generate web services from the tool you are using (like eclipse/jdev so on so forth)
what is the port type that you have and the port number ?
-Rtiee

Fail to lookup jndi in EJB

Similar Messages

Maybe you are looking for