Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4318587

Block of RMI-IIOP communication with multithreaded client

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 1.3.0
    • Fix Version/s: 1.3.1
    • Component/s: other-libs
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      ladybird
    • CPU:
      x86, sparc
    • OS:
      solaris_2.6, windows_nt

      Backports

        Description



        Name: stC104175 Date: 03/03/2000


        java -version

        java version "1.3.0rc1"
        Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc1-T)
        Java HotSpot(TM) Client VM (build 1.3.0rc1-S, mixed mode)

          Description of the problem:

        The RMI-IIOP server (RemoteServer.java) implements a remote interface
        (RemoteItf.java) with one method. On startup of the server, it creates an
        instance of the remote object and registers that instance using JNDI (tnameserv
        is running).
        On startup, the client (client.java) looks for the registered remote object
        using JNDI, creates as many threads as specified with the "-t=xxx" option and
        passes the interface of the remote object to each thread.
        Each thread calls the method of the remote interface os often as specified with
        the "-l=xxx" option.

        Error situation:
        After an arbitrary number of calls, the following exception is thrown in the
        client.
        java.rmi.MarshalException: CORBA MARSHAL 1398079496 Maybe; nested exception is:
                org.omg.CORBA.MARSHAL: minor code: 1398079496 completed: Maybe

        After that, the client blocks and is never terminated.

        steps to reproduce the error:
        - start tnameserv in one command shell
        - start the remote server in a second command shell (java RemoteServer)
        - start the client in a third command shell (java client -t=20 -l=2000)

        Try to vary the number of threads/calls per thread. It may take a while until
        the error occures.

        Additional information:
        This error occures also with JDK1.1.8/1.2.2. There, a block of the communication
        occures with AND without the exception described, whereas with JDK1.3/RC1, the
        exception is always thrown (as far as I have seen)

        I could provide Java source code to reproduce the problem, but could not find a
        way to attach the code to that bug report. Please contact me under my EMail
        address.
        (Review ID: 101966)
        ======================================================================

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                ajindalsunw Anita Jindal (Inactive)
                Reporter:
                stompkinsunw Sean Tompkins (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: