March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6305) Add CXF artefacts required by Camel integration

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-6305?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated WFLY-6305: --------------------------------- Description: CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1046 > Add CXF artefacts required by Camel integration > ------------------------------------------------ > > Key: WFLY-6305 > URL: https://issues.jboss.org/browse/WFLY-6305 > Project: WildFly > Issue Type: Task > Components: Web Services > Affects Versions: 10.0.0.Final > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 10.1.0.Final > > > CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1046 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6305) Add CXF artefacts required by Camel integration

by Thomas Diesler (JIRA)

Thomas Diesler created WFLY-6305: ------------------------------------ Summary: Add CXF artefacts required by Camel integration Key: WFLY-6305 URL: https://issues.jboss.org/browse/WFLY-6305 Project: WildFly Issue Type: Feature Request Components: Web Services Affects Versions: 10.0.0.Final Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 10.1.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6305) Add CXF artefacts required by Camel integration

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-6305?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated WFLY-6305: --------------------------------- Issue Type: Task (was: Feature Request) > Add CXF artefacts required by Camel integration > ------------------------------------------------ > > Key: WFLY-6305 > URL: https://issues.jboss.org/browse/WFLY-6305 > Project: WildFly > Issue Type: Task > Components: Web Services > Affects Versions: 10.0.0.Final > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-431) Improve Elytron HTTP API/SPIs to support a broader range of authentication mechanisms

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-431?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-431: --------------------------- Summary: Improve Elytron HTTP API/SPIs to support a broader range of authentication mechanisms (was: Improve Elytron HTTP API/SPIs to support more complex authentication mechanisms) > Improve Elytron HTTP API/SPIs to support a broader range of authentication mechanisms > ------------------------------------------------------------------------------------- > > Key: ELY-431 > URL: https://issues.jboss.org/browse/ELY-431 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > This is task is being driven by the requirements around Keycloak and Elytron integration, which will provide as a result a baseline to implement a Keycloak OIDC adapter based on Elytron HTTP API and SPI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-431) Improve Elytron HTTP API/SPIs to support more complex authentication mechanisms

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-431?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-431: --------------------------- Description: This is task is being driven by the requirements around Keycloak and Elytron integration, which will provide as a result a baseline to implement a Keycloak OIDC adapter based on Elytron HTTP API and SPI. (was: Implement a Keycloak OIDC adapter based on Elytron HTTP APIs.) > Improve Elytron HTTP API/SPIs to support more complex authentication mechanisms > ------------------------------------------------------------------------------- > > Key: ELY-431 > URL: https://issues.jboss.org/browse/ELY-431 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > This is task is being driven by the requirements around Keycloak and Elytron integration, which will provide as a result a baseline to implement a Keycloak OIDC adapter based on Elytron HTTP API and SPI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-431) Improve Elytron HTTP API/SPIs to support more complex authentication mechanisms

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-431?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-431: --------------------------- Summary: Improve Elytron HTTP API/SPIs to support more complex authentication mechanisms (was: Keycloak OIDC Adapter based on Elytron APIs) > Improve Elytron HTTP API/SPIs to support more complex authentication mechanisms > ------------------------------------------------------------------------------- > > Key: ELY-431 > URL: https://issues.jboss.org/browse/ELY-431 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > Implement a Keycloak OIDC adapter based on Elytron HTTP APIs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-431) Keycloak OIDC Adapter based on Elytron APIs

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-431?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-431: --------------------------- Issue Type: Task (was: Feature Request) > Keycloak OIDC Adapter based on Elytron APIs > ------------------------------------------- > > Key: ELY-431 > URL: https://issues.jboss.org/browse/ELY-431 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > Implement a Keycloak OIDC adapter based on Elytron HTTP APIs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-431) Keycloak OIDC Adapter based on Elytron APIs

by Pedro Igor (JIRA)

Pedro Igor created ELY-431: ------------------------------ Summary: Keycloak OIDC Adapter based on Elytron APIs Key: ELY-431 URL: https://issues.jboss.org/browse/ELY-431 Project: WildFly Elytron Issue Type: Feature Request Components: HTTP Affects Versions: 1.0.2.Final Reporter: Pedro Igor Assignee: Pedro Igor Implement a Keycloak OIDC adapter based on Elytron HTTP APIs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1077) [POST] /containers/{id} is outdated

