[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)
8 years, 3 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)
8 years, 3 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)
8 years, 3 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)
8 years, 3 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:
--------------------------------
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)
8 years, 3 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 moved WFLY-7237 to JBJCA-1334:
--------------------------------------
Project: IronJacamar (was: WildFly)
Key: JBJCA-1334 (was: WFLY-7237)
Workflow: classic default workflow (was: GIT Pull Request workflow )
Component/s: Deployer
(was: JCA)
> 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)
8 years, 3 months
[JBoss JIRA] (WFLY-7237) Add DataSource to ManagementRepository only after deployed successfully
by Lin Gao (JIRA)
Lin Gao created WFLY-7237:
-----------------------------
Summary: Add DataSource to ManagementRepository only after deployed successfully
Key: WFLY-7237
URL: https://issues.jboss.org/browse/WFLY-7237
Project: WildFly
Issue Type: Bug
Components: JCA
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)
8 years, 3 months
[JBoss JIRA] (WFLY-7236) DatasourceNonCcmTestCase fails with security manager
by Jan Tymel (JIRA)
Jan Tymel created WFLY-7236:
-------------------------------
Summary: DatasourceNonCcmTestCase fails with security manager
Key: WFLY-7236
URL: https://issues.jboss.org/browse/WFLY-7236
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Jan Tymel
Assignee: Jan Tymel
*org.jboss.as.test.integration.jca.datasource.DatasourceNonCcmTestCase#testJTADS*
*org.jboss.as.test.integration.jca.datasource.DatasourceNonCcmTestCase#testNonJTADS*
{{./integration-tests.sh -DtestLogToFile=false -Dts.noSmoke -Dts.basic -Dtest=org.jboss.as.test.integration.jca.datasource.DatasourceNonCcmTestCase -Dsecurity.manager}}
{code}
Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("org.jboss.remoting3.security.RemotingPermission" "createEndpoint")" in code source "(vfs:/content/dummy.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.dummy.jar:main" from Service Module Loader")
at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278)
at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:85)
at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:112)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:120)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:64)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:139)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:114)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
... 146 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-7235) InfinispanResourceRefTestCase fails with security manager
by Jan Tymel (JIRA)
Jan Tymel created WFLY-7235:
-------------------------------
Summary: InfinispanResourceRefTestCase fails with security manager
Key: WFLY-7235
URL: https://issues.jboss.org/browse/WFLY-7235
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Jan Tymel
Assignee: Jan Tymel
*org.jboss.as.test.integration.ee.injection.resource.infinispan.InfinispanResourceRefTestCase#test*
{{./integration-tests.sh -DtestLogToFile=false -Dts.noSmoke -Dts.basic -Dtest=org.jboss.as.test.integration.ee.injection.resource.infinispan.InfinispanResourceRefTestCase -Dsecurity.manager}}
{code}
Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "getClassLoader")" in code source "(vfs:/content/infinispan-resource-ref.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.infinispan-resource-ref.war:main" from Service Module Loader")
at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278)
at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
at java.lang.ClassLoader.checkClassLoaderPermission(ClassLoader.java:1528)
at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1442)
at org.infinispan.commons.util.Util.getClassLoaders(Util.java:127)
at org.infinispan.commons.util.Util.loadClassStrict(Util.java:163)
at org.infinispan.commons.util.ReflectionUtil.getClassForName(ReflectionUtil.java:319)
at org.infinispan.commons.util.ReflectionUtil.toClassArray(ReflectionUtil.java:313)
at org.infinispan.factories.AbstractComponentRegistry$Component.buildInjectionMethodsList(AbstractComponentRegistry.java:810)
at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:213)
at org.infinispan.factories.ComponentRegistry.registerComponentInternal(ComponentRegistry.java:193)
at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:171)
at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:163)
at org.infinispan.factories.ComponentRegistry.<init>(ComponentRegistry.java:79)
... 210 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-7226) Missing realm-map attribute for mapped-regex-realm-mapper throws IllegalArgumentException to server log
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7226?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas commented on WFLY-7226:
------------------------------------
Hi [~ivassile],
realm-map for mapped-regex-realm-mapper is an Object attribute. It can be set in CLI command like this:
{code}
/subsystem=elytron/mapped-regex-realm-mapper=someName:add(pattern="(.?)",realm-map={a=b,c=d})
{code}
However the point of this issue is to provide users some understandable log for cases when realm-map attribute is missing (see CLI command in Steps to Reproduce). Currently it only throws mentioned above exception.
Try to use following command:
{code}
/subsystem=elytron/mapped-regex-realm-mapper=someName:add(realm-map={a=b,c=d})
{code}
it will result to exception with clear failure-description that pattern may not be null:
{code}
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0155: pattern may not be null",
"rolled-back" => true
}
{code}
The same should happen for missing required realm-map attribute.
> Missing realm-map attribute for mapped-regex-realm-mapper throws IllegalArgumentException to server log
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7226
> URL: https://issues.jboss.org/browse/WFLY-7226
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
>
> In case when mapped-regex-realm-mapper is added through CLI and realm-map attribute is not used then IllegalArgumentException is thrown to server log instead of some CLI failure message like "realm-map may not be null".
> Expcetion in server log:
> {code}
> ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("mapped-regex-realm-mapper" => "MappedRealmMapper")
> ]): java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:139)
> at org.jboss.dmr.ModelNode.keys(ModelNode.java:1378)
> at org.wildfly.extension.elytron.RealmMapperDefinitions$MappedRegexRealmMapperAddHandler.performRuntime(RealmMapperDefinitions.java:221)
> at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:337)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months