June 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12656) fileUpload doesn't work with filenames containing spaces

by Raul Piaggio (JIRA)

[ https://issues.jboss.org/browse/RF-12656?page=com.atlassian.jira.plugin.s... ] Raul Piaggio commented on RF-12656: ----------------------------------- I stumbled upon the same bug. The problem happens when there is an "acceptedTypes" attributes in the "rich:fileUpload" control, and one attempts to upload a file with an allowed extension, but with a space right before the extension. It is treated as an invalid extension. > fileUpload doesn't work with filenames containing spaces > -------------------------------------------------------- > > Key: RF-12656 > URL: https://issues.jboss.org/browse/RF-12656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 3.3.3.Final > Reporter: Domenique Tilleuil > Fix For: 3.Future > > > The fileUpload component doesn't accept filenames with trailing whitespaces. > I've tested it on the richfaces showcase application: > http://showcase-rf3.richfaces.org/richfaces/fileUpload.jsf?c=fileUpload&t... > * uploading a file with "test .jpg" fails because the file format is not allowed. > * uploading a file with "test with spaces.jpg" works however. > This issue is not reproducible in richfaces 4.0.0 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12899) Deadlock appears in push component

by Nicola Nick (JIRA)

[ https://issues.jboss.org/browse/RF-12899?page=com.atlassian.jira.plugin.s... ] Nicola Nick commented on RF-12899: ---------------------------------- Lukas, I have a Web Application that used the push mechanism. With the last grow up of user from 10 to 50 user the lock appears systematically after 1 day of use. The web app is used 24-7-365 and i want to minimize the restart due to this lock. There is some hack out of the richfaces release flow that you can suggest me. Thank you in advance. Nicola. > Deadlock appears in push component > ---------------------------------- > > Key: RF-12899 > URL: https://issues.jboss.org/browse/RF-12899 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.2.Final > Reporter: Jiří Mikulášek > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Our application freezes occasionally. We used Jstack and have seen the deadlock below. It seems to be very simillar to RF-12013, but the stack is slightly different > Found one Java-level deadlock: > ============================= > {code} > "localhost-startStop-2": > waiting to lock monitor 0x000000000782a368 (object 0x000000078da957e0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "http-nio-30085-exec-4" > "http-nio-30085-exec-4": > waiting to lock monitor 0x00000000085cbe00 (object 0x000000078e8ecf90, a org.atmosphere.cpr.AtmosphereResourceImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x000000000782a368 (object 0x000000078da957e0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "http-nio-30085-exec-4" > {code} > Java stack information for the threads listed above: > =================================================== > {code} > "localhost-startStop-2": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x000000078da957e0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:128) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:136) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:658) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:607) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:591) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:187) > - locked <0x000000078e8b64a8> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at org.atmosphere.cpr.DefaultBroadcaster.resumeAll(DefaultBroadcaster.java:300) > - locked <0x000000078e8d1ac8> (a java.util.concurrent.ConcurrentLinkedQueue) > at org.atmosphere.cpr.DefaultBroadcasterFactory.destroy(DefaultBroadcasterFactory.java:274) > - locked <0x000000078cb112d8> (a org.atmosphere.cpr.DefaultBroadcasterFactory) > at org.atmosphere.cpr.AtmosphereServlet.destroy(AtmosphereServlet.java:867) > at org.atmosphere.cpr.MeteorServlet.destroy(MeteorServlet.java:88) > at org.apache.catalina.core.StandardWrapper.unload(StandardWrapper.java:1481) > - locked <0x0000000784b6a168> (a org.apache.catalina.core.StandardWrapper) > at org.apache.catalina.core.StandardWrapper.stopInternal(StandardWrapper.java:1842) > - locked <0x0000000784b6a168> (a org.apache.catalina.core.StandardWrapper) > at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) > - locked <0x0000000784b6a168> (a org.apache.catalina.core.StandardWrapper) > at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5471) > - locked <0x000000078312e828> (a org.apache.catalina.core.StandardContext) > at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) > - locked <0x000000078312e828> (a org.apache.catalina.core.StandardContext) > at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1575) > at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1564) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > "http-nio-30085-exec-4": > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:168) > - waiting to lock <0x000000078e8ecf90> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at org.atmosphere.cpr.Meteor.resume(Meteor.java:240) > at org.richfaces.application.push.impl.RequestImpl.resume(RequestImpl.java:71) > at org.richfaces.application.push.impl.SessionImpl.releaseRequest(SessionImpl.java:112) > at org.richfaces.application.push.impl.SessionImpl.connect(SessionImpl.java:85) > - locked <0x000000078da957e0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.onSuspend(RequestImpl.java:119) > at org.atmosphere.cpr.AtmosphereResourceImpl.onSuspend(AtmosphereResourceImpl.java:652) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:611) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:591) > at org.atmosphere.cpr.AtmosphereResourceImpl.suspend(AtmosphereResourceImpl.java:347) > at org.atmosphere.cpr.Meteor.suspend(Meteor.java:213) > at org.richfaces.application.push.impl.RequestImpl.suspend(RequestImpl.java:67) > at org.richfaces.webapp.PushHandlerFilter.doFilter(PushHandlerFilter.java:107) > at org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:139) > at org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:116) > at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:293) > at org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:151) > at org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:219) > at org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:154) > at org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:85) > at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1218) > at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:1286) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484) > at org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1686) > - locked <0x000000078e7fcc28> (a org.apache.tomcat.util.net.NioChannel) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x000000078da957e0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:128) > at org.richfaces.application.push.impl.RequestImpl.onDisconnect(RequestImpl.java:140) > at org.atmosphere.cpr.AtmosphereResourceImpl.onDisconnect(AtmosphereResourceImpl.java:664) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:609) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:591) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:719) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:749) > - locked <0x000000078e8ecf90> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > {code} > Found 1 deadlock. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12922) rich:validator: only first message from multiple validation will appear

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12922?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12922: ------------------------------- Fix Version/s: 5-Tracking > rich:validator: only first message from multiple validation will appear > ----------------------------------------------------------------------- > > Key: RF-12922 > URL: https://issues.jboss.org/browse/RF-12922 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux > Firefox 18.0 @ Linux x86_64 > Reporter: Jiří Štefek > Assignee: Brian Leathem > Fix For: 5-Tracking > > > When an input is validated by e.g. 2 rules and the value put in it does not pass both validations, only one message is displayed to the client. > Is it intention? > Message components: rich:messages and rich:notifyMessages -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13006) Rename SessionTopicListener2 to SessionTopicListener

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13006?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13006: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > Rename SessionTopicListener2 to SessionTopicListener > ---------------------------------------------------- > > Key: RF-13006 > URL: https://issues.jboss.org/browse/RF-13006 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Priority: Trivial > Fix For: 5.0.0.Alpha2 > > > After deleting the old {{SessionTopicListener}} the {{SessionTopicListener2}} can be renamed back to {{SessionTopicListener}}. > However, in this comment it is noted that you wanted to left the 2 in the name. > https://issues.jboss.org/browse/RF-12745?focusedCommentId=12765159&page=c... > Is it still correct ? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13031) Rebrand all RichFaces 4 to RichFaces 5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13031?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13031: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > Rebrand all RichFaces 4 to RichFaces 5 > -------------------------------------- > > Key: RF-13031 > URL: https://issues.jboss.org/browse/RF-13031 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Priority: Minor > Fix For: 5.0.0.Alpha2 > > > We should rename all occurences of "RichFaces 4" in richfaces & docs repositories to "RichFaces 5" -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13031) Rebrand all RichFaces 4 to RichFaces 5

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13031?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13031: ---------------------------- Description: We should rename all occurences of "RichFaces 4" in richfaces & docs repositories to "RichFaces 5" > Rebrand all RichFaces 4 to RichFaces 5 > -------------------------------------- > > Key: RF-13031 > URL: https://issues.jboss.org/browse/RF-13031 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Minor > > We should rename all occurences of "RichFaces 4" in richfaces & docs repositories to "RichFaces 5" -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13031) Rebrand all RichFaces 4 to RichFaces 5

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13031?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-13031: ------------------------------- Assignee: (was: Lukáš Fryč) Clarified. > Rebrand all RichFaces 4 to RichFaces 5 > -------------------------------------- > > Key: RF-13031 > URL: https://issues.jboss.org/browse/RF-13031 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Priority: Minor > > We should rename all occurences of "RichFaces 4" in richfaces & docs repositories to "RichFaces 5" -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13006) Rename SessionTopicListener2 to SessionTopicListener

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13006?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13006: --------------------------------- That's safe and straight-forward for migration. > Rename SessionTopicListener2 to SessionTopicListener > ---------------------------------------------------- > > Key: RF-13006 > URL: https://issues.jboss.org/browse/RF-13006 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Priority: Trivial > > After deleting the old {{SessionTopicListener}} the {{SessionTopicListener2}} can be renamed back to {{SessionTopicListener}}. > However, in this comment it is noted that you wanted to left the 2 in the name. > https://issues.jboss.org/browse/RF-12745?focusedCommentId=12765159&page=c... > Is it still correct ? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13006) Rename SessionTopicListener2 to SessionTopicListener

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13006?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13006: ---------------------------- Assignee: (was: Lukáš Fryč) > Rename SessionTopicListener2 to SessionTopicListener > ---------------------------------------------------- > > Key: RF-13006 > URL: https://issues.jboss.org/browse/RF-13006 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Priority: Trivial > > After deleting the old {{SessionTopicListener}} the {{SessionTopicListener2}} can be renamed back to {{SessionTopicListener}}. > However, in this comment it is noted that you wanted to left the 2 in the name. > https://issues.jboss.org/browse/RF-12745?focusedCommentId=12765159&page=c... > Is it still correct ? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13053) Showcase: push doesn't work on EAP 6.1

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13053?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13053: ---------------------------- Fix Version/s: 5.0.0.Alpha2 (was: 5-Tracking) > Showcase: push doesn't work on EAP 6.1 > -------------------------------------- > > Key: RF-13053 > URL: https://issues.jboss.org/browse/RF-13053 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.2 > Reporter: Pavol Pitonak > Fix For: 4.3.3, 5.0.0.Alpha2 > > > EAP 6.1 has more strict conditions for user passwords so we need to update JMS password in both web.xml and readme.md. It has to contain one number and one special character. -- 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, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues June 2013