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.

Connection cache problems

2 posts in General Discussion (old) Last posting was on 2000-02-24 22:02:37.0Z
Sergey Starosek Posted on 2000-02-24 15:50:43.0Z
Newsgroups: sybase.public.easerver
Date: Thu, 24 Feb 2000 17:50:43 +0200
From: Sergey Starosek <star@sunbay.com>
Organization: Sunbay Software AG
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Connection cache problems
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 34
NNTP-Posting-Host: local-nat.sunbay.crimea.ua 212.110.138.66
Message-ID: <347_38B55353.64F1F872@sunbay.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27926
Article PK: 159622

Hi,

We are using Jaguar 3.0.1 (build 30031) under WinNT. Connection cache is
configured to connect to remote MS SQL server v7 using Weblogic type 4
JDBC driver.

Problem is visible both in runtime monitoring window of Jaguar manager
as well as in MS SQL Enterprise manager:

JagManager shows that
Connections Active: -5
Connections Opened: 20
Connection Closed: 22
Waited: 0
No Wait: 1093
Forced: 0
Total: 1093
Last Maximum: 0
Peek Maximum: 3

MS SQL Enterprise Manager shows that number of connections grow while
almost of them are inactive (sleeping).

The configured size of the cache doesn't matter (it happens either when
size is 10 or 2). If we try to uncheck "connection sanity" checkbox then
Exception saying "Object was closed and cannot be used anymore" is
raised on Jaguar side when trying to obtain statement object from
connection.

We faced the problem when there were about 1500 connection opened to MS
SQL while connection size was set to 10. Also if our customer is using
limited license for JDBC driver then they get license exception which is
raised by JDBC driver.

Any suggestions?

Sergey


Dave Wolf [Sybase] Posted on 2000-02-24 22:02:37.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Connection cache problems
Date: Thu, 24 Feb 2000 17:02:37 -0500
Lines: 48
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: 158.159.8.12
Message-ID: <347_IHAojNxf$GA.151@forums.sybase.com>
References: <347_38B55353.64F1F872@sunbay.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27879
Article PK: 159581

Please open a case with support. It must be something odd with the Weblogic
driver. I reccoemdn the Merant drivers.

Dave Wolf
Internet Applications Division

"Sergey Starosek" <star@sunbay.com> wrote in message
news:38B55353.64F1F872@sunbay.com...
> Hi,
>
> We are using Jaguar 3.0.1 (build 30031) under WinNT. Connection cache is
> configured to connect to remote MS SQL server v7 using Weblogic type 4
> JDBC driver.
>
> Problem is visible both in runtime monitoring window of Jaguar manager
> as well as in MS SQL Enterprise manager:
>
> JagManager shows that
> Connections Active: -5
> Connections Opened: 20
> Connection Closed: 22
> Waited: 0
> No Wait: 1093
> Forced: 0
> Total: 1093
> Last Maximum: 0
> Peek Maximum: 3
>
> MS SQL Enterprise Manager shows that number of connections grow while
> almost of them are inactive (sleeping).
>
> The configured size of the cache doesn't matter (it happens either when
> size is 10 or 2). If we try to uncheck "connection sanity" checkbox then
> Exception saying "Object was closed and cannot be used anymore" is
> raised on Jaguar side when trying to obtain statement object from
> connection.
>
> We faced the problem when there were about 1500 connection opened to MS
> SQL while connection size was set to 10. Also if our customer is using
> limited license for JDBC driver then they get license exception which is
> raised by JDBC driver.
>
> Any suggestions?
>
> Sergey
>