You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by semanticfire <ba...@netage.nl> on 2016/08/08 17:40:44 UTC

Changes in JDBC 1.7.4 -> 7.0.1

Hi,

I run a webapp which uses polling through Quartz to query a ORACLE Database.

When I use a plain Tomee+ 7.0.1 server I run into cursor errors on the JDBC
connection.
using the same war on a Tomee+ 1.7.4 works without issues.

Any hints would be welcome

Bart van Leeuwen



--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654.html
Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Changes in JDBC 1.7.4 -> 7.0.1

Posted by semanticfire <ba...@netage.nl>.
After some discussion on IRC it turns out that with the newer tomee the
connection pool is more picky on not closing statements and resultsets, even
if the connection is closed.

Updating my code and closing statements did the trick, it would be
interesting to figure out what has changed that causes this behaviour.

Alternative solutions:
- select dbcp as connection pool, this solved the problem without modifying
the code.
- Use: org.apache.tomcat.jdbc.pool.interceptor.StatementFinalizer


semanticfire wrote
> I did notice that some of the default settings on the connection are
> different between 1.7.4 and 7.0.1 if I look at the attributes of:
> openejb.management -> datasources -> 
> <DB>
> MinSize, Initialsize, MaxSize , NumIdle, TestOnBorrow





--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654p4679698.html
Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Changes in JDBC 1.7.4 -> 7.0.1

Posted by semanticfire <ba...@netage.nl>.
I did notice that some of the default settings on the connection are
different between 1.7.4 and 7.0.1 if I look at the attributes of:
openejb.management -> datasources -> <DB>

MinSize, Initialsize, MaxSize , NumIdle, TestOnBorrow





--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654p4679671.html
Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Changes in JDBC 1.7.4 -> 7.0.1

Posted by Romain Manni-Bucau <rm...@gmail.com>.
Then we need:
- full boot logs
- a thread dump when it is slow
- maybe debug logs to check connections are closed

Le 8 août 2016 21:21, "semanticfire" <ba...@netage.nl> a écrit :

> Error codes from oracle:
>
>
>
> I don't see anything out of the ordinary in the JMX logging
>
>
> semanticfire wrote
> > Hi,
> >
> > I don't see any errors, other then it seems the startup seems somewhat
> > slow.
> > I'll look at the JMX connection logs again.
> >
> > Configuration:
>
> >
> > Bart
> > Romain Manni-Bucau wrote
> >> Hi
> >>
> >> Tomcat jdbc got some param renaming. Check warnings at startup, it
> should
> >> be logged.
> >>
> >> Also maybe monitor through jmx the number of active connections per
> >> invocation of the method to ensure it is released.
> >>
> >> Le 8 août 2016 20:26, "semanticfire" &lt;
>
> >> bart@
>
> >> &gt; a écrit :
> >>
> >>> Hi,
> >>>
> >>> I run a webapp which uses polling through Quartz to query a ORACLE
> >>> Database.
> >>>
> >>> When I use a plain Tomee+ 7.0.1 server I run into cursor errors on the
> >>> JDBC
> >>> connection.
> >>> using the same war on a Tomee+ 1.7.4 works without issues.
> >>>
> >>> Any hints would be welcome
> >>>
> >>> Bart van Leeuwen
> >>>
> >>>
> >>>
> >>> --
> >>> View this message in context: http://tomee-openejb.979440.
> >>> n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654.html
> >>> Sent from the TomEE Users mailing list archive at Nabble.com.
> >>>
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654p4679659.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

Re: Changes in JDBC 1.7.4 -> 7.0.1

Posted by semanticfire <ba...@netage.nl>.
Error codes from oracle:



I don't see anything out of the ordinary in the JMX logging


semanticfire wrote
> Hi,
> 
> I don't see any errors, other then it seems the startup seems somewhat
> slow.
> I'll look at the JMX connection logs again.
> 
> Configuration:

> 
> Bart
> Romain Manni-Bucau wrote
>> Hi
>> 
>> Tomcat jdbc got some param renaming. Check warnings at startup, it should
>> be logged.
>> 
>> Also maybe monitor through jmx the number of active connections per
>> invocation of the method to ensure it is released.
>> 
>> Le 8 août 2016 20:26, "semanticfire" &lt;

>> bart@

>> &gt; a écrit :
>> 
>>> Hi,
>>>
>>> I run a webapp which uses polling through Quartz to query a ORACLE
>>> Database.
>>>
>>> When I use a plain Tomee+ 7.0.1 server I run into cursor errors on the
>>> JDBC
>>> connection.
>>> using the same war on a Tomee+ 1.7.4 works without issues.
>>>
>>> Any hints would be welcome
>>>
>>> Bart van Leeuwen
>>>
>>>
>>>
>>> --
>>> View this message in context: http://tomee-openejb.979440.
>>> n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654.html
>>> Sent from the TomEE Users mailing list archive at Nabble.com.
>>>





--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654p4679659.html
Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Changes in JDBC 1.7.4 -> 7.0.1

Posted by semanticfire <ba...@netage.nl>.
Hi,

I don't see any errors, other then it seems the startup seems somewhat slow.
I'll look at the JMX connection logs again.

Configuration:


Bart


Romain Manni-Bucau wrote
> Hi
> 
> Tomcat jdbc got some param renaming. Check warnings at startup, it should
> be logged.
> 
> Also maybe monitor through jmx the number of active connections per
> invocation of the method to ensure it is released.
> 
> Le 8 août 2016 20:26, "semanticfire" &lt;

> bart@

> &gt; a écrit :
> 
>> Hi,
>>
>> I run a webapp which uses polling through Quartz to query a ORACLE
>> Database.
>>
>> When I use a plain Tomee+ 7.0.1 server I run into cursor errors on the
>> JDBC
>> connection.
>> using the same war on a Tomee+ 1.7.4 works without issues.
>>
>> Any hints would be welcome
>>
>> Bart van Leeuwen
>>
>>
>>
>> --
>> View this message in context: http://tomee-openejb.979440.
>> n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654.html
>> Sent from the TomEE Users mailing list archive at Nabble.com.
>>





--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654p4679657.html
Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Changes in JDBC 1.7.4 -> 7.0.1

Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi

Tomcat jdbc got some param renaming. Check warnings at startup, it should
be logged.

Also maybe monitor through jmx the number of active connections per
invocation of the method to ensure it is released.

Le 8 août 2016 20:26, "semanticfire" <ba...@netage.nl> a écrit :

> Hi,
>
> I run a webapp which uses polling through Quartz to query a ORACLE
> Database.
>
> When I use a plain Tomee+ 7.0.1 server I run into cursor errors on the JDBC
> connection.
> using the same war on a Tomee+ 1.7.4 works without issues.
>
> Any hints would be welcome
>
> Bart van Leeuwen
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>