March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1257) SemaphoreConcurrentLinkedQueueManagedConnectionPool

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1257?page=com.atlassian.jira.plugin... ] Radim Vansa updated JBJCA-1257: ------------------------------- Description: With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this {code} log.throwableWhileTryingMatchManagedConnectionThenDestroyingConnection(clw.getConnectionListener(), t); {code} https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... causes NPE since clw == null. This way, the NPE is eventually swallowed on https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... and only generic ResourceException (without much info) is thrown. was: With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this {code} log.throwableWhileTryingMatchManagedConnectionThenDestroyingConnection(clw.getConnectionListener(), t); {code} https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... causes NPE since clw == null. > SemaphoreConcurrentLinkedQueueManagedConnectionPool > --------------------------------------------------- > > Key: JBJCA-1257 > URL: https://issues.jboss.org/browse/JBJCA-1257 > Project: IronJacamar > Issue Type: Feature Request > Components: Core > Affects Versions: 1.0.31.Final > Reporter: Radim Vansa > Assignee: Jesper Pedersen > Priority: Minor > > With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this > {code} > log.throwableWhileTryingMatchManagedConnectionThenDestroyingConnection(clw.getConnectionListener(), t); > {code} > https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... > causes NPE since clw == null. This way, the NPE is eventually swallowed on https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... and only generic ResourceException (without much info) is thrown. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1257) SemaphoreConcurrentLinkedQueueManagedConnectionPool

by Radim Vansa (JIRA)

Radim Vansa created JBJCA-1257: ---------------------------------- Summary: SemaphoreConcurrentLinkedQueueManagedConnectionPool Key: JBJCA-1257 URL: https://issues.jboss.org/browse/JBJCA-1257 Project: IronJacamar Issue Type: Feature Request Components: Core Affects Versions: 1.0.31.Final Reporter: Radim Vansa Assignee: Jesper Pedersen Priority: Minor With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this {code} log.throwableWhileTryingMatchManagedConnectionThenDestroyingConnection(clw.getConnectionListener(), t); {code} https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... causes NPE since clw == null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-611) Add way to validating operation by its definition

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-611?page=com.atlassian.jira.plugin... ] Tomaz Cerar updated WFCORE-611: ------------------------------- Fix Version/s: (was: 1.0.0.CR1) > Add way to validating operation by its definition > ------------------------------------------------- > > Key: WFCORE-611 > URL: https://issues.jboss.org/browse/WFCORE-611 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha19 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 1.0.0.Beta1 > > > we could use OperationDefinition#validateAndSet(operation,model) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-487) Instability in RespawnHttpTestCase

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-487?page=com.atlassian.jira.plugin... ] Tomaz Cerar commented on WFCORE-487: ------------------------------------ looking at the build logs it looks fixed. > Instability in RespawnHttpTestCase > ----------------------------------- > > Key: WFCORE-487 > URL: https://issues.jboss.org/browse/WFCORE-487 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Affects Versions: 1.0.0.Alpha14 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 1.0.0.Beta1 > > Attachments: respawn-http-threads.txt > > > We have the following error message in the traces: > 2014-12-15 19:19:53,574 ERROR [org.jboss.remoting.remote.connection] (XNIO-1 I/O-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host > http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=32341&buildTyp...! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-612) Fix composite response structures

by Heiko Braun (JIRA)

