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

6 posts in General Discussion (old) Last posting was on 2000-03-20 18:44:35.0Z
Chris J. Frattinger Posted on 2000-03-17 04:09:34.0Z
Newsgroups: sybase.public.easerver
From: "Chris J. Frattinger" <chris_frattinger@vpaf.unr.edu>
Subject: Connection Cache Problems
Date: Thu, 16 Mar 2000 20:09:34 -0800
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: RAS3.admin.unr.edu 134.197.70.152
Message-ID: <347_b3jBfd8j$GA.151@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26236
Article PK: 156904

Hi,
I'm having some very big problems with connection caching in Jaguar 3.5
to Oracle. Our workshop noticed that when using the native Oracle driver
that instead of managing and utilizing a set number of pre-existing
connections, Jaguar was constantly opening a new thread to the database. We
had the max connections set at 10 and we're convinced that it wasn't working
when there were over 20 active connections from Jaguar. I switched to the
Oracle ODBC driver and then noticed that Jaguar would open say 4 to 7
connections, but would never use more than 1. If four requests were made
for data, three would have to wait even though there were enough physical
connections existing. I tried to setup a JDBC connection but can't seem to
get that working. My understanding is that you must have a Java
interpretation of the Oracle listener on the Oracle server in order for JDBC
calls to be successful. Our dba is not Java savvy and isn't sure what's
involved if this is the case. I don't have much confidence with the JDBC
driver working if the OCI and ODBC calls are failing. I wasn't having this
much trouble prior to the 3.5 upgrade. In an earlier post, it was suggested
that JDBC would be the best client interface. I'm not quite sure how to
troubleshoot my JDBC setup.

Any ideas or tips on what's happening?
Thanks, Chris


Chris J. Frattinger Posted on 2000-03-17 19:37:37.0Z
Newsgroups: sybase.public.easerver
From: "Chris J. Frattinger" <chris_frattinger@vpaf.unr.edu>
Subject: Re: Connection Cache Problems
Date: Fri, 17 Mar 2000 11:37:37 -0800
Lines: 12
Organization: UNR
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
NNTP-Posting-Host: ChrisF.admin.unr.edu 134.197.70.97
Message-ID: <347_CT9#KkEk$GA.285@forums.sybase.com>
References: <347_b3jBfd8j$GA.151@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26166
Article PK: 156841

Apparently my problem with pinging the database with the OCI driver may be
related to the fact that I installed the Oracle 8.1.5 client over the 8.0.5
client. Others are also experiencing this problem with Jaguar 3.5 and
Oracle 8.1.5. I'm going to uninstall 8.1.5 and reinstall 8.0.5. If that
gets me connected, then I can work on the other issue of why Jaguar
continuously opens a new thread to the database when a db request is made
from my PB components.

Then I can figure out what's wrong with my JDBC setup.
This is fun!


Chris J. Frattinger Posted on 2000-03-20 18:44:35.0Z
Newsgroups: sybase.public.easerver
From: "Chris J. Frattinger" <chris_frattinger@vpaf.unr.edu>
Subject: Re: Connection Cache Problems
Date: Mon, 20 Mar 2000 10:44:35 -0800
Lines: 20
Organization: UNR
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
NNTP-Posting-Host: ChrisF.admin.unr.edu 134.197.70.97
Message-ID: <347_6oq$h0pk$GA.285@forums.sybase.com>
References: <347_b3jBfd8j$GA.151@forums.sybase.com> <347_CT9#KkEk$GA.285@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26067
Article PK: 156072

I rolled back on two machines to the 8.0.5 client and the OCI driver now
works.

Chris J. Frattinger <chris_frattinger@vpaf.unr.edu> wrote in message
news:CT9#KkEk$GA.285@forums.sybase.com...
> Apparently my problem with pinging the database with the OCI driver may be
> related to the fact that I installed the Oracle 8.1.5 client over the
8.0.5
> client. Others are also experiencing this problem with Jaguar 3.5 and
> Oracle 8.1.5. I'm going to uninstall 8.1.5 and reinstall 8.0.5. If that
> gets me connected, then I can work on the other issue of why Jaguar
> continuously opens a new thread to the database when a db request is made
> from my PB components.
>
> Then I can figure out what's wrong with my JDBC setup.
> This is fun!
>
>


