December 2014 - jboss-jira - Jboss List Archives

[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)

10 years

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)

10 years

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)

10 years

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)

10 years

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 updated WFLY-3966: -------------------------------- Attachment: SAAJ-74.patch > 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)

10 years

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 reassigned WFLY-3966: ----------------------------------- Assignee: Bartosz Baranowski (was: Alessio Soldano) > 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 > > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2900) Performance issue with Xalan transformer and very large text nodes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2900?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2900: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1065128, https://bugzilla.redhat.com/show_bug.cgi?id=1175982 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1065128) > Performance issue with Xalan transformer and very large text nodes > ------------------------------------------------------------------ > > Key: WFLY-2900 > URL: https://issues.jboss.org/browse/WFLY-2900 > Project: WildFly > Issue Type: Bug > Components: XML Frameworks > Reporter: Kyle Lape > Assignee: Jason Greene > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > It has been observed that when using the {{Transfomer}} to convert a {{StreamSource}} to {{DOMResult}}, the performance of Transform gets worse as the size of the > character data increases. If you have a 50MB text blob in XML, this will take a very long time to finish. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2900) Performance issue with Xalan transformer and very large text nodes

by Kyle Lape (JIRA)

[ https://issues.jboss.org/browse/WFLY-2900?page=com.atlassian.jira.plugin.... ] Kyle Lape edited comment on WFLY-2900 at 12/18/14 9:40 PM: ----------------------------------------------------------- After reviewing the regresssion in the above BZ, it looks like it was actually caused by the use of the wrong {{TransformerFactoryImpl}}. See: https://bugzilla.redhat.com/show_bug.cgi?id=1087993. It actually looks like this patch was never pulled in to EAP at all. With that in mind, can you look into merging this fix into WF again? was (Author: klape): After reviewing the regresssion in the above BZ, it looks like it was actually caused by the use of the wrong {{TransformerFactoryImpl}}. See: https://bugzilla.redhat.com/show_bug.cgi?id=1087993. With that in mind, can you look into merging this fix into WF again? > Performance issue with Xalan transformer and very large text nodes > ------------------------------------------------------------------ > > Key: WFLY-2900 > URL: https://issues.jboss.org/browse/WFLY-2900 > Project: WildFly > Issue Type: Bug > Components: XML Frameworks > Reporter: Kyle Lape > Assignee: Jason Greene > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > It has been observed that when using the {{Transfomer}} to convert a {{StreamSource}} to {{DOMResult}}, the performance of Transform gets worse as the size of the > character data increases. If you have a 50MB text blob in XML, this will take a very long time to finish. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2900) Performance issue with Xalan transformer and very large text nodes

by Kyle Lape (JIRA)

[ https://issues.jboss.org/browse/WFLY-2900?page=com.atlassian.jira.plugin.... ] Kyle Lape commented on WFLY-2900: --------------------------------- After reviewing the regresssion in the above BZ, it looks like it was actually caused by the use of the wrong {{TransformerFactoryImpl}}. See: https://bugzilla.redhat.com/show_bug.cgi?id=1087993. With that in mind, can you look into merging this fix into WF again? > Performance issue with Xalan transformer and very large text nodes > ------------------------------------------------------------------ > > Key: WFLY-2900 > URL: https://issues.jboss.org/browse/WFLY-2900 > Project: WildFly > Issue Type: Bug > Components: XML Frameworks > Reporter: Kyle Lape > Assignee: Jason Greene > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > It has been observed that when using the {{Transfomer}} to convert a {{StreamSource}} to {{DOMResult}}, the performance of Transform gets worse as the size of the > character data increases. If you have a 50MB text blob in XML, this will take a very long time to finish. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBVFS-200) FileURLConnection fails on relative URLs working on stock Java handler

by Arcadiy Ivanov (JIRA)

[ https://issues.jboss.org/browse/JBVFS-200?page=com.atlassian.jira.plugin.... ] Arcadiy Ivanov commented on JBVFS-200: -------------------------------------- https://github.com/jbossas/jboss-vfs/pull/23 > FileURLConnection fails on relative URLs working on stock Java handler > ---------------------------------------------------------------------- > > Key: JBVFS-200 > URL: https://issues.jboss.org/browse/JBVFS-200 > Project: JBoss VFS > Issue Type: Bug > Components: Release > Affects Versions: 3.2.5.Final > Reporter: Arcadiy Ivanov > Assignee: Tomaz Cerar > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > A URL "file:./target/bundleA.txt" will not be handled appropriately by FileURLConnection resulting in the following exception: > {noformat} > java.lang.IllegalArgumentException: VFS000021: path must not be null > at org.jboss.vfs.VFS.getChild(VFS.java:175) > at org.jboss.vfs.VFS.getChild(VFS.java:163) > at org.jboss.vfs.protocol.FileURLConnection.<init>(FileURLConnection.java:51) > at org.jboss.vfs.protocol.FileURLStreamHandler.openConnection(FileURLStreamHandler.java:38) > at java.net.URL.openConnection(URL.java:972) > at java.net.URL.openStream(URL.java:1038) > at org.jboss.osgi.repository.spi.FileBasedRepositoryStorage.getResourceContent(FileBasedRepositoryStorage.java:225) > at org.jboss.osgi.repository.spi.FileBasedRepositoryStorage.createResourceInternal(FileBasedRepositoryStorage.java:201) > at org.jboss.osgi.repository.spi.FileBasedRepositoryStorage.addContentResource(FileBasedRepositoryStorage.java:140) > at org.jboss.osgi.repository.spi.FileBasedRepositoryStorage.addResourceInternal(FileBasedRepositoryStorage.java:122) > at org.jboss.osgi.repository.spi.FileBasedRepositoryStorage.addResource(FileBasedRepositoryStorage.java:107) > {noformat} > The reason is that in the following code > {noformat} > public static VirtualFile getChild(URI uri) { > return getChild(uri.getPath()); > } > {noformat} > {{uri.getPath()}} will return {{null}} due to URI being constructed from URL not being parsed as hierarchical only evaluating to "scheme-specific-part". > This behavior is different from a stock Java file URL handler that will accept "file:./target/bundleA.txt" and handle it appropriately. > A possible fix would be to call {{uri.getPath()}} first and if that returns {{null}}, fallback onto {{uri.getSchemeSpecificPart()}}. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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