September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated WFLY-4937: ---------------------------------- Component/s: XTS > Implement graceful shutdown for transactions > -------------------------------------------- > > Key: WFLY-4937 > URL: https://issues.jboss.org/browse/WFLY-4937 > Project: WildFly > Issue Type: Feature Request > Components: Transactions, XTS > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > This feature will allow EAP supported transaction services to react to suspend and resume requests. The supported services are JTA, JTS, WS-AT, and WS-BA. > After suspend, all the services remain functional. All external requests bound to the existing transactions are allowed in. All external requests requiring new transaction are blocked. All remote transaction management requests, except begin, are allowed in. > After resume, all requests are allowed in. > After suspend timeout, all services must shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated WFLY-4937: ---------------------------------- Affects Version/s: (was: 11.0.0.Alpha1) > Implement graceful shutdown for transactions > -------------------------------------------- > > Key: WFLY-4937 > URL: https://issues.jboss.org/browse/WFLY-4937 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > This feature will allow EAP supported transaction services to react to suspend and resume requests. The supported services are JTA, JTS, WS-AT, and WS-BA. > After suspend, all the services remain functional. All external requests bound to the existing transactions are allowed in. All external requests requiring new transaction are blocked. All remote transaction management requests, except begin, are allowed in. > After resume, all requests are allowed in. > After suspend timeout, all services must shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated WFLY-4937: ---------------------------------- Fix Version/s: 11.0.0.Alpha1 (was: 11.0.0.CR1) > Implement graceful shutdown for transactions > -------------------------------------------- > > Key: WFLY-4937 > URL: https://issues.jboss.org/browse/WFLY-4937 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > This feature will allow EAP supported transaction services to react to suspend and resume requests. The supported services are JTA, JTS, WS-AT, and WS-BA. > After suspend, all the services remain functional. All external requests bound to the existing transactions are allowed in. All external requests requiring new transaction are blocked. All remote transaction management requests, except begin, are allowed in. > After resume, all requests are allowed in. > After suspend timeout, all services must shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated WFLY-4937: ---------------------------------- Priority: Critical (was: Major) > Implement graceful shutdown for transactions > -------------------------------------------- > > Key: WFLY-4937 > URL: https://issues.jboss.org/browse/WFLY-4937 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > This feature will allow EAP supported transaction services to react to suspend and resume requests. The supported services are JTA, JTS, WS-AT, and WS-BA. > After suspend, all the services remain functional. All external requests bound to the existing transactions are allowed in. All external requests requiring new transaction are blocked. All remote transaction management requests, except begin, are allowed in. > After resume, all requests are allowed in. > After suspend timeout, all services must shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated WFLY-4937: ---------------------------------- Affects Version/s: 11.0.0.Alpha1 (was: 10.0.0.Alpha5) > Implement graceful shutdown for transactions > -------------------------------------------- > > Key: WFLY-4937 > URL: https://issues.jboss.org/browse/WFLY-4937 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 11.0.0.Alpha1 > > > This feature will allow EAP supported transaction services to react to suspend and resume requests. The supported services are JTA, JTS, WS-AT, and WS-BA. > After suspend, all the services remain functional. All external requests bound to the existing transactions are allowed in. All external requests requiring new transaction are blocked. All remote transaction management requests, except begin, are allowed in. > After resume, all requests are allowed in. > After suspend timeout, all services must shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated WFLY-4937: ---------------------------------- Description: This feature will allow EAP supported transaction services to react to suspend and resume requests. The supported services are JTA, JTS, WS-AT, and WS-BA. After suspend, all the services remain functional. All external requests bound to the existing transactions are allowed in. All external requests requiring new transaction are blocked. All remote transaction management requests, except begin, are allowed in. After resume, all requests are allowed in. After suspend timeout, all services must shutdown. was: We will handle suspend for JTA and JTS by disallowing new transactions and then block the suspend thread until the count of active transactions drops to zero. We will also suspend the recovery manager. We will *not* do graceful shutdown for the optional XTS subsystem. For example an incoming XTS request for an existing transaction will be blocked. Question: should we - raise a new JIRA for this XTS case; - document the deficiency and see if there are complaints; - document the deficiency and fix it in a subsequent release > Implement graceful shutdown for transactions > -------------------------------------------- > > Key: WFLY-4937 > URL: https://issues.jboss.org/browse/WFLY-4937 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 10.0.0.Alpha5 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 11.0.0.CR1 > > > This feature will allow EAP supported transaction services to react to suspend and resume requests. The supported services are JTA, JTS, WS-AT, and WS-BA. > After suspend, all the services remain functional. All external requests bound to the existing transactions are allowed in. All external requests requiring new transaction are blocked. All remote transaction management requests, except begin, are allowed in. > After resume, all requests are allowed in. > After suspend timeout, all services must shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1308) Rules compilation failure depending on condition ordering

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1308?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1308: ------------------------------------- Documented by https://github.com/droolsjbpm/kie-docs/commit/922383ff3231b77cbbfb4aea85c... > Rules compilation failure depending on condition ordering > --------------------------------------------------------- > > Key: DROOLS-1308 > URL: https://issues.jboss.org/browse/DROOLS-1308 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > > When creating rules in guided editor, we are running into validation errors depending on the order of the conditions. The problem is that the order of the conditions is important: > {noformat} > when > COND_X > COND_Y => works > when > COND_Y > COND_X => fails > java.lang.AssertionError: [10,18]: [ERR 101] Line 10:18 no viable alternative at input 'Number' in rule "ATO_Negative_AU_Test" > [0,0]: Parser returned a null Package > {noformat} > Test cases showing the compilation failures (@Test testOrder1 vs > testOrder2) can be found here: > https://gist.github.com/martinweiler/e684a0e75a2c9f4de4dee5a13affb8b0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7229) WFLYCLWEBUT0001 for server-side invalidated sessions