Carson Hager[Team Sybase] Posted on 2000-03-17 07:10:16.0Z
Newsgroups: sybase.public.easerver
From: chager@dyn-data.com (Carson Hager[Team Sybase])
Subject: Re: Connection Cache Problems
Date: Fri, 17 Mar 2000 07:10:16 GMT
Organization: Dynamic Data Solutions, Inc.
X-Newsreader: Forte Free Agent 1.21/32.243
Lines: 113
NNTP-Posting-Host: charon.lifescape.com 63.86.26.130
Message-ID: <347_38d1d91c.49557740@forums.sybase.com>
References: <347_b3jBfd8j$GA.151@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26233
Article PK: 156905


> I'm having some very big problems with connection caching in Jaguar 3.5
>to Oracle. Our workshop noticed that when using the native Oracle driver
>that instead of managing and utilizing a set number of pre-existing
>connections, Jaguar was constantly opening a new thread to the database. We
>had the max connections set at 10 and we're convinced that it wasn't working
>when there were over 20 active connections from Jaguar.

This is the expected behavior with PB components. By default, PB will
force a new connection. You can change this behavior by using the
additional DBParm settings. What type of components are you using?
If you are using Java, you specify this behavior in the
JCMCache.getConnection() call. JCMCache.JCM_FORCE is the Java version
of the property I mentioned before.

> I switched to the
>Oracle ODBC driver and then noticed that Jaguar would open say 4 to 7
>connections, but would never use more than 1. If four requests were made
>for data, three would have to wait even though there were enough physical
>connections existing.

That's interesting. It's possible that the driver has code to
prohibit being multi-threaded. I've never heard of it but it seems to
be what's happening.

>I tried to setup a JDBC connection but can't seem to
>get that working. My understanding is that you must have a Java
>interpretation of the Oracle listener on the Oracle server in order for JDBC
>calls to be successful.

We've never had to do anything special to use JDBC on Oracle 7.3, 8.0
or 8i. It is likely just a connection cache configuration issue.
Would you mind posting your cache properties, without the password of
course. :)

> Our dba is not Java savvy and isn't sure what's
>involved if this is the case. I don't have much confidence with the JDBC
>driver working if the OCI and ODBC calls are failing. I wasn't having this
>much trouble prior to the 3.5 upgrade.

That's interesting. Are you running NT4?

>In an earlier post, it was suggested
>that JDBC would be the best client interface. I'm not quite sure how to
>troubleshoot my JDBC setup.

OCI will outperform the JDBC drivers every time. It depends upon what
you mean by "best".


Carson

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training
http://www.dyn-data.com

DDS is now hiring EAServer consultants
to support its exploding EAServer business!
Please submit your resume to
hr@dyn-data.com!


On Thu, 16 Mar 2000 20:09:34 -0800, "Chris J. Frattinger"
<chris_frattinger@vpaf.unr.edu> wrote:

>Hi,
> I'm having some very big problems with connection caching in Jaguar 3.5
>to Oracle. Our workshop noticed that when using the native Oracle driver
>that instead of managing and utilizing a set number of pre-existing
>connections, Jaguar was constantly opening a new thread to the database. We
>had the max connections set at 10 and we're convinced that it wasn't working
>when there were over 20 active connections from Jaguar. I switched to the
>Oracle ODBC driver and then noticed that Jaguar would open say 4 to 7
>connections, but would never use more than 1. If four requests were made
>for data, three would have to wait even though there were enough physical
>connections existing. I tried to setup a JDBC connection but can't seem to
>get that working. My understanding is that you must have a Java
>interpretation of the Oracle listener on the Oracle server in order for JDBC
>calls to be successful. Our dba is not Java savvy and isn't sure what's
>involved if this is the case. I don't have much confidence with the JDBC
>driver working if the OCI and ODBC calls are failing. I wasn't having this
>much trouble prior to the 3.5 upgrade. In an earlier post, it was suggested
>that JDBC would be the best client interface. I'm not quite sure how to
>troubleshoot my JDBC setup.
>
>Any ideas or tips on what's happening?
>Thanks, Chris
>
>


