[JBoss JIRA] Commented: (RF-11155) a4j:push In CDI Push sample java.lang.IllegalStateException is thrown randomly and also firebug shows error: abordingConnection is not defined
by Juraj Huska (JIRA)
[ https://issues.jboss.org/browse/RF-11155?page=com.atlassian.jira.plugin.s... ]
Juraj Huska commented on RF-11155:
----------------------------------
The exception is more often thrown at JBoss AS 7.
> a4j:push In CDI Push sample java.lang.IllegalStateException is thrown randomly and also firebug shows error: abordingConnection is not defined
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-11155
> URL: https://issues.jboss.org/browse/RF-11155
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase 4.1.0-Snapshot, containers JBoss AS 6, 7, browsers firefox 3.6, Chrome 12
> Reporter: Juraj Huska
> Assignee: Lukáš Fryč
> Fix For: 4.1.0.Milestone2
>
>
> After while an exception is thrown, it is generated randomly, I notice this exception after some time spent with invoking new consumers, closing some of them, and sending messages to them.
> {code}
> The exception is:
> 13:19:10,997 SEVERE [org.atmosphere.handler.ReflectorServletProcessor] (http-localhost.localdomain-127.0.0.1-8080-2) onRequest(): java.lang.RuntimeException: java.lang.IllegalStateException: Broadcaster ID already assigned to SCOPE.REQUEST. Cannot change the id
> at org.atmosphere.cpr.Meteor.build(Meteor.java:158) [atmosphere-runtime-0.7.1.jar:]
> at org.richfaces.webapp.PushHandlerFilter.doFilter(PushHandlerFilter.java:76) [richfaces-core-impl-4.1.0-20110713.100430-59.jar:]
> at org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:139) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:116) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:294) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:152) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:191) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:142) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:91) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1185) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1167) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1153) [atmosphere-runtime-0.7.1.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.AS7.jar:2011-07-06 12:26]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.0.Final.jar:7.0.0.Final]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.0.Final.jar:7.0.0.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
> Caused by: java.lang.IllegalStateException: Broadcaster ID already assigned to SCOPE.REQUEST. Cannot change the id
> at org.atmosphere.cpr.DefaultBroadcaster.setID(DefaultBroadcaster.java:198) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.DefaultBroadcaster.<init>(DefaultBroadcaster.java:109) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.DefaultBroadcaster.<init>(DefaultBroadcaster.java:102) [atmosphere-runtime-0.7.1.jar:]
> at sun.reflect.GeneratedConstructorAccessor50.newInstance(Unknown Source) [:1.6.0_22]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_22]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_22]
> at java.lang.Class.newInstance0(Class.java:355) [:1.6.0_22]
> at java.lang.Class.newInstance(Class.java:308) [:1.6.0_22]
> at org.atmosphere.cpr.DefaultBroadcasterFactory.get(DefaultBroadcasterFactory.java:125) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.Meteor.build(Meteor.java:156) [atmosphere-runtime-0.7.1.jar:]
> ... 30 more
> {code}
> There is also an error showed by firebug when any of the consumer window is closed.
> The error is: abordingConnection is not defined
> {code}
> if (abordingConnection) return;
> and code line is 182 in jquery-atmosphere.js
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Issue Comment Edited: (RF-11155) a4j:push In CDI Push sample java.lang.IllegalStateException is thrown randomly and also firebug shows error: abordingConnection is not defined
by Juraj Huska (JIRA)
[ https://issues.jboss.org/browse/RF-11155?page=com.atlassian.jira.plugin.s... ]
Juraj Huska edited comment on RF-11155 at 8/17/11 10:37 AM:
------------------------------------------------------------
The exception is far more often thrown at JBoss AS 7.
was (Author: jhuska):
The exception is more often thrown at JBoss AS 7.
> a4j:push In CDI Push sample java.lang.IllegalStateException is thrown randomly and also firebug shows error: abordingConnection is not defined
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-11155
> URL: https://issues.jboss.org/browse/RF-11155
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase 4.1.0-Snapshot, containers JBoss AS 6, 7, browsers firefox 3.6, Chrome 12
> Reporter: Juraj Huska
> Assignee: Lukáš Fryč
> Fix For: 4.1.0.Milestone2
>
>
> After while an exception is thrown, it is generated randomly, I notice this exception after some time spent with invoking new consumers, closing some of them, and sending messages to them.
> {code}
> The exception is:
> 13:19:10,997 SEVERE [org.atmosphere.handler.ReflectorServletProcessor] (http-localhost.localdomain-127.0.0.1-8080-2) onRequest(): java.lang.RuntimeException: java.lang.IllegalStateException: Broadcaster ID already assigned to SCOPE.REQUEST. Cannot change the id
> at org.atmosphere.cpr.Meteor.build(Meteor.java:158) [atmosphere-runtime-0.7.1.jar:]
> at org.richfaces.webapp.PushHandlerFilter.doFilter(PushHandlerFilter.java:76) [richfaces-core-impl-4.1.0-20110713.100430-59.jar:]
> at org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:139) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:116) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:294) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:152) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:191) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:142) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:91) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1185) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1167) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1153) [atmosphere-runtime-0.7.1.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.AS7.jar:2011-07-06 12:26]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.0.Final.jar:7.0.0.Final]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.0.Final.jar:7.0.0.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
> Caused by: java.lang.IllegalStateException: Broadcaster ID already assigned to SCOPE.REQUEST. Cannot change the id
> at org.atmosphere.cpr.DefaultBroadcaster.setID(DefaultBroadcaster.java:198) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.DefaultBroadcaster.<init>(DefaultBroadcaster.java:109) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.DefaultBroadcaster.<init>(DefaultBroadcaster.java:102) [atmosphere-runtime-0.7.1.jar:]
> at sun.reflect.GeneratedConstructorAccessor50.newInstance(Unknown Source) [:1.6.0_22]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_22]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_22]
> at java.lang.Class.newInstance0(Class.java:355) [:1.6.0_22]
> at java.lang.Class.newInstance(Class.java:308) [:1.6.0_22]
> at org.atmosphere.cpr.DefaultBroadcasterFactory.get(DefaultBroadcasterFactory.java:125) [atmosphere-runtime-0.7.1.jar:]
> at org.atmosphere.cpr.Meteor.build(Meteor.java:156) [atmosphere-runtime-0.7.1.jar:]
> ... 30 more
> {code}
> There is also an error showed by firebug when any of the consumer window is closed.
> The error is: abordingConnection is not defined
> {code}
> if (abordingConnection) return;
> and code line is 182 in jquery-atmosphere.js
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Commented: (RF-11156) a4j:push Performance problem in CDI sample of push in showcase
by Juraj Huska (JIRA)
[ https://issues.jboss.org/browse/RF-11156?page=com.atlassian.jira.plugin.s... ]
Juraj Huska commented on RF-11156:
----------------------------------
Some performance tips I have found:
- Start the consumer before you start the producer so that the initial messages do not need to queue.
- Use a ConnectionConsumer to process messages concurrently with a ServerSessionPool.
- Close resources (e.g. connections, session objects, producers, consumers) when finished with them.
- DUPS_OK_ACKNOWLEDGE and AUTO_ACKNOWLEDGE perform better than CLIENT_ACKNOWLEDGE.
- Use separate transactional sessions and non-transactional sessions for transactional and non-transactional messages.
- Tune the Destination parameters: a smaller capacity increases message throughput; a higher redelivery delay and lower redelivery limit reduces the overhead.
- Choose non-durable (NON_PERSISTENT) messages wherever appropriate to avoid the persistency overhead.
- Set the TimeToLive value as low as feasible (default is for messages to never expire).
- Receive messages asynchronously with a MessageListener implementation.
- Choose the message type that minimizes memory overheads.
- Use 'transient' variables to reduce serialization overheads.
> a4j:push Performance problem in CDI sample of push in showcase
> --------------------------------------------------------------
>
> Key: RF-11156
> URL: https://issues.jboss.org/browse/RF-11156
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase 4.1.0-Snapshot, containers - JBoss AS 6 and 7
> Reporter: Juraj Huska
> Assignee: Juraj Huska
> Fix For: 4.1.0.Milestone2
>
>
> When there is more than 5 consumers windows, it causes performance problems(take up to 20 seconds to render message on consumer), at least from the beginning, after some messsages like 3-4 the performance is improved on AS 7.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Commented: (RF-11156) a4j:push Performance problem in CDI sample of push in showcase
by Juraj Huska (JIRA)
[ https://issues.jboss.org/browse/RF-11156?page=com.atlassian.jira.plugin.s... ]
Juraj Huska commented on RF-11156:
----------------------------------
Another thing I noticed is that on Chrome (I am using 12), the maximal number of consumers when the performance is good is 6, instead of 5.
> a4j:push Performance problem in CDI sample of push in showcase
> --------------------------------------------------------------
>
> Key: RF-11156
> URL: https://issues.jboss.org/browse/RF-11156
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase 4.1.0-Snapshot, containers - JBoss AS 6 and 7
> Reporter: Juraj Huska
> Assignee: Juraj Huska
> Fix For: 4.1.0.Milestone2
>
>
> When there is more than 5 consumers windows, it causes performance problems(take up to 20 seconds to render message on consumer), at least from the beginning, after some messsages like 3-4 the performance is improved on AS 7.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Commented: (RF-11156) a4j:push Performance problem in CDI sample of push in showcase
by Juraj Huska (JIRA)
[ https://issues.jboss.org/browse/RF-11156?page=com.atlassian.jira.plugin.s... ]
Juraj Huska commented on RF-11156:
----------------------------------
When the number of consumers exceeds 5 on either local or remote machine the performance problem is noticeable. The number of clients on remote client or on local client does not affect each other performance. It means when the performance is bad on my local machine due to more than 5 consumers, the performance is good on remote machine till there is also more than 5 consumers. Therefore it looks like the problem is on the client side.
> a4j:push Performance problem in CDI sample of push in showcase
> --------------------------------------------------------------
>
> Key: RF-11156
> URL: https://issues.jboss.org/browse/RF-11156
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase 4.1.0-Snapshot, containers - JBoss AS 6 and 7
> Reporter: Juraj Huska
> Assignee: Juraj Huska
> Fix For: 4.1.0.Milestone2
>
>
> When there is more than 5 consumers windows, it causes performance problems(take up to 20 seconds to render message on consumer), at least from the beginning, after some messsages like 3-4 the performance is improved on AS 7.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Commented: (RF-11156) a4j:push Performance problem in CDI sample of push in showcase
by Juraj Huska (JIRA)
[ https://issues.jboss.org/browse/RF-11156?page=com.atlassian.jira.plugin.s... ]
Juraj Huska commented on RF-11156:
----------------------------------
On this configuration the number of consumers is more than five, although on different machines, and the behavior is not noticeable, in other word run smoothly
5 consumers are invoked on my local machine and 5 on the remote machine
same configurations of the JBoss AS 7 server
> a4j:push Performance problem in CDI sample of push in showcase
> --------------------------------------------------------------
>
> Key: RF-11156
> URL: https://issues.jboss.org/browse/RF-11156
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase 4.1.0-Snapshot, containers - JBoss AS 6 and 7
> Reporter: Juraj Huska
> Assignee: Juraj Huska
> Fix For: 4.1.0.Milestone2
>
>
> When there is more than 5 consumers windows, it causes performance problems(take up to 20 seconds to render message on consumer), at least from the beginning, after some messsages like 3-4 the performance is improved on AS 7.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Issue Comment Edited: (RF-11156) a4j:push Performance problem in CDI sample of push in showcase
by Juraj Huska (JIRA)
[ https://issues.jboss.org/browse/RF-11156?page=com.atlassian.jira.plugin.s... ]
Juraj Huska edited comment on RF-11156 at 8/17/11 10:19 AM:
------------------------------------------------------------
The behavior is noticeable on this configurations, the type of the container is not important, behave same on all of them:
All consumers are invoked from one machine
JBoss 7 with: JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m
host and client on my local machine with 3 GB RAM, CPU: 4 cores, Intel Core i5 M540 2.53Ghz
host on my local machine, client on remote machine with 3.8 GB RAM, CPU 4 cores, 2.7 GHz each
JBoss 7 with: JAVA_OPTS: -server -Xms512m -Xmx1024m -XX:MaxPermSize=256m
same hosts and clients configurations as mentioned above
was (Author: jhuska):
The behavior is noticeable on this configurations, the type of the container is not important, behave same on all of them:
- All consumers are invoked from one machine
JBoss 7 with: JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m
host and client on my local machine with 3 GB RAM, CPU: 4 cores, Intel Core i5 M540 2.53Ghz
host on my local machine, client on remote machine with 3.8 GB RAM, CPU 4 cores, 2.7 GHz each
JBoss 7 with: JAVA_OPTS: -server -Xms512m -Xmx1024m -XX:MaxPermSize=256m
same hosts and clients configurations as mentioned above
> a4j:push Performance problem in CDI sample of push in showcase
> --------------------------------------------------------------
>
> Key: RF-11156
> URL: https://issues.jboss.org/browse/RF-11156
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase 4.1.0-Snapshot, containers - JBoss AS 6 and 7
> Reporter: Juraj Huska
> Assignee: Juraj Huska
> Fix For: 4.1.0.Milestone2
>
>
> When there is more than 5 consumers windows, it causes performance problems(take up to 20 seconds to render message on consumer), at least from the beginning, after some messsages like 3-4 the performance is improved on AS 7.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Commented: (RF-11156) a4j:push Performance problem in CDI sample of push in showcase
by Juraj Huska (JIRA)
[ https://issues.jboss.org/browse/RF-11156?page=com.atlassian.jira.plugin.s... ]
Juraj Huska commented on RF-11156:
----------------------------------
The behavior is noticeable on this configurations, the type of the container is not important, behave same on all of them:
- All consumers are invoked from one machine
JBoss 7 with: JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m
host and client on my local machine with 3 GB RAM, CPU: 4 cores, Intel Core i5 M540 2.53Ghz
host on my local machine, client on remote machine with 3.8 GB RAM, CPU 4 cores, 2.7 GHz each
JBoss 7 with: JAVA_OPTS: -server -Xms512m -Xmx1024m -XX:MaxPermSize=256m
same hosts and clients configurations as mentioned above
> a4j:push Performance problem in CDI sample of push in showcase
> --------------------------------------------------------------
>
> Key: RF-11156
> URL: https://issues.jboss.org/browse/RF-11156
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase 4.1.0-Snapshot, containers - JBoss AS 6 and 7
> Reporter: Juraj Huska
> Assignee: Juraj Huska
> Fix For: 4.1.0.Milestone2
>
>
> When there is more than 5 consumers windows, it causes performance problems(take up to 20 seconds to render message on consumer), at least from the beginning, after some messsages like 3-4 the performance is improved on AS 7.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months