Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 7 of 7 total |
EDB and IntraWeb |
Tue, Mar 3 2009 2:12 PM | Permanent Link |
Michael Fullerton | I am using EDB 109 in an Intraweb app. All works fine if the person
logs out properly. But if they just close the browser they get a session name already exists error when they try to access the software again from their browser. In the user session destructor I do close the session. Could someone explain how I can address this problem? Thanks in advance. |
Wed, Mar 4 2009 10:40 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< I am using EDB 109 in an Intraweb app. All works fine if the person logs out properly. But if they just close the browser they get a session name already exists error when they try to access the software again from their browser. In the user session destructor I do close the session. Could someone explain how I can address this problem? >> I'm not entirely familiar with IntraWeb, but it sounds like the session isn't being freed. Are you using session pooling, or something similar that will keep sessions around for re-use ? -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Mar 4 2009 12:12 PM | Permanent Link |
Michael Fullerton | On Wed, 4 Mar 2009 10:40:05 -0500, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote: >Michael, > ><< I am using EDB 109 in an Intraweb app. All works fine if the person logs >out properly. But if they just close the browser they get a session name >already exists error when they try to access the software again from their >browser. In the user session destructor I do close the session. Could >someone explain how I can address this problem? >> > >I'm not entirely familiar with IntraWeb, but it sounds like the session >isn't being freed. Are you using session pooling, or something similar that >will keep sessions around for re-use ? No, I don't do any session pooling or anything like that Tim. |
Thu, Mar 5 2009 3:25 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< No, I don't do any session pooling or anything like that Tim. >> Well, somewhere in the IntraWeb application, there are two TEDBSessions using the same SessionName. You need to find out what IntraWeb is doing with the sessions in order to resolve this issue. As I said, I know next to nothing about IntraWeb, so you might want to ask them or perhaps someone else here can shed some light on how IntraWeb handles the sessions. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Mar 6 2009 2:51 AM | Permanent Link |
"Farshad Mohajeri" | In Intraweb each new web connection creates a new Intraweb session in a
different thread. So each Intraweb session should own its separate copy of EDB session component. You must place a edb session component on UserSession module and ofcourse set the AutoSessionName to True. All EDB data access components should use its related ebdsession instead of the default session. "Michael Fullerton" <fullerm@spamkiller-remove-cybermatrix.com> wrote in message news:usqqq4d1nukp4f7c5bktoa1tsunisvdu74@4ax.com... >I am using EDB 109 in an Intraweb app. All works fine if the person > logs out properly. But if they just close the browser they get a > session name already exists error when they try to access the software > again from their browser. In the user session destructor I do close > the session. Could someone explain how I can address this problem? > Thanks in advance. > |
Fri, Mar 6 2009 4:16 PM | Permanent Link |
Michael Fullerton | Yes setting AutoSessionName to True solves the problem. Thanks
Farshad. On Fri, 6 Mar 2009 09:51:22 +0200, "Farshad Mohajeri" <farshad@ATfmsoftDOT.net> wrote: >In Intraweb each new web connection creates a new Intraweb session in a >different thread. So each Intraweb session should own its separate copy of >EDB session component. You must place a edb session component on UserSession >module and ofcourse set the AutoSessionName to True. All EDB data access >components should use its related ebdsession instead of the default session. > >"Michael Fullerton" <fullerm@spamkiller-remove-cybermatrix.com> wrote in >message news:usqqq4d1nukp4f7c5bktoa1tsunisvdu74@4ax.com... >>I am using EDB 109 in an Intraweb app. All works fine if the person >> logs out properly. But if they just close the browser they get a >> session name already exists error when they try to access the software >> again from their browser. In the user session destructor I do close >> the session. Could someone explain how I can address this problem? >> Thanks in advance. >> > |
Tue, Mar 10 2009 4:31 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Farshad,
<< In Intraweb each new web connection creates a new Intraweb session in a different thread. So each Intraweb session should own its separate copy of EDB session component. You must place a edb session component on UserSession module and ofcourse set the AutoSessionName to True. All EDB data access components should use its related ebdsession instead of the default session. >> Thanks very much for your input. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |