db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d..@apache.org
Subject cvs commit: db-torque/xdocs changes.xml
Date Fri, 20 Jun 2003 16:01:50 GMT
dlr         2003/06/20 09:01:50

  Modified:    xdocs    Tag: TORQUE_3_0_BRANCH changes.xml
  Log:
  Tweaked wording of thread deadlock problem.
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.54.2.15 +7 -6      db-torque/xdocs/changes.xml
  
  Index: changes.xml
  ===================================================================
  RCS file: /home/cvs/db-torque/xdocs/changes.xml,v
  retrieving revision 1.54.2.14
  retrieving revision 1.54.2.15
  diff -u -u -r1.54.2.14 -r1.54.2.15
  --- changes.xml	20 Jun 2003 10:54:09 -0000	1.54.2.14
  +++ changes.xml	20 Jun 2003 16:01:49 -0000	1.54.2.15
  @@ -42,12 +42,13 @@
         generated
       </li>  
       <li>
  -      Corrected deadly multi-CPU thread deadlock problem discovered by Ed
  -      Korthof <ed@apache.org> and John McNally <jmcnally@apache.org>.  The
  -      problem was due to emulation of synchronization using an int counter
  -      (to improve performance by avoiding Java "synchronized" keyword).
  -      Post-increment and decrement operators compile to three op codes (with
  -      Sun's JDK 1.3.1 for Linux), unsafe on a multi-CPU box.      
  +      Corrected deadly thread deadlock problem discovered by Ed
  +      Korthof <ed@apache.org> and John McNally <jmcnally@apache.org>.
  +      The problem was due to emulation of synchronization using an int
  +      counter (to improve performance by avoiding Java "synchronized"
  +      keyword).  Post-increment and decrement operators compile to
  +      three op codes (with Sun's JDK 1.3.1 for Linux), unsafe used as
  +      a mutex.
       </li>
     </ul>
   </p>
  
  
  

Mime
View raw message