September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-88) Release Remoting JMX 1.1.3.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-88?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-88: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1113251|https://bugzilla.redhat.com/show_bug.cgi?id=1113251] from ASSIGNED to POST > Release Remoting JMX 1.1.3.Final > -------------------------------- > > Key: REMJMX-88 > URL: https://issues.jboss.org/browse/REMJMX-88 > Project: Remoting JMX > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (REMJMX-88) Release Remoting JMX 1.1.3.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-88?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-88: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1113249|https://bugzilla.redhat.com/show_bug.cgi?id=1113249] from ASSIGNED to POST > Release Remoting JMX 1.1.3.Final > -------------------------------- > > Key: REMJMX-88 > URL: https://issues.jboss.org/browse/REMJMX-88 > Project: Remoting JMX > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3874) Upgrade to HornetQ 2.4.4.Final

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFLY-3874?page=com.atlassian.jira.plugin.... ] Clebert Suconic updated WFLY-3874: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/6733, https://github.com/wildfly/wildfly/pull/6734 (was: https://github.com/wildfly/wildfly/pull/6733) > Upgrade to HornetQ 2.4.4.Final > ------------------------------ > > Key: WFLY-3874 > URL: https://issues.jboss.org/browse/WFLY-3874 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Affects Versions: 9.0.0.Alpha1 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.2.0.CR1, 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3874) Upgrade to HornetQ 2.4.4.Final

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFLY-3874?page=com.atlassian.jira.plugin.... ] Clebert Suconic updated WFLY-3874: ---------------------------------- Fix Version/s: 8.2.0.CR1 > Upgrade to HornetQ 2.4.4.Final > ------------------------------ > > Key: WFLY-3874 > URL: https://issues.jboss.org/browse/WFLY-3874 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Affects Versions: 9.0.0.Alpha1 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.2.0.CR1, 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-104) SyslogHandler doesn't handle multi-byte characters correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-104?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on LOGMGR-104: ------------------------------------------------ Nikoleta Ziakova <nziakova(a)redhat.com> changed the Status of [bug 1096053|https://bugzilla.redhat.com/show_bug.cgi?id=1096053] from ON_QA to VERIFIED > SyslogHandler doesn't handle multi-byte characters correctly > ------------------------------------------------------------ > > Key: LOGMGR-104 > URL: https://issues.jboss.org/browse/LOGMGR-104 > Project: JBoss Log Manager > Issue Type: Bug > Components: core > Affects Versions: 1.5.2.Final > Environment: - WildFly 8.0.0.Final > - Oracle JDK7u51 > - OS X 10.9.2 > Reporter: Kyle Shanahan > Assignee: James Perkins > Fix For: 1.5.3.Final, 2.0.0.Beta1 > > Attachments: corrupted.png, corrupted2.png, corrupted3.png > > > SyslogHandler doesn't handle multi-byte characters correctly. > I tried to log multi-byte message with both of org.jboss.logmanager.handlers.SyslogHandler and org.apache.log4j.net.SyslogAppender for same message, only SyslogHandler output were corrupted. > Step to reproduce (It might need to define -Dfile.encoding=UTF-8 in _JAVA_OPTIONS): > 1. define a facility local1 at localhost and make syslog accept UDP packets. > 2. define a logger: > {noformat} > /subsystem=logging/logger=utf8mb4log:add(level=INFO) > {noformat} > 3. define a SyslogHandler: > {noformat} > /subsystem=logging/custom-handler=TEST_SH:add(class="org.jboss.logmanager.handlers.SyslogHandler", module="org.jboss.logmanager", formatter="SyslogHandler: %s%e", level=INFO, properties={serverHostname="localhost:514", facility="LOCAL_USE_1", truncate=false, maxLength=1024, syslogType="RFC3164" }) > /subsystem=logging/logger=utf8mb4log:assign-handler(name=TEST_SH) > {noformat} > 4. define a SyslogAppender: > {noformat} > /subsystem=logging/custom-handler=TEST_LOG4J:add(class="org.apache.log4j.net.SyslogAppender", module="org.apache.log4j", formatter="log4j: %s%e", level=INFO, properties={syslogHost="localhost:514", facility="local1"}) > /subsystem=logging/logger=utf8mb4log:assign-handler(name=TEST_LOG4J) > {noformat} > 5. get and deploy example project at https://github.com/lbtc-xxx/utf8mb4log > 6. Access the servlet http://localhost:8080/utf8mb4log/ > And you will get like this: (I can't put 4 byte UTF-8 characters here... because database error occured): > {noformat} > Mar 8 17:29:09 UNKNOWN_HOSTNAME java[9896]: SyslogHandler: ???????????? > {noformat} > I would send a pull request later. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-101) logging-profile works for a servlet, but doesn't for a JSP

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-101?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-101: ------------------------------------------------ Nikoleta Ziakova <nziakova(a)redhat.com> changed the Status of [bug 1031448|https://bugzilla.redhat.com/show_bug.cgi?id=1031448] from ON_QA to VERIFIED > logging-profile works for a servlet, but doesn't for a JSP > ---------------------------------------------------------- > > Key: WFCORE-101 > URL: https://issues.jboss.org/browse/WFCORE-101 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Osamu Nagano > Assignee: James Perkins > Fix For: 1.0.0.Alpha9 > > Attachments: logone.zip > > > Suppose the following logging-profile has been set in logging subsystem, and a web app has a proper entry in its MANIFEST.MF ({{Logging-Profile: logone}}). Then all messages via "com.example.logone" logger should go into a file, logone.log. It does so with a logger got in a servlet, but it doesn't work a logger got in a JSP. > {code} > <logging-profiles> > <logging-profile name="logone"> > <file-handler name="logone"> > <level name="INFO"/> > <file relative-to="jboss.server.log.dir" path="logone.log"/> > </file-handler> > <logger category="com.example.logone"> > <level name="INFO"/> > </logger> > <root-logger> > <level name="INFO"/> > <handlers> > <handler name="logone"/> > </handlers> > </root-logger> > </logging-profile> > </logging-profiles> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-111) ClassLoaderLogContextSelector should optionally include parent CL for context scanning

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-111?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on LOGMGR-111: ------------------------------------------------ Nikoleta Ziakova <nziakova(a)redhat.com> changed the Status of [bug 1031448|https://bugzilla.redhat.com/show_bug.cgi?id=1031448] from ON_QA to VERIFIED > ClassLoaderLogContextSelector should optionally include parent CL for context scanning > -------------------------------------------------------------------------------------- > > Key: LOGMGR-111 > URL: https://issues.jboss.org/browse/LOGMGR-111 > Project: JBoss Log Manager > Issue Type: Feature Request > Affects Versions: 1.5.2.Final > Reporter: Dominik Pospisil > Assignee: James Perkins > Fix For: 1.5.3.Final, 2.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3878) Wildfly rejects calls due to a bug in Undertow with an UnknownHostException

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3878?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-3878: ------------------------------ Fix Version/s: 8.2.0.CR1 9.0.0.Beta1 > Wildfly rejects calls due to a bug in Undertow with an UnknownHostException > --------------------------------------------------------------------------- > > Key: WFLY-3878 > URL: https://issues.jboss.org/browse/WFLY-3878 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Environment: All > Reporter: Mayank Goyal > Assignee: Stuart Douglas > Fix For: 8.2.0.CR1, 9.0.0.Beta1 > > > Refer to undertow commit: > https://github.com/undertow-io/undertow/commit/204684cc41fc369f56bd0305a7... > With proxy-address-forwarding="true" set in wildfly configuration & X-Forwarded-For headers passed in headers with additional proxies following behaviour can be noticed. > For example with X-Forwarded-For set as "123.123.123.123, 210.210.210.210" following IP is reported to the application "123.123.123.12". Which is incorrect and has its own implications. > With X-Forwarded-For set as "1.1.1.1, 2.2.2.2" an java.net.UnknownHostException is thrown in the undertow package. And the connection is terminated with an Internal server error returned to the caller. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-127) Use InMemory ApacheDS partitions when running tests with embedded LDAP

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-127?page=com.atlassian.jira.plugin... ] Josef Cacek updated WFCORE-127: ------------------------------- Component/s: Domain Management > Use InMemory ApacheDS partitions when running tests with embedded LDAP > ---------------------------------------------------------------------- > > Key: WFCORE-127 > URL: https://issues.jboss.org/browse/WFCORE-127 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Josef Cacek > Assignee: Josef Cacek > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3898) Use InMemory ApacheDS partitions when running tests with embedded LDAP

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-3898?page=com.atlassian.jira.plugin.... ] Josef Cacek updated WFLY-3898: ------------------------------ Component/s: Test Suite > Use InMemory ApacheDS partitions when running tests with embedded LDAP > ---------------------------------------------------------------------- > > Key: WFLY-3898 > URL: https://issues.jboss.org/browse/WFLY-3898 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

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 September 2014