[Mono-bugs] [Bug 54531][Wis] Changed - NullReferenceException in ExpiresBucket.Update()

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by mono-bug@jerryweb.info.

http://bugzilla.ximian.com/show_bug.cgi?id=54531

--- shadow/54531	2004-04-08 15:30:14.000000000 -0400
+++ shadow/54531.tmp.2386	2004-04-13 16:01:23.000000000 -0400
@@ -52,6 +52,16 @@
 
 ------- Additional Comments From mono-bug@jerryweb.info  2004-04-07 16:43 -------
 I will try it; I will give you a feedback in a few days.
 
 ------- Additional Comments From mono-bug@jerryweb.info  2004-04-08 15:30 -------
 See bug 55909 :-/
+
+------- Additional Comments From mono-bug@jerryweb.info  2004-04-13 16:01 -------
+Probably I solved it. Problem can be caused by the fact that when
+calling _lock.UpgradeToWriterLock() method, the values of variables
+after calling can be different from the values of variables before
+calling. It is necessary to re-read and check all the values whether
+they are not changed; or, not to use ReaderWriterLock and get back to
+original solution - locking with lock() (the latter seems to me to be
+more effective in this context).
+