[JBoss JIRA] (WFLY-2900) Performance issue with Xalan transformer and very large text nodes
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2900?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2900:
-------------------------------
Fix Version/s: 8.2.0.CR1
(was: 8.1.0.Final)
> 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
> Security Level: Public(Everyone can see)
> Components: XML Frameworks
> Reporter: Kyle Lape
> Assignee: Jason Greene
> Priority: Blocker
> Fix For: 8.2.0.CR1
>
>
> 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.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-3345) Compilation error in clustering/web/infinispan w/ JDK 8u20 and Windows
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-3345?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-3345:
-------------------------------
Fix Version/s: 8.2.0.CR1
(was: 8.1.0.Final)
(was: 9.0.0.Alpha1)
> Compilation error in clustering/web/infinispan w/ JDK 8u20 and Windows
> ----------------------------------------------------------------------
>
> Key: WFLY-3345
> URL: https://issues.jboss.org/browse/WFLY-3345
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.1.0.CR2
> Reporter: Juergen Zimmermann
> Assignee: Paul Ferraro
> Priority: Blocker
> Fix For: 8.2.0.CR1
>
>
> In clustering/web/infinispan/src/main/java/org/wildfly/clustering/web/infinispan/session/SimpleImmutableSessionAttributes.java I'm getting the following compilation error which IMHO is also a logical error:
> {code}
> [ERROR] /C:/temp/wildfly-8.1.0.CR2/clustering/web/infinispan/src/main/java/org/wildfly/clustering/web/infinispan/session/SimpleImmutableSessionAttributes.java:[42,17] variable attributes might not have been initialized
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-80) Product Version should not prepend product name with JBoss
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-80?page=com.atlassian.jira.plugin.sy... ]
Jason Greene updated WFLY-80:
-----------------------------
Fix Version/s: 9.0.0.CR1
(was: 8.1.0.Final)
> Product Version should not prepend product name with JBoss
> ----------------------------------------------------------
>
> Key: WFLY-80
> URL: https://issues.jboss.org/browse/WFLY-80
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Server
> Reporter: NadirX
> Assignee: Jason Greene
> Priority: Minor
> Fix For: 9.0.0.CR1
>
>
> version/src/main/java/org/jboss/as/version/ProductConfig.java prepends the Product Name with 'JBoss' which is inappropriate for community projects. The result is that at startup I get the following
> "INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss Infinispan Server 5.3.0-SNAPSHOT (AS 7.2.0.Final) started in 3059ms"
> where instead I should see
> "INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: Infinispan Server 5.3.0-SNAPSHOT (AS 7.2.0.Final) started in 3059ms"
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-3402) Patch upload in console does not work
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-3402?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-3402:
-------------------------------
Fix Version/s: 8.2.0.CR1
(was: 8.1.0.Final)
> Patch upload in console does not work
> -------------------------------------
>
> Key: WFLY-3402
> URL: https://issues.jboss.org/browse/WFLY-3402
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.1.0.CR2
> Reporter: Emanuel Muckenhuber
> Assignee: Emanuel Muckenhuber
> Priority: Critical
> Fix For: 8.2.0.CR1
>
>
> The domain http upload handler behaves a bit different than the version in EAP and the way the console uploads streams does not work in upstream. We probably should just change it to the way EAP processes requests.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-1895) Provide a "default" role for management users with no other role specified
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-1895?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-1895:
-------------------------------
Fix Version/s: 8.2.0.CR1
(was: 8.1.0.Final)
> Provide a "default" role for management users with no other role specified
> --------------------------------------------------------------------------
>
> Key: WFLY-1895
> URL: https://issues.jboss.org/browse/WFLY-1895
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Domain Management, Security
> Reporter: Jakub Cechacek
> Assignee: Emanuel Muckenhuber
> Labels: rbac-filed-by-qa
> Fix For: 8.2.0.CR1
>
>
> Currently it seems that when using RBAC provider users with no defined role are unable to read domain model at all. Consequently logging into Admin Console leads to 500 error page. Similar errors in CLI.
> In relation to this, it should be considered what is the expected behavior of unsecured management interface.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-343) lower messaging's min-large-message-size value in standalone-full.xml
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-343?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-343:
------------------------------
Fix Version/s: 8.2.0.CR1
(was: 8.1.0.Final)
> lower messaging's min-large-message-size value in standalone-full.xml
> ---------------------------------------------------------------------
>
> Key: WFLY-343
> URL: https://issues.jboss.org/browse/WFLY-343
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 8.2.0.CR1
>
>
> AS7's messaging subsystem defines 2 attributes:
> journal-file-size => 10MiB
> min-large-message-size => 100KiB
> However, for startup performance issue, the standalone-full.xml sets the journal-file-size at 1OOKiB. This leads to issues since it's the same value than the min-large-message-size.
> If we want to keep a low journal-file-size value in standalone-full.xml, the min-large-message-size must also bet set appropriately (eg 75KiB?)
> For production use, however, we should suggest to the users to remove the journal-file-size and min-large-message-size from standalone-full.xml to use the default values (resp. 10MiB & 100KiB)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-368) Naming subsystem <lookup> could use LinkRef/Reference
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-368?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-368:
------------------------------
Fix Version/s: 8.2.0.CR1
(was: 8.1.0.Final)
> Naming subsystem <lookup> could use LinkRef/Reference
> -----------------------------------------------------
>
> Key: WFLY-368
> URL: https://issues.jboss.org/browse/WFLY-368
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Naming
> Reporter: James Livingston
> Assignee: Eduardo Martins
> Fix For: 8.2.0.CR1
>
>
> NameBindingAdd.installLookup() sets up the machinery so that when Context.lookup() is done it looks up the redirected name and returns it.
> It should be possible to do that by binding a LinkRef, Reference or similar object into JNDI instead.
> Where this could make a difference is when Context.lookupLink() is called instead.
> Currently if you have
> <simple name="java:/v" value="hello"/>
> <lookup name="java:/a" lookup="java:/b"/>
> lookupLink("java:/a") will return "hello" rather a LinkRef/Reference/whatever pointing to java:/b.
> We need to decide whether a <lookup> should be considered a "link" for the purposes of lookup() or not. If it should be considered one, then we should change NameBindingAdd.installLookup() to make lookupLink() return the other value.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-2893) Determine cause of unreported test failures
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2893?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2893:
-------------------------------
Fix Version/s: 8.2.0.CR1
(was: 8.1.0.Final)
> Determine cause of unreported test failures
> -------------------------------------------
>
> Key: WFLY-2893
> URL: https://issues.jboss.org/browse/WFLY-2893
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, Test Suite
> Affects Versions: 8.0.0.CR1
> Reporter: Brian Stansberry
> Assignee: Tomaz Cerar
> Fix For: 8.2.0.CR1
>
>
> Identify the reason why the failing tests that needed https://github.com/wildfly/wildfly/commit/90643bc435a9ba439cf2988e5b7407d... to get working did not fail the build. Those tests were failing for 2.5 months. Fortunately it was just a test problem, not a broken feature.
> They involved separate surefire executions. We want to avoid those, but sometimes they are needed to use different config files. We have separate executions in testsuite/integration/basic as well, covering a much broader scope, so if this kind of problem happened there as well we could have a big problem.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months