commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nils Hildebrand (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DBCP-350) Problem with DBCP 1.3 /jdk 6 and oracle spatial
Date Mon, 06 Dec 2010 15:41:15 GMT

    [ https://issues.apache.org/jira/browse/DBCP-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967225#action_12967225
] 

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

Hi,

find below an example of the full error message - imho it does not say
much, since the first exception mentioned seems to be the problem.

I did a network trace of the DB-connection and found some ORA-not-found
messages.
How can I trace this further down?

Since I am not a java-developer I can't give you a short code snippet
that will trigger the same error.


FATAL 2010-11-24 11:08:29,245 - TP-Processor8
de.ivu.web.common.web.FrontController: FrontController.doGet():
Exception im FrontController.doGet!!!
org.hibernate.HibernateException:
org.hibernatespatial.helper.FinderException: Couldn't get at the
OracleSpatial Connection object from the PreparedStatement.
        at
org.hibernatespatial.oracle.SDOGeometryType.nullSafeSet(SDOGeometryType.
java:109)
        at
org.hibernatespatial.GeometryUserType.nullSafeSet(GeometryUserType.java:
184)
        at
org.hibernate.type.CustomType.nullSafeSet(CustomType.java:156)
        at
org.hibernate.loader.Loader.bindPositionalParameters(Loader.java:1707)
        at
org.hibernate.loader.Loader.bindParameterValues(Loader.java:1678)
        at
org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1563)
        at org.hibernate.loader.Loader.doQuery(Loader.java:673)
        at
org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loade
r.java:236)
        at org.hibernate.loader.Loader.doList(Loader.java:2220)
        at
org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104)
        at org.hibernate.loader.Loader.list(Loader.java:2099)
        at
org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:94
)
        at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1569)
        at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283)
        at
de.ivu.bamf.webgis.db.bohelper.SportvereinHelper.createBOs(SportvereinHe
lper.java:61)
        at
de.ivu.bamf.webgis.db.bohelper.SportvereinHelper.createBOs(SportvereinHe
lper.java:83)
        at
de.ivu.bamf.webgis.db.DefaultDBController.getFeatures(DefaultDBControlle
r.java:198)
        at
de.ivu.bamf.webgis.worker.search.CalculateExtendedSearchResultWorker.dot
heWork(CalculateExtendedSearchResultWorker.java:576)
        at de.ivu.web.common.web.WebCommand.execute(WebCommand.java:93)
        at
de.ivu.web.common.web.Dispatcher.dispatch(Dispatcher.java:106)
        at
de.ivu.web.common.web.FrontController.doGet(FrontController.java:94)
        at
de.ivu.web.common.web.FrontController.doPost(FrontController.java:177)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
        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.StandardWrapperValve.invoke(StandardWrapperValv
e.java:213)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:172)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:127)
        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)
Caused by: org.hibernatespatial.helper.FinderException: Couldn't get at
the OracleSpatial Connection object from the PreparedStatement.
        at
org.hibernatespatial.oracle.DefaultConnectionFinder.find(DefaultConnecti
onFinder.java:73)
        at
org.hibernatespatial.oracle.DefaultConnectionFinder.find(DefaultConnecti
onFinder.java:51)
        at
org.hibernatespatial.oracle.SDOGeometryType.nullSafeSet(SDOGeometryType.
java:105)
        ... 38 more

Kind regards

Nils





> 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.


Mime
View raw message