Irregular unhandled exceptions in Dragnet

TeamWiSE · Post by **TeamWiSE** » Thu Aug 10, 2006 3:39 am

Hello!

We're evaluating Vault and Dragnet currently and have installed both on one server, using a domain-account (the same for both) since SQL-Server is running on a different server. So far, everything seems to work fine (apart from the shadow folders of vault, but that is a different topic). However, studying the log of the server reveals that the dragnet app has unhandled exceptions at irregular intervals. The exception is always the same:

Code: Select all

Ereigniscode: 3005 
Ereignismeldung: An unhandled exception has occurred. 
Ereigniszeit: 10.08.2006 03:28:38 
Ereigniszeit (UTC): 10.08.2006 01:28:38 
Ereignis-ID: dbb680b6b44743e5abc00a85bd85cb1e 
Ereignissequenz: 77 
Vorkommen: 34 
Ereignisdetailcode: 0 
 
Anwendungsinformationen: 
    Anwendungsdomäne: /LM/W3SVC/1/Root/Dragnet-1-127995112645937976 
    Vertrauensebene: Full 
    Virtueller Anwendungspfad: /Dragnet 
    Anwendungspfad: C:\Inetpub\wwwroot\Dragnet\ 
    Computername: <computername>
 
Prozessinformationen: 
    Prozess-ID: 1704 
    Prozessname: aspnet_wp.exe 
    Kontoname: <computername>\ASPNET 
 
Ausnahmeinformationen: 
    Ausnahmetyp: NullReferenceException 
    Ausnahmemeldung: Object reference not set to an instance of an object. 
 
Anforderungsinformationen: 
    Anforderungs-URL:  
    Anforderungspfad:  
    Benutzerhostadresse:  
    Benutzer:  
    Ist authentifiziert: False 
    Authentifizierungstyp:  
    Threadkontoname: <domain>\sgVault 
 
Threadinformationen: 
    Thread-ID: 8 
    Threadkontoname: <domain>\sgVault 
    Identitätswechsel für: False 
    Stapelüberwachung:    at System.Web.Security.FormsAuthentication.SignOut()
   at MantisServiceLib.Helpers.DeleteSession(HttpSessionState hss)
   at Mantis.Global.Session_End(Object sender, EventArgs e)
 
 
Details des benutzerdefinierten Ereignisses: 

Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.

Any idea as to what causes this exception? Could this compromise the dragnet database?

Post by **jclausius** » Thu Aug 10, 2006 7:36 am

When a session times out, Dragnet tries to clean up any database session info. With the 2.0 .Net Framework, Microsoft changed the threading model, which causes this problem in the event viewer.

When using the 1.1 .Net Framework, the cleanup works correctly.

This isn't affecting the database because the thread cannot connect to the database. But you may want to keep an eye on the Dragnet sessions table to make sure it does not grow beyond control.

TeamWiSE · Post by **TeamWiSE** » Thu Aug 10, 2006 8:54 am

Thanks! This sure explains this behaviour. We had enough trouble ourselves with this total change in threading design. Could this also be the explanation of the other issue I posted?

Post by **jclausius** » Thu Aug 10, 2006 9:14 am

No. I don't believe so.

There are some other questions on that thread.