September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7209) Operation to list installed Resource Adapters

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-7209?page=com.atlassian.jira.plugin.... ] Stefano Maestri commented on WFLY-7209: --------------------------------------- I'm not sure I'm following 100%. Resource adapters could be activate in 2 different way: # w/ an entry in resource-adapters subsystem configuration # w/ ironjacamar.xml file in the rar archive in the first case you have all configuration and stats under its resource-adpater entry in DMR. In the second case you have all readonly attribute and stats under /deployment=<rar-name>. For example this is a valid command : /deployment=amq-ij.rar/subsystem=resource-adapters/ironjacamar=ironjacamar/resource-adapter=amq-ij.rar:read-resource() If you are not in one of those 2 cases the rar is not activated and in fact it's just a library deployment until it will be activated w/ a valid configuration. I don't understand what else you need, but maybe I'm not getting your use case. Could you explain a bit further? S. > Operation to list installed Resource Adapters > --------------------------------------------- > > Key: WFLY-7209 > URL: https://issues.jboss.org/browse/WFLY-7209 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Guillermo González de Agüero > Assignee: Stefano Maestri > Fix For: 10.1.0.Final > > > Currently there's no way to list all the installed Resource Adapters. Only configured resource adapters can be queried. However, they are automatically enabled at deployment time. > I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers. This would allow HAL to provide a wizard of available options when configuring them. > The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 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: ------------------------------------- Documentation backported to 6.5.x branch with https://github.com/droolsjbpm/kie-docs/commit/55b6aa8d23c2f31958e57b657aa... > 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)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1311) PDF asciidoc generation

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-1311: ---------------------------------------- Summary: PDF asciidoc generation Key: DROOLS-1311 URL: https://issues.jboss.org/browse/DROOLS-1311 Project: Drools Issue Type: Feature Request Components: docs Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Using approach from optaplanner-docs in asciidoc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7206) Graceful Shutdown and Quiescing for Transactions

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-7206?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed WFLY-7206. --------------------------------- Fix Version/s: (was: 11.0.0.Alpha1) Resolution: Duplicate Issue > Graceful Shutdown and Quiescing for Transactions > ------------------------------------------------ > > Key: WFLY-7206 > URL: https://issues.jboss.org/browse/WFLY-7206 > Project: WildFly > Issue Type: Feature Request > Components: Server, Transactions, Web Console, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > > * During the quiesce period - the server component will not accept new requests. > * Components of the server will support controlled shutdown or quiescence - ie. In-flight transactions and requests will be serviced before the shutdown. > This also implies eing able to control all request paths - HTTP (via mod_cluster), JMS and RMI (via smart proxies). > * The Quiesce operation will accept a timeout which will indicate the maximum period that a shutdown will wait for in-flight requests / transactions to complete. After the timeout expires the server component will shutdown immediately. > * It applies to servers that are started with all supported server profiles (i.e. default, default-ha, full and full-ha) in both standalone and domain modes. > * In a clustered environment if a node in cluster is on graceful shutdown, the other node(s) in the cluster should not log warnings, but infos (or debug or nothing) because this is a normal situation (Ref: PRODMGT-815) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 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: ---------------------------------- 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)

8 years, 3 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)

8 years, 3 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)

8 years, 3 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)

8 years, 3 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)

8 years, 3 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)

8 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016