Hi all

Sometimes when my client application(2) is reset by another application(3)
because of response timeout, the ASA server do not allow the connection to
application(2).
I look at the current connections and there was only Sybase Central
connection in the list. To be able to connect again, I had to reset the ASA
server.

Here is the environment where the problem occurs.

Computer
P IV / 3.2g / 512 RAM 133mb

On a single computer, three apps are running 24 hours/day 365 days/year :
1- ASA Network Server 8.0.2.4322 (use about 269 mb)
- DB Size = 1.9 gb
- Allowed memory used = 50% = 260 mb
- CheckPoint done every 2 minutes
- 1 record (310 bytes) inserted every 0.9 sec (average). Insert
Statements are done within threads because data comes from many serial port
(async).
- Each raw data record is treated by a Stored procedure to be
dispatch in many tables.
- Each row is converted within 0.2 and 0.5 sec. It depends on
rules.
- The dispatch rules are also in database.
- The Stored procedure is called 0.005 sec after the end of the last
execution.
- All querys request to database that do not need to update or
delete are WITH(NOLOCK).

2- Driver (use about 8.5 mb)
- The driver receives data from many serial port and send data to
database.
- It also put a copie data in sharedmemory for the display program.

3- Display program (use between 25 mb an 40 mb)
- Take realtime data from sharedmemory and display it.
- Take past data from database.
- This application will reinitialize the driver if it do not
response within 5 minutes. (Kill process)

It seems that the problem only happen when the driver is reset. The server
will allow reconnect almost every time.

Sounds like a reproducing test case is close to being realized.

Try out the latest ebfs (just to be safe) and if the pattern
persists, we would definitely like to see this.


"Frank" <fmorin (AT) cim-solutions (DOT) net> wrote

Hi Nick

I installed 8.0.2.4339 yesterday. I have to wait to know if the problem is
fixed.
if I do not have problem during the next two months (up to now it's max time
between two events), I will suppose that everything is fine.

Until then, I will try to find what is the exact sequence causing the
problem.

"Nick Elson" <no_spam_nicelson (AT) sybase (DOT) com> a écrit dans le message de
news:3fda0ca1$1 (AT) forums-1-dub (DOT) ..