Re: Killing off client thread
The command is onmode -z <pid>,where pid is the Unix Process ID/Session Id
for the User Transation you want to stop. I noticed that you mentioned
that the problem only occurs when your client program crashes.
Have you coded for a ROLLBACK (discard all changes thus far in transation)
or COMMIT {keep transations changes thus far in this transaction) when
an ERROR occurs? This should release all locks held by the transaction.
-------------------------------------------------------------------------
Cheryl Kendricks
Internet:cherylk@prod1.jcdc.doleta.gov OR cherylk@gwysmtp.jcdc.doleta.gov
DTSI, Inc.
Database Administrator - DOL Job Corps San Marcos, Texas
------------------------------------------------------------------------
On 17 Sep 1996, The Mist wrote:
} Hello -
} I've been following the discussion about idle client threads for
} the past couple of days because I'm having a similar problem. I'm using
} ODBC to connect to Informix 7.12 and occasionally, the driver does not
} release the connection when my client program crashes. I'm using
} Intersolv's DataDirect drivers for Informix 5 on an NT machine. I'm
} trying to get updates to happen using transactions, and occasionally the
} client crashes. When this happens, the database rows end up being locked
} and I have to restart the on-line server to flush the connections.
}
} Obviously there should be a way to just disconnect all of the
} clients and unlock those rows. Our soon-to-be DBA is off getting trained
} this week, but I'm getting tired of bringing things up and down every time
} I run into a bug in the client code. Can one of you send me the simple
} unix command that will let me disconnect idle users?
}
} Thanks,
}
} Anca Mosoiu
} Professional Services
} OneWave inc
} ammist@onewave.com
}
}