JDK1.2 client to EJB in Oracle8.1.6

I had my EJB client (JDK1.1.8) with my EJBs (in Oracle8.1.5) all worked before.
After I deployed the same EJBs (with SQLJs) into Oracle8.1.6, my EJB client (JDK1.2.2)
was able to connect and using the EJB sevices.
However, I got some strange behavior which never occurd with JDK1.1.8 and Oracle8.1.5.
I will sometimes get exception for calling the remote method as,
Exception in thread "main" org.omg.CORBA.COMM_FAILURE:
java.net.SocketException:Connection shoutdown:
JVM_recv in socket input stream read minor code: 0 completed: No
at com.visigenic.vbroker.orb.TcpConnection.read(TcpConnection.java, Compiled Code)
at com.visigenic.vbroker.orb.GiopConnectionImpl.receive_message(GiopConnectionImpl.java:436)
This normally occured after several calls. But it does not always happen.
Any suggestions?
--Yitao
null

Sorry, the problem still exists. If I repeated calling all the methods
in my EJB from the EJB client, I will eventually get the
"Peer disconnected socket" error.
Please let me know what could be the reason.
Thanks for any help.
--Yitao                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

Similar Messages

  • Jdk 1.2 clients running ejb deployed on oracle 8.1.5

    Oracle claims that it is possible to run jdk 1.2 clients with ejb on oracle 8.1.5 in the faq : http://technet.oracle.com/products/oracle8i/htdocs/jserver_faq/815faq0012.html
    If you have JDK1.2 on the client side and:
    8.1.5 clients connecting to an 8.1.5 server: This does not work, because of conflicts with the ORB supplied in JDK1.2.
    8.1.5 clients connecting to an 8.1.6 server: This does not work, because of conflicts with the ORB supplied in JDK1.2.
    8.1.6 clients connecting to an 8.1.5 server: This works provided the "server" portion of the application is developed/loaded using the client side tools and jars that are supplied with 8.1.5.
    What do they meen with 8.1.6 clients? and how to make 8.1.6 clients?

    Oracle 8.1.6's JVM uses JDK 1.2. Oracle's 8.1.6 JDBC drivers support JDBC2 and JDK2. The 8.1.6 drivers are available for download from OTN under the Technologies section.
    If you develop a client (application, applet, servlet, JSP, etc.) using the Oracle 8.1.6 JDBC drivers, then this is considered an Oracle 8.1.6 client.
    Laura

  • Running the client in ejb

    i have written code for the following.
    *Remote Interface
    *Home Interface
    *Stateless SessionBean
    *Client Program
    how do i run the client program. Im using a jboss application server. what files should be kept in which folder to run the program...

    Verify if the connect.properties match your deployment mode viz Local, EJB or Oracle8i.
    Uday

  • Help: applet call ejb in oracle8i

    Hello:
    Can someone tell me how to call ejb in oracle8i from applet?
    thanks a lot!
    tom
    null

    Hi mark tomlinson:
    It does not work(IE and Netscape). Did you run the example
    ejbclubmed?
    tom
    mark tomlinson (guest) wrote:
    : Here is an example snippet:
    : Assuming that the EJB MyEJB has been deployed and the generated
    : server stubs (MyEJB_generated.jar) is referenced to resolve the
    : Home and Bean objects, then:
    : MyEJB myejb_obj;
    : String user = "scott";
    : String password = "tiger"
    : String URL = "sess_iiop://<my8iserver>:2481:ORCL:/test/MyEJB";
    : // Creates the Hashtable to hold the environment variables.
    : Hashtable environment = new Hashtable();
    : // Tells JNDI to speak sess_iiop
    : environment.put(javax.naming.Context.URL_PKG_PREFIXES,
    : "oracle.aurora.jndi");
    : // Tells sess_iiop the userid, password, and credential
    : authentication.environment.put
    (Context.SECURITY_PRINCIPAL,user);
    : environment.put(Context.SECURITY_CREDENTIALS, password);
    : environment.put(Context.SECURITY_AUTHENTICATION,
    : ServiceCtx.NON_SSL_LOGIN);
    : // Creates the initial context.
    : Context ic = new InitialContext(environment);
    : // Gets an implementation of the EJB's home interface from the
    : // inital context.
    : MyEJBHome home = (RentalsEJBHome) ic.lookup(URL);
    : // Tells the home interface to create an instance of the bean
    : myejb_obj = home.create();
    : From there you invoke moethods exposed on the bean object as
    you
    : would any other java object...
    null

  • Using the 9i client's provider towards Oracle8i

    Will the OraOLEDB provider supplied in the Oracle9i client function towards an Oracle8i server?
    And do I gain anything from it: Is the Oracle9i provider more stable, or more feature-rich, even towards an Oracle8i server?
    Thanks for any answer.
    -tor

    That theme is tried here:
    Installation Guide for 32-Bit Windows Contents / Search / Index / PDF
    http://download-east.oracle.com/docs/pdf/A95493_01.pdf
    Joel Pérez

  • Corba Client For EJB

    Hello
    I am trying to connect Corba Client to EJB deployed in OC4J.
    I followed the instructions given on
    http://otn.oracle.com/tech/java/oc4j/htdocs/how-to-rmi-iiop.html
    But I am not getting success after making tries in different ways.
    Can some body tell how to connect to EJB by a corba client using Oc4j.
    If OC4J does't support RMI-IIOP , can you suggest other server which supports that.
    Thanx in advance.

    I'm stuck exactly with the same issue while trying to port my application from weblogic to jboss.
    I tried to specify different ORB implementations (JacORB, OpenORB) for jvm option org.omg.CORBA.ORBClass, but JBoss couldn't get them instantiated. Native Sun implementation which is used in JBoss by default and can be instantiated, apparently is not fully compatible with weblogic security module.
    So did you manage to find out the solution?
    Edited by DigitalDude at 04/09/2008 11:47 PM

  • Restrict number of simultaneous connection from client to EJB bean

    I have EJB bean and JavaSE client. I want to restrict number of simultaneous connection from client to EJB bean. For example to maximum allowed 3. How I can do it?

    :) but answer is too general.
    I want to know how to design such "simple reference counting". As I understand it is not recommended to use static variables in EJB. so how to implement such counting in a right way?
    Edited by: NoName on Aug 20, 2009 1:25 AM
    Edited by: NoName on Aug 20, 2009 1:31 AM

  • Corba client to EJB on OAS408 ?

    I have an EJB deployed on OAS408. Can I call the EJB methods from a Corba client? How will I setup a CORBA client to communicate RMI over IIOP ?
    I found the following statement on the Oracle Java roadmap :
    "Enterprise beans and Common Ojbect Request Broker Architecture (CORBA) clients can inter-operate with each other opening up the possibility of multiple types of clients accessing EJB servers accross the enterprise."
    Can anybody please help me on how to do this
    null

    I am trying to do exactly the same thing
    But I am unable to read the zip file on
    the newsgroup.
    Can someone mail me the zip of the sample
    code.
    Thanks inAdvance.
    Irfan Lateef

  • Ejb client to ejb communication- slow performance ?

    I think BEA has a very nasty implementation of ejb client to ejb server communication.
    When a client looks up a an ejb component it gets a t3client eastablishing a socket connection to the ejb server (WL server).
    For one client VM there is one such client and all ejb client to server packets go through this one socket. To me it seems to be a major bottleneck for performance.
    Any body has any info ideas on how to get around this.

    What makes you think it's a bottleneck? It nearly always greatly improves performance.
    -- Rob
    Vyask wrote:
    I think BEA has a very nasty implementation of ejb client to ejb server communication.
    When a client looks up a an ejb component it gets a t3client eastablishing a socket connection to the ejb server (WL server).
    For one client VM there is one such client and all ejb client to server packets go through this one socket. To me it seems to be a major bottleneck for performance.
    Any body has any info ideas on how to get around this.

  • Rmi-iiop client for EJBs

    [att1.html]

    I've been fighting the same issues over the past few days. The answer you gave still left me
    wondering which tool to use. Should it be rmi -iiop or ejbc -iiop? I get the idl files on
    WLS 5.1 generated but then I can't get the idlj to execute properly on the generated
    HelloHome.idl and Hello.idl.
    Wayne
    Andy Piper wrote:
    Abhishek <[email protected]> writes:
    But How do I write Rmi - iiop clients for EJBs.
    when I try to generate the IDL for my EJB by running the weblogic.rmic utility I get an
    error that none of my classes ( Remote, Home and Impl ) implement the remote
    interface. Which is true as EJBs do not directly implement the remote interface.You may be able to get this to work with WLS6.0SP1 and the
    -idlMethodSignatures flag. Take a look at the methods target in
    examples/rmi_iiop/ejb/generic_idl or at
    examples/rmi_iiop/ejb/simplified_idl. This all works fine in
    Silversword.
    andy

  • Client in ejbs

    explain the term client in ejbs ? where do we install a client on the server? If the client is a standalone program how i user like me can use the client? explain briefly where this client is used in enterprise applications? I got the doubt because a standalone program is compiled into a class file. As a user how i know what is there in client program?
    I am the student learning j2ee Please help me in this regard
    Thank You

    A client is a standalone program or a web interface that connects to the
    server your business logic (written using the EJB technology) runs. Take a
    web shop for instance. The web interface is the client. When you order
    something, the web interface connects to the server, passes the data,
    waits for the result to be returned and displays the result (e.g. one more
    item in the cart, higher total and so on).
    When you want a web client, you have to deploy a WAR file that contains all
    the stuff that is needed (JSPs, Beans, deployment descriptor, ...).
    If it is a standalone program, you use it like every other program. You start
    it using java -jar client.jar. This program contains some libraries that
    enables it to connect the server if needed.
    You as a user know that there is a client as you just use it. You may not now
    that there is an EJB backend.
    HTH
    -Danny

  • How to create a WEB client in EJB module in NB 4.1 ?

    hi
    I am using SUN AS and NB 4.1
    I want to invoke a WS from an EJB. For some reason NB 4.1 doesn't allow me to create a WS client. Why ?

    netbeans forum may prove to be more useful because
    this seems to be a netbeans specific problem; an EJB
    can be a WS client and this works as is evident with
    the Adventure Builder sample app from blueprintsI generated WS stub manually without NB 4.1.

  • Creating multiple stateful session beans from a java client. (EJB 3.0)

    I'm having difficulties with the following:
    To access the ShoppingCartBean, I have to put the following annotation in my standalone java client:
    @EJB
    private static ShoppingCartRemote shoppingCartBean;
    The static must be there, thus only one ShoppingCartBean will exist within my java client. But as the ShoppingCartBean is a stateful session bean, I want to be able to get different beans of the same type.
    What is the correct way to do this in EJB 3.0?

    Great question. Because Home interfaces have been removed for the EJB 3.0 simplified
    API, stateful session bean creation happens as a side-effect of injection. However, the
    same is true of EJB 3.0 business interface lookups. The easiest way to create additional
    stateful session beans is to lookup the same dependency that was declared via your
    @EJB annotation.
    E.g.,
    // Assuming the declaring class is pkg1.ShoppingCartClient.java
    InitialContext ic = new InitialContext();
    ShoppingCartRemote scr1 = (ShoppingCartRemote)
    ic.lookup("java:comp/env/pkg1.ShoppingCartClient/shoppingCartBean");
    Note that the name relative to java:comp/env is the default associated with your
    @EJB annotation since the name() attribute wasn't used. Alternatively, you
    could have used :
    @EJB(name="scb") private static ShoppingCartRemote shoppingCartBean;
    InitialContext ic = new InitialContext();
    ShoppingCartRemote scr1 = (ShoppingCartRemote) ic.lookup("java:comp/env/scb");
    Yet another alternative is to declare the @EJB at the class-level. This just defines
    the dependency without any injection, which is fine if you want to create a bunch of
    them via lookup anyway.
    @EJB(name="scb", beanInterface=ShoppingCartRemote.class)
    public class .... {                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Writing a Standalone Client for EJB 3.0 Bean For Weblogic 10

    Steps for Writing a Standalone Client
    Client Code
    package com.client;
    import java.util.Properties;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import javax.rmi.PortableRemoteObject;
    import com.StatelessService;
    public class StatelessClient {
         public static void main(String [] args){
              Context ctx = null;
              try {
                   ctx = getInitialContext("t3://localhost:7001/protossbservice","weblogic","weblogic");
                   Object ref = ctx.lookup("StatelessService#"+StatelessService.class.getName());
                   StatelessService service = (StatelessService)PortableRemoteObject.narrow(ref,StatelessService.class);     
                   System.out.println("StatelessClient.getMessage() ++");
                   String  message = service.getMessage();
                   System.out.println("StatelessClient.getMessage --");
                        System.out.println("Message from Bean "+message);
         } catch (NamingException e) {
                   e.printStackTrace();
         private static Context getInitialContext(String url, String user, String password) throws NamingException {
            Properties h = new Properties();
            h.put(Context.INITIAL_CONTEXT_FACTORY,
                    "weblogic.jndi.WLInitialContextFactory");
            h.put(Context.PROVIDER_URL, url);
            h.put(Context.SECURITY_PRINCIPAL, user);
            h.put(Context.SECURITY_CREDENTIALS, password);
            return new InitialContext(h);
    Business Interface
    package com;
    public interface StatelessService {
         public String getMessage();
    Stateless Session Bean
    package com;
    import javax.annotation.PostConstruct;
    import javax.ejb.Remote;
    import javax.ejb.Stateless;
    * Test Stateless Session Bean
    @Stateless(mappedName="StatelessService")
    @Remote(StatelessService.class)
    public class StatelessServiceBean implements StatelessService {
         public String getMessage(){
              return "I am invoked";

    emekaco wrote:
    Hi,
    I am a trainee although with a good background in java.
    I'm urgently in need of a free ebook for EJB 3.0 with the latest version of Netbean. Pls, help me with one if you have. my email is [email protected]
    http://www.theserverside.com/tt/books/wiley/masteringEJB3/index.tss
    Here's a good free e-book but without Netbean. It covers everything you would need to know about EJBs.
    >
    Again, is container managed bean good for a big project?
    The question is too vague to be answered. It's a design decision that needs more details.

  • Memory leak in a client using EJBs deployed in a Bea Weblogic 10.0.0 cluste

    Hi all,
    We are having a memory leak in a client using stateless EJBs deployed in cluster. The client is a Tomcat 6.0.18 with java 6 but it is reproduced using Tomcat 5 with java 5. The client is calling a Weblogic Server 10.0 making
    calls to an EJB deployed in cluster that has two instances installed in two different machines.
    The client works fine if we shutdown one of the server instances and so when the client is using only one instance.
    Resuming the environment:
    Client Side:
    1 HP-Itanium machine with HP-UX.
    1 Tomcat 6 with java 6 (reproduced with java 5)
    Bea Weblogic client (wlclient.jar) for Weblogic 10.0.0
    Server Side:
    2 HP-Itanium machines with HP-UX
    Bea Weblogic Server 10.0.0 installed in both machines
    An unique domain
    Two Bea instances (one per machines) associated to a Bea Cluster
    EJBs deployed in both instances
    We have monitored the memory consumed in Tomcat and we have noticed that the VM memory PS OLD GEN grows up permanently when we make tests having the two server side Bea Instances up. We have extended
    the memory VM parameters in Tomcat client till 1G and it's only a way to delay the end: the free memory is empty, the GC is not able to free no more byte and the CPU is 100% consumed by the GC work. At the end Tomcat Client
    doesn't accept more http petitions and must be restarted.
    Besides, we have studied the VM memory in Tomcat using jmap and importing it using Eclipse Memory Analyzer. We have seen some strange memory blocks of several Mbytes that are always growing up and that are stored
    under data structures in the package com.sun.corba:
    com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl (4.5Mb)
    |
    -> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl
    |
    -> java.util.Hashtable
    |
    -> java.util.Hashtable$Entry
    |
    -> java.util.Hashtable$Entry
    -> java.util.Hashtable$Entry
    -> java.util.Hashtable$Entry
    Has anybody any idea about this problem?
    Thanks in advance.

    Hi all,
    We are having a memory leak in a client using stateless EJBs deployed in cluster. The client is a Tomcat 6.0.18 with java 6 but it is reproduced using Tomcat 5 with java 5. The client is calling a Weblogic Server 10.0 making
    calls to an EJB deployed in cluster that has two instances installed in two different machines.
    The client works fine if we shutdown one of the server instances and so when the client is using only one instance.
    Resuming the environment:
    Client Side:
    1 HP-Itanium machine with HP-UX.
    1 Tomcat 6 with java 6 (reproduced with java 5)
    Bea Weblogic client (wlclient.jar) for Weblogic 10.0.0
    Server Side:
    2 HP-Itanium machines with HP-UX
    Bea Weblogic Server 10.0.0 installed in both machines
    An unique domain
    Two Bea instances (one per machines) associated to a Bea Cluster
    EJBs deployed in both instances
    We have monitored the memory consumed in Tomcat and we have noticed that the VM memory PS OLD GEN grows up permanently when we make tests having the two server side Bea Instances up. We have extended
    the memory VM parameters in Tomcat client till 1G and it's only a way to delay the end: the free memory is empty, the GC is not able to free no more byte and the CPU is 100% consumed by the GC work. At the end Tomcat Client
    doesn't accept more http petitions and must be restarted.
    Besides, we have studied the VM memory in Tomcat using jmap and importing it using Eclipse Memory Analyzer. We have seen some strange memory blocks of several Mbytes that are always growing up and that are stored
    under data structures in the package com.sun.corba:
    com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl (4.5Mb)
    |
    -> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl
    |
    -> java.util.Hashtable
    |
    -> java.util.Hashtable$Entry
    |
    -> java.util.Hashtable$Entry
    -> java.util.Hashtable$Entry
    -> java.util.Hashtable$Entry
    Has anybody any idea about this problem?
    Thanks in advance.

Maybe you are looking for