[
https://issues.apache.org/jira/browse/DBCP-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968691#action_12968691
]
Nils Hildebrand commented on DBCP-350:
--------------------------------------
Hi,
ok - that was the trace of another error, that, too - was gone when
downgrading to 1.2.2 - I thought it was the same thing.
But again - dbcp is not visible in that stacktrace. At the moment I am
following a different path:
This could be a oracle-rights-problem. We tried to reproduce the error
with dbcp 1.3 (tomcat 5.5.31) while using our developement environment
(Eclipse) - there the error was absent. After further invstigation we
found that the db-access was done with the scheme-owner - so the rights
of the access-user were unlimited in the development environment.
I am now comparing sql-traces between dbcp 1.4 with limited access-user
(where the problem exists) and dbcp 1.2.2 with the same limited
access-user (where the problem does not exist).
Was there a change regarding access-error handling where dbcp 1.2.2
ignored the error and 1.4/1.3?
But why does dbcp not turn up in the stacktrace?
Here it comes:
ERROR 2010-12-07 12:31:12,640 - TP-Processor2
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/BAMF].[f
rontControl]: ApplicationDispatcher.invoke(): Servlet.service() for
servlet frontControl threw exception
java.io.IOException: org.hibernatespatial.helper.FinderException:
Couldn't get at the OracleSpatial Connection object from the
PreparedStatement.
at
de.ivu.web.common.web.FrontController.doGet(FrontController.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:188)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc
her.java:659)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(Applicatio
nDispatcher.java:459)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDisp
atcher.java:395)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispat
cher.java:311)
at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java
:364)
at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java
:285)
at
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.j
ava:229)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:135)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
74)
at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200)
at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:775)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:
704)
at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.
java:897)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:689)
at java.lang.Thread.run(Thread.java:662)
> 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
>
> We have a GIS-application running on Tomcat 5.5. As webserver we are using
> 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 change
> 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 broken
> Oracle-Locator operations in dbcp 1.3
> I've seen some bug-reports for dbcp 1.3.1 which point in the same direction
> (oracle-db-error lead to java error) - perhaps these are the same problems...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
