[wildfly-dev] Transactions requirement during the graceful shutdown

[Stuart Douglas]

Local transaction creation has to be allowed during graceful shutdown. e.g.
if a web request is in the process of running and it attempts to start a
transaction this must be allowed (the core requirement of graceful shutdown
is that requests that have already been accepted continue to run as normal).

The only case when transactions should be disallowed are remote
transactions, such as remote EJB and CORBA, which I think should already be
dealt with at the respective endpoints (in terms of disallowing new
transaction creation). I think the main thing that needs consideration here
is what to do with EJB requests that would otherwise be rejected that are
part of an existing remote transaction. We probably need some way of
identifying these requests and allowing them to proceed.

Stuart



On Mon, Jul 4, 2016 at 11:11 PM, Gytis Trikleris <gtrikler at redhat.com>
wrote:

> Hello,
>
> I’m in the process of writing an analysis document for
> https://issues.jboss.org/browse/EAP7-459 and need your input.
> Specifically I’m looking for the list of subsystems which might need to
> create new transactions during the graceful shutdown. Normally new
> transactions would not be allowed then, but this might stop other
> subsystems to shutdown properly. If such subsystems exist we’ll need to
> think of the way how to filter out their requests (e.g. providing SPI for
> them).
>
> Thanks,
> Gytis
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20160706/39724366/attachment.html