[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)
11 years, 7 months
[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)
11 years, 7 months
[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 edited comment on JBVFS-200 at 12/18/14 8:15 PM:
----------------------------------------------------------------
PR: https://github.com/jbossas/jboss-vfs/pull/23
was (Author: arcivanov):
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)
11 years, 7 months
[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 updated JBVFS-200:
---------------------------------
Workaround Description: (was: This is not really a workaround but URL of type file://./target/bundleA.txt would be parsed by URI constructor as hierarchical and would have getPath(). So if the URL format can be mandated externally, the use of the authority section "//" can be used to get around this bug.)
Workaround: (was: Workaround Exists)
> 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)
11 years, 7 months
[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 updated JBVFS-200:
---------------------------------
Description:
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()}}.
was:
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}}.
This behavior is different from a stock Java file URL handler that will accept "file:./target/bundleA.txt" and handle appropriately.
A possible workaround would be to call {{uri.getPath()}} first and if that returns {{null}}, fallback onto {{uri.getSchemeSpecificPart()}}.
> 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)
11 years, 7 months
[JBoss JIRA] (JBVFS-200) FileURLConnection fails on relative URLs working on stock Java handler
by Arcadiy Ivanov (JIRA)
Arcadiy Ivanov created JBVFS-200:
------------------------------------
Summary: 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
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}}.
This behavior is different from a stock Java file URL handler that will accept "file:./target/bundleA.txt" and handle appropriately.
A possible workaround 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)
11 years, 7 months