by Michał Nowakowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-7229?page=com.atlassian.jira.plugin.... ] Michał Nowakowski updated WFLY-7229: ------------------------------------ Description: Attached is a simple webapp (pardon the name) with a single servlet "/main", that does the following: - a session is assigned (or created, if none existed before) - its details are printed and the browser is told to refresh after 20 seconds - before the browser refreshes, the session is invalidated server-side by separate thread. Expected behaviour is, that WF should give the user a new session. That's indeed how it works in standalone mode and without <distributable/> in web.xml. But in domain mode, OR with <distributable/> added (and, possibly, full-ha profile chosen), I get errors: - The first stacktrace happens when the thread invalidates the session. - The second stacktrace happens, when the browser refreshes. The user sees "Error 500". - Then, after a minute or so, I get the last one. It then repeats periodically. We can't upgrade from 10.0 because of this - and we know we need an upgrade because of fixes in Infinispan. was: Attached is a simple webapp (pardon the name) with a single servlet "/main", that does the following: - a session is assigned (or created, if none existed before) - its details are printed and the browser is told to refresh after 20 seconds - before the browser refreshes, the session is invalidated server-side by separate thread. Expected behaviour is, that WF should give the user a new session. That's indeed how it works in standalone mode and without <distributable/> in web.xml. But in domain mode, OR with <distributable/> added (and, possibly, full-ha profile chosen), I get errors: - The first stacktrace happens when the thread invalidates the session. - The second stacktrace happens, when the browser refreshes. The user sees "Error 500". - The, after a minute or so, I get the last one. It then repeats periodically. We can't upgrade from 10.0 because of this - and we know we need an upgrade because of fixes in Infinispan. > WFLYCLWEBUT0001 for server-side invalidated sessions > ---------------------------------------------------- > > Key: WFLY-7229 > URL: https://issues.jboss.org/browse/WFLY-7229 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Environment: Happens whenever <distributable/> is used in web.xml, both in standalone and domain modes. > Reporter: Michał Nowakowski > Assignee: Stuart Douglas > Attachments: stacktrace_01.txt, stacktrace_02.txt, stacktrace_03.txt, testPortlet.tar.gz > > > Attached is a simple webapp (pardon the name) with a single servlet "/main", that does the following: > - a session is assigned (or created, if none existed before) > - its details are printed and the browser is told to refresh after 20 seconds > - before the browser refreshes, the session is invalidated server-side by separate thread. > Expected behaviour is, that WF should give the user a new session. That's indeed how it works in standalone mode and without <distributable/> in web.xml. But in domain mode, OR with <distributable/> added (and, possibly, full-ha profile chosen), I get errors: > - The first stacktrace happens when the thread invalidates the session. > - The second stacktrace happens, when the browser refreshes. The user sees "Error 500". > - Then, after a minute or so, I get the last one. It then repeats periodically. > We can't upgrade from 10.0 because of this - and we know we need an upgrade because of fixes in Infinispan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7229) WFLYCLWEBUT0001 for server-side invalidated sessions

