Tim,

When I execute a query that results in an exception, and terminate the application after
that, and repeat this a few times, the server freezes - can't be stopped anymore, just
killed via taskmanager.

This is somewhat new...a few builds before it worked fine. So before I try to reproduce it
in EDB Manager or isolate the problem in my app, do you remember any recent changes that
could cause this ?

TIA,

Heiko

Heiko,

<< When I execute a query that results in an exception, and terminate the
application after that, and repeat this a few times, the server freezes -
can't be stopped anymore, just killed via taskmanager.

This is somewhat new...a few builds before it worked fine. So before I try
to reproduce it in EDB Manager or isolate the problem in my app, do you
remember any recent changes that could cause this ? >>

Unfortunately, no.  I have no idea what you're seeing.  I kill remote
sessions all of the time, and don't experience any issues with the ElevateDB
Server.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

OK, thanks. I'll take a closer look.

Heiko

Tim,

some news on this one.

When I connect as a single user to the EDB server, do a few not really sophisticated
things (opening a few tables, traversing some data to stringlists, display data in grids
and treeviews, I think the DB trees are setting a big amount of bookmarks) and then close
the application, the line in the EDB server grid showing the connection disappears
instantly, and everything is fine.

When I do the same thing, but encounter an exception, after that halt program execution
and terminate the program with STRG+F2, the line in the EDB server grid is still present.
The adress column shows "Adress (disconnected)". Now I wait 5 minutes. After that, exactly
at the moment this line disappears, the CPU load goes up to 100% and remains so until the
server task is killed.

If you need more info about what I'm doing exactly to the database before terminating the
app, I think I could extract it to a sample project - but it would be nice if I wouldn't
have to

Heiko

Heiko,

<< When I do the same thing, but encounter an exception, after that halt
program execution and terminate the program with STRG+F2, the line in the
EDB server grid is still present.  The adress column shows "Adress
(disconnected)". Now I wait 5 minutes. After that, exactly at the moment
this line disappears, the CPU load goes up to 100% and remains so until the
server task is killed. >>

If you need more info about what I'm doing exactly to the database before
terminating the app, I think I could extract it to a sample project - but it
would be nice if I wouldn't have to >>

I'll see what I can dig up before that, but it may come down to me asking
for it anyways.

--
Tim Young
Elevate Software
www.elevatesoft.com

Heiko,

<< When I do the same thing, but encounter an exception, after that halt
program execution and terminate the program with STRG+F2, the line in the
EDB server grid is still present. The adress column shows "Adress
(disconnected)". Now I wait 5 minutes. After that, exactly at the moment
this line disappears, the CPU load goes up to 100% and remains so until the
server task is killed.

If you need more info about what I'm doing exactly to the database before
terminating the app, I think I could extract it to a sample project - but it
would be nice if I wouldn't have to >>

Actually, if you could just give me a general description of what you're
doing right before the reset, including the operation that causes the
exception, that would be a good start.  I'm not having much luck with
general tries on this - I've tried running queries, having open tables, etc.
and nothing seems to having any issues when the server finally removes the
dead session that results from the remote application reset.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I managed to narrow it down. Damn, even with lowest DeadSession-settings there's almost a
minute between tries

When you open a query or a table in EDB Manager with an external function in the
where-clause or the filter expression, and kill the EDB Manager task after that, you see
this error. With a SQL/PSM function it works.

Heiko

Heiko,

<< I managed to narrow it down. Damn, even with lowest DeadSession-settings
there's almost a minute between  tries  >>

Yes, sorry about that - the dead session expiration checking is only done
once a minute in order to keep the processor usage at a minimum.

<< When you open a query or a table in EDB Manager with an external function
in the where-clause or the filter expression, and kill the EDB Manager task
after that, you see this error. With a SQL/PSM function it works. >>

Cool, thanks very much.  I was thinking that it might be related to
functions due to the fact that you use them extensively.  I'll see what I
can find here and let you know.

--
Tim Young
Elevate Software
www.elevatesoft.com