We had various problems with our AppServer using the MIDAS and SocketServer
that came with D7.
We now use both MIDAS 9 and SocketServer 9. Seems alot more stable!
Regards
Paul McKenzie
Wellington
New Zealand
Stacey Verner wrote:
The socked server is version 6.0 (6.0.6.240). It's the one that comes
with Delphi 6 Service Pack 2.
Stacey
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul McKenzie
Sent: Friday, 2 September 2005 10:23
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] DataSnap/Midas App Server Error
Ok, there goes my idea about old version...
Is the SocketServer version 9 also?
When it dies are the any event log events?
Regards
Paul McKenzie
Wellington
New Zealand
Stacey Verner wrote:
We are using Delphi 6 service Pack 2.
The versions in midas.dll say 9.0 and 9.0.1761.24408.
Stacey
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul McKenzie
Sent: Friday, 2 September 2005 9:58
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] DataSnap/Midas App Server Error
Which version of MIDAS are you using ?
Regards
Paul McKenzie
Wellington
New Zealand
Stacey Verner wrote:
We have an DataSnap/Midas app server which fails randomly.
We can't make it happen no matter how hard we try, but it happens
fairly regularly on our production machine.
A little bit of info on the app and app server:
* The applicaiton is a normal database application.
* The application also needs to get information from a settings
(metadata) database such as:
* Which databases they have access to
* What permissions they have on the database etc
* Instead of connecting directly to the settings database we use
the app server which shares one database connection between
all clients.
* This means that there is one database connection for
each application instead of 2 which reduces licencing costs
* We use the borland socket server and a socket connection to
connect to the app server.
* When we used a normal DCOM connection each client got
its own copy of the app server, so the settings database
connection is
not shared and in effect each application had two
connections to the
database.
Sometimes the app server locks up and the clients can't connect.
We have a work around that will try app servers on other
machines if
this fails which works OK, but if it never gets a
connection the all
sorts of odd things happen.
Firstly, does anyone have any thoughts on this. Debug ideas etc?
Secondly, when the connection to the app server fails it
takes forever
(minutes) to return no matter what I set the socket
connection timeout
to.
Thanks
Stacey
Stacey Verner Ph: +64-9-4154790
Software Developer Fax: +64-9-4154791
DDI: +64-9-4154797
CJN Technologies Ltd. Email: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
PO Box 302-278, North Harbour, Auckland 1330, New Zealand
12 Piermark Drive, North Harbour, Auckland, New Zealand Visit our
website at http://www.cjntech.co.nz/ <http://www.cjntech.co.nz/>
------------------------------------------------------------
----------
--
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