Heiko Braun created WFCORE-612: ---------------------------------- Summary: Fix composite response structures Key: WFCORE-612 URL: https://issues.jboss.org/browse/WFCORE-612 Project: WildFly Core Issue Type: Sub-task Reporter: Heiko Braun 'address' and 'outcome' are not set {noformat} [domain@localhost:9990 /] /host=master/server-config=*:query(select=[name], where={status=STARTED}) { "outcome" => "success", "result" => [ { "address" => undefined, "outcome" => undefined, "result" => {"name" => "server-one"} }, { "address" => undefined, "outcome" => undefined, "result" => {"name" => "server-two"} }, { "address" => undefined, "outcome" => undefined, "result" => undefined } ], "server-groups" => undefined } {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-282) Wildcard operations that span multiple processes

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFCORE-282?page=com.atlassian.jira.plugin... ] Heiko Braun updated WFCORE-282: ------------------------------- Comment: was deleted (was: any update on this?) > Wildcard operations that span multiple processes > ------------------------------------------------ > > Key: WFCORE-282 > URL: https://issues.jboss.org/browse/WFCORE-282 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Labels: as7-ignored > Fix For: 1.0.0.Beta1 > > > Handle host=* and host=y,server=* type operations. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-282) Wildcard operations that span multiple processes

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFCORE-282?page=com.atlassian.jira.plugin... ] Heiko Braun commented on WFCORE-282: ------------------------------------ An example (related to WFCORE-287), what I would like to see provided: {noformat} [domain@localhost:9990 /] /host=*/server-config=*:query(select=[name], where={status=STARTED}) Failed to get the list of the operation properties: "WFLYCTL0030: No resource definition is registered for address [ ("host" => "*"), ("server-config" => "*") ]" {noformat} > Wildcard operations that span multiple processes > ------------------------------------------------ > > Key: WFCORE-282 > URL: https://issues.jboss.org/browse/WFCORE-282 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Labels: as7-ignored > Fix For: 1.0.0.Beta1 > > > Handle host=* and host=y,server=* type operations. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-287) Provide an operation to execute domain wide queries on the server side

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFCORE-287?page=com.atlassian.jira.plugin... ] Heiko Braun commented on WFCORE-287: ------------------------------------ Another domain example: {noformat} [domain@localhost:9990 /] /host=master/server-config=*:query(where={status=STARTED}) { "outcome" => "success", "result" => [ { "address" => undefined, "outcome" => undefined, "result" => { "auto-start" => true, "cpu-affinity" => undefined, "group" => "main-server-group", "name" => "server-one", "priority" => undefined, "socket-binding-default-interface" => undefined, "socket-binding-group" => undefined, "socket-binding-port-offset" => 0, "status" => "STARTED", "update-auto-start-with-server-status" => false, "interface" => undefined, "jvm" => undefined, "path" => undefined, "system-property" => undefined } }, { "address" => undefined, "outcome" => undefined, "result" => { "auto-start" => true, "cpu-affinity" => undefined, "group" => "main-server-group", "name" => "server-two", "priority" => undefined, "socket-binding-default-interface" => undefined, "socket-binding-group" => undefined, "socket-binding-port-offset" => 150, "status" => "STARTED", "update-auto-start-with-server-status" => false, "interface" => undefined, "jvm" => undefined, "path" => undefined, "system-property" => undefined } }, { "address" => undefined, "outcome" => undefined, "result" => undefined } ], "server-groups" => undefined } {noformat} > Provide an operation to execute domain wide queries on the server side > ---------------------------------------------------------------------- > > Key: WFCORE-287 > URL: https://issues.jboss.org/browse/WFCORE-287 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 1.0.0.Beta1 > > > i.e. retrieve all 'enabled' datasources that use the 'h2' driver: > {code:java} > ModelNode address = new ModelNode(); > address.add("profile", "*") > .add("subsystem", "datasources") > .add("data-source", "*"); > ModelNode filter = new ModelNode(); > filter.add("driver-name", "h2") > .add("enabled", true); > ModelNode op = new ModelNode(); > op.get(OP).set(QUERY); > op.get(ADDRESS).set(address); > op.get(WHERE).set(filter); > {code} > Another example using the CLI: > {code} > [standalone@localhost:9990 /] /path=*:query(select=[path], where={name="jboss.home.dir"}) > { > "outcome" => "success", > "result" => [{ > "address" => [("path" => "jboss.home.dir")], > "outcome" => "success", > "result" => {"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT"} > }] > } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4444) Ability to set WSDL URL

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on WFLY-4444 at 3/26/15 4:38 AM: ---------------------------------------------------------------- The feature you're trying to use (https://issues.jboss.org/browse/JBWS-3628) is implemented in JBossWS 5.0.0.Beta1 (which is installed on WildFly 9). WildFly 8.2.0.Final comes with JBossWS 4.3.2.Final (that's also why it's not covered in WFLY 8 doc, https://docs.jboss.org/author/display/WFLY8/Advanced+User+Guide) was (Author: asoldano): The feature you're trying to use (https://issues.jboss.org/browse/JBWS-3628) is implemented in JBossWS 5.0.0.Beta1. WildFly 8.2.0.Final comes with JBossWS 4.3.2.Final (that's also why it's not covered in WFLY 8 doc, https://docs.jboss.org/author/display/WFLY8/Advanced+User+Guide) > Ability to set WSDL URL > ----------------------- > > Key: WFLY-4444 > URL: https://issues.jboss.org/browse/WFLY-4444 > Project: WildFly > Issue Type: Feature Request > Components: Web Services > Affects Versions: 8.2.0.Final > Reporter: John Ament > Assignee: Alessio Soldano > > There's no way to correctly set a WSDL URL. The properties are: > {code} > <modify-wsdl-address>true</modify-wsdl-address> > <wsdl-host>${public.app.host:localhost}</wsdl-host> > <wsdl-port>${public.http.port:80}</wsdl-port> > <wsdl-secure-port>${public.https.port:443}</wsdl-secure-port> > {code} > We need a way to set the WSDL URL, regardless of the protocol used. The issue being that our app servers run on HTTP, but the incoming request to the first load balancer is over HTTPS. The result is that the WSDL generated includes http://public-host:80/ instead of https://public-host:443/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4444) Ability to set WSDL URL

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-4444: --------------------------------------- The feature you're trying to use (https://issues.jboss.org/browse/JBWS-3628) is implemented in JBossWS 5.0.0.Beta1. WildFly 8.2.0.Final comes with JBossWS 4.3.2.Final (that's also why it's not covered in WFLY 8 doc, https://docs.jboss.org/author/display/WFLY8/Advanced+User+Guide) > Ability to set WSDL URL > ----------------------- > > Key: WFLY-4444 > URL: https://issues.jboss.org/browse/WFLY-4444 > Project: WildFly > Issue Type: Feature Request > Components: Web Services > Affects Versions: 8.2.0.Final > Reporter: John Ament > Assignee: Alessio Soldano > > There's no way to correctly set a WSDL URL. The properties are: > {code} > <modify-wsdl-address>true</modify-wsdl-address> > <wsdl-host>${public.app.host:localhost}</wsdl-host> > <wsdl-port>${public.http.port:80}</wsdl-port> > <wsdl-secure-port>${public.https.port:443}</wsdl-secure-port> > {code} > We need a way to set the WSDL URL, regardless of the protocol used. The issue being that our app servers run on HTTP, but the incoming request to the first load balancer is over HTTPS. The result is that the WSDL generated includes http://public-host:80/ instead of https://public-host:443/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 March 2015