[
https://issues.apache.org/jira/browse/AMQ-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709578#comment-13709578
]
Pedro de Lara commented on AMQ-4372:
------------------------------------
After some further testing I am not sure this issue is solved. I have applied
the patches to 5.8.0 and it seems to make it more stable however not
completely. I have managed to browse the queue using the webconsole a few times
however other times it will still try to load for a while and return with the
following error
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2367)
at java.io.CharArrayWriter.write(CharArrayWriter.java:105)
at java.io.PrintWriter.write(PrintWriter.java:426)
at
com.opensymphony.module.sitemesh.filter.RoutablePrintWriter.write(RoutablePrintWriter.java:144)
at
org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:181)
at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:449)
at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:462)
at
org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:394)
at
org.apache.jsp.browse_jsp$browse_jspHelper.invoke(org.apache.jsp.browse_jsp:450)
at
org.apache.jsp.tag.web.jms.forEachMessage_tag.doTag(org.apache.jsp.tag.web.jms.forEachMessage_tag:89)
at
org.apache.jsp.browse_jsp._jspx_meth_jms_forEachMessage_0(org.apache.jsp.browse_jsp:170)
at org.apache.jsp.browse_jsp._jspService(org.apache.jsp.browse_jsp:100)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1329)
at
org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129)
at
com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:77)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:445)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> WebConsole throw Java Heap Space when browse a queue with more than 100
> elements
> --------------------------------------------------------------------------------
>
> Key: AMQ-4372
> URL: https://issues.apache.org/jira/browse/AMQ-4372
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.8.0
> Environment: Linux/Ubuntu
> Reporter: Grégory OLIVER
> Assignee: Timothy Bish
> Labels: web-console
> Fix For: 5.9.0
>
>
> I have a standalone installation of activemq.
> When I want to browse a queue with more than 100 elements, the console throw
> a Java Heap Space, because he try to show all elements in the queue.
> But when I have 40 elements, the page work well, and i can browse messages.
> It should be interesting to paginate this page, to only show, for example,
> the first 100 elements.
> The page :
> http://localhost:8161/admin/browse.jsp?JMSDestination=TestQueueOne
> Added :
> I have tested with the 5.7.0 version of activemq and this bug doesn't exist.
--
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