by Filippe Spolti (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1077?page=com.atlassian.jira.plugi... ] Filippe Spolti updated DROOLS-1077: ----------------------------------- Description: The REST URI to send the command fire-all-rules to an running container is outdated. Using the URI described in the docs I get the following result: {code} 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Allow: HEAD, DELETE, GET, OPTIONS, PUT 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Content-Type: text/html;charset=utf-8 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Content-Length: 1022 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Date: Mon, 29 Feb 2016 20:03:58 GMT Exception in thread "main" java.lang.RuntimeException: Failed with HTTP error code : 405 at org.jboss.test.arquillian.ce.decisionserver.DecisionServerSecureTest.main(DecisionServerSecureTest.java:404) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) {code} The correct URI is: . [POST] containers/instances/{id} After to change the REST call worked as expected. > [POST] /containers/{id} is outdated > ------------------------------------ > > Key: DROOLS-1077 > URL: https://issues.jboss.org/browse/DROOLS-1077 > Project: Drools > Issue Type: Bug > Components: docs > Affects Versions: 6.3.0.Final > Environment: The REST URI to send the command fire-all-rules to an running container is outdated. > Using the URI described in the docs I get the following result: > {code} > 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Allow: HEAD, DELETE, GET, OPTIONS, PUT > 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Content-Type: text/html;charset=utf-8 > 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Content-Length: 1022 > 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Date: Mon, 29 Feb 2016 20:03:58 GMT > Exception in thread "main" java.lang.RuntimeException: Failed with HTTP error code : 405 > at org.jboss.test.arquillian.ce.decisionserver.DecisionServerSecureTest.main(DecisionServerSecureTest.java:404) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) > {code} > The correct URI is: > . [POST] instances/containers/{id} > After to change the REST call worked as exp > Documentation link: https://docs.jboss.org/drools/release/6.3.0.Final/drools-docs/pdf/drools-... > Item 22.6.7. > Reporter: Filippe Spolti > Assignee: Mario Fusco > Labels: doc, rest_api > > The REST URI to send the command fire-all-rules to an running container is outdated. > Using the URI described in the docs I get the following result: > {code} > 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Allow: HEAD, DELETE, GET, OPTIONS, PUT > 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Content-Type: text/html;charset=utf-8 > 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Content-Length: 1022 > 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Date: Mon, 29 Feb 2016 20:03:58 GMT > Exception in thread "main" java.lang.RuntimeException: Failed with HTTP error code : 405 > at org.jboss.test.arquillian.ce.decisionserver.DecisionServerSecureTest.main(DecisionServerSecureTest.java:404) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) > {code} > The correct URI is: > . [POST] containers/instances/{id} > After to change the REST call worked as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1310) NPE when validating database connection (and the validation failed) if connection pool statistics is enabled

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1310?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1310: ----------------------------------- Attachment: ironjacamar-core-impl.jar Could you try with the attached JAR, with TRACE and the Tracer enabled ? Also enable statistics, and then attached both log files. Thanks. > NPE when validating database connection (and the validation failed) if connection pool statistics is enabled > ------------------------------------------------------------------------------------------------------------ > > Key: JBJCA-1310 > URL: https://issues.jboss.org/browse/JBJCA-1310 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: WildFly/IronJacamar 1.3.2.Final, 1.2.6.Final > Reporter: Hugh Nguyen > Assignee: Jesper Pedersen > Priority: Critical > Attachments: ironjacamar-core-impl.jar > > > - An xa-datasource connection pool is configured with: statistic-enabled=true, validate-on-match=true > - When validation failed, after the failure, the following is logged: > {code} > 2016-02-10 12:23:12,580 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Sched1_Worker-13) IJ000621: Destroying connection that could not be validated: null > {code} > - This appears to come from SemaphoreConcurrentLinkedDequeManagedConnectionPool.java, line 436: > {code} > log.destroyingConnectionNotValidated(clw.getConnectionListener()); > {code} > - So apparently clw.getConnectionListener() is null at this point, causing line 441/442 to throw NPE, if statistics is enabled: > {code} > pool.getInternalStatistics().deltaTotalPoolTime(lastUsed - clw.getConnectionListener().getLastReturnedTime()); > {code} > - NPE is caught by the catch clause, and line 456 write the following to the log: > {code} > 2016-02-10 12:23:12,580 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Sched1_Worker-13) IJ000613: Throwable while trying to match managed connection, destroying connection: null: java.lang.NullPointerException > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:441) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getTransactionNewConnection(AbstractPool.java:708) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:607) > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:590) > at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:429) > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:747) > {code} > - However, this catch clause try to do the same thing that cause the NPE in line 461/462 > {code} > pool.getInternalStatistics().deltaTotalPoolTime(lastUsed - clw.getConnectionListener().getLastReturnedTime()); > {code} > - And finally this NPE is throw all the way out to the user of the connection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2016