I've been testing my CS version on a VMWare machine.  Installed the
DBISAM 4.25 B6 Server and it has a MaxConnections of 1 (Since the "user"
only has a single user license for the app).  When the client starts, it
uses the Admin port and Administrator UserID and Password to obtain
details about the user.  Then I close the session, set the user's UserID
and Password, and open the session again.  I do the same sort of thing
whenever I have to access a server side procedure.

This works fine when the client runs on my development machine (outside
of the VMWare machine).  But if I run the client on the VMWare machine I
get frequent 11282 errors (exceeded MaxConnections).  I can stop and
start the Server and get the app to run, but once the error occurs, any
connection by the client generates the 11282 error until I stop and
start the Server again.

The server allows all IP Addresses and the client is connecting via the
server's IP address, not 127.0.0.1 (or else the server name - both
values are in the INI file and I'm not sure which one wins out in case
both exist).  No sessions displayed at all in the SysAdmin tool before
the app starts.

So two questions...
1. Why the behavior when running the client on the server machine?
2. What constitutes a connection that would be affected by the
MaxConnections value?  Connecting on the UserPort only?  Connecting as a
Database User only?
--
Gordon Turner
Mycroft Computing
http://www.mycroftcomputing.com

Gordon,

<< 1. Why the behavior when running the client on the server machine? >>

Are you sure that the client is disconnecting cleanly according to the
DBISAM Database Server ?  IOW, did you check to see if there is still a
session present on the database server ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:
>
> Are you sure that the client is disconnecting cleanly according to the
> DBISAM Database Server ?  IOW, did you check to see if there is still a
> session present on the database server ?

At the time the error message is displayed, the Server Admin utility
shows 0 in both Total Sessions and Total Connected Sessions.  No entries
appear in the Status window.  The Max # Connections is set to 1.

What confuses me is this behavior only occurs when the client is run on
the server machine.  If I run the client app on my development machine
accessing the same server, everything works fine - even after the 11282
messages start appearing when I run the client on the server.

Trying to add some debugging code (ShowMessage statements) it seems as
though performing the ShowMessage prevents the problem from occurring.
When I take out the ShowMessage statements, the problem re-occurs.
Could it be some kind of timing thing with disconnecting and
re-connecting as different users that bumps into the limit?

--
Gordon Turner
Mycroft Computing
http://www.mycroftcomputing.com

Gordon,

<< What confuses me is this behavior only occurs when the client is run on
the server machine.  If I run the client app on my development machine
accessing the same server, everything works fine - even after the 11282
essages start appearing when I run the client on the server. >>

My guess is that something within VMWare is interfering with the
connection/disconnection process, especially since you cannot reproduce it
on another machine and the error becomes permanent (very weird).

<< Trying to add some debugging code (ShowMessage statements) it seems as
though performing the ShowMessage prevents the problem from occurring. When
I take out the ShowMessage statements, the problem re-occurs. Could it be
some kind of timing thing with disconnecting and re-connecting as different
users that bumps into the limit? >>

It's doubtful.  If it was a frequency issue, then it should also occur on
your development machine unless your development machine is significantly
slower than the VMWare machine.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:
>
> My guess is that something within VMWare is interfering with the
> connection/disconnection process, especially since you cannot reproduce it
> on another machine and the error becomes permanent (very weird).

I agree.  But I'm still not sure, from the DBISAM Server perspective,
when a connection counts against the Max # Connections.  Obviously, when
I connect through the server Admin utility it does not as both the
Connected Sessions and the list of logged on users are blank in the utility.

> It's doubtful.  If it was a frequency issue, then it should also occur on
> your development machine unless your development machine is significantly
> slower than the VMWare machine.

The VMWare server runs on my development machine as well (I'm using
VMWare Server 1.04).  I use it mostly to test installations as I can
reset it easily to a clean install, and it lets me test different
versions of Windows without constantly re-booting another PC (and to run
a separate copy of XP without needing to purchase an additional license.)

So I access the DBISAM Server from a client running within the VMWare
environment (causing the problem), or from outside the environment with
no problems, but all run on the same hardware.

--
Gordon Turner
Mycroft Computing
http://www.mycroftcomputing.com

Gordon,

<< I agree.  But I'm still not sure, from the DBISAM Server perspective,
when a connection counts against the Max # Connections.  Obviously, when I
connect through the server Admin utility it does not as both the Connected
Sessions and the list of logged on users are blank in the utility. >>

Only normal data connections count against the max connections setting.

<< So I access the DBISAM Server from a client running within the VMWare
environment (causing the problem), or from outside the environment with no
problems, but all run on the same hardware. >>

Just for kicks, have you tried using 127.0.0.1 instead just to see if
there's any difference ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:
>
> Only normal data connections count against the max connections setting.

OK.  So any connection to the User port counts, and any connection to
the Admin port does not - correct?

> Just for kicks, have you tried using 127.0.0.1 instead just to see if
> there's any difference ?

No real difference.  I don't ever expect a customer to run the
application on the server itself.  I was mostly trying to test calling
my server procedure when a maximum number of users are connected.  In
testing the setup on my real server (instead of a VMWare machine) the
problem does not occur, so I'm guessing it has something to do with the
way VMWare handles stuff.

--
Gordon Turner
Mycroft Computing
http://www.mycroftcomputing.com

Hi,

is anyone running DBISAM successfully on a VMware Server without 11282 errors ?

I'm especially interested in running DBSIAM server on VMware ESX server
Has anyone gained experience with that ?

Are there any problems known with other virtual server environments (like MS Virtual
servers etc.) ?

Gordon,

<< OK.  So any connection to the User port counts, and any connection to the
Admin port does not - correct? >>

Correct.

<< No real difference.  I don't ever expect a customer to run the
application on the server itself.  I was mostly trying to test calling my
server procedure when a maximum number of users are connected.  In testing
the setup on my real server (instead of a VMWare machine) the problem does
not occur, so I'm guessing it has something to do with the
way VMWare handles stuff. >>

I suspect that you're correct.   I'm finally getting around to installing
Virtual PC 2007 this weekend, so I'll have to give it a shot with that and
see if I can replicate the situation.

--
Tim Young
Elevate Software
www.elevatesoft.com