___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training

DDS Enterprise Application Framework
Available Now as Open Source!
http://www.dyn-data.com


Chris J. Frattinger Posted on 2000-03-17 19:16:23.0Z
Newsgroups: sybase.public.easerver
From: "Chris J. Frattinger" <chris_frattinger@vpaf.unr.edu>
Subject: Re: Connection Cache Problems
Date: Fri, 17 Mar 2000 11:16:23 -0800
Lines: 58
Organization: UNR
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
NNTP-Posting-Host: ChrisF.admin.unr.edu 134.197.70.97
Message-ID: <347_bdnXTYEk$GA.261@forums.sybase.com>
References: <347_b3jBfd8j$GA.151@forums.sybase.com> <347_38d1d91c.49557740@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26173
Article PK: 156850

When you say that PB will force a new connection, are you implying that when
all cached connections are in use that it will by default open a new
connection, use it, and then close it as part of the 'GetConnectionOption'
DBParm default? In our case, even when a cached connection is available,
Jaguar is opening a new connection and keeps it open after it is finished
using it and it continues to do so way beyond the cache limit.

Not to throw all my problems at you, but I re-installed Jaguar and the
Oracle client and I can't seem to successfully connect via the OCI call
anymore.
My database server name is 'contprod' and this is my setup:
ServerName: contprod
UseriD : www_financial
Password: *******
Driver: OCI 8.x
DLL: oci.dll
The ping keeps failing (even after a sever restart) and the server log is
posting the following messages:
Mar 17 10:47:20 2000: Jaguar/Management refresh ConnCache ContProd
Mar 17 10:47:20 2000: AFLIB Message: 18011/11/0: DLL lookup for
'af_dll_lookup()' failed, OS Message: 'xa80.dll'

Mar 17 10:47:20 2000: AFLIB Message: 18011/11/0: DLL lookup for
'af_dll_lookup()' failed, OS Message: 'xa80.dll'

Mar 17 10:47:20 2000: DLL lookup failed for CM xagetconn
Mar 17 10:47:20 2000: Connection cache initialization failed
ailed for CM xagetconn
Mar 17 10:47:20 2000: Connection cache initialization failed
/***************************************************************************
*******************************************/

I couldn't find anything in the ODBC properties that distinguished between
single-thread or multi-thread support. Maybe Oracle just doesn't allow it
with their ODBC driver?
As for my noble attempt at using JDBC here were my cache properties:
Server: jdbc:oracle:thin:@contprod:1521:contprod
ClassName: oracle:jdbc:driver:OracleDriver

Where @contprod signifies my database alias name as defined in the
tnsnames.ora file and 'contprod' signifies my sid also defined in the
tnsnames.ora file.
I also tried replacing '@contprod' with the db server name and tried the
server IP address.
I reinstalled my Oracle client (as mentioned above) to work with a clean
slate and verified that the JDBC thin client was included in the install.
/***************************************************************************
*******************************************/
Jaguar 3.5 is running on an NT4 machine with SP 5.
If I understood the earlier post right, the JDBC driver is a more reliable
interface than Oracle's OCI driver.
/***************************************************************************
*******************************************/
Thanks for your help Carson! You guys are a big help.
Chris
...and just when I thought I was getting good at this stuff !


