I was getting confused as to where to post so I thought I'd start a new thread.

Had an idea this morning. Start the server first, open EDBManager, open C/S session open a few tables then do things in f/s mode. That works. Close EDBManager & reopen and things are still fine. So why does it work in this sequence and not if I open the f/s app first?


Roy Lambert

I think I have it sussed


ExcludeFromLicensedSessions
This property specifies whether the current session should be
included in the session license count controlled by the
TEDBEngine LicensedSessions property for local sessions, or
by the ElevateDB Server for remote sessions.

I altered this to True for every session my app creates and things seem to be working as they should.

I remember a discussion with Tim about not being able to use LicencedSessions to manage logins with a file/server app so this surprises me. I also think its wrong so I'll log a fault report.

I know that you set the maximum licenced sessions in the engine component. Anyone know where you can read how many have been used?

Roy Lambert

Roy Lambert wrote:

>I know that you set the maximum licenced sessions in the engine component. Anyone know where you can read how many have been used?<

Why can't you use (on C/S connection):

select count(*) from configuration.serversessions

or

select count(*) from configuration.serversessions

Of course executing this statement will count as a connected session if that's all it is doing. (Check the "Created" value to see when the session was created).

Barry

Barry



>Why can't you use (on C/S connection):
>
>select count(*) from configuration.serversessions
>
>or
>
>select count(*) from configuration.serversessions
>
>Of course executing this statement will count as a connected session if that's all it is doing. (Check the "Created" value to see when the session was created).

Licenced sessions are similar to but different from connections, which in turn are different to logons which are more similar to licenced sessions. Fun aint it.

However, since I don't have the source I can't answer this properly. All I can say that when starting the f/s first c/s would not start because I'd exceeded the connection limit. Start c/s first then the f/s and all was well, and if I ran a query in c/s it reported one connection which is exactly what I would expect.

I know there are technical difficulties in differentiating between main thread connections and subsidiary thread connections which is why Tim introduced the ExcludeFromLicensedSessions property. What I wasn't aware of is that this had crossed the c/s f/s boundary. Again since I do not have the source I can't say how both things (connections & non ExcludeFromLicensedSessions sessions) are monitored but it could be that the solution (or at least a quick solution) is for the 5 connection version of the server to have the LicencedSessions count set to 4096. However, that depends on how things are monitored.

Roy Lambert

ps

Are the two sql statements intended to be different?

Roy,

Wow. I did not realize it was that difficult. I have the C/S but without source code so I can't shed any more light on it.
To eliminate you from pulling any more of your hair out (do you have any left? vbg), your best bet is to email Tim and see if he wants to add to your thread so we can all learn from it. It could just be a quirk in his code that needs to be fixed.

>ps
Are the two sql statements intended to be different?<

Oops, it was a typo. The 2nd sql stmt should have been simply:
  select * from configuration.serversessions;


Barry

Barry


This is the response from Tim

<<This is as-designed.  The license counts are enforced at the configuration
level with OS lock counts, not at the process level.>>

I decided to scan the ngs for ExcludeFromLicensedSessions to refresh my memory the discussion goes all the way back to 2008, and in 2011 as part of a thread Tim did confirm that LicensedSessions were tracked for both c/s & f/s so its my memory at fault.

I keep thinking in terms of app logins where EDBSvr things in terms of database logins ie sessions connected and never the twain shall meet (at least for my app or where you have threads accessing the database)

Roy Lambert

On 9/16/2014 4:38 AM, Roy Lambert wrote:
> I decided to scan the ngs for ExcludeFromLicensedSessions to refresh my memory the discussion goes all the way back to 2008, and in 2011 as part of a thread Tim did confirm that LicensedSessions were tracked for both c/s & f/s so its my memory at fault.

Thanks for update - good to know.

Based on your postys did you run into into a EDBServer bug though still
- when it minimized and became non-responsive ? (as i recall you were
unable to restore the edbserver UI from tray which to me says crashed).

Raul

Raul


>Based on your postys did you run into into a EDBServer bug though still
>- when it minimized and became non-responsive ? (as i recall you were
>unable to restore the edbserver UI from tray which to me says crashed).

I think that was down to me being daft enough to run the 64bit server with 32bit dlls.

At least I have no better explanation.

Roy