October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7267) [Proxy] No failover on empty response from node

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7267?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-6311 to WFLY-7267: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7267 (was: JBEAP-6311) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) Affects Version/s: (was: 7.0.1.GA) (was: 7.0.2.GA) (was: 7.1.0.DR4) > [Proxy] No failover on empty response from node > ----------------------------------------------- > > Key: WFLY-7267 > URL: https://issues.jboss.org/browse/WFLY-7267 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > Undertow balancer do not recognizes empty response as an error. > Can happen when JVM got killed when handling request (System.exit()) > {code} > @Override > public void failed(final HttpServerExchange exchange) { > final long time = System.currentTimeMillis(); > if (tries++ < maxRetryAttempts) { > ... > {code} > Undertow make curl hang. > Apache httpd correctly recognizes empty response as error and starts fail over method. If unsuccessful, 50x is returned in response. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-114) Actually make use of the provided callback handler in RemotingConnector or set up the callback handler appropriately if it hasn't been provided

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/REMJMX-114?page=com.atlassian.jira.plugin... ] Farah Juma updated REMJMX-114: ------------------------------ Git Pull Request: https://github.com/jbossas/remoting-jmx/pull/23 > Actually make use of the provided callback handler in RemotingConnector or set up the callback handler appropriately if it hasn't been provided > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: REMJMX-114 > URL: https://issues.jboss.org/browse/REMJMX-114 > Project: Remoting JMX > Issue Type: Bug > Reporter: Farah Juma > Assignee: Farah Juma > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-114) Actually make use of the provided callback handler in RemotingConnector or set up the callback handler appropriately if it hasn't been provided

by Farah Juma (JIRA)

Farah Juma created REMJMX-114: --------------------------------- Summary: Actually make use of the provided callback handler in RemotingConnector or set up the callback handler appropriately if it hasn't been provided Key: REMJMX-114 URL: https://issues.jboss.org/browse/REMJMX-114 Project: Remoting JMX Issue Type: Bug Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7031) Redirect Port Fails to Redirect to 3rd Party HTTP Port

by Joe Carder (JIRA)

[ https://issues.jboss.org/browse/WFLY-7031?page=com.atlassian.jira.plugin.... ] Joe Carder commented on WFLY-7031: ---------------------------------- Hi, Just curious if any additional information is needed for this issue? Thank you. > Redirect Port Fails to Redirect to 3rd Party HTTP Port > ------------------------------------------------------ > > Key: WFLY-7031 > URL: https://issues.jboss.org/browse/WFLY-7031 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR1 > Reporter: Joe Carder > Assignee: Stuart Douglas > Priority: Minor > > When setting a redirect socket to port not opened by Wildfly (IE: a port opened by Apache HTTPD or IIS), Wildfly throws the following exception: > ERROR [io.undertow.request] (default task-2) UT005001: An exception occurred processing the request: java.lang.IllegalStateException: UT010053: No confidential port is available to redirect the current request. > With the redirect socket to a port opened by JBoss, it works as expected. I'm not 100% sure this is a bug, or functional decision made for Wildfly 10 and is working as expected. However, in Previous Widlfly version (Widlfly 8) it was possible to set the redirect port to a third party service without out issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-124) Change switch statements to if/else blocks when translating levels

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-124?page=com.atlassian.jira.plu... ] James Perkins reopened JBLOGGING-124: ------------------------------------- > Change switch statements to if/else blocks when translating levels > ------------------------------------------------------------------ > > Key: JBLOGGING-124 > URL: https://issues.jboss.org/browse/JBLOGGING-124 > Project: JBoss Logging > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 3.3.0.Final > > > Currently a switch statement is used when levels are translated from a JBoss Logging level to the back end log level. This will likely perform better as an if/else block with the mostly likely used level at the top of the comparison. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-124) Change switch statements to if/else blocks when translating levels

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-124?page=com.atlassian.jira.plu... ] James Perkins updated JBLOGGING-124: ------------------------------------ Fix Version/s: 3.3.1.Final (was: 3.3.0.Final) > Change switch statements to if/else blocks when translating levels > ------------------------------------------------------------------ > > Key: JBLOGGING-124 > URL: https://issues.jboss.org/browse/JBLOGGING-124 > Project: JBoss Logging > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 3.3.1.Final > > > Currently a switch statement is used when levels are translated from a JBoss Logging level to the back end log level. This will likely perform better as an if/else block with the mostly likely used level at the top of the comparison. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-124) Change switch statements to if/else blocks when translating levels

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-124?page=com.atlassian.jira.plu... ] James Perkins closed JBLOGGING-124. ----------------------------------- Fix Version/s: 3.3.0.Beta2 Resolution: Done > Change switch statements to if/else blocks when translating levels > ------------------------------------------------------------------ > > Key: JBLOGGING-124 > URL: https://issues.jboss.org/browse/JBLOGGING-124 > Project: JBoss Logging > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 3.3.0.Beta2 > > > Currently a switch statement is used when levels are translated from a JBoss Logging level to the back end log level. This will likely perform better as an if/else block with the mostly likely used level at the top of the comparison. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-92) Add support for Equinox ExtendedLogService

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-92?page=com.atlassian.jira.plug... ] James Perkins closed JBLOGGING-92. ---------------------------------- Resolution: Out of Date I'm going to close this as I think it's out of date. I'd prefer in most cases not add support for other logging frameworks in jboss-logging itself and rather have the project itself supply a [{{LoggerProvider}}|https://github.com/jboss-logging/jboss-logging/blob/master/src/main/java/org/jboss/logging/LoggerProvider.java] This uses a standard ServiceLoader to find a matching provider. > Add support for Equinox ExtendedLogService > ------------------------------------------ > > Key: JBLOGGING-92 > URL: https://issues.jboss.org/browse/JBLOGGING-92 > Project: JBoss Logging > Issue Type: Feature Request > Components: jboss-logging-spi > Reporter: Philippe Marschall > Assignee: David Lloyd > > We are running some JBoss libraries that use jboss-logging inside Eclipse RCP. We'd like to centralise all our logging. Unfortunately OSGi LogService does not support named loggers, for now they're only available through the Equinox ExtendedLogService. > I'll attach a pull request. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-123) Support for tinylog

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-123?page=com.atlassian.jira.plu... ] James Perkins closed JBLOGGING-123. ----------------------------------- Resolution: Out of Date I'm going to close this based on this commit to tinylog itself https://github.com/pmwmedia/tinylog/commit/108dd2cb4043e903fd066add372946... > Support for tinylog > ------------------- > > Key: JBLOGGING-123 > URL: https://issues.jboss.org/browse/JBLOGGING-123 > Project: JBoss Logging > Issue Type: Feature Request > Reporter: Martin Winandy > Assignee: James Perkins > > tinylog is a lightweight logging framework for Java with a static logger class. For supporting tinylog in JBoss Logging, a logger provider has to be implemented and added to the LoggerProviders class. > Link to tinylog website: http://www.tinylog.org/ > Example implementation for JBoss Logging: https://github.com/pmwmedia/jboss-logging/ > The tinylog implementation for JBoss Logging is out-dated, but I could adapt to the newest version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1318) Using java enum when setting a variable of type enum does not work