Carson Hager[Team Sybase] Posted on 2000-03-20 17:29:46.0Z
Newsgroups: sybase.public.easerver
From: chager@dyn-data.com (Carson Hager[Team Sybase])
Subject: Re: Connection Cache Problems
Date: Mon, 20 Mar 2000 17:29:46 GMT
Organization: Dynamic Data Solutions, Inc.
X-Newsreader: Forte Free Agent 1.21/32.243
Lines: 101
NNTP-Posting-Host: charon.lifescape.com 63.86.26.130
Message-ID: <347_38d65ebd.2425858@forums.sybase.com>
References: <347_b3jBfd8j$GA.151@forums.sybase.com> <347_38d1d91c.49557740@forums.sybase.com> <347_bdnXTYEk$GA.261@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26082
Article PK: 156086

If that's happening, you are likely misspelling something (
case-sensitive as well ) and PB is not able to make a match with
EAServer. I would try using the cachename syntax as a test.


Carson

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training
http://www.dyn-data.com

DDS is now hiring EAServer consultants
to support its exploding EAServer business!
Please submit your resume to
hr@dyn-data.com!


On Fri, 17 Mar 2000 11:16:23 -0800, "Chris J. Frattinger"

<chris_frattinger@vpaf.unr.edu> wrote:

>When you say that PB will force a new connection, are you implying that when
>all cached connections are in use that it will by default open a new
>connection, use it, and then close it as part of the 'GetConnectionOption'
>DBParm default? In our case, even when a cached connection is available,
>Jaguar is opening a new connection and keeps it open after it is finished
>using it and it continues to do so way beyond the cache limit.
>
> Not to throw all my problems at you, but I re-installed Jaguar and the
>Oracle client and I can't seem to successfully connect via the OCI call
>anymore.
>My database server name is 'contprod' and this is my setup:
> ServerName: contprod
> UseriD : www_financial
> Password: *******
> Driver: OCI 8.x
> DLL: oci.dll
>The ping keeps failing (even after a sever restart) and the server log is
>posting the following messages:
> Mar 17 10:47:20 2000: Jaguar/Management refresh ConnCache ContProd
> Mar 17 10:47:20 2000: AFLIB Message: 18011/11/0: DLL lookup for
>'af_dll_lookup()' failed, OS Message: 'xa80.dll'
>
> Mar 17 10:47:20 2000: AFLIB Message: 18011/11/0: DLL lookup for
>'af_dll_lookup()' failed, OS Message: 'xa80.dll'
>
> Mar 17 10:47:20 2000: DLL lookup failed for CM xagetconn
> Mar 17 10:47:20 2000: Connection cache initialization failed
> ailed for CM xagetconn
> Mar 17 10:47:20 2000: Connection cache initialization failed
>/***************************************************************************
>*******************************************/
>
>I couldn't find anything in the ODBC properties that distinguished between
>single-thread or multi-thread support. Maybe Oracle just doesn't allow it
>with their ODBC driver?
>As for my noble attempt at using JDBC here were my cache properties:
> Server: jdbc:oracle:thin:@contprod:1521:contprod
> ClassName: oracle:jdbc:driver:OracleDriver
>
>Where @contprod signifies my database alias name as defined in the
>tnsnames.ora file and 'contprod' signifies my sid also defined in the
>tnsnames.ora file.
>I also tried replacing '@contprod' with the db server name and tried the
>server IP address.
>I reinstalled my Oracle client (as mentioned above) to work with a clean
>slate and verified that the JDBC thin client was included in the install.
>/***************************************************************************
>*******************************************/
>Jaguar 3.5 is running on an NT4 machine with SP 5.
>If I understood the earlier post right, the JDBC driver is a more reliable
>interface than Oracle's OCI driver.
>/***************************************************************************
>*******************************************/
>Thanks for your help Carson! You guys are a big help.
>Chris
> ...and just when I thought I was getting good at this stuff !
>
>

___________________________________________________________

Carson Hager
Team Sybase
Dynamic Data Solutions, Inc.
Enterprise Application Studio 3.0 Consulting and Training

DDS Enterprise Application Framework
Available Now as Open Source!
http://www.dyn-data.com