[JBoss JIRA] Updated: (RF-11154) JMS connection is left opened in showcase JMSMessageProducer.java on JBoss AS 7
by Jay Balunas (JIRA)
[ https://issues.jboss.org/browse/RF-11154?page=com.atlassian.jira.plugin.s... ]
Jay Balunas updated RF-11154:
-----------------------------
Component/s: component-push/poll
> JMS connection is left opened in showcase JMSMessageProducer.java on JBoss AS 7
> -------------------------------------------------------------------------------
>
> Key: RF-11154
> URL: https://issues.jboss.org/browse/RF-11154
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll, examples
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase 4.1.0.-SNAPSHOT, container JBoss AS 7.0.0.Final
> Reporter: Juraj Huska
> Assignee: Lukáš Fryč
> Fix For: 4.1.0.Milestone2
>
>
> When I am deploying showcase multiple times during running test suite(this multiple deployment is needed in Arquillian, since for every test class is application deployed again), I am encountering with java.lang.OutOfMemoryError: PermGen space error which in my opinion caused by this:
> {code}
> WARN [org.hornetq.jms.client.HornetQConnection] (Finalizer) I'm closing a JMS connection you left open. Please make sure you close all JMS connections explicitly before letting them go out of scope!
> 13:03:33,712 WARN [org.hornetq.jms.client.HornetQConnection] (Finalizer) The JMS connection you didn't close was created here:: java.lang.Exception
> at org.hornetq.jms.client.HornetQConnection.<init>(HornetQConnection.java:152)
> at org.hornetq.jms.client.HornetQTopicConnection.<init>(HornetQTopicConnection.java:35)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:682)
> at org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:145)
> at org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:140)
> at org.richfaces.demo.push.JMSMessageProducer.initializeMessaging(JMSMessageProducer.java:86)
> at org.richfaces.demo.push.JMSMessageProducer.sendMessage(JMSMessageProducer.java:66)
> at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57)
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
> {code}
> When I am deploying showcase.war which is without Push example(4.0.0.Final), so no JMS communication is opened, no Perm Gen error is thrown.
--
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 Jay Balunas (JIRA)
[ https://issues.jboss.org/browse/RF-11156?page=com.atlassian.jira.plugin.s... ]
Jay Balunas commented on RF-11156:
----------------------------------
Juraj - can you describe the setup you have? Is it one machine running all of this? Do you have separate servers and clients? Are the machine limited in some way ( RAM, CPU, etc... )?
Please assign back to Lukas after you have updated.
> 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: Lukáš Fryč
> 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] Created: (RF-11222) Pick List - showButton attribute
by Jan Papousek (JIRA)
Pick List - showButton attribute
--------------------------------
Key: RF-11222
URL: https://issues.jboss.org/browse/RF-11222
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Milestone1
Environment: * RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc
* Metamer 4.1.0-SNAPSHOT r.22608
* Mojarra 2.0.4-b09
* Apache Tomcat 6.0.32
* OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
* Firefox 3.6.19 @ Linux i686 (x86_64)
Reporter: Jan Papousek
When the attribute *showButton* is set to *false*, the buttons are still displayed.
--
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] Created: (RF-11177) OrderingList: disabling moving buttons when the items can't be moved
by Jan Papousek (JIRA)
OrderingList: disabling moving buttons when the items can't be moved
--------------------------------------------------------------------
Key: RF-11177
URL: https://issues.jboss.org/browse/RF-11177
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0-SNAPSHOT r.
Metamer 4.1.0-SNAPSHOT r.22594
Mojarra 2.0.4-b09-jbossorg-4
JBoss Web 7.0.0.CR4
OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
Firefox 5.0 @ Linux x86_64
Reporter: Jan Papousek
When the item is moved to the first position in the list, the "First" and "Up" button should be disabled. User has to refocused the item to make the button disabled. It's the same with moving the item to the last position.
--
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] Created: (RF-11311) Ordering List - attribute showButton
by Jan Papousek (JIRA)
Ordering List - attribute showButton
------------------------------------
Key: RF-11311
URL: https://issues.jboss.org/browse/RF-11311
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0.20110805-M1 r.10246d45dddd1d2aa2034317d5a832394cc919f9
Metamer 4.1.0.20110805-M1 r.22604
Mojarra 2.0.4-b09
Apache Tomcat 6.0.32
OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
Firefox 5.0 @ Linux x86_64
Reporter: Jan Papousek
When the attribute _showButton_ is set to false, all buttons are present.
--
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] Created: (RF-11316) Improve the data model handling in select components
by Brian Leathem (JIRA)
Improve the data model handling in select components
----------------------------------------------------
Key: RF-11316
URL: https://issues.jboss.org/browse/RF-11316
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: component-selects
Affects Versions: 4.1.0.Milestone1
Reporter: Brian Leathem
Assignee: Brian Leathem
Fix For: 4.1.0.Milestone2
The Pick and Ordering list store their clientSelectItem values in a value attribute of the <tr> or <span> element that lists them.
The Select and InPlaceSelect use the clientSelectItems passed through as a script option, but loop over the list for every loookup.
Consolidate and improve these approaches by using the clientSelectItems script option, but make use of the jQuery#data() method to store the values in the DOM elements during component initialization.
--
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] Created: (RF-10987) Improve GraphValidator performance
by Alexander Smirnov (JIRA)
Improve GraphValidator performance
----------------------------------
Key: RF-10987
URL: https://issues.jboss.org/browse/RF-10987
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-validators
Affects Versions: 4.0.0.Final
Reporter: Alexander Smirnov
Assignee: Alexander Smirnov
ClonedObjectResolver became performance bootleneck.
We have a very simple page that displays a rich:datatable. We noticed that on the backend ClonedObjectResolver.resolveCloned gets called a lot and is very slow. Looking at the method (code below) I think the issue is that it scans the request map every time and looks for a graph prefix validator. If we comment this code out the performance improves 50%. The main question is what is it trying to do and is this only needed in some specific situations like a particular component on the page?
{code}
public static Object resolveCloned(ELContext context, Object base, Object property){
if(null != base || null != property){
FacesContext facesContext = FacesContext.getCurrentInstance();
Map<String, Object> requestMap = facesContext.getExternalContext().getRequestMap();
for (String key : requestMap.keySet()) {
if(null != key && key.startsWith(UIGraphValidator.STATE_ATTRIBUTE_PREFIX)){
UIGraphValidator.GraphValidatorState state = (GraphValidatorState) requestMap.get(key);
if(state.isSame(base, property)){
return state.getCloned();
}
}
}
}
return null;
}
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months