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 Thu, 23 Feb 2017 11:06:40 GMT
Yes, summarized it could be said this way I think: "quartz doc is valid but
tomee usage of quartz is 'internal' and outside the EJB".

If you use yourself quartz from the EJB then you could use the CMT config
but not the case using @Schedule IIRC.


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-23 11:58 GMT+01:00 tschuler <thomas.schuler@opentext.com>:

> Hi Romain!
>
> We configured quartz for using JDBC-JobStoreCMT (see
> http://www.quartz-scheduler.org/documentation/quartz-2.2.x/configuration/
> ConfigJobStoreCMT.html).
> It is suggested to be used if "applications are using JTA transactions
> (such
> as via EJB Session Beans) to perform their work."
> To my way of thinking that's exactly what we do if we use scheduled beans.
> The configuration needs two datasources (CMT and non-CMT).
> If we change the configuration to use the non-CMT datasource also as CMT
> datasource - no more open connections are left behind.
>
> That means that even if scheduled beans are used the quartz handling
> happens
> outside the transaction - did I get it right?
>
> So JDBC-JobStoreTX (see
> http://www.quartz-scheduler.org/documentation/quartz-2.2.x/configuration/
> ConfigJobStoreTX.html)
> should be used instead?
>
> Best regards,
>         Thomas
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/TomEE-7-0-2-increasing-quartz-tx-database-
> connections-tp4681007p4681137.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

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