by Nicolas Heron (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1318?page=com.atlassian.jira.plugi... ] Nicolas Heron commented on DROOLS-1318: --------------------------------------- [~mfusco] In your case, the enum is in the Class definition. The error is in the when part in the example Period( seasonType == SeasonType.day ) > Using java enum when setting a variable of type enum does not work > ------------------------------------------------------------------ > > Key: DROOLS-1318 > URL: https://issues.jboss.org/browse/DROOLS-1318 > Project: Drools > Issue Type: Bug > Affects Versions: 6.4.0.Final > Reporter: Nicolas Heron > Assignee: Nicolas Heron > Labels: OnBoarding > > In project https://github.com/chtiJBUG/onboarding-nautic-project > when running the TestBirthday reduction > TestBirthdayReduction : [Error: could not access/write property (seasonType) in: org.chtijbug.example.swimmingpool.Period] [Near : > the source code of the rule is > package org.training.leisure.swimmingpool; > import java.lang.Number; > import org.chtijbug.example.swimmingpool.CalculatedAttribute; > import org.chtijbug.example.swimmingpool.Price; > import org.chtijbug.example.swimmingpool.Person; > import org.chtijbug.example.swimmingpool.Period; > import org.chtijbug.example.swimmingpool.PriceType; > rule "BirthdayReduction" > dialect "mvel" > ruleflow-group "reduction" > when > ccat : CalculatedAttribute( key == "IsPersonBirthday" , stringValue == "true" ) > pper : Person( calculatedAttributeList contains ccat , sprice : standardPrice > 0.0B ) > not (pprice : Price( description == "BirthdayReduction" ) and Person( priceList contains pprice , this == pper )) > Period( seasonType == SeasonType.day ) > then > Price nprice = new Price(); > nprice.setDescription( "BirthdayReduction" ); > nprice.setAmount( sprice.divide(new BigDecimal("10.0"),BigDecimal.ROUND_HALF_UP) ); > nprice.setPriceType( PriceType.promotion ); > insert( nprice ); > pper.addPrice( nprice ); > modify( pper ) { > setPriceList( pper.getPriceList() ) > } > end -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2016