[JBoss JIRA] (WFLY-7759) Mixed domain with EAP 6 slaves: data sources operations broken
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-7759?page=com.atlassian.jira.plugin.... ]
Lin Gao commented on WFLY-7759:
-------------------------------
Moved to WFLY, the checking should be done in +connector+ subsystem.
> Mixed domain with EAP 6 slaves: data sources operations broken
> --------------------------------------------------------------
>
> Key: WFLY-7759
> URL: https://issues.jboss.org/browse/WFLY-7759
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JCA
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Blocker
>
> Run a mixed domain where EAP 7.1.0.DR9 is the master and EAP 6.4.0/6.3.0/6.2.0 is a slave server. Operations on data sources are broken due to incompatibility of models:
> {noformat}
> [domain@127.0.0.100:9990 /] /host=eap640/server=server-one/subsystem=datasources/data-source=ExampleDS:test-connection-in-pool
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0297: Transforming operation {
> \"address\" => [
> (\"host\" => \"eap640\"),
> (\"server\" => \"server-one\"),
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\")
> ],
> \"operation\" => \"test-connection-in-pool\",
> \"operation-headers\" => {
> \"caller-type\" => \"user\",
> \"access-mechanism\" => \"NATIVE\",
> \"domain-uuid\" => \"ae186a65-8c76-41d0-bd23-79154b5f92f7\"
> }
> } at resource [
> (\"host\" => \"eap640\"),
> (\"server\" => \"server-one\"),
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\")
> ] to subsystem 'datasources' model version '1.3.0' -- attributes [connection-url] WFLYCTL0336: The following attributes are nillable in the current model but must be defined in the target model version: [connection-url]",
> "rolled-back" => true,
> "result" => [true]
> }
> {noformat}
> The fix for JBEAP-5770 seems to be the cause.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-7759) Mixed domain with EAP 6 slaves: data sources operations broken
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-7759?page=com.atlassian.jira.plugin.... ]
Lin Gao moved WFCORE-2091 to WFLY-7759:
---------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-7759 (was: WFCORE-2091)
Component/s: Domain Management
JCA
(was: Domain Management)
> Mixed domain with EAP 6 slaves: data sources operations broken
> --------------------------------------------------------------
>
> Key: WFLY-7759
> URL: https://issues.jboss.org/browse/WFLY-7759
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JCA
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Blocker
>
> Run a mixed domain where EAP 7.1.0.DR9 is the master and EAP 6.4.0/6.3.0/6.2.0 is a slave server. Operations on data sources are broken due to incompatibility of models:
> {noformat}
> [domain@127.0.0.100:9990 /] /host=eap640/server=server-one/subsystem=datasources/data-source=ExampleDS:test-connection-in-pool
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0297: Transforming operation {
> \"address\" => [
> (\"host\" => \"eap640\"),
> (\"server\" => \"server-one\"),
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\")
> ],
> \"operation\" => \"test-connection-in-pool\",
> \"operation-headers\" => {
> \"caller-type\" => \"user\",
> \"access-mechanism\" => \"NATIVE\",
> \"domain-uuid\" => \"ae186a65-8c76-41d0-bd23-79154b5f92f7\"
> }
> } at resource [
> (\"host\" => \"eap640\"),
> (\"server\" => \"server-one\"),
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\")
> ] to subsystem 'datasources' model version '1.3.0' -- attributes [connection-url] WFLYCTL0336: The following attributes are nillable in the current model but must be defined in the target model version: [connection-url]",
> "rolled-back" => true,
> "result" => [true]
> }
> {noformat}
> The fix for JBEAP-5770 seems to be the cause.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFCORE-2091) Mixed domain with EAP 6 slaves: data sources operations broken
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2091?page=com.atlassian.jira.plugi... ]
Lin Gao commented on WFCORE-2091:
---------------------------------
The problem in this case is that there is a +RejectAttributeChecker+ registered for attribute: +connection-url+ under resource: +/subsystem=datasources/data-source=ExampleDS+, when
{code:java}
/host=eap640/server=server-one/subsystem=datasources/data-source=ExampleDS:test-connection-in-pool
{code}
is called, this +test-connection-in-pool+ operation is to be transformed, which delegates to [AttributeTransformationRule.doTransform()|https://github.com/wildfly/wild...] method. This method checks whether the +connection-url+ attribute should be rejected or not. Apparently, this operation does not have a parameter named +connection-url+, so it is wrong to be rejected here.
> Mixed domain with EAP 6 slaves: data sources operations broken
> --------------------------------------------------------------
>
> Key: WFCORE-2091
> URL: https://issues.jboss.org/browse/WFCORE-2091
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Blocker
>
> Run a mixed domain where EAP 7.1.0.DR9 is the master and EAP 6.4.0/6.3.0/6.2.0 is a slave server. Operations on data sources are broken due to incompatibility of models:
> {noformat}
> [domain@127.0.0.100:9990 /] /host=eap640/server=server-one/subsystem=datasources/data-source=ExampleDS:test-connection-in-pool
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0297: Transforming operation {
> \"address\" => [
> (\"host\" => \"eap640\"),
> (\"server\" => \"server-one\"),
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\")
> ],
> \"operation\" => \"test-connection-in-pool\",
> \"operation-headers\" => {
> \"caller-type\" => \"user\",
> \"access-mechanism\" => \"NATIVE\",
> \"domain-uuid\" => \"ae186a65-8c76-41d0-bd23-79154b5f92f7\"
> }
> } at resource [
> (\"host\" => \"eap640\"),
> (\"server\" => \"server-one\"),
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\")
> ] to subsystem 'datasources' model version '1.3.0' -- attributes [connection-url] WFLYCTL0336: The following attributes are nillable in the current model but must be defined in the target model version: [connection-url]",
> "rolled-back" => true,
> "result" => [true]
> }
> {noformat}
> The fix for JBEAP-5770 seems to be the cause.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-7214) Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-7214?page=com.atlassian.jira.plugin.... ]
Lin Gao updated WFLY-7214:
--------------------------
Description:
When a data-source was failed to be added because of missing connection-properties:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
{code}
, it can be added by correcting the information, like:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
{"outcome" => "success"}
{code}
But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
{
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
"rolled-back" => true
}
{code}
{panel:title=NOTE FOR THE VERIFY}
Changing the Step 1 to:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
{code}
for the verifying, because of with fixing of https://issues.jboss.org/browse/JBJCA-1331, the original step 1 will not cause problems any more.
{panel}
was:
When a data-source was failed to be added because of missing connection-properties:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
{code}
, it can be added by correcting the information, like:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
{"outcome" => "success"}
{code}
But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
{
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
"rolled-back" => true
}
{code}
{panel:title=NOTE FOR THE VERIFY}
Changing the Step 1 to:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
{code}
for the verifying
{panel}
> Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7214
> URL: https://issues.jboss.org/browse/WFLY-7214
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Lin Gao
> Assignee: Lin Gao
>
> When a data-source was failed to be added because of missing connection-properties:
> {code:}
> /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
> {code}
> , it can be added by correcting the information, like:
> {code:}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
> {"outcome" => "success"}
> {code}
> But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
> {code:}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
> "rolled-back" => true
> }
> {code}
> {panel:title=NOTE FOR THE VERIFY}
> Changing the Step 1 to:
> {code:}
> /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
> {code}
> for the verifying, because of with fixing of https://issues.jboss.org/browse/JBJCA-1331, the original step 1 will not cause problems any more.
> {panel}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-7214) Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-7214?page=com.atlassian.jira.plugin.... ]
Lin Gao updated WFLY-7214:
--------------------------
Description:
When a data-source was failed to be added because of missing connection-properties:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
{code}
, it can be added by correcting the information, like:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
{"outcome" => "success"}
{code}
But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
{
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
"rolled-back" => true
}
{code}
{panel:title=NOTE FOR THE VERIFY}
Changing the Step 1 to:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
{code}
for the verifying, because of with fixing of https://issues.jboss.org/browse/JBJCA-1331 (also fixed in ironjacamar-1.3.5.Final), the original step 1 will not cause problems any more.
{panel}
was:
When a data-source was failed to be added because of missing connection-properties:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
{code}
, it can be added by correcting the information, like:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
{"outcome" => "success"}
{code}
But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
{
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
"rolled-back" => true
}
{code}
{panel:title=NOTE FOR THE VERIFY}
Changing the Step 1 to:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
{code}
for the verifying, because of with fixing of https://issues.jboss.org/browse/JBJCA-1331, the original step 1 will not cause problems any more.
{panel}
> Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7214
> URL: https://issues.jboss.org/browse/WFLY-7214
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Lin Gao
> Assignee: Lin Gao
>
> When a data-source was failed to be added because of missing connection-properties:
> {code:}
> /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
> {code}
> , it can be added by correcting the information, like:
> {code:}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
> {"outcome" => "success"}
> {code}
> But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
> {code:}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
> "rolled-back" => true
> }
> {code}
> {panel:title=NOTE FOR THE VERIFY}
> Changing the Step 1 to:
> {code:}
> /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
> {code}
> for the verifying, because of with fixing of https://issues.jboss.org/browse/JBJCA-1331 (also fixed in ironjacamar-1.3.5.Final), the original step 1 will not cause problems any more.
> {panel}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-7214) Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-7214?page=com.atlassian.jira.plugin.... ]
Lin Gao updated WFLY-7214:
--------------------------
Description:
When a data-source was failed to be added because of missing connection-properties:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
{code}
, it can be added by correcting the information, like:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
{"outcome" => "success"}
{code}
But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
{
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
"rolled-back" => true
}
{code}
{panel:title=NOTE FOR THE VERIFY}
Changing the Step 1 to:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
{code}
for the verifying
{panel}
was:
When a data-source was failed to be added either because of missing connection-properties:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
{code}
, it can be added by correcting the information, like:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
{"outcome" => "success"}
{code}
But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
{
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
"rolled-back" => true
}
{code}
> Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7214
> URL: https://issues.jboss.org/browse/WFLY-7214
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Lin Gao
> Assignee: Lin Gao
>
> When a data-source was failed to be added because of missing connection-properties:
> {code:}
> /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
> {code}
> , it can be added by correcting the information, like:
> {code:}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
> {"outcome" => "success"}
> {code}
> But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
> {code:}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
> "rolled-back" => true
> }
> {code}
> {panel:title=NOTE FOR THE VERIFY}
> Changing the Step 1 to:
> {code:}
> /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
> {code}
> for the verifying
> {panel}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-7214) Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-7214?page=com.atlassian.jira.plugin.... ]
Lin Gao updated WFLY-7214:
--------------------------
Description:
When a data-source was failed to be added either because of missing connection-properties:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
{code}
, it can be added by correcting the information, like:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
{"outcome" => "success"}
{code}
But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
{
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
"rolled-back" => true
}
{code}
was:
When a data-source was failed to be added either because of missing connection-properties:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
{code}
or missing of connection-url:
{code:}
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2)
{code}
, it can be added by correcting the information, like:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
{"outcome" => "success"}
{code}
But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source.
> Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7214
> URL: https://issues.jboss.org/browse/WFLY-7214
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Lin Gao
> Assignee: Lin Gao
>
> When a data-source was failed to be added either because of missing connection-properties:
> {code:}
> /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
> {code}
> , it can be added by correcting the information, like:
> {code:}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
> {"outcome" => "success"}
> {code}
> But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source:
> {code:}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months