[Mono-bugs] [Bug 424797] New: SessionStateStoreProviderBase. SetAndReleaseItemExclusive error

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue Sep 9 11:05:45 EDT 2008


https://bugzilla.novell.com/show_bug.cgi?id=424797


           Summary: SessionStateStoreProviderBase.SetAndReleaseItemExclusive
                    error
           Product: Mono: Class Libraries
           Version: 1.9
          Platform: i386
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: jcsegui at cae.net
         QAContact: mono-bugs at lists.ximian.com
          Found By: Community User


Created an attachment (id=238578)
 --> (https://bugzilla.novell.com/attachment.cgi?id=238578)
Class to manage custom session state

Hello,

I'm developing my own custom session state provider based on databases. When my
overrided SetAndReleaseItemExclusive is called when a new session is created,
the last parameter (bool newItem) is always false which is not correct. This
parameter must be true when the session is about to be created. As a result of
this I can't save any session elements and my app doesn't work. In .NET it
works ok.

On this same method the 4th parameter (object lockId) is null and I think it
should be zero (as in .NET).

I'm using MONO 1.9.1 in Debian Etch with apache 2 and mod_mono 1.9.1

Attached is my SessionStateStoreProviderBase derived class and in my web.config
I've the following in sessionState section:
<system.web>
<sessionState regenerateExpiredSessionId="true" mode="Custom"
customProvider="VTSessionProvider">
        <providers>
          <add name="VTSessionProvider"
            type="VirtualTutor.Services.SessionStateProvider"
            writeExceptionsToEventLog="false" />
        </providers>
      </sessionState>
</system.web>

I hope you have enough information


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list