[Mono-bugs] [Bug 76602][Wis] Changed - Changing timezone and time while program is running makes remoting quit not work

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Nov 1 01:46:27 EST 2005


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 carlos at applianz.com.

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

--- shadow/76602	2005-11-01 01:37:27.000000000 -0500
+++ shadow/76602.tmp.31167	2005-11-01 01:46:27.000000000 -0500
@@ -91,6 +91,21 @@
 TimeZoneData.DaylightSavingStartIdx]),                                
          new DateTime (data[(int)TimeZoneData.DaylightSavingEndIdx]),
          new TimeSpan (data[(int)
 TimeZoneData.AdditionalDaylightOffsetIdx])
 );
 
+
+------- Additional Comments From carlos at applianz.com  2005-11-01 01:46 -------
+I really don't know what fully caused it but I can give you a longer
+description of what my code was doing.
+I have several apps and webservices talking to each other with
+remoting, several of the objects are complex MarshalObjByRef and a few
+are serialized. Everything was working fine when I noticed the system
+time was wrong so I used KDE to change it, thats when I noticed the
+timezone was wrong, so I ended up changing the timezone which made the
+time really wrong, then I changed the time, right after that all the
+remoting calls started failing with the exception I pasted on the
+original post.
+Hope these all helps, its really something we won't encounter again
+and even if we do its easy to restart the code.
+


More information about the mono-bugs mailing list