June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4801) When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4801?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4801: ----------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1232781|https://bugzilla.redhat.com/show_bug.cgi?id=1232781] from NEW to ASSIGNED > When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4801 > URL: https://issues.jboss.org/browse/WFLY-4801 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.Alpha3 > Reporter: Chao Wang > Assignee: Chao Wang > > {noformat} > Description of problem: > ======================== > - Expression is added in the datasource JNDI name attribute as below: > ----- > <datasource jndi-name="${ds}" pool-name="ExampleDS" enabled="true" use-java-context="true"> > ----- > - Value for the expression is passed to the JBoss server during the JBoss startup as below: > ----- > ./standalone.sh -Dds=java:jboss/datasources/ExampleDS > ----- > - In the server.log file below is the information regarding the datasource. > ----- > INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [${ds}] > ----- > - Test the datasource using the below command and here is the result: > ---- > [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:test-connection-in-pool() > { > "outcome" => "failed", > "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:/${ds}", > "rolled-back" => true > } > ---- > - Here is the information regarding the JNDI name attribute: > ---- > [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-resource-description(recursive=true) > { > "outcome" => "success", > "result" => { > : > "jndi-name" => { > "type" => STRING, > "description" => "Specifies the JNDI name for the datasource", > "expressions-allowed" => true, > "nillable" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > : > } > ----- > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4801) When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4801?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4801: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1232781 > When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4801 > URL: https://issues.jboss.org/browse/WFLY-4801 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.Alpha3 > Reporter: Chao Wang > Assignee: Chao Wang > > {noformat} > Description of problem: > ======================== > - Expression is added in the datasource JNDI name attribute as below: > ----- > <datasource jndi-name="${ds}" pool-name="ExampleDS" enabled="true" use-java-context="true"> > ----- > - Value for the expression is passed to the JBoss server during the JBoss startup as below: > ----- > ./standalone.sh -Dds=java:jboss/datasources/ExampleDS > ----- > - In the server.log file below is the information regarding the datasource. > ----- > INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [${ds}] > ----- > - Test the datasource using the below command and here is the result: > ---- > [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:test-connection-in-pool() > { > "outcome" => "failed", > "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:/${ds}", > "rolled-back" => true > } > ---- > - Here is the information regarding the JNDI name attribute: > ---- > [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-resource-description(recursive=true) > { > "outcome" => "success", > "result" => { > : > "jndi-name" => { > "type" => STRING, > "description" => "Specifies the JNDI name for the datasource", > "expressions-allowed" => true, > "nillable" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > : > } > ----- > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4802) Impossible to edit Mail Session attributes from web console

by Renann Prado (JIRA)

