Can we bind hibernate sessionFactory to weblogic JNDI from remote client?

Hi,
Is it possible to bind a hibernate sessionfactory from a remote jee client application to weblogic 10.3 server ?
Thanks
ow005480

Hi Michael,
Please make sure that your Mail Session "mail/MYAPP_MAIL" is targeted to the same Server where you are trying to deploy your Spring based application. It means in the JNDi tree of the Server do you see the JNDI name "mail/MYAPP_MAIL" where you are trying to deploy your application?
You can check the JNDI tree of your server using AdminConsole after login please nevigate to the following :
AdminConsole---->Servers ----[SERVER_NAME] click ----> (View jndi tree) link
Thanks
Jay SenSharma
http://middlewaremagic.com/weblogic/  (Middleware Magic Is Here)

Similar Messages

  • Getting error while hitting weblogic server from EBS client instance

    Hi,
    We are trying to hit weblogic server from EBS client instance.
    Steps Done from our side :-
    1. Created a self signed key store and certificate (.cer file) with server host name and used it for SSL enabling on weblogic server.
    2. Created a self signed key store and certificate (.cer file) with client host name and used it for SSL enabling on oracle EBS client.
    3. Imported client certificate .cer file in Server Side Trust Store.
    4. Used Server keystore for client side verification.
    We are getting these logs from Client Side (Oracle EBS AS) :-
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:34 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:34 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:34 AM AST> <Warning> <Security> <BEA-090542> <Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    <Nov 9, 2012 10:40:34 AM AST> <Warning> <Security> <BEA-090542> <Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    <Nov 9, 2012 10:40:34 AM AST> <Warning> <Security> <BEA-090542> <Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    javax.net.ssl.SSLKeyException: [Security:090542]Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
    at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
    at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
    at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
    at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:158)
    at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:363)
    at oracle.apps.nmc.filetransmission.DigitalSigner.sendSignedFileToBank(DigitalSigner.java:532)
    at oracle.apps.nmc.filetransmission.DigitalSigner.signXmlFile(DigitalSigner.java:330)
    at oracle.apps.nmc.filetransmission.DigitalSigner.invokerInit(DigitalSigner.java:437)
    at oracle.apps.nmc.filetransmission.DigitalSigner.runProgram(DigitalSigner.java:390)
    at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
    We are getting these logs from Server Side (Weblogic server) :-
    <Nov 9, 2012 10:34:51 AM AST> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from whjed-apstest3.nmc.com - 192.168.100.246. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    Kindly suggest on this.
    Regards
    Deepak Gupta

    Hi;
    Please make a search BEA-090482 Check the peer to determine why it rejected at metalink. There are 8 docs avaliable, please review them
    Regard
    Helios

  • Binding custom objects in weblogic JNDI

    I noticed that if I bind a custom object, the object is not available after the weblogic
    restart. Is there anyway to bind an object permanently in the weblogic JNDI..

    In article <[email protected]>, [email protected] says...
    Murali <[email protected]> wrote:
    I noticed that if I bind a custom object, the object is not available after the weblogic
    restart. Is there anyway to bind an object permanently in the weblogic JNDI..No.
    Perhaps what your trying to accomplish could be handled via a startup
    class that did the bind for you.
    Bob

  • Deploying WebLogic JNDI classes to clients

    I would like to use WebLogic's JNDI classes from a client application. None of the required classes exist in weblogicaux.jar and the ones in applet.jar seem to be missing some classes, WLInitialContextFactoryDelegate for instance. Is there a standard jar that I'm overlooking? I don't really want to jar up the whole of the weblogic/classes directory to do this. Alternatively, is there a list anywhere of the minimum set of classes required on the client to enable it to use WebLogic JNDI ?

    Unfortunately we don't distinguish between client classes and server
    classes. You could probably import all of the weblogic.jndi.* package and
    see if that helps. I bet that should be sufficient.
    -- Prasad
    "Des Marshall" <[email protected]> wrote in message
    news:3a34e556$[email protected]..
    I would like to use WebLogic's JNDI classes from a client application.None of the required classes exist in weblogicaux.jar and the ones in
    applet.jar seem to be missing some classes, WLInitialContextFactoryDelegate
    for instance. Is there a standard jar that I'm overlooking? I don't really
    want to jar up the whole of the weblogic/classes directory to do this.
    Alternatively, is there a list anywhere of the minimum set of classes
    required on the client to enable it to use WebLogic JNDI ?

  • Error while trying to connect to weblogic from remote client

    Hi
    I was trying to connect to JMX MBeanserver from a aremote client using some sample code that was posted. Ive tried even the samples that I found in the Admin Guide itself. Im not certain if any server configuration is needed. Ive tried the below with all three protocols t3, iiop, http with the same result. I had also enabled IIOP on the server through the console.
    I get an error when trying to conenct using the JMXConnection Factory i.e. at the last line of the following code:
    String protocol = "t3"; // can be t3, http, iiop
    String hostname = "santapoco.eng";
    int port = 7001;
    String uri = "/jndi/"+"weblogic.management.mbeanservers.runtime";
    JMXServiceURL serviceURL = new JMXServiceURL(protocol, hostname, port, uri);
    Hashtable h = new Hashtable();
    h.put(Context.SECURITY_PRINCIPAL, "weblogic");
    h.put(Context.SECURITY_CREDENTIALS, "weblogic");
         h.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES, "weblogic.management.remote");
    JMXConnector connector =JMXConnectorFactory.connect(serviceURL, h);
    The error is:
    "Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.io.EOFException]
         at weblogic.jrmp.Context.lookup(Context.java:189)"

    Pratima Gogineni <> writes:
    This is what worked for me:
    URI uri = new URI(args[0]);
    JMXServiceURL serviceURL =
    new JMXServiceURL(uri.getScheme(), uri.getHost(), uri.getPort(),
    "/jndi/weblogic/management/mbeanservers/runtime");
    Hashtable h = new Hashtable();
    h.put(Context.SECURITY_PRINCIPAL, "system");
    h.put(Context.SECURITY_CREDENTIALS, "ejb2come");
    // String[] jmxCredentials = new String[]{ "system", "ejb2come" };
    // h.put(JMXConnector.CREDENTIALS, jmxCredentials);
    h.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES,
    "weblogic.management.remote");
    h.put(Context.PROVIDER_URL, args[0]);
    // h.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
    h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    // InitialContext ic = new InitialContext(h);
    // ic.lookup("weblogic/management");
    JMXConnector connector = JMXConnectorFactory.connect(serviceURL, h);
    MBeanServerConnection connection = connector.getMBeanServerConnection();
    NOTE this was with weblogic 91--

  • Why only j2sdkee1.3 support JNDI lookup "java:comp/env" from remote client?

    Hi:
    I have been puzzled by this function of j2sdkee1.3.1 support JNDI lookup "java:comp/env" from client. I always think that "java:comp/env" namespace can only be access by the application server self for it is a private namespace. The weblogic and websphere doest support this.
    Why?
    Regards!
    John Lee

    Hi:I'm unable to get JNDI reference object from remote application client with "java:comp/env/ejb/<lookupName>".
    The exception says:
    Application threw an exception:javax.naming.CommunicationException: Cannot connect to ORB [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201 completed: No]
    The J2EE server and client are run on different machines, and needs to be like this. There isn't any problem with JSP/Servlet (cause they run/execute on the server itself). How will the client find out the JNDI refernce my mere specification of "java:comp/env/..."?
    Am I making a mistake anywhere?
    BEA Weblogic & IBM Websphere allows explicitly specifying the server name, while doing JNDI lookup. Is there anything similary for J2EE?
    I couldn't find reference for this anywhere in the J2EE tutorial or EJB books.
    - Devashish

  • Why j2sdkee1.3.1 support JNDI lookup "java:comp/env" from  remote client?

    Hi:
    I have been puzzled by this function of j2sdkee1.3.1 support JNDI lookup "java:comp/env"
    from client. I always think that "java:comp/env" namespace can only be access
    by the application server self for it is a private namespace. The weblogic and
    websphere doest support this.
    Why?
    Regards!
    John

    Hi:I'm unable to get JNDI reference object from remote application client with "java:comp/env/ejb/<lookupName>".
    The exception says:
    Application threw an exception:javax.naming.CommunicationException: Cannot connect to ORB [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201 completed: No]
    The J2EE server and client are run on different machines, and needs to be like this. There isn't any problem with JSP/Servlet (cause they run/execute on the server itself). How will the client find out the JNDI refernce my mere specification of "java:comp/env/..."?
    Am I making a mistake anywhere?
    BEA Weblogic & IBM Websphere allows explicitly specifying the server name, while doing JNDI lookup. Is there anything similary for J2EE?
    I couldn't find reference for this anywhere in the J2EE tutorial or EJB books.
    - Devashish

  • HowTo:Publish Msg to JMS queue deployed in a Weblogic Cluster from a client

    Hello All-
    I am new to Weblogic and need help from this forum. Forgive me for my ignorance. I am learning.
    Below is a brief about the context and the issues that we are facing:
    Background
    =======
    1. We have Oracle Service Bus (OSB) installed on top of Oracle Weblogic Server (ver 10.3). In OSB we have developed a proxy service that listens to a JMS queue for an incoming message
    2. The Weblogic environment is a cluster having 2 managed servers listening to different ports and it is front-ended by a Apache Load Balancer.
    3. Our requirement is to post an XML message from a Java client to the JMS queue which will then initiate the proxy service deployed. We are using t3 protocol to post the message from the client to the JMS queue
    Issue
    ====
    1. To post an XML message from the client, how do we give the address of the JMS queue in the clustered environment to enable failover/loadbalancing if one managed server goes down. I understand from your earlier posts in this forum that directly hitting the JMS queue on a particular managed server will not enable failover/loadbalancing in case one of them goes down
    2. Do we need to modify any config file in the Apache Proxy Plugin?
    3. Do we need to provide the address of the Apache proxy in the client to send the message?
    Kindly clarify and let me know me know if you need any additional information.
    Greatly appreciate your help!!!
    Regards,
    Dibya

    Hi Dibya,
    Please refer to : http://weblogic-wonders.com/weblogic/2010/05/13/apache-proxy-as-static-content-repository/#comment-1379
    Thanks
    Jay SenSharma

  • How can i restart my iPhone 4 accidentally erased from remotely of fine me

    Hiiii
    I one to restar my son's iphone 4,
    last night i was using fine me in my iphone 4s and i erase my son's iphone 4 dives in my iphone 4s,
    i accidentally erase from fine me,
    pls. help me how to restar?
    it's not starting, there are in serch mode now.
    pls. help.

    i just conect in itune but itune can't found it.
    can't turn off also,
    i turn off using "turn on/off" switch and the "round main" switch.
    it's start for 10 second and then again turn off and now is in searching mode.
    pls. help.

  • Can't login to ML server network user from a client

    Hi,
    The computer name on my customer's ML server was changed post OD installation. Now I can't login with network user credentials from a MacBook.
    I also see the old server/hostname displayed in workgroup manager under "location" (see attached).
    I've tried destroying OD by deleting it in Server app then re-adding it again but it still shows the old name in WGM as shown in the screenshot above.
    I suspect this is related to authentication problems. Should I be running a utility like changeDirData.pl to update the old values? If so, what is the syntaxt?
    Old name was: server1.stmarys.lan
    New name is: server1.local
    I ran the following: sudo /Applications/Server.app/Contents/ServerRoot/usr/libexec/changeDirData.pl -i -s 192.168.2.2 -u diradmin -o server1.stmarys.lan -n server1.local
    But got an error: cant contact ldap server to get config info

    After contacting Apple server support, I was told there were two issues:
    1- ".local" cannot be used in a hostname due to conflict with Bonjour
    2- Hostnames must have three parts like "server.company.lan" & "server.lan" cannot be used
    I wish Apple would inform users with a pop-up about these rules before they waste a lot of time having to re-do everything from scrath. I was lucky enough to have an export of all users.
    If these rules are followed from the begining, DNS would auto-configure itself with the appropriate forward & reverse records.

  • Can a servlet do something without a request from a client?

    Hi,
    is a servlet only invoked when a client calls doGet() or doPost() or is there a way to let the servlet do something while it is idle.
    Maybe with a thread? Can a servlet start a thread that will work forever? And do servers usually close servlets while it has a thread running?
    thanx

    Servlets are invoked as a result of client request. But you can certainly make your servlet implement the runnable interface to do background processing.
    Imagine a servlet that is processing an image to send to the client but suppose the image processing takes 4-5 minutes to complete. You wouldn't wanna make your client to wait to see the result for 5 minutes. So you may send the partially processed image while still working on the processing in the background. All the subsequent requests from client will see a bit improved image. You can do something like this:
    public class MyServlet extends HttpServlet implements Runnable {
    public void init() throws ServletException {
    //Initialize your thread here
    public void run() {
    // do your background processing here
    public void doGet(HttpServletRequest req, HttpServletResponse res)
    throws ServletException, IOException {
    // Handle the request here
    public void destroy() {
    // Be a good programmer and stop your thread here
    Hope it helps.

  • JNDI location error from remote client

    Hi,
    I got the following error when I'm trying to access an EJB from a remote client.Could anybody help me to identify the error?
    John
    Caught an unexpected exception!
    javax.naming.NoInitialContextException: Need to specify class name in environmen
    t or system property, or as an applet parameter, or in an application resource f
    ile: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.lookup(Unknown Source)
    at xyz.pqr.client.TestClient.main(TestClient.java:43)

    Hi 392415,
    It looks like you haven't specified the INITIAL_CONTEXT_FACTORY property -- the name of the class that creates the "java.naming.InitialContext" class.
    Perhaps you would care to show the entire error message and stack trace, as well as the part of your code that is causing the error, and perhaps a few details about your environment.
    Then I might be able to help you some more.
    Good Luck,
    Avi.

  • Accessing Weblogi JNDI

    i'm trying to access weblogic JNDI from my code and it gaves me this Error:
    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         at weblogic.jndi.Environment.getContext(Environment.java:285)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
         at com.etech.common.ldap.ad.UserLdapHandler.initLdapContext(UserLdapHandler.java:141)
         ... 42 more
    Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination
         at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
         at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:344)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
         ... 50 more
    the enviroment i use is like this :
    environment.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    environment.put(Context.PROVIDER_URL, "t3://localhost:7001");
    environment.put(Context.REFERRAL, "follow");
    Any help will be great.

    i'm trying to access weblogic JNDI from my code and it gaves me this Error:
    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         at weblogic.jndi.Environment.getContext(Environment.java:285)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
         at com.etech.common.ldap.ad.UserLdapHandler.initLdapContext(UserLdapHandler.java:141)
         ... 42 more
    Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination
         at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
         at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:344)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
         ... 50 more
    the enviroment i use is like this :
    environment.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    environment.put(Context.PROVIDER_URL, "t3://localhost:7001");
    environment.put(Context.REFERRAL, "follow");
    Any help will be great.

  • WebLogic Builder remote-client-timeout

    Just wondering if anyone has encountered this before.
    After using WebLogic Builder to make and save changes to an EAR file the weblogic-ejb-jar.xml file is updated to include the remote-client-timeout tag. This tag causes warning messages in the weblogic console.
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>HelloWorldEJB</ejb-name>
    <transaction-descriptor>
    </transaction-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>test.HelloWorldHome</jndi-name>
    <remote-client-timeout>0</remote-client-timeout>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    Warning Messages
    <Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout specifies a rmi level timeout in seconds for remote clients that call the home and remote methods of the ejb. The method call(s) timeout on the client side after the specified number of seconds. The server will continue to process the request(s) and may change the state. The rmi level timeout shall be set by the container only for non-transactional methods (i.e, method with tx-attributes of Never or Not-Supported). Please ensure that the parameter is used only for methods that are idempotent in nature.>

    I think the tool sets the default value for this flag. The default value
    should not have any effect. However, I would expect the tool (weblogic
    builder) not to insert this element in the descriptor.
    More details on this setting can be found here -
    http://e-docs.bea.com/wls/docs81/rmi/rmi_api.html#rmi_timeout
    --Sathish
    <Colin Yeung> wrote in message news:[email protected]..
    Just wondering if anyone has encountered this before.
    After using WebLogic Builder to make and save changes to an EAR file the
    weblogic-ejb-jar.xml file is updated to include the remote-client-timeout
    tag. This tag causes warning messages in the weblogic console.
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>HelloWorldEJB</ejb-name>
    <transaction-descriptor>
    </transaction-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>test.HelloWorldHome</jndi-name>
    <remote-client-timeout>0</remote-client-timeout>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    Warning Messages
    <Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB
    HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout
    specifies a rmi level timeout in seconds for remote clients that call the
    home and remote methods of the ejb. The method call(s) timeout on the
    client side after the specified number of seconds. The server will
    continue to process the request(s) and may change the state. The rmi level
    timeout shall be set by the container only for non-transactional methods
    (i.e,
    method with tx-attributes of Never or Not-Supported). Please ensure that
    the parameter is used only for methods that are idempotent in nature.>

  • NameNotFoundException when looking up datasource jndi from standalone clien

    Hi,
    I'm trying to lookup datasource jndi from standalone client, but always get exceptions.
    I configured an oralce datasource with jndi name "oracleDataSource". When looking it up in servlet, I can get connection.
    In order to test it from standalone client, I created following code:
    public class DataSourceTest
    * Attempt to authenticate the user.
    public static void main(String[] args)
    String datasource = null;
    if (args.length == 1 ) {
    datasource = args[0];
    System.out.println("datasource = "+datasource);
    if(datasource == null)
    datasource = "oracleDataSource";
    try{
    Connection conn = null;
    Properties env = new Properties();
    env.put("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
    env.put("java.naming.provider.url", "iiop://localhost:3700");
    Context initial = new InitialContext(env);
    if(datasource != null){
    DataSource ds = (DataSource)initial.lookup(datasource);
    conn = ds.getConnection();
    if(conn != null){
    System.out.println("datasource is gotten.");
    conn.close();
    else
    System.out.println("datasource is error.");
    System.exit(0);
    } catch (Exception ex) {
    System.err.println("Caught an unexpected exception!");
    ex.printStackTrace();
    When running, I get following exception:
    [java] datasource = oracleDataSource
    [java] Caught an unexpected exception!
    [java] javax.naming.NameNotFoundException. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound
    [java] at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:34)
    [java] at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:402)
    [java] at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:368)
    [java] at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:417)
    [java] at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:395)
    [java] at javax.naming.InitialContext.lookup(InitialContext.java:350)
    [java] at com.tbcn.ceap.test.cilent.DataSourceTest.main(DataSourceTest.java:42)
    I also tried many other methods but always got exceptions. What's wrong with it? How can I lookup the datasource jndi from standalone client?
    Thanks in advance!

    Thank Tuan!
    I tried. When running, the server will read security.properties and ejb.properties. But I didn't use ejb and I didn't know how to configure ejb.properties, so I let ejb.properties empty. The security.properties is as following:
    client.sendpassword=true
    server.trustedhosts=*
    interop.ssl.required=false
    interop.authRequired.enabled=false
    interop.nameservice.ssl.required=false
    The result is:
    [java] javax.naming.CommunicationException: Can't find SerialContextProvider
    [java] at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:63)
    [java] at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:120)
    [java] at javax.naming.InitialContext.lookup(InitialContext.java:347)
    [java] at com.tbcn.ceap.test.cilent.DataSourceTest.main(DataSourceTest.java:42)
    Also, I tried it with ACC. In sun sample ConverterClient.java under rmi-iiop/simple, I added following code under with ACC and without ACC. With ACC, I can get connection. But without ACC, I can't get it.
    try{
              DataSource ds = (DataSource)initial.lookup("oracleDataSource");
              Connection conn = ds.getConnection();
              if(conn != null){
              System.out.println("datasource oracleDataSource gotten.");
              conn.close();
              else
              System.out.println("oracleDataSource is error.");
    Does it means that we must lookup datasource jndi with ACC?

Maybe you are looking for