× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I avoided using WebSphere native connection pooling in my last project as
the eventual target application server was ambiguous at the time. I plan to
replace my own pooling algorithm with the WebSphere pooling now that
WebSphere on the iSeries is the actual platform used, and especially as
there is a significant performance gain due to caching when you use this.
(See
 http://www-3.ibm.com/software/webservers/appserv/ws_bestpractices.pdf )

As another person mentioned, the technique adopted by WebSphere for
connection pooling is akin to Sun's newer API anyway, so it wouldn't be too
costly to replace the one with the other.

Chris Jewell

-----Original Message-----
From: java400-l-admin@midrange.com
[mailto:java400-l-admin@midrange.com]On Behalf Of Larry Loen
Sent: Wednesday, January 09, 2002 1:02 PM
To: java400-l@midrange.com
Subject: Re: Java and Relations DBs..



>No doubt [connection pooling] should be handled by the Java environment,
IMHO, and
>probably will one day.

Check out WebSphere.  I lose track of all the distinctions involved between
the various levels of the product (since I don't have to pay for it ;-) ),
but I think you'll find connection pooling is available in WebSphere and
probably at all levels of it.

As long as your application is sufficiently simple, writing your own
"pooling" function is not terribly difficult.  Certainly, to prototype
things while running in Microsoft land, it probably can be made to work
well enough for the pre-OS/400 testing.  If you like WebSphere, you can
probably pre-plan so you can encapsulate a quick-and-dirty version for
basic test before the migration.

I still suspect you're going to find that you have a problem with the
Order(N something) effect sooner or later, probably when you scale it up
(unless I've misunderstood your description).

As for the DB versus Table terminology thing, "it's a fair cop" as the
British put it.  Too many years on OS/400.


Larry W. Loen  -   Senior Linux, Java, and iSeries Performance Analyst
                          Dept HP4, Rochester MN


_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.