[ https://issues.jboss.org/browse/WFLY-4802?page=com.atlassian.jira.plugin.... ] Renann Prado updated WFLY-4802: ------------------------------- Steps to Reproduce: 1 - Open the web console 2 - Go to Configuration > Subsystems > Mail and add new Mail Session 3 - Select your new created Mail Session and click in "View" 4 - Click in add 5 - Fill in the form 6 - Hit save 7 - Console (in browser) error appears *Tested in chrome.* was: 1 - Open the web console 2 - Go to Configuration > Subsystems > Mail and add new Mail Session 3 - Select your new created Mail Session and click in "View" 4 - Click in add 5 - Fill in the form 6 - Hit save 7 - Console (in browser) error appears > Impossible to edit Mail Session attributes from web console > ----------------------------------------------------------- > > Key: WFLY-4802 > URL: https://issues.jboss.org/browse/WFLY-4802 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 9.0.0.CR2 > Reporter: Renann Prado > Assignee: Heiko Braun > Attachments: console-error.png > > > It is not possible to add a new Mail Session from web console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4802) Impossible to edit Mail Session attributes from web console

by Renann Prado (JIRA)

Renann Prado created WFLY-4802: ---------------------------------- Summary: Impossible to edit Mail Session attributes from web console Key: WFLY-4802 URL: https://issues.jboss.org/browse/WFLY-4802 Project: WildFly Issue Type: Bug Components: Web Console Affects Versions: 9.0.0.CR2 Reporter: Renann Prado Assignee: Heiko Braun Attachments: console-error.png It is not possible to add a new Mail Session from web console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4802) Impossible to edit Mail Session attributes from web console

by Renann Prado (JIRA)

[ https://issues.jboss.org/browse/WFLY-4802?page=com.atlassian.jira.plugin.... ] Renann Prado updated WFLY-4802: ------------------------------- Attachment: console-error.png > Impossible to edit Mail Session attributes from web console > ----------------------------------------------------------- > > Key: WFLY-4802 > URL: https://issues.jboss.org/browse/WFLY-4802 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 9.0.0.CR2 > Reporter: Renann Prado > Assignee: Heiko Braun > Attachments: console-error.png > > > It is not possible to add a new Mail Session from web console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4801) When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working

by Chao Wang (JIRA)

Chao Wang created WFLY-4801: ------------------------------- Summary: When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working Key: WFLY-4801 URL: https://issues.jboss.org/browse/WFLY-4801 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 10.0.0.Alpha3 Reporter: Chao Wang Assignee: Chao Wang {noformat} Description of problem: ======================== - Expression is added in the datasource JNDI name attribute as below: ----- <datasource jndi-name="${ds}" pool-name="ExampleDS" enabled="true" use-java-context="true"> ----- - Value for the expression is passed to the JBoss server during the JBoss startup as below: ----- ./standalone.sh -Dds=java:jboss/datasources/ExampleDS ----- - In the server.log file below is the information regarding the datasource. ----- INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [${ds}] ----- - Test the datasource using the below command and here is the result: ---- [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:test-connection-in-pool() { "outcome" => "failed", "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:/${ds}", "rolled-back" => true } ---- - Here is the information regarding the JNDI name attribute: ---- [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-resource-description(recursive=true) { "outcome" => "success", "result" => { : "jndi-name" => { "type" => STRING, "description" => "Specifies the JNDI name for the datasource", "expressions-allowed" => true, "nillable" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, : } ----- {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-467) improve "patch inspect" functionality to support patch bundles

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-467?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-467: ------------------------------------------------ baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1144022|https://bugzilla.redhat.com/show_bug.cgi?id=1144022] from NEW to CLOSED > improve "patch inspect" functionality to support patch bundles > -------------------------------------------------------------- > > Key: WFCORE-467 > URL: https://issues.jboss.org/browse/WFCORE-467 > Project: WildFly Core > Issue Type: Enhancement > Components: Patching > Reporter: Martin Simka > Assignee: Alexey Loubyansky > Fix For: 1.0.0.Beta4 > > > WFLY-2710 added new command "patch inspect" that displays information (patch id, patch type, target identity name and version, description) from the patch.xml of the specified patch file. > However it works only for "one-off" patches, not for cumulative patches. CPs don't contain patch.xml file but patches.xml. > It would be nice if it could display list of patches included in CP together with their metadata. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4764) XSD schema for transaction subsytem does not contain element of commit-markable-resource

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/WFLY-4764?page=com.atlassian.jira.plugin.... ] Amos Feng commented on WFLY-4764: --------------------------------- yeah, I will confirm this with Stefano. > XSD schema for transaction subsytem does not contain element of commit-markable-resource > ---------------------------------------------------------------------------------------- > > Key: WFLY-4764 > URL: https://issues.jboss.org/browse/WFLY-4764 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 9.0.0.CR1 > Reporter: Ondřej Chaloupka > Assignee: Amos Feng > > The commit-markable-resource element was removed from the xsd template for transaction subsystem in version 2.0 (in comparison with version 1.5) > This is trouble only of the xsd template as management model still contains `commit-markable-resource` node. > As commit markable resource functionality should be supported for EAP7 as well this element should be returned back to xsd template. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-570) Provide ability to display module dependencies via Management API

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-570?page=com.atlassian.jira.plugin... ] Tomaz Cerar commented on WFCORE-570: ------------------------------------ Sample output of current WIP {noformat} [standalone@localhost:9990 /] /core-service=module-loading:module-info(name=io.undertow.core) { "outcome" => "success", "result" => { "name" => "io.undertow.core:main", "fallback-loader" => "<not defined>", "dependencies" => [ { "dependency-name" => "ModuleDependency", "module-name" => "org.jboss.xnio:main", "export-filter" => "Reject", "import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}", "optional" => false }, { "dependency-name" => "ModuleDependency", "module-name" => "org.jboss.xnio.nio:main", "export-filter" => "Reject", "import-filter" => "multi-path filter {include equals \"META-INF/services\", include children of \"META-INF/services/\", exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}", "optional" => false }, { "dependency-name" => "ModuleDependency", "module-name" => "org.jboss.logging:main", "export-filter" => "Reject", "import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}", "optional" => false }, { "dependency-name" => "ModuleDependency", "module-name" => "javax.api:main", "export-filter" => "Reject", "import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}", "optional" => false }, { "dependency-name" => "ModuleDependency", "module-name" => "sun.jdk:main", "export-filter" => "Reject", "import-filter" => "multi-path filter {exclude children of \"META-INF/\", exclude equals \"META-INF\", default accept}", "optional" => false } ], "resource-loaders" => [ { "type" => "org.jboss.modules.JarFileResourceLoader", "paths" => "[, io/undertow/security/idm, META-INF/maven/io.undertow/undertow-core, io/undertow/websockets/core, io/undertow/server/session, io/undertow/websockets/core/protocol/version13, META-INF/maven/io.undertow, io/undertow/server /handlers/error, io/undertow/security, io/undertow/server/protocol/http, io/undertow/client/spdy, io/undertow/protocols/spdy, io/undertow/server, io/undertow/protocols/ajp, io/undertow/client, io/undertow/protocols/http2, io/undertow/websockets/core/ protocol/version08, io/undertow/client/http2, io, io/undertow/client/http, io/undertow/security/api, io/undertow/server/handlers/builder, io/undertow/websockets/client, io/undertow/server/protocol/spdy, io/undertow/conduits, io/undertow/server/protoc ol, io/undertow/websockets/core/protocol/version07, META-INF, io/undertow/websockets, io/undertow/server/handlers/cache, io/undertow/client/ajp, META-INF/maven, io/undertow/protocols, io/undertow/server/protocol/framed, io/undertow, io/undertow/serve r/handlers/resource, io/undertow/server/handlers/proxy, io/undertow/server/handlers/accesslog, META-INF/services, io/undertow/security/handlers, io/undertow/server/handlers/encoding, io/undertow/server/handlers/proxy/mod_cluster, io/undertow/websocke ts/spi, io/undertow/server/protocol/ajp, io/undertow/server/handlers, io/undertow/server/protocol/http2, io/undertow/server/handlers/sse, io/undertow/server/handlers/form, io/undertow/util, io/undertow/security/impl, io/undertow/websockets/core/proto col, io/undertow/predicate, io/undertow/websockets/extensions, io/undertow/protocols/ssl, io/undertow/attribute, io/undertow/channels, io/undertow/websockets/core/function, io/undertow/io]" }, { "type" => "org.jboss.modules.NativeLibraryResourceLoader", "paths" => "[]" } ] } } {noformat} > Provide ability to display module dependencies via Management API > ----------------------------------------------------------------- > > Key: WFCORE-570 > URL: https://issues.jboss.org/browse/WFCORE-570 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 2.0.0.Alpha5 > > > Provide ability to display module dependencies via Management API -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3449) Add a unit test that verifies that Hibernate ORM 4.1.x jars can be included with an application

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3449?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-3449: ------------------------------- Summary: Add a unit test that verifies that Hibernate ORM 4.1.x jars can be included with an application (was: Add a unit test that verifies that Hibernate ORM 4.3.5 jars can be included with an application) > Add a unit test that verifies that Hibernate ORM 4.1.x jars can be included with an application > ----------------------------------------------------------------------------------------------- > > Key: WFLY-3449 > URL: https://issues.jboss.org/browse/WFLY-3449 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > > Unit test should get the classloader for one of the Hibernate classes and verify that its the application classloader. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2015