[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1239) Throw distinquishable exception time if size limit of MultipartRequest is exceeded
9:48 a.m.
Throw distinquishable exception time if size limit of MultipartRequest is exceeded
----------------------------------------------------------------------------------
Key: JBSEAM-1239
URL: http://jira.jboss.com/jira/browse/JBSEAM-1239
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Christian Bauer
Priority: Minor
java.lang.RuntimeException: Multipart request is larger than allowed size
org.jboss.seam.web.MultipartRequest.<init>(MultipartRequest.java:282)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
I can't catch this and display a proper error message. Also the pages.xml exception
handling doesn't catch it, since it happens too early in a filter. If there is any
reasonable way we need to make this exception case more customizable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:50 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-1239) Throw distinquishable exception type if size limit of MultipartRequest is exceeded
[ http://jira.jboss.com/jira/browse/JBSEAM-1239?page=all ]
Shane Bryzak reassigned JBSEAM-1239:
------------------------------------
Assignee: Shane Bryzak
Throw distinquishable exception type if size limit of
MultipartRequest is exceeded
----------------------------------------------------------------------------------
Key: JBSEAM-1239
URL: http://jira.jboss.com/jira/browse/JBSEAM-1239
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Christian Bauer
Assigned To: Shane Bryzak
Priority: Minor
java.lang.RuntimeException: Multipart request is larger than allowed size
org.jboss.seam.web.MultipartRequest.<init>(MultipartRequest.java:282)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
I can't catch this and display a proper error message. Also the pages.xml exception
handling doesn't catch it, since it happens too early in a filter. If there is any
reasonable way we need to make this exception case more customizable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:50 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1239) Throw distinquishable exception type if size limit of MultipartRequest is exceeded
[ http://jira.jboss.com/jira/browse/JBSEAM-1239?page=all ]
Christian Bauer updated JBSEAM-1239:
------------------------------------
Summary: Throw distinquishable exception type if size limit of MultipartRequest is
exceeded (was: Throw distinquishable exception time if size limit of MultipartRequest is
exceeded)
Throw distinquishable exception type if size limit of
MultipartRequest is exceeded
----------------------------------------------------------------------------------
Key: JBSEAM-1239
URL: http://jira.jboss.com/jira/browse/JBSEAM-1239
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Christian Bauer
Priority: Minor
java.lang.RuntimeException: Multipart request is larger than allowed size
org.jboss.seam.web.MultipartRequest.<init>(MultipartRequest.java:282)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
I can't catch this and display a proper error message. Also the pages.xml exception
handling doesn't catch it, since it happens too early in a filter. If there is any
reasonable way we need to make this exception case more customizable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:52 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1239) Throw distinquishable exception type if size limit of MultipartRequest is exceeded
[ http://jira.jboss.com/jira/browse/JBSEAM-1239?page=all ]
Shane Bryzak closed JBSEAM-1239.
--------------------------------
Fix Version/s: 1.3.0.ALPHA
Resolution: Done
A FileUploadException is now thrown instead of a RuntimeException.
Throw distinquishable exception type if size limit of
MultipartRequest is exceeded
----------------------------------------------------------------------------------
Key: JBSEAM-1239
URL: http://jira.jboss.com/jira/browse/JBSEAM-1239
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Christian Bauer
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 1.3.0.ALPHA
java.lang.RuntimeException: Multipart request is larger than allowed size
org.jboss.seam.web.MultipartRequest.<init>(MultipartRequest.java:282)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
I can't catch this and display a proper error message. Also the pages.xml exception
handling doesn't catch it, since it happens too early in a filter. If there is any
reasonable way we need to make this exception case more customizable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:13 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1239) Throw distinquishable exception type if size limit of MultipartRequest is exceeded
[ http://jira.jboss.com/jira/browse/JBSEAM-1239?page=comments#action_12365153 ]
Christian Bauer commented on JBSEAM-1239:
-----------------------------------------
Can the multipart filter run after the exception filter, so we can use pages.xml exception
handling?
Throw distinquishable exception type if size limit of
MultipartRequest is exceeded
----------------------------------------------------------------------------------
Key: JBSEAM-1239
URL: http://jira.jboss.com/jira/browse/JBSEAM-1239
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Christian Bauer
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 1.3.0.ALPHA
java.lang.RuntimeException: Multipart request is larger than allowed size
org.jboss.seam.web.MultipartRequest.<init>(MultipartRequest.java:282)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
I can't catch this and display a proper error message. Also the pages.xml exception
handling doesn't catch it, since it happens too early in a filter. If there is any
reasonable way we need to make this exception case more customizable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:09 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1239) Throw distinquishable exception type if size limit of MultipartRequest is exceeded
[ http://jira.jboss.com/jira/browse/JBSEAM-1239?page=comments#action_12365179 ]
Shane Bryzak commented on JBSEAM-1239:
--------------------------------------
Try it now, I've placed it within the exception filter.
Throw distinquishable exception type if size limit of
MultipartRequest is exceeded
----------------------------------------------------------------------------------
Key: JBSEAM-1239
URL: http://jira.jboss.com/jira/browse/JBSEAM-1239
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Christian Bauer
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 1.3.0.ALPHA
java.lang.RuntimeException: Multipart request is larger than allowed size
org.jboss.seam.web.MultipartRequest.<init>(MultipartRequest.java:282)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
I can't catch this and display a proper error message. Also the pages.xml exception
handling doesn't catch it, since it happens too early in a filter. If there is any
reasonable way we need to make this exception case more customizable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:53 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1239) Throw distinquishable exception type if size limit of MultipartRequest is exceeded
[ http://jira.jboss.com/jira/browse/JBSEAM-1239?page=comments#action_12365190 ]
Christian Bauer commented on JBSEAM-1239:
-----------------------------------------
It is caught now but I can't handle it (I am in a LR conversation):
<exception class="org.jboss.seam.web.FileUploadException">
<redirect view-id="/message.xhtml">
<message severity="ERROR">File upload failed, possibly due to
size limitation (max.
#{wiki:displayFilesize(org.jboss.seam.web.multipartFilter.maxRequestSize)}).</message>
</redirect>
</exception>
13:50:50,622 ERROR [ExceptionFilter] uncaught exception
org.jboss.seam.web.FileUploadException: Multipart request is larger than allowed size
at org.jboss.seam.web.MultipartRequest.<init>(MultipartRequest.java:280)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:76)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:56)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:60)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:56)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:47)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:56)
at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:293)
at
org.jboss.seam.web.AbstractAjax4jsfFilter.doFilter(AbstractAjax4jsfFilter.java:35)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:56)
at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:127)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127)
at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:613)
13:50:50,624 ERROR [ExceptionFilter] exception root cause
13:50:50,624 DEBUG [ExceptionFilter] ending request
13:50:50,625 DEBUG [Lifecycle] >>> Begin exception recovery
13:50:50,625 DEBUG [Navigator] redirecting to: /message.xhtml
13:50:50,625 DEBUG [Lifecycle] After render response, destroying contexts
13:50:50,625 DEBUG [Lifecycle] destroying conversation context
13:50:50,625 DEBUG [Lifecycle] flushing server-side conversation context
13:50:50,625 DEBUG [Lifecycle] flushing session context
13:50:50,626 DEBUG [Lifecycle] destroying event context
13:50:50,626 DEBUG [Lifecycle] <<< End JSF request
13:50:50,626 DEBUG [ExceptionFilter] ended request
13:50:50,626 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw
exception
java.lang.IllegalArgumentException: Stack must not be null
at org.jboss.seam.core.ConversationEntry.<init>(ConversationEntry.java:40)
at
org.jboss.seam.core.ConversationEntries.createConversationEntry(ConversationEntries.java:52)
at org.jboss.seam.core.Manager.createConversationEntry(Manager.java:685)
at org.jboss.seam.core.Manager.beforeRedirect(Manager.java:834)
at org.jboss.seam.core.Manager.beforeRedirect(Manager.java:852)
at org.jboss.seam.core.Manager.redirect(Manager.java:1058)
at org.jboss.seam.core.Navigator.redirect(Navigator.java:45)
at org.jboss.seam.exceptions.RedirectHandler.handle(RedirectHandler.java:45)
at org.jboss.seam.core.Exceptions.handle(Exceptions.java:78)
at
org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:85)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:66)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:56)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:47)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:56)
at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:293)
at
org.jboss.seam.web.AbstractAjax4jsfFilter.doFilter(AbstractAjax4jsfFilter.java:35)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:56)
at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:127)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127)
at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:613)
Throw distinquishable exception type if size limit of
MultipartRequest is exceeded
----------------------------------------------------------------------------------
Key: JBSEAM-1239
URL: http://jira.jboss.com/jira/browse/JBSEAM-1239
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Christian Bauer
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 1.3.0.ALPHA
java.lang.RuntimeException: Multipart request is larger than allowed size
org.jboss.seam.web.MultipartRequest.<init>(MultipartRequest.java:282)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
I can't catch this and display a proper error message. Also the pages.xml exception
handling doesn't catch it, since it happens too early in a filter. If there is any
reasonable way we need to make this exception case more customizable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6425
days inactive
6475
days old
6 comments
2 participants
participants (2)
-
Christian Bauer (JIRA) -
Shane Bryzak (JIRA)