<div dir="ltr"><div>Not at the moment.<br><br></div>Stuart<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 12, 2016 at 11:38 PM, Michael Musgrove <span dir="ltr"><<a href="mailto:mmusgrov@redhat.com" target="_blank">mmusgrov@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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?</div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Thu, Jul 7, 2016 at 11:02 AM, Gytis Trikleris <span dir="ltr"><<a href="mailto:gtrikler@redhat.com" target="_blank">gtrikler@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Sounds that we shouldn’t do extra shutdown logic for JTA and JTS other than possibly provide SPI for EJB and CORBA? <span><font color="#888888"><div><br></div><div>Gytis</div></font></span><div><div><div><br></div><div><div><blockquote type="cite"><div>On 6 Jul 2016, at 01:00, Stuart Douglas <<a href="mailto:stuart.w.douglas@gmail.com" target="_blank">stuart.w.douglas@gmail.com</a>> wrote:</div><br><div><div dir="ltr"><div><div>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).<br><br></div>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. <br><br></div>Stuart<br><div><div><br><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 4, 2016 at 11:11 PM, Gytis Trikleris <span dir="ltr"><<a href="mailto:gtrikler@redhat.com" target="_blank">gtrikler@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
I’m in the process of writing an analysis document for <a href="https://issues.jboss.org/browse/EAP7-459" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/EAP7-459</a> 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).<br>
<br>
Thanks,<br>
Gytis<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div><br></div>
</div></blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="">-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div>Michael Musgrove</div><div>Transactions Team</div><div>e: <a href="mailto:mmusgrov@redhat.com" target="_blank">mmusgrov@redhat.com</a></div><div>t: <a href="tel:%2B44%20191%20243%200870" value="+441912430870" target="_blank">+44 191 243 0870</a></div><div><br></div><div>Registered in England and Wales under Company Registration No. 03798903</div><div>Directors: Michael Cunningham (US), Paul Hickey (Ireland), Matt Parson</div><div>(US), Charles Peters (US)</div><div><br></div><div>Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael O'Neill(Ireland)</div></div></div>
</span></div>
</blockquote></div><br></div>