Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

statement.cancel() deadlock

2 posts in JDBC Connect (product renamed to JConnect) Last posting was on 1997-07-08 14:17:17.0Z
Ellen Carroll Posted on 1997-07-07 21:32:37.0Z
Message-ID: <33C16075.4EAD@raba.com>
Date: Mon, 07 Jul 1997 17:32:37 -0400
From: Ellen Carroll <ellen.carroll@raba.com>
Reply-To: ellen.carroll@raba.com
Organization: RABA Technologies
X-Mailer: Mozilla 3.0Gold (Win95; U)
MIME-Version: 1.0
Subject: statement.cancel() deadlock
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 22
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:586
Article PK: 252340

I am still having a problem with my application hanging if I have one
thread calling cancel() for a statement that is executing in another
thread.

The thread (A) that is executing the statement is blocked on a call to
com.sybase.utils.CacheManager.getChunk().

The thread (B) that is calling statement.cancel() is blocked on a call
to com.sybase.utils.CacheStream.close().

Thread A owns the lock on com.sybase.utils.CacheStream, and
is waiting on a lock on com.sybase.utils.CacheManager.
Meanwhile, Thread B owns the lock on com.sybase.utils.CacheManager, and
is waiting on a lock on com.sybase.utils. Hence, deadlock.

++++++++++

% java Version
Using JDBC driver version 2.1

jConnect (TM) for JDBC(TM)/2.1/P/EBF7373/JDK11/Mon Jun 16 17:48:29 1997

% java -version
java version "1.1.1"

+++++++++

Thanks,

Ellen Carroll


Lance Andersen Posted on 1997-07-08 14:17:17.0Z
Message-ID: <33C24BED.6242@sybase.com>
Date: Tue, 08 Jul 1997 10:17:17 -0400
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 sun4m)
MIME-Version: 1.0
To: ellen.carroll@raba.com
Subject: Re: statement.cancel() deadlock
References: <33C16075.4EAD@raba.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 38
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:581
Article PK: 252333

Ellen,

Can you provide a working example of the problem possibly
that accesses pubs2.

thanks

-lance

Ellen Carroll wrote:
>
> I am still having a problem with my application hanging if I have one
> thread calling cancel() for a statement that is executing in another
> thread.
>
> The thread (A) that is executing the statement is blocked on a call to
> com.sybase.utils.CacheManager.getChunk().
>
> The thread (B) that is calling statement.cancel() is blocked on a call
> to com.sybase.utils.CacheStream.close().
>
> Thread A owns the lock on com.sybase.utils.CacheStream, and
> is waiting on a lock on com.sybase.utils.CacheManager.
> Meanwhile, Thread B owns the lock on com.sybase.utils.CacheManager, and
> is waiting on a lock on com.sybase.utils. Hence, deadlock.
>
> ++++++++++
>
> % java Version
> Using JDBC driver version 2.1
>
> jConnect (TM) for JDBC(TM)/2.1/P/EBF7373/JDK11/Mon Jun 16 17:48:29 1997
>
> % java -version
> java version "1.1.1"
>
> +++++++++
>
> Thanks,
>
> Ellen Carroll

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Technical Support Phone:(617) 564-6336
77 South Bedford Street Fax: (617) 564-6148
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================