Tim

I suggested a while ago a property would be nice to prevent sessions being counted for LicensedSessions purposes. Did it get done and if so where is it hidden?

Roy Lambert

Roy,

<< I suggested a while ago a property would be nice to prevent sessions
being counted for LicensedSessions purposes. Did it get done and if so where
is it hidden? >>

No, I just looked at this last week and unfortunately it cannot be done, at
least not for local sessions.  It has to do with the way that sessions are
"counted" with the local engine.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


In that case.

I used to use semaphore flags to control the number of users accessing the system. What do you suggest I now use. And before you say it suggesting a table of my own isn't particularly suitable.

Roy Lambert

Roy,

<< I used to use semaphore flags to control the number of users accessing
the system. >>

That's effectively what EDB is using, and is the main reason why you can't
just leave out certain sessions from the count.  Each session occupies a
slot, and that's all that any other session can tell about that session.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

><< I used to use semaphore flags to control the number of users accessing
>the system. >>
>
>That's effectively what EDB is using, and is the main reason why you can't
>just leave out certain sessions from the count. Each session occupies a
>slot, and that's all that any other session can tell about that session.

Duh, from the manual "These methods are no longer supported. ElevateDB does not
support semaphore locks."

But ignoring that do you have a suggestion? The LicencedSessions will be fine IF there are no background threads.

Roy Lambert

Roy,

<< Duh, from the manual "These methods are no longer supported. ElevateDB
does not support semaphore locks." >>

Well, it doesn't in terms of user-defined semaphore locks like what DBISAM
had.

<< But ignoring that do you have a suggestion? The LicencedSessions will be
fine IF there are no background threads. >>

How many background threads are you using ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>How many background threads are you using ?

There is the problem. There will be at least one (a notifier thread checking on wether there are new emails for the user etc) but also a variable amount depending on what they are doing eg do a search through all cv's on file for a specific phrase.

Are the semaphore flags something you have done yourself or are they based on a Windows API call. If the latter then with a pointer in the right direction I might be able to come up with something myself.

Also thinking about your previous post <<That's effectively what EDB is using, and is the main reason why you can't
just leave out certain sessions from the count.>> I wonder why I can't have a property to simply stop the session "licensing" itself. Unless the semaphore is set for another reason but <<Each session occupies a slot, and that's all that any other session can tell about that session.>> makes me doubt that.

Roy Lambert

Roy,

I was just thinking, if you were to set the licensed sessions to something
less than 4096, then the difference between the licensed sessions setting
and 4096 could be used for this "don't include" space.  That will most
likely work.

<< I wonder why I can't have a property to simply stop the session
"licensing" itself. >>

You can - just set the number of licensed sessions to 4096, which is the max
number of licensed sessions that EDB supports.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>I was just thinking, if you were to set the licensed sessions to something
>less than 4096, then the difference between the licensed sessions setting
>and 4096 could be used for this "don't include" space. That will most
>likely work.

I think I follow, but my brain is still in the cotton wool stage of the bug.

Lets say 10 users = 10 "licensed" sessions and each user could have between 1 and 5 background threads running giving a maximum of 60 sessions in total.

What would I do? what would ElevateDB do? how would I stop user 11 logging on?

Roy Lambert

Roy,

<< Lets say 10 users = 10 "licensed" sessions and each user could have
between 1 and 5 background threads running giving a maximum of 60 sessions
in total.

What would I do? what would ElevateDB do? how would I stop user 11 logging
on? >>

You would just set the licensed session count to 10, and then mark any
thread sessions as "don't include in license count" via a property.   EDB
would then basically use slots 11 to 4096 for these "don't include"
sessions, thus they would never interfere with the proper counting of the 10
licensed sessions.

--
Tim Young
Elevate Software
www.elevatesoft.com