July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6856) Jboss CLI reporting wrong readings of datasource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6856?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-6856: -------------------------------------- Assignee: Jesper Pedersen (was: Scott Marlow) > Jboss CLI reporting wrong readings of datasource > ------------------------------------------------ > > Key: WFLY-6856 > URL: https://issues.jboss.org/browse/WFLY-6856 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.2.0.Final > Reporter: ritesh ranjan > Assignee: Jesper Pedersen > Labels: wildfly > > Jboss's CLI is reporting wrong values of datasource parameters.(active count,idlecount etc..) > As per the reading , idle connections on the database side have been closed but actually the connections are indeed active. > Probably, jboss isn't checking on the oracle side. > PS : found in wildfly 8 and our db is Oracle -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6856) Jboss CLI reporting wrong readings of datasource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6856?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-6856: ----------------------------------- Component/s: JCA (was: JPA / Hibernate) > Jboss CLI reporting wrong readings of datasource > ------------------------------------------------ > > Key: WFLY-6856 > URL: https://issues.jboss.org/browse/WFLY-6856 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.2.0.Final > Reporter: ritesh ranjan > Assignee: Scott Marlow > Labels: wildfly > > Jboss's CLI is reporting wrong values of datasource parameters.(active count,idlecount etc..) > As per the reading , idle connections on the database side have been closed but actually the connections are indeed active. > Probably, jboss isn't checking on the oracle side. > PS : found in wildfly 8 and our db is Oracle -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBAS-9581) misleading error message when datasource is disabled

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/JBAS-9581?page=com.atlassian.jira.plugin.... ] Carlo de Wolf closed JBAS-9581. ------------------------------- Resolution: Rejected Please file the appropriate issue at either WFLY or JBEAP. > misleading error message when datasource is disabled > ---------------------------------------------------- > > Key: JBAS-9581 > URL: https://issues.jboss.org/browse/JBAS-9581 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: JCA service > Reporter: Johnathon Lee > Assignee: Carlo de Wolf > Priority: Minor > > test-connection-in-pool fails on a disabled datasource with: > {code:java} > JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS" > {code} > {code:java} > [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:add(jndi-name=java:jboss/datasources/MyExampleDS, connection-url=\"jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE\", driver-name=h2, user-name=sa, password=sa, max-pool-size=10) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:test-connection-in-pool() > { > "outcome" => "failed", > "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS", > "rolled-back" => true > } > {code} > The error message should rather convey that an operation was attempted on a disabled datasource. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBAS-9581) misleading error message when datasource is disabled

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/JBAS-9581?page=com.atlassian.jira.plugin.... ] Carlo de Wolf reassigned JBAS-9581: ----------------------------------- Assignee: Carlo de Wolf (was: JBoss SET) > misleading error message when datasource is disabled > ---------------------------------------------------- > > Key: JBAS-9581 > URL: https://issues.jboss.org/browse/JBAS-9581 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: JCA service > Reporter: Johnathon Lee > Assignee: Carlo de Wolf > Priority: Minor > > test-connection-in-pool fails on a disabled datasource with: > {code:java} > JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS" > {code} > {code:java} > [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:add(jndi-name=java:jboss/datasources/MyExampleDS, connection-url=\"jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE\", driver-name=h2, user-name=sa, password=sa, max-pool-size=10) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:test-connection-in-pool() > { > "outcome" => "failed", > "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS", > "rolled-back" => true > } > {code} > The error message should rather convey that an operation was attempted on a disabled datasource. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1669) SERVER_SSL constraint is not modifiable in a mixed domain

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1669: ---------------------------------------- Summary: SERVER_SSL constraint is not modifiable in a mixed domain Key: WFCORE-1669 URL: https://issues.jboss.org/browse/WFCORE-1669 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Tomaz Cerar Fix For: 3.0.0.Alpha4, 2.2.0.CR9 This is related to WFCORE-1649; it's the specific case that led to the discovery of WFCORE-1649. 1649 is meant to track more general improvements; this one is for a specific fix for the SERVER_SSL issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-597) Enable discovery of our java.security.Provider implementation using ServiceLoader discovery.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-597: ------------------------------------ Summary: Enable discovery of our java.security.Provider implementation using ServiceLoader discovery. Key: ELY-597 URL: https://issues.jboss.org/browse/ELY-597 Project: WildFly Elytron Issue Type: Feature Request Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1667) After a full-replace-deployment operation on a managed domain in a composite operation onf of the enabled timestamp is not updated

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1667?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1667: ---------------------------------------- Assignee: (was: Brian Stansberry) > After a full-replace-deployment operation on a managed domain in a composite operation onf of the enabled timestamp is not updated > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1667 > URL: https://issues.jboss.org/browse/WFCORE-1667 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > > When executing a {{full-replace-deployment}} in a composite operation the deployment associated with the first step does not get it's {{enabled-time}} attribute updated. The second one always has an updated attribute. > I've created a test to show the odd behavior, https://github.com/wildfly/wildfly-core/commit/452e2149571c87ff4cfcdfbd78.... Note that if you change the order of the archive arguments on the redeploy you'll see the failure happens on the second deployment instead of the first. > Do note that this test may not be needed, but it was an easy way to show what the issue is. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBAS-9581) misleading error message when datasource is disabled

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/JBAS-9581?page=com.atlassian.jira.plugin.... ] Johnathon Lee updated JBAS-9581: -------------------------------- Priority: Minor (was: Major) > misleading error message when datasource is disabled > ---------------------------------------------------- > > Key: JBAS-9581 > URL: https://issues.jboss.org/browse/JBAS-9581 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: JCA service > Reporter: Johnathon Lee > Assignee: JBoss SET > Priority: Minor > > test-connection-in-pool fails on a disabled datasource with: > {code:java} > JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS" > {code} > {code:java} > [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:add(jndi-name=java:jboss/datasources/MyExampleDS, connection-url=\"jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE\", driver-name=h2, user-name=sa, password=sa, max-pool-size=10) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:test-connection-in-pool() > { > "outcome" => "failed", > "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS", > "rolled-back" => true > } > {code} > The error message should rather convey that an operation was attempted on a disabled datasource. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBAS-9581) misleading error message when datasource is disabled

