[JBoss JIRA] (WFCORE-1627) CLI tab comple should reflect curent position of prompt
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1627?page=com.atlassian.jira.plugi... ]
Chao Wang moved JBEAP-5142 to WFCORE-1627:
------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1627 (was: JBEAP-5142)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 3.0.0.Alpha2
(was: 7.0.0.GA)
> CLI tab comple should reflect curent position of prompt
> -------------------------------------------------------
>
> Key: WFCORE-1627
> URL: https://issues.jboss.org/browse/WFCORE-1627
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha2
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> CLI tab completion cannot be used in the middle of the command. Whole command is taken as a context, ignoring the current position of prompt. Auto-completed string is inserted to the current position of the prompt (no matter it can be placed in the middle of the command).
> [] is used to show the current position of the prompt
> *actual*
> tab completion in the middle doesn't work
> {noformat}
> /subsystem=loggin[]<TAB>/root-logger=ROOT
> /subsystem=loggin[]/root-logger=ROOT
> {noformat}
> tab completion with prompt in the middle
> {noformat}
> /subsystem=logging/[]<TAB>root-logger=R
> /subsystem=logging/ROOT[]root-logger=R
> {noformat}
> *expected*
> tab completion in the middle works
> {noformat}
> /subsystem=loggin[]<TAB>/root-logger=ROOT
> /subsystem=logging[]/root-logger=ROOT
> {noformat}
> tab completion with prompt in the middle doesn't add anything unless it's a valid part of the command
> {noformat}
> /subsystem=logging/[]<TAB>root-logger=R
> /subsystem=logging/[]root-logger=R
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6773) Provide ability to start/stop Data Source creation without restart of server
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-6773?page=com.atlassian.jira.plugin.... ]
Stefano Maestri commented on WFLY-6773:
---------------------------------------
That's expected: driver is still required, since the Datasource is not effective removed until a server reload happen, so the driver is still in use.
> Provide ability to start/stop Data Source creation without restart of server
> ----------------------------------------------------------------------------
>
> Key: WFLY-6773
> URL: https://issues.jboss.org/browse/WFLY-6773
> Project: WildFly
> Issue Type: Enhancement
> Components: JCA
> Affects Versions: 10.0.0.Final
> Reporter: Ramesh Reddy
> Assignee: Stefano Maestri
>
> Currently in WF 10, where a data source is created / removed using the CLI the "reload-status" is set to "requires restart", based how the resource is expected to be managed in WF.
> h3. Why We need it?
> In Teiid, it is common practice to add/remove data sources dynamically and restarting server will affect performance and usability severely.
> * Because delete/re-add is in Teiid's workflow to manage a data sources and when we have to restart we loose the whole state of the virtual database. That means we need re-establish runtime status. For example, all the existing sessions will be killed.
> * Runtime environment are often shared, that could kill other person's tasks in flight leaving them hanging with errors.
> * Every time data source starts we fetch metadata from the source, this is very expensive operation.
> * With multi-source feature, it is a feature that user dynamically brings in/out sources as they show up on their dashboard, it would be not possible to support this feature.
> * This is a change of behavior from earlier versions of the EAP, our users and customers rely on this feature
> As per Teiid project is concerned, we consider this is regression on WF and thus a bug.
> h3. Proposed Solution
> [~brian.stansberry] suggested the WF management practices here in this document https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-Apply...
> Based on this the conclusion is that Data Sources, is developed under "all-services" paradigm, not under "resource-services" paradigm, where a explicit header from client to whether to restart or not can avoid having to "reload" the server when a new DS is added or removed. We understand the nature of service dependencies in WF, and how this can affect the other dependent services, but we verified that Teiid will not have those side effects as we designed. Since these sources are effectively exclusively defined for Teiid should not interfere with others. Also, since the request is explicit, should not affect current behavior.
> h3. Workarounds Considered
> Since this highly dependent on configuration based data source creation, we can opt to a deployment based data source creation (-ds.xml), however GSS is quick to dismiss this as this not supported feature.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6789) 'xa-datasource-properties' is not found among the supported properties
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-6789?page=com.atlassian.jira.plugin.... ]
Stefano Maestri resolved WFLY-6789.
-----------------------------------
Resolution: Done
You are doing it wrong. You can't set properties like this, but exactly as before you have to add xads, and then use /xa-datasource-properties subresource add command. Since the first command return a reload-required you just need to use the batch mode feature of CLI
https://developer.jboss.org/wiki/CLIBatchMode
Your example become:
[standalone@localhost:9990 /] batch
[standalone@localhost:9990 / #] /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true)
[standalone@localhost:9990 / #] /subsystem=datasources/xa-data-source=MariaDBXADS/xa-datasource-properties=test:add(value=test-value)
[standalone@localhost:9990 / #] run-batch
The batch executed successfully
> 'xa-datasource-properties' is not found among the supported properties
> ----------------------------------------------------------------------
>
> Key: WFLY-6789
> URL: https://issues.jboss.org/browse/WFLY-6789
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Final
> Reporter: Kylin Soong
> Assignee: Stefano Maestri
> Priority: Critical
>
> WildFly 10 wants a xa-datasource-properties, but xa-datasource-properties not added as a xa datasources attributes in management resource definition , eg, execute
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true, xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost])
> {code}
> will throw a exception
> {code}
> 'xa-datasource-properties' is not found among the supported properties: [allocation-retry, allocation-retry-wait-millis, allow-multiple-users, background-validation, background-validation-millis, blocking-timeout-wait-millis, capacity-decrementer-class, capacity-decrementer-properties, capacity-incrementer-class, capacity-incrementer-properties, check-valid-connection-sql, connectable, connection-listener-class, connection-listener-property, driver-name, enabled, enlistment-trace, exception-sorter-class-name, exception-sorter-properties, flush-strategy, idle-timeout-minutes, initial-pool-size, interleaving, jndi-name, max-pool-size, mcp, min-pool-size, new-connection-sql, no-recovery, no-tx-separate-pool, pad-xid, password, pool-fair, pool-prefill, pool-use-strict-min, prepared-statements-cache-size, query-timeout, reauth-plugin-class-name, reauth-plugin-properties, recovery-password, recovery-plugin-class-name, recovery-plugin-properties, recovery-security-domain, recovery-username, same-rm-override, security-domain, set-tx-query-timeout, share-prepared-statements, spy, stale-connection-checker-class-name, stale-connection-checker-properties, statistics-enabled, track-statements, tracking, transaction-isolation, url-delimiter, url-property, url-selector-strategy-class-name, use-ccm, use-fast-fail, use-java-context, use-try-lock, user-name, valid-connection-checker-class-name, valid-connection-checker-properties, validate-on-match, wrap-xa-resource, xa-datasource-class, xa-resource-timeout]
> {code}
> If execute without xa-datasource-properties which like previous version
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true)
> {code}
> the exception like
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0069: At least one xa-datasource-property is required for an xa-datasource",
> "rolled-back" => true
> }
> {code}
> To create with xa-data-source add command is a workaround
> {code}
> xa-data-source add --name=MariaDBXADS --driver-name=mariadb-xa --jndi-name=java:jboss/datasources/MariaDBXADS --user-name=jdv_user --password=jdv_pass --use-java-context=true --xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost]
> {code}
> but most users expect the tree-structure cli and xa-data-source compatible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6789) 'xa-datasource-properties' is not found among the supported properties
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-6789?page=com.atlassian.jira.plugin.... ]
Stefano Maestri reopened WFLY-6789:
-----------------------------------
> 'xa-datasource-properties' is not found among the supported properties
> ----------------------------------------------------------------------
>
> Key: WFLY-6789
> URL: https://issues.jboss.org/browse/WFLY-6789
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Final
> Reporter: Kylin Soong
> Assignee: Stefano Maestri
> Priority: Critical
>
> WildFly 10 wants a xa-datasource-properties, but xa-datasource-properties not added as a xa datasources attributes in management resource definition , eg, execute
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true, xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost])
> {code}
> will throw a exception
> {code}
> 'xa-datasource-properties' is not found among the supported properties: [allocation-retry, allocation-retry-wait-millis, allow-multiple-users, background-validation, background-validation-millis, blocking-timeout-wait-millis, capacity-decrementer-class, capacity-decrementer-properties, capacity-incrementer-class, capacity-incrementer-properties, check-valid-connection-sql, connectable, connection-listener-class, connection-listener-property, driver-name, enabled, enlistment-trace, exception-sorter-class-name, exception-sorter-properties, flush-strategy, idle-timeout-minutes, initial-pool-size, interleaving, jndi-name, max-pool-size, mcp, min-pool-size, new-connection-sql, no-recovery, no-tx-separate-pool, pad-xid, password, pool-fair, pool-prefill, pool-use-strict-min, prepared-statements-cache-size, query-timeout, reauth-plugin-class-name, reauth-plugin-properties, recovery-password, recovery-plugin-class-name, recovery-plugin-properties, recovery-security-domain, recovery-username, same-rm-override, security-domain, set-tx-query-timeout, share-prepared-statements, spy, stale-connection-checker-class-name, stale-connection-checker-properties, statistics-enabled, track-statements, tracking, transaction-isolation, url-delimiter, url-property, url-selector-strategy-class-name, use-ccm, use-fast-fail, use-java-context, use-try-lock, user-name, valid-connection-checker-class-name, valid-connection-checker-properties, validate-on-match, wrap-xa-resource, xa-datasource-class, xa-resource-timeout]
> {code}
> If execute without xa-datasource-properties which like previous version
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true)
> {code}
> the exception like
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0069: At least one xa-datasource-property is required for an xa-datasource",
> "rolled-back" => true
> }
> {code}
> To create with xa-data-source add command is a workaround
> {code}
> xa-data-source add --name=MariaDBXADS --driver-name=mariadb-xa --jndi-name=java:jboss/datasources/MariaDBXADS --user-name=jdv_user --password=jdv_pass --use-java-context=true --xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost]
> {code}
> but most users expect the tree-structure cli and xa-data-source compatible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6789) 'xa-datasource-properties' is not found among the supported properties
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-6789?page=com.atlassian.jira.plugin.... ]
Stefano Maestri resolved WFLY-6789.
-----------------------------------
Resolution: Rejected
> 'xa-datasource-properties' is not found among the supported properties
> ----------------------------------------------------------------------
>
> Key: WFLY-6789
> URL: https://issues.jboss.org/browse/WFLY-6789
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Final
> Reporter: Kylin Soong
> Assignee: Stefano Maestri
> Priority: Critical
>
> WildFly 10 wants a xa-datasource-properties, but xa-datasource-properties not added as a xa datasources attributes in management resource definition , eg, execute
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true, xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost])
> {code}
> will throw a exception
> {code}
> 'xa-datasource-properties' is not found among the supported properties: [allocation-retry, allocation-retry-wait-millis, allow-multiple-users, background-validation, background-validation-millis, blocking-timeout-wait-millis, capacity-decrementer-class, capacity-decrementer-properties, capacity-incrementer-class, capacity-incrementer-properties, check-valid-connection-sql, connectable, connection-listener-class, connection-listener-property, driver-name, enabled, enlistment-trace, exception-sorter-class-name, exception-sorter-properties, flush-strategy, idle-timeout-minutes, initial-pool-size, interleaving, jndi-name, max-pool-size, mcp, min-pool-size, new-connection-sql, no-recovery, no-tx-separate-pool, pad-xid, password, pool-fair, pool-prefill, pool-use-strict-min, prepared-statements-cache-size, query-timeout, reauth-plugin-class-name, reauth-plugin-properties, recovery-password, recovery-plugin-class-name, recovery-plugin-properties, recovery-security-domain, recovery-username, same-rm-override, security-domain, set-tx-query-timeout, share-prepared-statements, spy, stale-connection-checker-class-name, stale-connection-checker-properties, statistics-enabled, track-statements, tracking, transaction-isolation, url-delimiter, url-property, url-selector-strategy-class-name, use-ccm, use-fast-fail, use-java-context, use-try-lock, user-name, valid-connection-checker-class-name, valid-connection-checker-properties, validate-on-match, wrap-xa-resource, xa-datasource-class, xa-resource-timeout]
> {code}
> If execute without xa-datasource-properties which like previous version
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true)
> {code}
> the exception like
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0069: At least one xa-datasource-property is required for an xa-datasource",
> "rolled-back" => true
> }
> {code}
> To create with xa-data-source add command is a workaround
> {code}
> xa-data-source add --name=MariaDBXADS --driver-name=mariadb-xa --jndi-name=java:jboss/datasources/MariaDBXADS --user-name=jdv_user --password=jdv_pass --use-java-context=true --xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost]
> {code}
> but most users expect the tree-structure cli and xa-data-source compatible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6790) Typo in datasource and resource adapters subsystem configuration
by Martin Stefanko (JIRA)
Martin Stefanko created WFLY-6790:
-------------------------------------
Summary: Typo in datasource and resource adapters subsystem configuration
Key: WFLY-6790
URL: https://issues.jboss.org/browse/WFLY-6790
Project: WildFly
Issue Type: Bug
Components: CLI, Web Console
Affects Versions: 10.0.0.Final
Reporter: Martin Stefanko
Assignee: Martin Stefanko
Priority: Trivial
In XA and non-XA datasource configuration screen of datasource subsystem configuration view, in attributes tab, the Need help? window reads out
{quote}Statistics enabled?: define if runtime statistics is enabled or not.{quote}
Other field descriptions are capitalised, so maybe this one should be too. I would also reformulate it to something along the lines of "Define whether the runtime statistics are enabled or not.".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6402) EJBs accessible too early (spec violation)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-6402?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-6402:
-----------------------------------------------
Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1310908|https://bugzilla.redhat.com/show_bug.cgi?id=1310908] from ON_QA to VERIFIED
> EJBs accessible too early (spec violation)
> ------------------------------------------
>
> Key: WFLY-6402
> URL: https://issues.jboss.org/browse/WFLY-6402
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Fedor Gavrilov
> Labels: downstream_dependency
> Attachments: auto-test-reproducer.zip
>
>
> {code}
> EJB 3.1 spec, section 4.8.1:
> "If the Startup annotation appears on the Singleton bean class or if the Singleton has been designated via the deployment descriptor as requiring eager initialization, the container must initialize the Singleton bean instance during the application startup sequence. The container must initialize all such startup-time Singletons before any external client requests (that is, client requests originating outside of the application) are delivered to any enterprise bean components in the application.
> {code}
> Wildlfy does not implement this correctly, and allows calls to other EJBs before a @Startup @Singleton finishes its @PostConstruct call.
> This Jira ticket handles two PR's on WFLY:
> https://github.com/wildfly/wildfly/pull/8824 (that is already merged)
> and https://github.com/wildfly/wildfly/pull/8989
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6789) 'xa-datasource-properties' is not found among the supported properties
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-6789?page=com.atlassian.jira.plugin.... ]
Stefano Maestri reassigned WFLY-6789:
-------------------------------------
Assignee: Stefano Maestri (was: Jesper Pedersen)
> 'xa-datasource-properties' is not found among the supported properties
> ----------------------------------------------------------------------
>
> Key: WFLY-6789
> URL: https://issues.jboss.org/browse/WFLY-6789
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Final
> Reporter: Kylin Soong
> Assignee: Stefano Maestri
> Priority: Critical
>
> WildFly 10 wants a xa-datasource-properties, but xa-datasource-properties not added as a xa datasources attributes in management resource definition , eg, execute
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true, xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost])
> {code}
> will throw a exception
> {code}
> 'xa-datasource-properties' is not found among the supported properties: [allocation-retry, allocation-retry-wait-millis, allow-multiple-users, background-validation, background-validation-millis, blocking-timeout-wait-millis, capacity-decrementer-class, capacity-decrementer-properties, capacity-incrementer-class, capacity-incrementer-properties, check-valid-connection-sql, connectable, connection-listener-class, connection-listener-property, driver-name, enabled, enlistment-trace, exception-sorter-class-name, exception-sorter-properties, flush-strategy, idle-timeout-minutes, initial-pool-size, interleaving, jndi-name, max-pool-size, mcp, min-pool-size, new-connection-sql, no-recovery, no-tx-separate-pool, pad-xid, password, pool-fair, pool-prefill, pool-use-strict-min, prepared-statements-cache-size, query-timeout, reauth-plugin-class-name, reauth-plugin-properties, recovery-password, recovery-plugin-class-name, recovery-plugin-properties, recovery-security-domain, recovery-username, same-rm-override, security-domain, set-tx-query-timeout, share-prepared-statements, spy, stale-connection-checker-class-name, stale-connection-checker-properties, statistics-enabled, track-statements, tracking, transaction-isolation, url-delimiter, url-property, url-selector-strategy-class-name, use-ccm, use-fast-fail, use-java-context, use-try-lock, user-name, valid-connection-checker-class-name, valid-connection-checker-properties, validate-on-match, wrap-xa-resource, xa-datasource-class, xa-resource-timeout]
> {code}
> If execute without xa-datasource-properties which like previous version
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true)
> {code}
> the exception like
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0069: At least one xa-datasource-property is required for an xa-datasource",
> "rolled-back" => true
> }
> {code}
> To create with xa-data-source add command is a workaround
> {code}
> xa-data-source add --name=MariaDBXADS --driver-name=mariadb-xa --jndi-name=java:jboss/datasources/MariaDBXADS --user-name=jdv_user --password=jdv_pass --use-java-context=true --xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost]
> {code}
> but most users expect the tree-structure cli and xa-data-source compatible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6773) Provide ability to start/stop Data Source creation without restart of server
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/WFLY-6773?page=com.atlassian.jira.plugin.... ]
Kylin Soong commented on WFLY-6773:
-----------------------------------
Another inconvenience caused by restart of server to make sure data source be removed.added, execute the following cli
{code}
xa-data-source remove --name=MariaDBXADS // output hints reload is necessary
:reload() // the MariaDBXADS should be remove after reload, check standalone.xml, MariaDBXADS be removed
/subsystem=datasources/jdbc-driver=mariadb-xa:remove() // due to MariaDBXADS removed ,so remove driver, this should be success, but it execute failed
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
Service jboss.jdbc-driver.mariadb-xa was depended upon by service org.wildfly.data-source.MariaDBXADS, service jboss.driver-demander.java:jboss/datasources/MariaDBXADS",
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}
{code}
> Provide ability to start/stop Data Source creation without restart of server
> ----------------------------------------------------------------------------
>
> Key: WFLY-6773
> URL: https://issues.jboss.org/browse/WFLY-6773
> Project: WildFly
> Issue Type: Enhancement
> Components: JCA
> Affects Versions: 10.0.0.Final
> Reporter: Ramesh Reddy
> Assignee: Stefano Maestri
>
> Currently in WF 10, where a data source is created / removed using the CLI the "reload-status" is set to "requires restart", based how the resource is expected to be managed in WF.
> h3. Why We need it?
> In Teiid, it is common practice to add/remove data sources dynamically and restarting server will affect performance and usability severely.
> * Because delete/re-add is in Teiid's workflow to manage a data sources and when we have to restart we loose the whole state of the virtual database. That means we need re-establish runtime status. For example, all the existing sessions will be killed.
> * Runtime environment are often shared, that could kill other person's tasks in flight leaving them hanging with errors.
> * Every time data source starts we fetch metadata from the source, this is very expensive operation.
> * With multi-source feature, it is a feature that user dynamically brings in/out sources as they show up on their dashboard, it would be not possible to support this feature.
> * This is a change of behavior from earlier versions of the EAP, our users and customers rely on this feature
> As per Teiid project is concerned, we consider this is regression on WF and thus a bug.
> h3. Proposed Solution
> [~brian.stansberry] suggested the WF management practices here in this document https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-Apply...
> Based on this the conclusion is that Data Sources, is developed under "all-services" paradigm, not under "resource-services" paradigm, where a explicit header from client to whether to restart or not can avoid having to "reload" the server when a new DS is added or removed. We understand the nature of service dependencies in WF, and how this can affect the other dependent services, but we verified that Teiid will not have those side effects as we designed. Since these sources are effectively exclusively defined for Teiid should not interfere with others. Also, since the request is explicit, should not affect current behavior.
> h3. Workarounds Considered
> Since this highly dependent on configuration based data source creation, we can opt to a deployment based data source creation (-ds.xml), however GSS is quick to dismiss this as this not supported feature.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months