March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1251) Only allow certain decrementer policies for CRI pools

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1251?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1251: ----------------------------------- Description: Otherwise there could be configurations where the pools never would empty Allow * TimedOutDecrementer * MinPoolSizeDecrementer * SizeDecrementer was:Otherwise there could be configurations where the pools never would empty > Only allow certain decrementer policies for CRI pools > ----------------------------------------------------- > > Key: JBJCA-1251 > URL: https://issues.jboss.org/browse/JBJCA-1251 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.2.3.Final > > > Otherwise there could be configurations where the pools never would empty > Allow > * TimedOutDecrementer > * MinPoolSizeDecrementer > * SizeDecrementer -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1251) Exclude decrementer policy for CRI pools

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1251?page=com.atlassian.jira.plugin... ] Jesper Pedersen reopened JBJCA-1251: ------------------------------------ > Exclude decrementer policy for CRI pools > ---------------------------------------- > > Key: JBJCA-1251 > URL: https://issues.jboss.org/browse/JBJCA-1251 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.2.3.Final > > > Otherwise there could be configurations where the pools never would empty -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1251) Only allow certain decrementer policies for CRI pools

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1251?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1251: ----------------------------------- Summary: Only allow certain decrementer policies for CRI pools (was: Exclude decrementer policy for CRI pools) > Only allow certain decrementer policies for CRI pools > ----------------------------------------------------- > > Key: JBJCA-1251 > URL: https://issues.jboss.org/browse/JBJCA-1251 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.2.3.Final > > > Otherwise there could be configurations where the pools never would empty -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1256) IronJacamar 1.2.3.Final

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1256?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1256. ------------------------------------ Resolution: Done > IronJacamar 1.2.3.Final > ----------------------- > > Key: JBJCA-1256 > URL: https://issues.jboss.org/browse/JBJCA-1256 > Project: IronJacamar > Issue Type: Release > Components: Build > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.2.3.Final > > > Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4464) JDBC driver module-slot is not persisted in domain mode

by Lin Gao (JIRA)

Lin Gao created WFLY-4464: ----------------------------- Summary: JDBC driver module-slot is not persisted in domain mode Key: WFLY-4464 URL: https://issues.jboss.org/browse/WFLY-4464 Project: WildFly Issue Type: Bug Components: JCA Reporter: Lin Gao Assignee: Jesper Pedersen The module-slot of jdbc-driver is NOT persisted in domain mode, but it is persisted in standalone mode. After debugging, I found that the performRuntime() method of JdbcDriverAdd.java is not called in domain mode, but is called in standalone mode. For more information about the issue, please refer to the thread: https://developer.jboss.org/thread/253654 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-750) Cannot resolve custom accumulate functions after declaring metadata for an existing type

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-750?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-750. -------------------------------- Fix Version/s: 6.3.0.Beta1 Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/45f32b52a > Cannot resolve custom accumulate functions after declaring metadata for an existing type > ---------------------------------------------------------------------------------------- > > Key: DROOLS-750 > URL: https://issues.jboss.org/browse/DROOLS-750 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.3.0.Beta1 > > > Importing a custom accumulate function and a pojo from a different package the DRL compilation fails with the following message: "Error: Unknown accumulate function: 'myfunc' on rule 'test'. All accumulate functions must be registered before building a resource" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-750) Cannot resolve custom accumulate functions after declaring metadata for an existing type

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-750: ---------------------------------- Summary: Cannot resolve custom accumulate functions after declaring metadata for an existing type Key: DROOLS-750 URL: https://issues.jboss.org/browse/DROOLS-750 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco Importing a custom accumulate function and a pojo from a different package the DRL compilation fails with the following message: "Error: Unknown accumulate function: 'myfunc' on rule 'test'. All accumulate functions must be registered before building a resource" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

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

by John Ament (JIRA)

[ https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin.... ] John Ament edited comment on WFLY-4444 at 3/25/15 10:16 AM: ------------------------------------------------------------ What does undertow have to do with this? This is pure HTTP. So I can confirm that I get better results/control over the generated WSDL when I remove Policy and EndpointConfig, which doesn't help as that will turn off security options, but it avoids the extra overwrite of the WSDL. It still doesn't help me as I can't get it to use a hardcoded HTTPS protocol. was (Author: meetoblivion): What does undertow have to do with this? This is pure HTTP. So I can confirm that I get better results/control over the generated WSDL when I remove Policy and EndpointConfig, which doesn't help as that will turn off security options, but it avoids the extra overwrite of the WSDL. It still doesn't help me as I can't get use a hardcoded HTTPS protocol. > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-306) Add support for TLS 1.1 and 1.2 to Apr

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-306?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-306: ----------------------------------------------- Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 1158184|https://bugzilla.redhat.com/show_bug.cgi?id=1158184] from NEW to CLOSED > Add support for TLS 1.1 and 1.2 to Apr > -------------------------------------- > > Key: JBWEB-306 > URL: https://issues.jboss.org/browse/JBWEB-306 > Project: JBoss Web > Issue Type: Enhancement > Affects Versions: JBossWeb-7.4.0.GA, JBossWeb-7.5.0.GA > Environment: JBoss Enterprise Application Platform (EAP) 6.3 > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > > Just as with Tomcat 7 (https://issues.apache.org/bugzilla/show_bug.cgi?id=53952), JBossWeb does not support TLS 1.1 and 1.2 for APR connectors. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

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

by John Ament (JIRA)

[ https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin.... ] John Ament commented on WFLY-4444: ---------------------------------- What does undertow have to do with this? This is pure HTTP. So I can confirm that I get better results/control over the generated WSDL when I remove Policy and EndpointConfig, which doesn't help as that will turn off security options, but it avoids the extra overwrite of the WSDL. It still doesn't help me as I can't get use a hardcoded HTTPS protocol. > 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, 3 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