[wildfly-dev] Transactions requirement during the graceful shutdown

[Stuart Douglas]

Not at the moment.

Stuart

On Tue, Jul 12, 2016 at 11:38 PM, Michael Musgrove <mmusgrov at redhat.com>
wrote:

> If a remote server has created a transaction and made an ejb call into the
> shutting down server then initially our (CORBA) interceptors will trigger
> and we will create a subordinate transaction and put that on the thread. So
> provided the EJB subsystem checks the association and lets the request
> through if it finds a transaction then we will be covered. Does the EJB
> subsystem perform this check?
>
> On Thu, Jul 7, 2016 at 11:02 AM, Gytis Trikleris <gtrikler at redhat.com>
> wrote:
>
>> Sounds that we shouldn’t do extra shutdown logic for JTA and JTS other
>> than possibly provide SPI for EJB and CORBA?
>>
>> Gytis
>>
>> On 6 Jul 2016, at 01:00, Stuart Douglas <stuart.w.douglas at gmail.com>
>> wrote:
>>
>> 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
>>
>>
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>
>
>
> --
> Michael Musgrove
> Transactions Team
> e: mmusgrov at redhat.com
> t: +44 191 243 0870
>
> Registered in England and Wales under Company Registration No. 03798903
> Directors: Michael Cunningham (US), Paul Hickey (Ireland), Matt Parson
> (US), Charles Peters (US)
>
> Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael
> O'Neill(Ireland)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20160713/2a83f34e/attachment.html