[plug] web page problem

Beau Kuiper ekuiperba at cc.curtin.edu.au
Mon Jan 3 19:46:55 WST 2000


Your search was just unlucky. I am suprised that the command wasn't automaticly
restarted by the database.

What happens with deadlocks is something like this. Firstly you have 2 or more
threads and they all can share locks.

* Process One grabs lock A
* Process Two grabs lock B
* Process Two grabs lock A and has to wait for process one to finish with it.
* Process One grabs lock B and has to wait for process two to finish with it.

At this point, both processes are waiting for each other indefinitly, which is
what we computer people call a deadlock. Deadlocks are bad. Databases will
always look out for deadlock conditions, either by detecting or preventing
them. MS SQL appears to detect when deadlocks occur. In your case the sql
server detected a deadlock between your request and some other request, and
decided it should about your request so the other request finishes.

I wouldn't worry too much about it, just run whatever you were doing again, and
it should work. The browser you use should make no difference

Beau Kuiper
ekuiperba at cc.curtin.edu.au

On Mon, 03 Jan 2000, you wrote:
> Hi,
> I am using KDE k-file manager to browse and I got this
> message at the http://www.seek.com.au web site when I tried
> to do a search:
> --------------------------------------
> Microsoft OLE DB Provider for ODBC Drivers error
> '80004005' 
> [Microsoft][ODBC SQL Server Driver][SQL Server]Your
> server  command (process id 135) was deadlocked with
> another process  and has been chosen as deadlock victim.
> Re-run your command 
> /include/session.asp, line 40
> --------------------------------------
> I've never seen this before and was curious if anyone
> knows what it means? I don't get this error using netscape.
> Thanks
> --
> Regards
> russ
> http://www.powerstech.com/hex

More information about the plug mailing list