Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Thu, 11 Aug 2011 08:12:29 +0000 (UTC)
From: "Nils Hildebrand (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: 
 <2059152782.27252.1313050349693.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <28342998.128911291646950764.JavaMail.jira@thor>
Subject: [jira] [Commented] (DBCP-350) Problem with DBCP 1.3 /jdk 6 and
 oracle spatial
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DBCP-350?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D130830=
05#comment-13083005 ]=20

Nils Hildebrand commented on DBCP-350:
--------------------------------------

Hi,

=20

I asked the question on a GIS-Forum at Stack-Exchange.

I=E2=80=99ve got an answer that sounds very like the root-cause of the prob=
lem =E2=80=93 located within hibernatespatial.

See below=E2=80=A6

=20

Does it ring a bell with you?

=20

Kind regards

=20

Nils

=20

=20

Von: Stack Exchange [mailto:do-not-reply@stackexchange.com]=20
Gesendet: Donnerstag, 11. August 2011 06:00


Any known problems after Tomcat-upgrade using oracle locator? <http://gis.s=
tackexchange.com/questions/13105/any-known-problems-after-tomcat-upgrade-us=
ing-oracle-locator>=20


> Problem with DBCP 1.3 /jdk 6 and oracle spatial
> -----------------------------------------------
>
>                 Key: DBCP-350
>                 URL: https://issues.apache.org/jira/browse/DBCP-350
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.3, 1.4
>         Environment: CentOS 5.5 x86_64, Oracle JDK 1.6u22 32bit, Tomcat 5=
.5.31, ojdbc6.jar
>            Reporter: Nils Hildebrand
>             Fix For: 1.3.1, 1.4.1
>
>
> We have a GIS-application running on Tomcat 5.5. As webserver we are usin=
g
> Apache httpd 2.2 connected to tomcat via ajp (mod_proxy_ajp).
> The application worked fine with Tomcat 5.5.28 until we tried to upgrade =
to Tomcat 5.5.31.
> After the upgrade we get - in certain situations a:
> java.io.IOException: org.hibernatespatial.helper.FinderException: Couldn'=
t get
> at the OracleSpatial Connection object from the PreparedStatement.
> After looking through the Tomcat 5.5 changelogs we stumbled across a chan=
ge
> made in 5.5.30: Upgrade to DBCP 1.3.
> I can affirm now that the problem is gone when downgrading to DBCP 1.2.2.
> The same problem occurs when using DBCP 1.4.
> It seems something has changed from 1.2.2 to 1.3 that has partially broke=
n Oracle-Locator operations in dbcp 1.3
> I've seen some bug-reports for dbcp 1.3.1 which point in the same directi=
on (oracle-db-error lead to java error) - perhaps these are the same proble=
ms...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira