jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1975) Connection timed out IO Exceptions
Date Mon, 16 Feb 2009 17:26:00 GMT

     [ https://issues.apache.org/jira/browse/JCR-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-1975:
-------------------------------

    Component/s:     (was: jackrabbit-text-extractors)
                     (was: jackrabbit-spi-commons)
                     (was: jackrabbit-jcr-commons)
                     (was: jackrabbit-spi)
                     (was: jackrabbit-api)

It looks like your database connections are simply timing out. You might want to check with
your DBA on the timeout settings of your Oracle database.

Anyway, Jackrabbit should be able to deal with such issues by automatically reconnecting to
the database, but it may be that the connection pool you have configured in JNDI is preventing
Jackrabbit from doing this. You might want to try specifying the database connection parameters
directly in Jackrabbit (workspace) configuration.

> Connection timed out IO Exceptions
> ----------------------------------
>
>                 Key: JCR-1975
>                 URL: https://issues.apache.org/jira/browse/JCR-1975
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: core 1.4.5
>         Environment: Linux (CentOs), Oracle XE 10g, Tomcat 6, JDK 1.6, Magnolia Enterprise
3.6.3, JNDI
>            Reporter: Edgar Vonk
>         Attachments: jackrabbit_ioexceptionlog.txt
>
>
> We are running Jackrabbit 1.4.5 as part of the Magnolia Enterprise CMS. We are running
into Jackrabbit - database connection problems on some occasions. We do not understand why
and when these happen. When they do all we can do is restart Tomcat (with Magnolia) and then
everything seems to run fine again until the next time this happens.
> We have looked into this issue together with Magnolia but have so far failed to come
up with a solution. We have not even been able to reproduce the issue. It only happens on
our production environment (where we have the database server on a separate machine from our
two app servers).
> I have also reported this issue on the Magnolia form: http://www.nabble.com/Using-Oracle-with-a-JNDI-datasource-in-Tomcat-td21114284.html
> We are using a JNDI persistence manager set-up. Our Jackrabbit persistence manager configuration
looks as follows:
> {code}
> <PersistenceManager class="org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager">
>   <param name="driver" value="javax.naming.InitialContext" />
>   <param name="url" value="java:comp/env/jdbc/magnolia" />
>   <param name="schemaObjectPrefix" value="${wsp.name}_" />
>   <param name="externalBLOBs" value="false" />
> </PersistenceManager>
> {code}
> Our datasource in Tomcat:
> {code}
> 	<Resource 
> 		name="jdbc/magnolia" 
> 		auth="Container" 
> 		type="javax.sql.DataSource"
> 		driverClassName="oracle.jdbc.OracleDriver" 
> 		url="jdbc:oracle:thin:@//CHANGEME:1521/XEXDB"
> 		username="CHANGEME" 
> 		password="CHANGEME" 
> 		maxActive="20" 
> 		maxIdle="10" 
> 		maxWait="-1" />
> {code}
> In the log files we see:
> java.sql.SQLRecoverableException: Io exception: Connection timed out
> I will upload the full log file excerpt. 

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