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

Thread unsafe code in rmi classes.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not an Issue
    • Icon: P4 P4
    • None
    • 1.2.0
    • core-libs
    • sparc
    • solaris_2.6


      allan.jacobs@Eng 1998-03-24
      Thread unsafe code is present in at least three classes in the
      RMI classes.


      Only the static variables that are set and used in thread-unsafe
      methods are listed. Only methods that are thread-unsafe are listed.

      Not all of the thread unsafe methods detected in this survey
      should be changed. The non-private methods that are unsafe should be
      documented as thread-unsafe. Those non-private methods that can
      eventually cause a private, thread-unsafe method to be called in an
      unsynchronized manner need to be documented, too.

      /**********************************************************************/
      java/rmi/activation
      Variable: theAuthenticator
         Methods: setDefault(Authenticator),
             requestPasswordAuthentication(InetAddress,int,String,String,String)

      /**********************************************************************/
      java/rmi/server/ObjID.java
      Unnecessary synchronization?
         Methods: ObjID()

      /**********************************************************************/
      java/rmi/server/RemoteServer.java
      Variable: log
         Methods: setLog(OutputStream),getLog()

            acolleysunw Adrian Colley (Inactive)
            ajacobssunw Allan Jacobs (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: