Joerg Beekmann wrote:
From
time to time in a development environment ODBC connections get into an
InvalidTransaction state. When this happens the quiesce method will
fail trying to rollback a transaction and it is not possible to shut
down the image.
It
is possible to deal with this by either forcing a return from the
quiesce or by killing the VM process. However it seems the image should
deal with the more gracefully, perhaps by making a best effort to clean
up resources but proceeding if it can't.
What we did to deal with these kinds of situations is something like
this
exit
[
(Delay forSeconds: 2) wait.
ObjectMemory quitPrimitive
] fork.
ObjectMemory quit
So after 2 seconds it just forces the image to quit (if its still
there).
Joerg
-----
Joerg Beekmann
DeepCove Labs
4th floor 595 Howe Street
Vancouver, BC, V6C 2T5
voice +1.604.689.0322
fax +1.604.689.0311
[hidden email]
CONFIDENTIALITY NOTICE
Unless otherwise indicated this email contains information that is
private
and confidential. If you have received it in error, please notify the
sender
and delete this message along with any attachments.
--
Dennis Smith +1 416.798.7948
Cherniak Software Development Corporation Fax: +1 416.798.0948
509-2001 Sheppard Avenue East [hidden email]
Toronto, ON M2J 4Z8 <a class="moz-txt-link-freetext"
href="sip:dennis@CherniakSoftware.com">sip:dennis@...
Canada http://www.CherniakSoftware.com
Entrance off Yorkland Blvd south of Sheppard Ave east of the DVP
Locked