by Michał Nowakowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-7229?page=com.atlassian.jira.plugin.... ] Michał Nowakowski updated WFLY-7229: ------------------------------------ Issue Type: Bug (was: Feature Request) > WFLYCLWEBUT0001 for server-side invalidated sessions > ---------------------------------------------------- > > Key: WFLY-7229 > URL: https://issues.jboss.org/browse/WFLY-7229 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Environment: Happens whenever <distributable/> is used in web.xml, both in standalone and domain modes. > Reporter: Michał Nowakowski > Assignee: Stuart Douglas > Attachments: stacktrace_01.txt, stacktrace_02.txt, stacktrace_03.txt, testPortlet.tar.gz > > > Attached is a simple webapp (pardon the name) with a single servlet "/main", that does the following: > - a session is assigned (or created, if none existed before) > - its details are printed and the browser is told to refresh after 20 seconds > - before the browser refreshes, the session is invalidated server-side by separate thread. > Expected behaviour is, that WF should give the user a new session. That's indeed how it works in standalone mode and without <distributable/> in web.xml. But in domain mode, OR with <distributable/> added (and, possibly, full-ha profile chosen), I get errors: > - The first stacktrace happens when the thread invalidates the session. > - The second stacktrace happens, when the browser refreshes. The user sees "Error 500". > - The, after a minute or so, I get the last one. It then repeats periodically. > We can't upgrade from 10.0 because of this - and we know we need an upgrade because of fixes in Infinispan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7229) WFLYCLWEBUT0001 for server-side invalidated sessions

by Michał Nowakowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-7229?page=com.atlassian.jira.plugin.... ] Michał Nowakowski commented on WFLY-7229: ----------------------------------------- My mistake. Of course, this is a bug report. > WFLYCLWEBUT0001 for server-side invalidated sessions > ---------------------------------------------------- > > Key: WFLY-7229 > URL: https://issues.jboss.org/browse/WFLY-7229 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Environment: Happens whenever <distributable/> is used in web.xml, both in standalone and domain modes. > Reporter: Michał Nowakowski > Assignee: Stuart Douglas > Attachments: stacktrace_01.txt, stacktrace_02.txt, stacktrace_03.txt, testPortlet.tar.gz > > > Attached is a simple webapp (pardon the name) with a single servlet "/main", that does the following: > - a session is assigned (or created, if none existed before) > - its details are printed and the browser is told to refresh after 20 seconds > - before the browser refreshes, the session is invalidated server-side by separate thread. > Expected behaviour is, that WF should give the user a new session. That's indeed how it works in standalone mode and without <distributable/> in web.xml. But in domain mode, OR with <distributable/> added (and, possibly, full-ha profile chosen), I get errors: > - The first stacktrace happens when the thread invalidates the session. > - The second stacktrace happens, when the browser refreshes. The user sees "Error 500". > - The, after a minute or so, I get the last one. It then repeats periodically. > We can't upgrade from 10.0 because of this - and we know we need an upgrade because of fixes in Infinispan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016