[Mono-bugs] [Bug 74778][Blo] New - unknown method exception.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sat, 30 Apr 2005 15:46:49 -0400 (EDT)

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 ryoung@novell.com.


--- shadow/74778	2005-04-30 15:46:49.000000000 -0400
+++ shadow/74778.tmp.22844	2005-04-30 15:46:49.000000000 -0400
@@ -0,0 +1,68 @@
+Bug#: 74778
+Product: Mono: Runtime
+Version: 1.0
+OS Details: 
+Status: NEW   
+Priority: Blocker
+Component: io-layer
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: ryoung@novell.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Cc: gonzalo@ximian.com,jpallen@novell.com,miguel@ximian.com
+Summary: unknown method exception.
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+We see the following exception every few minutes.  This call is made often
+but every once in a while we see the unknown method exception.
+Exception: Simias.SimiasException
+Message: Request Failed
+Nested Exception
+Exception: System.Threading.ThreadAbortException
+Message: Thread was being aborted
+in <0x00000> <unknown method>
+in (wrapper managed-to-native) System.Threading.Monitor:Monitor_try_enter
+in <0x00012> System.Threading.Monitor:Enter (System.Object obj)
+in <0x0000a> Simias.Sync.CollectionLock:LockRequest ()
+in <0x0026f> Simias.Sync.SyncService:Start (Simias.Sync.StartSyncInfo si,
+System.String user, System.String sessionID)
+in <0x000de> Simias.Sync.Http.HttpService:StartSync (System.Web.HttpRequest
+request, System.Web.HttpResponse response,
+System.Web.SessionState.HttpSessionState session)
+in <0x001c0> Simias.Sync.Web.SyncHandler:ProcessRequest
+(System.Web.HttpContext context)
+We can also reproduce this calling some of our own native methods.  I have
+debuged this case and the native call is never hit. All the data is good
+when the method is invoked but the native code is never hit. With our call
+it seems to be fairly consistent if we make the call, return to managed
+code wait for 15 or more seconds and then issue the call again. 
+Steps to reproduce the problem:
+Actual Results:
+Expected Results:
+How often does this happen? 
+Additional Information: