<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Horror of Oracle&#8217;s OCI driver</title>
	<atom:link href="http://gregluck.com/blog/archives/2005/05/the-horror-of-oracles-oci-driver/feed/" rel="self" type="application/rss+xml" />
	<link>http://gregluck.com/blog/archives/2005/05/the-horror-of-oracles-oci-driver/</link>
	<description>I am sick of simple. Things should be great!</description>
	<lastBuildDate>Tue, 07 Sep 2010 21:33:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Guy Mac</title>
		<link>http://gregluck.com/blog/archives/2005/05/the-horror-of-oracles-oci-driver/comment-page-1/#comment-49</link>
		<dc:creator>Guy Mac</dc:creator>
		<pubDate>Thu, 12 May 2005 06:34:52 +0000</pubDate>
		<guid isPermaLink="false">http://gregluck.com/blog/2005/05/the-horror-of-oracles-oci-driver/#comment-49</guid>
		<description>Other horrors are
&lt;ul&gt;
&lt;li&gt;Oracle will probably be installed so the 64-bit libraries come first on the LD_LIBRARY_PATH, but your app server or java may not be 64-bit, resulting in hard-to debug segfaults.&lt;/li&gt;
&lt;li&gt;They may not play nice with connection pools. E.g. they may not be returned to the pool after being closed, so you quickly run out of connections.&lt;/li&gt;
&lt;li&gt;Using native libraries just does not work well with the classloaders on some app-servers. E.g. the native library can only be loaded once, if you deploy some new code that will try to load the native library, you&#039;ll have to restart the app server first.
&lt;/li&gt;
&lt;/ul&gt;
</description>
		<content:encoded><![CDATA[<p>Other horrors are</p>
<ul>
<li>Oracle will probably be installed so the 64-bit libraries come first on the LD_LIBRARY_PATH, but your app server or java may not be 64-bit, resulting in hard-to debug segfaults.</li>
<li>They may not play nice with connection pools. E.g. they may not be returned to the pool after being closed, so you quickly run out of connections.</li>
<li>Using native libraries just does not work well with the classloaders on some app-servers. E.g. the native library can only be loaded once, if you deploy some new code that will try to load the native library, you&#8217;ll have to restart the app server first.
</li>
</ul>
]]></content:encoded>
	</item>
</channel>
</rss>
