[JBoss JIRA] (JBWEB-236) JSF Mojarra has serious performance issues, add MyFaces integration
by Adrian Everett (JIRA)
Adrian Everett created JBWEB-236:
------------------------------------
Summary: JSF Mojarra has serious performance issues, add MyFaces integration
Key: JBWEB-236
URL: https://issues.jboss.org/browse/JBWEB-236
Project: JBoss Web
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Core
Affects Versions: JBossWeb-7.0.13.GA
Environment: JBoss 7.1.1 AS, Windows 7 64 bit
Reporter: Adrian Everett
Assignee: Remy Maucherat
Please add MyFaces support to JBoss AS7 as an alternative to JSF Mojarra, because Mojarra has serious performance issues.
For large data sets, a really bad JSF performance issue regarding AJAX requests has been identified. An issue ticket was created for this on the Mojarra issues tracker, but it might be quite a long time before they fix it, if it ever does get fixed.
Here is the link:
http://java.net/jira/browse/JAVASERVERFACES-2334
For every large data sets, the performance of a simple f:ajax calls slows down to the point it becomes as slow as a full page post. An f:ajax call passing 300 bytes of data could take 3+ seconds to perform a round trip, where the same exact f:ajax call might only take a 200ms if the page is smaller. The only difference between the big page and the small page might be several thousand h:outputText components that have no relation with the component associated with the f:ajax call.
This is a serious problem for a site such as the one I'm working on, where we sometimes have to load large amounts of data in an un-paginated manner, and also perform AJAX requests on the same page.
I took the example code attached to the Mojarra ticket and will be attaching it to this one. I have verified that it causes the problem by running the code on JBoss AS, the latest Glassfish server and even Tomcat. The problem isn't with JBoss, it's with the Mojarra implementation of JSF, so support for MyFaces would greatly benefit projects with large data sets.
Finally, as seen in the Mojarra ticket, the author of the PrimeFaces component library has also performed some tests with the attached code and found that the MyFaces JSF stack doesn't have the problem. His comments can be seen in the reference ticket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBRULES-3670) ClassNotFound on class declared in drl file
by Willem van Asperen (JIRA)
Willem van Asperen created JBRULES-3670:
-------------------------------------------
Summary: ClassNotFound on class declared in drl file
Key: JBRULES-3670
URL: https://issues.jboss.org/browse/JBRULES-3670
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.5.0.CR1
Environment: linux
Reporter: Willem van Asperen
Assignee: Mark Proctor
I compile a .drl file and save it as object in .drl.compiled file.
Loading that file does not work if I use insert() or retract() facts that are of a type declared in the .drl file.
The way to circumvent this is to use the full class name in the insert, like this:
insert(new vcm.planner.lock.standard.PossibleSlotLock($ship, $chamber,
$side, $schedule, $eta, $schedule.getTick(), "existing"));
And cast the variable to the full class name, like this:
rule "clean up possible slot lock, when no longer to schedule"
when
$p : PossibleSlotLock( $ship; )
not ToScheduleLock( mover == $ship )
then
retract( (vcm.planner.lock.standard.PossibleSlotLock)$p );
end
This did work in 5.4.0.Final.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBMETA-362) noop property replacer used for some env entries
by Stuart Douglas (JIRA)
Stuart Douglas created JBMETA-362:
-------------------------------------
Summary: noop property replacer used for some env entries
Key: JBMETA-362
URL: https://issues.jboss.org/browse/JBMETA-362
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 7.0.4
Reporter: Stuart Douglas
Assignee: Stuart Douglas
Fix For: 7.0.5
Some env entry parses are just using a noop property replacer, instead of using the one the AS passed in.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (AS7-5627) Scripts need to preserve arguments boundary
by Cheng Fang (JIRA)
Cheng Fang created AS7-5627:
-------------------------------
Summary: Scripts need to preserve arguments boundary
Key: AS7-5627
URL: https://issues.jboss.org/browse/AS7-5627
Project: Application Server 7
Issue Type: Bug
Components: Scripts
Affects Versions: 7.2.0.Alpha1
Reporter: Cheng Fang
Assignee: Brian Stansberry
When certain args are passed to jboss module Main class, they lost their orginal boundary, and jboss module can only tell one from another using space as the delimiter. For example:
standalone.sh -Dtitle="Vice President"
{noformat}
23:37:10,229 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.3.GA
JBAS015801: Invalid option 'President'Usage: ./domain.sh [args...]
where args include:
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (AS7-5845) Uninstalling the arquilllian-service does not remove the associate MBeans
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5845:
-----------------------------------
Summary: Uninstalling the arquilllian-service does not remove the associate MBeans
Key: AS7-5845
URL: https://issues.jboss.org/browse/AS7-5845
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
As a result you cannot run an ARQ test multiple times against an already running server
{code}
14:23:24,838 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.arquillian.testrunner: org.jboss.msc.service.StartException in service jboss.arquillian.testrunner: Failed to start Arquillian Test Runner
at org.jboss.as.arquillian.service.ArquillianService.start(ArquillianService.java:102)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
Caused by: javax.management.InstanceAlreadyExistsException: jboss.arquillian:service=jmx-test-runner
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453) [rt.jar:1.6.0_33]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484) [rt.jar:1.6.0_33]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963) [rt.jar:1.6.0_33]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) [rt.jar:1.6.0_33]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) [rt.jar:1.6.0_33]
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) [rt.jar:1.6.0_33]
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.java:550) [jboss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years