tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: TomEE 7.0.2 - increasing quartz tx database connections
Date Wed, 22 Feb 2017 11:41:11 GMT
Did you try passing a JtaManaged=false database to quartz? Quartz should be
the one responsible to close this connection.

I wonder if the changes related to isClosed() and close() are related to
that but shouldnt.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-02-22 12:29 GMT+01:00 tschuler <thomas.schuler@opentext.com>:

> Hi Romain!
>
> We want to share what we found out so far.
>
> We added some log messages in both versions (7.0.1 & 7.0.2) of
> org.apache.openejb.resource.jdbc.managed.local.ManagedConnection.java
> recording connection create & close.
> What we see is that while transaction completion the established
> connections used in transaction are closed.
> Afterwards the quartz handling happens requesting a connection to quartz
> database three times.
> As transaction got status 3 the connections are created at a "fallback"
> section commented with // we shouldn't come here, tempted to just throw an
> exception (see ManagedConnection.java).
>
> That happens for both versions 7.0.1 and 7.0.2. To my way of thinking the
> connections are closed to early in case of quartz handling.
> But nonetheless.
>
> TomEE 7.0.1 is able to resue and close the connection that was created in
> the "fallback" section. (see attachment extract701.txt)
> TomEE 7.0.2 is not able to resue and close these connections any more
> causing the error. (see attachment extract702.txt)
>
> So my questions so far:
> Do you have an idea where the "fallback" connection is closed within TomEE
> 7.0.1?
> Can you give me a hint what to look at to get a deeper insight?
>
> We are still not able to reproduce it within a small example.
> Maybe because 'in real' the timer is added using a web service call or
> because of an additional datasource is used within the transaction.
> But we will enhance the example step by step ...
>
> Best regards,
>                 Thomas
>
>
> extract702.txt (22K) <http://tomee-openejb.979440.
> n4.nabble.com/attachment/4681131/0/extract702.txt>
> extract701.txt (22K) <http://tomee-openejb.979440.
> n4.nabble.com/attachment/4681131/1/extract701.txt>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/TomEE-7-0-2-increasing-quartz-tx-database-
> connections-tp4681007p4681131.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message