[JBoss JIRA] (JBJCA-1334) Add DataSource to ManagementRepository only after deployed successfully
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1334?page=com.atlassian.jira.plugin... ]
Lin Gao updated JBJCA-1334:
---------------------------
Fix Version/s: WildFly/IronJacamar 1.3.5.Final
1.2.8.Final
> Add DataSource to ManagementRepository only after deployed successfully
> -----------------------------------------------------------------------
>
> Key: JBJCA-1334
> URL: https://issues.jboss.org/browse/JBJCA-1334
> Project: IronJacamar
> Issue Type: Bug
> Components: Deployer
> Affects Versions: WildFly/IronJacamar 1.3.4.Final, 1.2.7.Final
> Reporter: Lin Gao
> Assignee: Lin Gao
> Fix For: WildFly/IronJacamar 1.3.5.Final, 1.2.8.Final
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBJCA-1334) Add DataSource to ManagementRepository only after deployed successfully
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1334?page=com.atlassian.jira.plugin... ]
Lin Gao resolved JBJCA-1334.
----------------------------
Resolution: Done
> Add DataSource to ManagementRepository only after deployed successfully
> -----------------------------------------------------------------------
>
> Key: JBJCA-1334
> URL: https://issues.jboss.org/browse/JBJCA-1334
> Project: IronJacamar
> Issue Type: Bug
> Components: Deployer
> Affects Versions: WildFly/IronJacamar 1.3.4.Final, 1.2.7.Final
> Reporter: Lin Gao
> Assignee: Lin Gao
> Fix For: WildFly/IronJacamar 1.3.5.Final, 1.2.8.Final
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBJCA-1334) Add DataSource to ManagementRepository only after deployed successfully
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1334?page=com.atlassian.jira.plugin... ]
Lin Gao updated JBJCA-1334:
---------------------------
Affects Version/s: 1.2.7.Final
WildFly/IronJacamar 1.3.4.Final
> Add DataSource to ManagementRepository only after deployed successfully
> -----------------------------------------------------------------------
>
> Key: JBJCA-1334
> URL: https://issues.jboss.org/browse/JBJCA-1334
> Project: IronJacamar
> Issue Type: Bug
> Components: Deployer
> Affects Versions: WildFly/IronJacamar 1.3.4.Final, 1.2.7.Final
> 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)
> {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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7178) Review empty-role-decoder resource in Elytron subsystem
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7178?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-7178:
----------------------------------
role-decoder is used in RealmRef in SecurityDomain only and it is optional here. (covered by test)
I will remove empty-role-decoder.
> Review empty-role-decoder resource in Elytron subsystem
> -------------------------------------------------------
>
> Key: WFLY-7178
> URL: https://issues.jboss.org/browse/WFLY-7178
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
>
> We have an empty-role-decoder resource but it is a bit pointless really as it contains no configuration.
> Instead I think all references to role-decoder should be optional and where there is no reference to a role decoder we automatically use the empty implementation instead.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7178) Review empty-role-decoder resource in Elytron subsystem
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7178?page=com.atlassian.jira.plugin.... ]
Jan Kalina updated WFLY-7178:
-----------------------------
Description:
We have an empty-role-decoder resource but it is a bit pointless really as it contains no configuration.
Instead I think all references to role-decoder should be optional and where there is no reference to a role decoder we automatically use the empty implementation instead.
was:See description of JBEAP-6100 for more details.
> Review empty-role-decoder resource in Elytron subsystem
> -------------------------------------------------------
>
> Key: WFLY-7178
> URL: https://issues.jboss.org/browse/WFLY-7178
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
>
> We have an empty-role-decoder resource but it is a bit pointless really as it contains no configuration.
> Instead I think all references to role-decoder should be optional and where there is no reference to a role decoder we automatically use the empty implementation instead.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBJCA-1334) Add DataSource to ManagementRepository only after deployed successfully
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1334?page=com.atlassian.jira.plugin... ]
Lin Gao commented on JBJCA-1334:
--------------------------------
PR is up: https://github.com/ironjacamar/ironjacamar/pull/581
> Add DataSource to ManagementRepository only after deployed successfully
> -----------------------------------------------------------------------
>
> Key: JBJCA-1334
> URL: https://issues.jboss.org/browse/JBJCA-1334
> Project: IronJacamar
> Issue Type: Bug
> Components: Deployer
> 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)
> {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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBJCA-1334) Add DataSource to ManagementRepository only after deployed successfully
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1334?page=com.atlassian.jira.plugin... ]
Lin Gao updated JBJCA-1334:
---------------------------
Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/581
> Add DataSource to ManagementRepository only after deployed successfully
> -----------------------------------------------------------------------
>
> Key: JBJCA-1334
> URL: https://issues.jboss.org/browse/JBJCA-1334
> Project: IronJacamar
> Issue Type: Bug
> Components: Deployer
> 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)
> {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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBJCA-1334) Add DataSource to ManagementRepository only after deployed successfully
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1334?page=com.atlassian.jira.plugin... ]
Lin Gao reassigned JBJCA-1334:
------------------------------
Assignee: Lin Gao (was: Jesper Pedersen)
> Add DataSource to ManagementRepository only after deployed successfully
> -----------------------------------------------------------------------
>
> Key: JBJCA-1334
> URL: https://issues.jboss.org/browse/JBJCA-1334
> Project: IronJacamar
> Issue Type: Bug
> Components: Deployer
> 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)
> {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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBJCA-1334) Add DataSource to ManagementRepository only after deployed successfully
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1334?page=com.atlassian.jira.plugin... ]
Lin Gao edited comment on JBJCA-1334 at 9/29/16 4:09 AM:
---------------------------------------------------------
This Jira is created by cloning the WFLY-7214.
The reason for the problem is that {{AbstractDsDeployer}} [added the DataSource into ManagementRepository|https://github.com/ironjacamar/ironjacamar/blob/1.3/...] before it knows that the DataSource deployment will succeed. Move the addition a little late will solve the problem.
{{test-connection-in-pool()}} operation in WildFly CLI tries to match the DataSource by iterating DataSouces in the ManagementRepository.
Left the failed DataSource in the ManagementRepository is an error tone, so we need to clear it in case of exceptions.
was (Author: gaol):
This Jira is created by cloning the WFLY-7214.
The reason for the problem is that {{AbstractDsDeployer}} [added the DataSource into ManagementRepository|https://github.com/ironjacamar/ironjacamar/blob/1.3/...] before it knows that the DataSource deployment will succeed. Move the addition a little late will solve the problem.
> Add DataSource to ManagementRepository only after deployed successfully
> -----------------------------------------------------------------------
>
> Key: JBJCA-1334
> URL: https://issues.jboss.org/browse/JBJCA-1334
> Project: IronJacamar
> Issue Type: Bug
> Components: Deployer
> Reporter: Lin Gao
> Assignee: Jesper Pedersen
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months