December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-871) AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-871?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-871: -------------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1170764|https://bugzilla.redhat.com/show_bug.cgi?id=1170764] from NEW to ASSIGNED > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault > ---------------------------------------------------------------------------- > > Key: SECURITY-871 > URL: https://issues.jboss.org/browse/SECURITY-871 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4089) ServletContainerInitializerDeploymentProcessor does not handle comments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4089?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4089: ----------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1165967|https://bugzilla.redhat.com/show_bug.cgi?id=1165967] from POST to MODIFIED > ServletContainerInitializerDeploymentProcessor does not handle comments > ----------------------------------------------------------------------- > > Key: WFLY-4089 > URL: https://issues.jboss.org/browse/WFLY-4089 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.Alpha1 > Reporter: James Livingston > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > > ServletContainerInitializerDeploymentProcessor.loadSci() has code to read the service file, rather than using the JDK-provided mechanisms, and it does not handle comments. > The API documentation at https://docs.oracle.com/javase/7/docs/api/java/util/ServiceLoader.html says that the # symbols and all following characters on the line should be ignored. It also notes the file must be UTF-8 encoded, and ServletContainerInitializerDeploymentProcessor does not appear to force that either. > Log4j 2.1 triggers this bug (https://issues.apache.org/jira/browse/LOG4J2-890) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4149) NamingExceptions not properly handled in InitialContext

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4149?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4149: ----------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1171243|https://bugzilla.redhat.com/show_bug.cgi?id=1171243] from POST to MODIFIED > NamingExceptions not properly handled in InitialContext > ------------------------------------------------------- > > Key: WFLY-4149 > URL: https://issues.jboss.org/browse/WFLY-4149 > Project: WildFly > Issue Type: Bug > Components: Naming > Reporter: David Lloyd > Assignee: Eduardo Martins > Fix For: 9.0.0.Beta1 > > > The change in https://github.com/jbossas/jboss-eap/commit/db525bf1d90a40eb909c8f915fca7... catches all Exception and rewraps them with NamingException. This behavior is undesirable if the original exception was already a NamingException. Catch and re-throw that exception type as-is before wrapping other exceptions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4173) Server side EJB Handler not compression response

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-4173?page=com.atlassian.jira.plugin.... ] Tomas Hofman reassigned WFLY-4173: ---------------------------------- Assignee: Tomas Hofman (was: David Lloyd) > Server side EJB Handler not compression response > ------------------------------------------------ > > Key: WFLY-4173 > URL: https://issues.jboss.org/browse/WFLY-4173 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Tomas Hofman > > When compression is enabled for request/response, the jboss-ejb-client is sending a compressed request, but the application server is responding with an uncompressed response. > On the server enabling TRACE on org.jboss.as.ejb3, we can see the server receives a compressed request > TRACE [org.jboss.as.ejb3] (default task-5) Got message with header 0x1b on channel Channel ID 56b01772 (inbound) of Remoting connection TRACE [org.jboss.as.ejb3.invocation] (default task-5) Received a compressed message stream > Client side, Enabling TRACE on the client side for org.jboss.ejb.client we see it is 0x5 where it should be 0x1b > TRACE org.jboss.ejb.client.remoting.ChannelAssociation - Received message with header 0x5 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4173) Server side EJB Handler not compression response

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4173?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4173: ----------------------------------------------- Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1172856|https://bugzilla.redhat.com/show_bug.cgi?id=1172856] from NEW to ASSIGNED > Server side EJB Handler not compression response > ------------------------------------------------ > > Key: WFLY-4173 > URL: https://issues.jboss.org/browse/WFLY-4173 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: David Lloyd > > When compression is enabled for request/response, the jboss-ejb-client is sending a compressed request, but the application server is responding with an uncompressed response. > On the server enabling TRACE on org.jboss.as.ejb3, we can see the server receives a compressed request > TRACE [org.jboss.as.ejb3] (default task-5) Got message with header 0x1b on channel Channel ID 56b01772 (inbound) of Remoting connection TRACE [org.jboss.as.ejb3.invocation] (default task-5) Received a compressed message stream > Client side, Enabling TRACE on the client side for org.jboss.ejb.client we see it is 0x5 where it should be 0x1b > TRACE org.jboss.ejb.client.remoting.ChannelAssociation - Received message with header 0x5 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

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

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-487?page=com.atlassian.jira.plugin... ] Emmanuel Hugonnet commented on WFCORE-487: ------------------------------------------ This seems to happen mostly on Windows. > 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: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > 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, 7 months

1
0
0 / 0

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

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFCORE-487: ---------------------------------------- Summary: 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: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet 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, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3966) Allow soapFaults to be returned for HTTP_BAD_REQUEST are per SOAP 1.2 spec

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3966?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3966: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1151530|https://bugzilla.redhat.com/show_bug.cgi?id=1151530] from ASSIGNED to MODIFIED > Allow soapFaults to be returned for HTTP_BAD_REQUEST are per SOAP 1.2 spec > -------------------------------------------------------------------------- > > Key: WFLY-3966 > URL: https://issues.jboss.org/browse/WFLY-3966 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Alpha1 > Reporter: Mustafa Musaji > Assignee: Bartosz Baranowski > Attachments: SAAJ-74.patch > > > SOAP 1.2 spec says that HTTP 400 should return a soapFault error. At the moment the code only returns SoapFault for HTTP 500 which is wrong. > The issue is recorded in the SAAJ JIRA: https://java.net/jira/browse/SAAJ-74 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3966) Allow soapFaults to be returned for HTTP_BAD_REQUEST are per SOAP 1.2 spec

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-3966?page=com.atlassian.jira.plugin.... ] Carlo de Wolf closed WFLY-3966. ------------------------------- Resolution: Migrated to another ITS See https://java.net/jira/browse/SAAJ-74 > Allow soapFaults to be returned for HTTP_BAD_REQUEST are per SOAP 1.2 spec > -------------------------------------------------------------------------- > > Key: WFLY-3966 > URL: https://issues.jboss.org/browse/WFLY-3966 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Alpha1 > Reporter: Mustafa Musaji > Assignee: Bartosz Baranowski > Attachments: SAAJ-74.patch > > > SOAP 1.2 spec says that HTTP 400 should return a soapFault error. At the moment the code only returns SoapFault for HTTP 500 which is wrong. > The issue is recorded in the SAAJ JIRA: https://java.net/jira/browse/SAAJ-74 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4192) Upgrade to Saaj 1.3.17+

by Carlo de Wolf (JIRA)

Carlo de Wolf created WFLY-4192: ----------------------------------- Summary: Upgrade to Saaj 1.3.17+ Key: WFLY-4192 URL: https://issues.jboss.org/browse/WFLY-4192 Project: WildFly Issue Type: Component Upgrade Components: Web Services Affects Versions: 9.0.0.Alpha1 Reporter: Carlo de Wolf Assignee: Alessio Soldano Upgrade Saaj to incorporate listed fixes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 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 December 2014