[JBoss JIRA] (WFCORE-1628) Create module using 'module add' CLI command with absolute-path in resource-root element
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1628?page=com.atlassian.jira.plugi... ]
Martin Simka updated WFCORE-1628:
---------------------------------
Description:
MODULES-218, included in WildFly 10/WildFly Core 2.0.10, allows absolute paths to be used for resource-roots in module.xml. But there is no way to create module with absolute paths in resource-roots using CLI command {{module add}}.
{quote}
resource-root's path previously only allowed resources within the module's directory, e.g.:
<resource-root path="wildfly-controller-2.2.0.CR2.jar"/>
With MODULES-218 it allows resources to exist anywhere on the filesystem, in the form of an absolute path, e.g.:
<resource-root path="/Users/whoever/mymodules/wildfly-controller-2.2.0.CR2.jar"/>
{quote}
was:
MODULES-218, included in EAP 7.0.0.GA, allows absolute paths to be used for resource-roots in module.xml. But there is no way to create module with absolute paths in resource-roots using CLI command {{module add}}.
{quote}
resource-root's path previously only allowed resources within the module's directory, e.g.:
<resource-root path="wildfly-controller-2.2.0.CR2.jar"/>
With MODULES-218 it allows resources to exist anywhere on the filesystem, in the form of an absolute path, e.g.:
<resource-root path="/Users/whoever/mymodules/wildfly-controller-2.2.0.CR2.jar"/>
{quote}
> Create module using 'module add' CLI command with absolute-path in resource-root element
> ----------------------------------------------------------------------------------------
>
> Key: WFCORE-1628
> URL: https://issues.jboss.org/browse/WFCORE-1628
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Reporter: Martin Simka
> Assignee: Alexey Loubyansky
>
> MODULES-218, included in WildFly 10/WildFly Core 2.0.10, allows absolute paths to be used for resource-roots in module.xml. But there is no way to create module with absolute paths in resource-roots using CLI command {{module add}}.
> {quote}
> resource-root's path previously only allowed resources within the module's directory, e.g.:
> <resource-root path="wildfly-controller-2.2.0.CR2.jar"/>
> With MODULES-218 it allows resources to exist anywhere on the filesystem, in the form of an absolute path, e.g.:
> <resource-root path="/Users/whoever/mymodules/wildfly-controller-2.2.0.CR2.jar"/>
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1628) Create module using 'module add' CLI command with absolute-path in resource-root element
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1628?page=com.atlassian.jira.plugi... ]
Martin Simka moved JBEAP-5145 to WFCORE-1628:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1628 (was: JBEAP-5145)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
Target Release: (was: 7.backlog.GA)
> Create module using 'module add' CLI command with absolute-path in resource-root element
> ----------------------------------------------------------------------------------------
>
> Key: WFCORE-1628
> URL: https://issues.jboss.org/browse/WFCORE-1628
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Reporter: Martin Simka
> Assignee: Alexey Loubyansky
>
> MODULES-218, included in EAP 7.0.0.GA, allows absolute paths to be used for resource-roots in module.xml. But there is no way to create module with absolute paths in resource-roots using CLI command {{module add}}.
> {quote}
> resource-root's path previously only allowed resources within the module's directory, e.g.:
> <resource-root path="wildfly-controller-2.2.0.CR2.jar"/>
> With MODULES-218 it allows resources to exist anywhere on the filesystem, in the form of an absolute path, e.g.:
> <resource-root path="/Users/whoever/mymodules/wildfly-controller-2.2.0.CR2.jar"/>
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-6780) could not spécify version 3 for ldap connection
by cyril leclerc (JIRA)
[ https://issues.jboss.org/browse/WFLY-6780?page=com.atlassian.jira.plugin.... ]
cyril leclerc edited comment on WFLY-6780 at 6/29/16 6:19 AM:
--------------------------------------------------------------
HI,
in fact to be more clear, the problem is this exception :
"LDAP: error code 4 - Sizelimit Exceeded"
because MaxPageSize is setted in AD to 500 and sometimes we have more than 1000 groups, furthermore in the org.jboss.security there is i think 2 ways to configure it (tested the first not second) :
in LdapExtModule.java (i recreate it and override it) : i add thos lines :
first the variable :
private static final String MAX_PAGE_SIZE = "maxPageSize";
then the code :
/**
* if there is more than 1000 groups in AD
*/
protected int maxPageSize = 500;
String maxPSize = (String) options.get(MAX_PAGE_SIZE);
if (maxPSize != null)
{
try
{
maxPageSize = Integer.parseInt(maxPSize);
}
catch (NumberFormatException e)
{
PicketBoxLogger.LOGGER.debugFailureToParseNumberProperty(MAX_PAGE_SIZE, this.maxPageSize);
}
}
//set a maxPagesize
ctx.setRequestControls(new Control[]{
new PagedResultsControl(maxPageSize, Control.CRITICAL) });
and in logging module you can add this configuration :
<module-option name="maxPageSize" value="1000"/>
i think it should be available directly in JBOSS classes
Second solution, in same class :
// Query for roles matching the role filter
SearchControls constraints = new SearchControls();
constraints.setSearchScope(searchScope);
constraints.setTimeLimit(searchTimeLimit);
add this line (but i am not sure if it is working)
constraints.setCountLimit(3500);
i make a workaround with the first solution but a had to redeclare SecuritYActions.java and Decode.java because protected classes
regards
was (Author: fdlprod):
HI,
in fact to be more clear, the problem is this exception :
"LDAP: error code 4 - Sizelimit Exceeded"
because MaxPageSize is setted in AD to 500 and sometimes we have more than 1000 groups, furthermore in the org.jboss.security there is i think 2 ways to configure it (tested the first not second) :
private static final String MAX_PAGE_SIZE = "maxPageSize";
in LdapExtModule.java (i recreate it and override it) : i add thos lines :
String maxPSize = (String) options.get(MAX_PAGE_SIZE);
if (maxPSize != null)
{
try
{
maxPageSize = Integer.parseInt(maxPSize);
}
catch (NumberFormatException e)
{
PicketBoxLogger.LOGGER.debugFailureToParseNumberProperty(MAX_PAGE_SIZE, this.maxPageSize);
}
}
//set a maxPagesize
ctx.setRequestControls(new Control[]{
new PagedResultsControl(maxPageSize, Control.CRITICAL) });
and in logging module you can add this configuration :
<module-option name="maxPageSize" value="1000"/>
i think it should be available directly in JBOSS classes
Second solution, in same class :
// Query for roles matching the role filter
SearchControls constraints = new SearchControls();
constraints.setSearchScope(searchScope);
constraints.setTimeLimit(searchTimeLimit);
add this line (but i am not sure if it is working)
constraints.setCountLimit(3500);
i make a workaround with the first solution but a had to redeclare SecuritYActions.java and Decode.java because protected classes
regards
> could not spécify version 3 for ldap connection
> -----------------------------------------------
>
> Key: WFLY-6780
> URL: https://issues.jboss.org/browse/WFLY-6780
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Reporter: cyril leclerc
> Assignee: Darran Lofthouse
>
> HI,
> in case of using LDAPExtLoginModule and ldap realm if in active directory there is more than 1000 groups it returns an error :
> Caused by: javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'CN=Users,DC=realad,DC=ad'
> i can't change in AD the MAXPAGESIZE parameter and i can't specify the module to use version 3 of ldap how i can do ?
> it is a big issue for me -)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-6780) could not spécify version 3 for ldap connection
by cyril leclerc (JIRA)
[ https://issues.jboss.org/browse/WFLY-6780?page=com.atlassian.jira.plugin.... ]
cyril leclerc commented on WFLY-6780:
-------------------------------------
HI,
in fact to be me clear, the problem is this exception :
"LDAP: error code 4 - Sizelimit Exceeded"
because MaxPageSize is setted in AD to 500 and sometimes we have more than 1000 groups, furthermore in the org.jboss.security there is i think 2 ways to configure it (tested the first not second) :
private static final String MAX_PAGE_SIZE = "maxPageSize";
in LdapExtModule.java (i recreate it and override it) : i add thos lines :
String maxPSize = (String) options.get(MAX_PAGE_SIZE);
if (maxPSize != null)
{
try
{
maxPageSize = Integer.parseInt(maxPSize);
}
catch (NumberFormatException e)
{
PicketBoxLogger.LOGGER.debugFailureToParseNumberProperty(MAX_PAGE_SIZE, this.maxPageSize);
}
}
//set a maxPagesize
ctx.setRequestControls(new Control[]{
new PagedResultsControl(maxPageSize, Control.CRITICAL) });
and in logging module you can add this configuration :
<module-option name="maxPageSize" value="1000"/>
i think it should be available directly in JBOSS classes
Second solution, in same class :
// Query for roles matching the role filter
SearchControls constraints = new SearchControls();
constraints.setSearchScope(searchScope);
constraints.setTimeLimit(searchTimeLimit);
add this line (but i am not sure if it is working)
constraints.setCountLimit(3500);
i make a workaround with the first solution but a had to redeclare SecuritYActions.java and Decode.java because protected classes
regards
> could not spécify version 3 for ldap connection
> -----------------------------------------------
>
> Key: WFLY-6780
> URL: https://issues.jboss.org/browse/WFLY-6780
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Reporter: cyril leclerc
> Assignee: Darran Lofthouse
>
> HI,
> in case of using LDAPExtLoginModule and ldap realm if in active directory there is more than 1000 groups it returns an error :
> Caused by: javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'CN=Users,DC=realad,DC=ad'
> i can't change in AD the MAXPAGESIZE parameter and i can't specify the module to use version 3 of ldap how i can do ?
> it is a big issue for me -)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-6780) could not spécify version 3 for ldap connection
by cyril leclerc (JIRA)
[ https://issues.jboss.org/browse/WFLY-6780?page=com.atlassian.jira.plugin.... ]
cyril leclerc edited comment on WFLY-6780 at 6/29/16 6:18 AM:
--------------------------------------------------------------
HI,
in fact to be more clear, the problem is this exception :
"LDAP: error code 4 - Sizelimit Exceeded"
because MaxPageSize is setted in AD to 500 and sometimes we have more than 1000 groups, furthermore in the org.jboss.security there is i think 2 ways to configure it (tested the first not second) :
private static final String MAX_PAGE_SIZE = "maxPageSize";
in LdapExtModule.java (i recreate it and override it) : i add thos lines :
String maxPSize = (String) options.get(MAX_PAGE_SIZE);
if (maxPSize != null)
{
try
{
maxPageSize = Integer.parseInt(maxPSize);
}
catch (NumberFormatException e)
{
PicketBoxLogger.LOGGER.debugFailureToParseNumberProperty(MAX_PAGE_SIZE, this.maxPageSize);
}
}
//set a maxPagesize
ctx.setRequestControls(new Control[]{
new PagedResultsControl(maxPageSize, Control.CRITICAL) });
and in logging module you can add this configuration :
<module-option name="maxPageSize" value="1000"/>
i think it should be available directly in JBOSS classes
Second solution, in same class :
// Query for roles matching the role filter
SearchControls constraints = new SearchControls();
constraints.setSearchScope(searchScope);
constraints.setTimeLimit(searchTimeLimit);
add this line (but i am not sure if it is working)
constraints.setCountLimit(3500);
i make a workaround with the first solution but a had to redeclare SecuritYActions.java and Decode.java because protected classes
regards
was (Author: fdlprod):
HI,
in fact to be me clear, the problem is this exception :
"LDAP: error code 4 - Sizelimit Exceeded"
because MaxPageSize is setted in AD to 500 and sometimes we have more than 1000 groups, furthermore in the org.jboss.security there is i think 2 ways to configure it (tested the first not second) :
private static final String MAX_PAGE_SIZE = "maxPageSize";
in LdapExtModule.java (i recreate it and override it) : i add thos lines :
String maxPSize = (String) options.get(MAX_PAGE_SIZE);
if (maxPSize != null)
{
try
{
maxPageSize = Integer.parseInt(maxPSize);
}
catch (NumberFormatException e)
{
PicketBoxLogger.LOGGER.debugFailureToParseNumberProperty(MAX_PAGE_SIZE, this.maxPageSize);
}
}
//set a maxPagesize
ctx.setRequestControls(new Control[]{
new PagedResultsControl(maxPageSize, Control.CRITICAL) });
and in logging module you can add this configuration :
<module-option name="maxPageSize" value="1000"/>
i think it should be available directly in JBOSS classes
Second solution, in same class :
// Query for roles matching the role filter
SearchControls constraints = new SearchControls();
constraints.setSearchScope(searchScope);
constraints.setTimeLimit(searchTimeLimit);
add this line (but i am not sure if it is working)
constraints.setCountLimit(3500);
i make a workaround with the first solution but a had to redeclare SecuritYActions.java and Decode.java because protected classes
regards
> could not spécify version 3 for ldap connection
> -----------------------------------------------
>
> Key: WFLY-6780
> URL: https://issues.jboss.org/browse/WFLY-6780
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Reporter: cyril leclerc
> Assignee: Darran Lofthouse
>
> HI,
> in case of using LDAPExtLoginModule and ldap realm if in active directory there is more than 1000 groups it returns an error :
> Caused by: javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'CN=Users,DC=realad,DC=ad'
> i can't change in AD the MAXPAGESIZE parameter and i can't specify the module to use version 3 of ldap how i can do ?
> it is a big issue for me -)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-351) CLI "revert to snapshot" command
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFCORE-351?page=com.atlassian.jira.plugin... ]
Ladislav Thon commented on WFCORE-351:
--------------------------------------
Agreed that this would be very nice to have. My usecase is, of course, testing: perform a bunch of management operations to bring the server to a desired state, perform a test, then roll back to the original configuration before some other test starts. Writing the required mgmt operations to rollback the server isn't a great fun :-), the ability to move back to a snapshot would make it much easier.
> CLI "revert to snapshot" command
> --------------------------------
>
> Key: WFCORE-351
> URL: https://issues.jboss.org/browse/WFCORE-351
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Environment: all
> Reporter: Rich Sharples
> Labels: eap6-ux
>
> The CLI has commands for taking snapshots, listing snapshots, deleting snapshots but no way to rollback or revert to a previous snapshot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[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)
9 years, 10 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)
9 years, 10 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)
9 years, 10 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)
9 years, 10 months