by Johnathon Lee (JIRA)

Johnathon Lee created JBAS-9581: ----------------------------------- Summary: misleading error message when datasource is disabled Key: JBAS-9581 URL: https://issues.jboss.org/browse/JBAS-9581 Project: Application Server 3 4 5 and 6 Issue Type: Bug Components: JCA service Reporter: Johnathon Lee Assignee: Jesper Pedersen test-connection-in-pool fails on a disabled datasource with: {code:java} JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS" {code} {code:java} [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:add(jndi-name=java:jboss/datasources/MyExampleDS, connection-url=\"jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE\", driver-name=h2, user-name=sa, password=sa, max-pool-size=10) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:test-connection-in-pool() { "outcome" => "failed", "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS", "rolled-back" => true } {code} The error message should rather convey that an operation was attempted on a disabled datasource. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBAS-9581) misleading error message when datasource is disabled

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/JBAS-9581?page=com.atlassian.jira.plugin.... ] Johnathon Lee reassigned JBAS-9581: ----------------------------------- Assignee: JBoss SET (was: Jesper Pedersen) > misleading error message when datasource is disabled > ---------------------------------------------------- > > Key: JBAS-9581 > URL: https://issues.jboss.org/browse/JBAS-9581 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: JCA service > Reporter: Johnathon Lee > Assignee: JBoss SET > > test-connection-in-pool fails on a disabled datasource with: > {code:java} > JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS" > {code} > {code:java} > [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:add(jndi-name=java:jboss/datasources/MyExampleDS, connection-url=\"jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE\", driver-name=h2, user-name=sa, password=sa, max-pool-size=10) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:test-connection-in-pool() > { > "outcome" => "failed", > "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS", > "rolled-back" => true > } > {code} > The error message should rather convey that an operation was attempted on a disabled datasource. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 July 2016