RE: (forte-users) Forte not letting go of Oracleconnections

Question

Hello Amin, Samer and David,
thank you for your fast reply.
The technical support in Germany give at least a good idea to prevent the
problem in future:
Available at Forte 3.5 and above
ER #35575 : user wants TOOL code to detect partition
shutdown and time to do something
Add a new interface, AtExitHandler, to Framework, with just one
method: RunAtExit();
Add a new method to Partition:
AtExit(AtExitHandler);
At shutdown time, managed partitions will call RunAtExit on all
registered AtExitHandlers in the same sequence that they called
AtExit on the partition.
This activity takes place synchronously before we start tearing the
partition apart, with the partition explicitly set by the active part
agent to the one we are supposed to be shutting down, so it should be
pretty safe for the user to run any code he likes.
We will catch and display any exceptions produced by the callbacks,
so that errors don't keep shutdown from proceeding (it is still possible
for the user to write code that hangs and blocks shutdown that way,
but I don't know what we could do about that besides getting into
timeouts etc.).
I think it is always a good idea to disconnect the DB-Session because you
do it with
most other tools from Database automatically, so why don't do it generally
by use of
a programming-language?!?
I try this feature in any case.
Thanks for all who answered to this message
Joseph Mirwald
GERMANY
At 17:13 13.03.01 -0500, Amin, Kamran wrote:
That was the initial problem. Forte as logged a bug on this issue and
hopefully fix it soon.
Look for bug# 54610.
-----Original Message-----
From: Joseph Mirwald [mailto:jomirweb.de]
Sent: Tuesday, March 13, 2001 4:12 PM
To: Forte Users
Subject: (forte-users) Forte not letting go of Oracle connections
Hello all,
some time ago we talked about the problem, that some DBSession-connects hang
if the partition where the DBSessionSO is used goes down.
Ok, there may be some problems with forte or the Database (TWO_TASK, and so
on).
Does anybody implement a DBSession.Disconnect() when partition goes down?
I mean the partition exits by a kill or by escript or econsole, not by a
Forte-Method call
of somewhere else.
I thought the solution must be a loop which registers for the
task.Shutdown-event, but at
the init-method I couldn't stay in a loop and wait, because i has to call
the service-objects
methods. Another solution may be a 'start task LoopMethod()' which are
registers the
event, but i don't try it now, because i don't know the side-effects
because the thread calls
a method of the 'mother-process' which goes down also.
What is your solution or idea?
Joseph Mirwald
GERMANY
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Answer 1

Hello Amin, Samer and David,
thank you for your fast reply.
The technical support in Germany give at least a good idea to prevent the
problem in future:
Available at Forte 3.5 and above
ER #35575 : user wants TOOL code to detect partition
shutdown and time to do something
Add a new interface, AtExitHandler, to Framework, with just one
method: RunAtExit();
Add a new method to Partition:
AtExit(AtExitHandler);
At shutdown time, managed partitions will call RunAtExit on all
registered AtExitHandlers in the same sequence that they called
AtExit on the partition.
This activity takes place synchronously before we start tearing the
partition apart, with the partition explicitly set by the active part
agent to the one we are supposed to be shutting down, so it should be
pretty safe for the user to run any code he likes.
We will catch and display any exceptions produced by the callbacks,
so that errors don't keep shutdown from proceeding (it is still possible
for the user to write code that hangs and blocks shutdown that way,
but I don't know what we could do about that besides getting into
timeouts etc.).
I think it is always a good idea to disconnect the DB-Session because you
do it with
most other tools from Database automatically, so why don't do it generally
by use of
a programming-language?!?
I try this feature in any case.
Thanks for all who answered to this message
Joseph Mirwald
GERMANY
At 17:13 13.03.01 -0500, Amin, Kamran wrote:
That was the initial problem. Forte as logged a bug on this issue and
hopefully fix it soon.
Look for bug# 54610.
-----Original Message-----
From: Joseph Mirwald [mailto:jomirweb.de]
Sent: Tuesday, March 13, 2001 4:12 PM
To: Forte Users
Subject: (forte-users) Forte not letting go of Oracle connections
Hello all,
some time ago we talked about the problem, that some DBSession-connects hang
if the partition where the DBSessionSO is used goes down.
Ok, there may be some problems with forte or the Database (TWO_TASK, and so
on).
Does anybody implement a DBSession.Disconnect() when partition goes down?
I mean the partition exits by a kill or by escript or econsole, not by a
Forte-Method call
of somewhere else.
I thought the solution must be a loop which registers for the
task.Shutdown-event, but at
the init-method I couldn't stay in a loop and wait, because i has to call
the service-objects
methods. Another solution may be a 'start task LoopMethod()' which are
registers the
event, but i don't try it now, because i don't know the side-effects
because the thread calls
a method of the 'mother-process' which goes down also.
What is your solution or idea?
Joseph Mirwald
GERMANY
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com