from:"zmhassan"


[ 
https://issues.apache.org/jira/browse/AMQ-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984745#comment-13984745
 ] 

zmhassan commented on AMQ-4848:
---

Hi Gary,

This example will save me time. Thank you for pointing me in the right 
direction. I will look at this example and use it to test this fix. 

Thanks,
Zak
 

> activemq:list - Should include the transport connectors and their urls
> --
>
> Key: AMQ-4848
> URL: https://issues.apache.org/jira/browse/AMQ-4848
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: OSGi/Karaf
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 5.11.0
>
>
> When using the karaf commands you can get a bit of information about the 
> broker.
> But we need to output the transport connectors in use as well, so you can see 
> the types and url's, eg tcp://localhost:61616, and ampq:xxx and so forth.
> We could add that to the list command that shows the broker names.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Issue Comment Deleted] (AMQ-4848) activemq:list - Should include the transport connectors and their urls


 [ 
https://issues.apache.org/jira/browse/AMQ-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

zmhassan updated AMQ-4848:
--

Comment: was deleted

(was: I followed these instructions.
https://activemq.apache.org/osgi-integration.html

Just wanted to confirm if the activemq install there is the exact same as the 
one I ran a build on during development?)

> activemq:list - Should include the transport connectors and their urls
> --
>
> Key: AMQ-4848
> URL: https://issues.apache.org/jira/browse/AMQ-4848
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: OSGi/Karaf
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 5.11.0
>
>
> When using the karaf commands you can get a bit of information about the 
> broker.
> But we need to output the transport connectors in use as well, so you can see 
> the types and url's, eg tcp://localhost:61616, and ampq:xxx and so forth.
> We could add that to the list command that shows the broker names.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Issue Comment Deleted] (AMQ-4848) activemq:list - Should include the transport connectors and their urls


 [ 
https://issues.apache.org/jira/browse/AMQ-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

zmhassan updated AMQ-4848:
--

Comment: was deleted

(was: I'm trying to test this fix on karaf. Any tips on how I can test my 
current install of activemq with karaf to see if I fixed this correctly. I'm a 
little new to karaf.)

> activemq:list - Should include the transport connectors and their urls
> --
>
> Key: AMQ-4848
> URL: https://issues.apache.org/jira/browse/AMQ-4848
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: OSGi/Karaf
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 5.11.0
>
>
> When using the karaf commands you can get a bit of information about the 
> broker.
> But we need to output the transport connectors in use as well, so you can see 
> the types and url's, eg tcp://localhost:61616, and ampq:xxx and so forth.
> We could add that to the list command that shows the broker names.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (AMQ-4848) activemq:list - Should include the transport connectors and their urls


[ 
https://issues.apache.org/jira/browse/AMQ-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984491#comment-13984491
 ] 

zmhassan commented on AMQ-4848:
---

I followed these instructions.
https://activemq.apache.org/osgi-integration.html

Just wanted to confirm if the activemq install there is the exact same as the 
one I ran a build on during development?

> activemq:list - Should include the transport connectors and their urls
> --
>
> Key: AMQ-4848
> URL: https://issues.apache.org/jira/browse/AMQ-4848
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: OSGi/Karaf
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 5.11.0
>
>
> When using the karaf commands you can get a bit of information about the 
> broker.
> But we need to output the transport connectors in use as well, so you can see 
> the types and url's, eg tcp://localhost:61616, and ampq:xxx and so forth.
> We could add that to the list command that shows the broker names.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (AMQ-4848) activemq:list - Should include the transport connectors and their urls


[ 
https://issues.apache.org/jira/browse/AMQ-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984478#comment-13984478
 ] 

zmhassan commented on AMQ-4848:
---

I'm trying to test this fix on karaf. Any tips on how I can test my current 
install of activemq with karaf to see if I fixed this correctly. I'm a little 
new to karaf.

> activemq:list - Should include the transport connectors and their urls
> --
>
> Key: AMQ-4848
> URL: https://issues.apache.org/jira/browse/AMQ-4848
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: OSGi/Karaf
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 5.11.0
>
>
> When using the karaf commands you can get a bit of information about the 
> broker.
> But we need to output the transport connectors in use as well, so you can see 
> the types and url's, eg tcp://localhost:61616, and ampq:xxx and so forth.
> We could add that to the list command that shows the broker names.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: The ActiveMQ community deserves better. Lets vote on new UI for AMQ

2014-04-28 Thread zmhassan

Clarification on my last post:

Sorry, I didn't mean to offend anyone with that remark about change. I just
wanted to motivate people, not offend them.






--
View this message in context: 
http://activemq.2283324.n4.nabble.com/The-ActiveMQ-community-deserves-better-Lets-vote-on-new-UI-for-AMQ-tp4680583p4680642.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: The ActiveMQ community deserves better. Lets vote on new UI for AMQ

2014-04-28 Thread zmhassan

I wanted to clarify what my goal was sorry I didn't provide more detail in
the messages I posted earlier.

Firstly, I'm just the type of person that when I see something I can make
better I can't help it but try to do something about it. Well the goal of a
new UI would be to add a better look first and then include better
functionality. Here are a list of features I want to add if everyone agrees
on this update to the UI.

1) Better looking UI.
2) I want to add a feature to add pagination to browse a JMS queue. This
will avoid OOM errors that we usually get.
3) I want to add a way to search a JMS queue.
4) I did some research and it could be possible to add elasticsearch to
levelDB so people can use a Rest API. Also this will allow us to have
something like Kibana which will display nice charts and graphs.
5) I wanted to add a dashboard on the first page kind of like what is used
in RabbitMQ first page which has benchmark metrics.
6) I plan on adding all these same features to Hawtio also if I have
everyone supporting me on this.

You know why Linux runs on computers with low memory?

Well its because someone asked Linus Torvald to make it possible for linux
to run on low memory computers. This is not exactly the same but what we can
take away is people might have different goals in a community. Some may
agree or disagree but really when you look back at this one day people might
admire you just like Linus Torvald. So question is will you accept change ?

--
View this message in context:
http://activemq.2283324.n4.nabble.com/The-ActiveMQ-community-deserves-better-Lets-vote-on-new-UI-for-AMQ-tp4680583p4680639.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[GitHub] activemq pull request: Add paging of messages to the webconsole wh...

2014-04-26 Thread zmhassan

Github user zmhassan closed the pull request at:

https://github.com/apache/activemq/pull/16


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: The ActiveMQ community deserves better. Lets vote on new UI for AMQ

2014-04-26 Thread zmhassan

Here is a screenshot of how it looks. I'm gonna focus first on the navbar and
sidebar first. By the way, I'm using bootstrap and jquery. It will comply
with the apache license. 

So what do you think?
 
 



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/The-ActiveMQ-community-deserves-better-Lets-vote-on-new-UI-for-AMQ-tp4680583p4680584.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[GitHub] activemq pull request: AMQ-4945 : IllegalArgumentException When No...

2014-04-25 Thread zmhassan

GitHub user zmhassan opened a pull request:

https://github.com/apache/activemq/pull/20

AMQ-4945 : IllegalArgumentException When No Destination Specified On Adm...

Description of problem:

This is a UI issue.
If I click the 'CREATE' queue button on the screen at '/admin/queues.jsp' 
it throws an exception, instead of simply putting out a message that a queue 
destination/name is required.


Jira issue:
https://issues.apache.org/jira/browse/AMQ-4945



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zmhassan/activemq AMQ-4945

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit 5b86a6edbf5a2d269547cb086e41ddf96be94b09
Author: zmhassan 
Date:   2014-04-26T04:40:16Z

AMQ-4945 : IllegalArgumentException When No Destination Specified On Admin 
Screen




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AMQ-4945) IllegalArgumentException When No Destination Specified On Admin Screen

2014-04-25 Thread zmhassan (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981849#comment-13981849
 ] 

zmhassan commented on AMQ-4945:
---

Okay I'm gonna work on this and send in a pull request tonight. 

> IllegalArgumentException When No Destination Specified On Admin Screen
> --
>
> Key: AMQ-4945
> URL: https://issues.apache.org/jira/browse/AMQ-4945
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.8.0, 5.9.0
> Environment: Linux
>Reporter: Jerome Lumpkin
>Priority: Trivial
>
> This is a UI issue.  
> If I click the 'CREATE' queue button on the screen at '/admin/queues.jsp'  it 
> throws an exception, instead of simply putting out a message that a queue 
> destination/name is required.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (AMQ-5024) Add paging of messages to the webconsole when viewing a deep queue

2014-02-14 Thread zmhassan (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902152#comment-13902152
 ] 

zmhassan commented on AMQ-5024:
---

Big fixed awaiting review:

Here is the pull request:

https://github.com/apache/activemq/pull/16



> Add paging of messages to the webconsole when viewing a deep queue
> --
>
> Key: AMQ-5024
> URL: https://issues.apache.org/jira/browse/AMQ-5024
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: webconsole
>Affects Versions: 5.9.0
>Reporter: Arthur Naseef
>Assignee: Arthur Naseef
>
> It is not feasible to browse a deep Queue via the webconsole: navigating to 
> the webconsole's Queue list, then browsing the Queue, if there are a large 
> number of messages stored, the webpage takes a very long time, and may 
> timeout.
> Adding pagination of messages so that the webconsole only displays a number 
> of messages per page will make it feasible to browse deep Queues.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[GitHub] activemq pull request: Add paging of messages to the webconsole wh...

2014-02-14 Thread zmhassan

GitHub user zmhassan opened a pull request:

https://github.com/apache/activemq/pull/16

Add paging of messages to the webconsole when viewing a deep queue. When 
queue depth is deep OOM issue occurs

Fix for the following use:

https://issues.apache.org/jira/browse/AMQ-5024

Currently we have an OOM problem when we browse the queue. I know that the 
sitemesh was also another problem and it was removed by Daniel.  This 
pagination we make it possible for users to view their JMS messages in queue no 
matter how deep the queue depth is.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/activemq trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq/pull/16.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #16


commit 894de8d6d45b6481f1896f5e18dd7b9e8bcbcf12
Author: Arthur Naseef 
Date:   2014-01-31T02:25:22Z

Changes to support paged web retreival of messages.

commit 52f3f0476796cfa18a7b05efe7e8653ccc67f96c
Author: Arthur Naseef 
Date:   2014-01-31T02:34:44Z

Merge https://github.com/artnaseef/activemq into trunk

commit 2dd9151898ee6e26e40da5d8b7aad353e38bfa65
Author: Arthur Naseef 
Date:   2014-02-05T03:37:25Z

Move EnumerationPage to a util folder.

commit 27cc34ff428e7206ba5800ca700814fc9dbc94b3
Author: artnaseef 
Date:   2014-02-05T05:45:18Z

Updates to use EnumerationPage from the new util folder.

commit 59dfe0ce723b0850331ddff208cb6d6a6410fda2
Author: Zakeria Hassan 
Date:   2014-02-06T04:24:55Z

Updated UI for activemq and fixed the java.lang out of memory

commit 00106daac5c0c8195b80cfbf96883cce3aff5c8e
Author: Zakeria Hassan 
Date:   2014-02-07T01:59:48Z

Optimizing browse page to display data in queue. original problem was that 
the page would break if the queue depth reached 200,000

commit c7a97a340517468854a417359b53529ab09ce8f1
Author: Zakeria Hassan 
Date:   2014-02-07T15:32:19Z

Merge pull request #1 from artnaseef/webQueueViewPaging

Web queue view paging

commit 3910efb807c7b0b123bfad1439b096ff9b451a34
Author: Zakeria Hassan 
Date:   2014-02-14T23:36:45Z

Fixing Pagination logic

commit 57870f70eef1923561ca78f1d9b35645a422fd0c
Author: Zakeria Hassan 
Date:   2014-02-14T23:47:52Z

Merging changes from the server with new bootstrap UI

[jira] [Commented] (AMQ-5024) Add paging of messages to the webconsole when viewing a deep queue

2014-02-06 Thread zmhassan (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894138#comment-13894138
 ] 

zmhassan commented on AMQ-5024:
---

See this issue for more details of where this originated from:
https://issues.apache.org/jira/browse/AMQ-4994

So far I've setup pagination and I am running on test send 200,000 jms messages 
to a queue. I will then paginate through it and then once I am satisfied I'll 
put in a pull request.

 

> Add paging of messages to the webconsole when viewing a deep queue
> --
>
> Key: AMQ-5024
> URL: https://issues.apache.org/jira/browse/AMQ-5024
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: webconsole
>Affects Versions: 5.9.0
>Reporter: Arthur Naseef
>Assignee: Arthur Naseef
>
> It is not feasible to browse a deep Queue via the webconsole: navigating to 
> the webconsole's Queue list, then browsing the Queue, if there are a large 
> number of messages stored, the webpage takes a very long time, and may 
> timeout.
> Adding pagination of messages so that the webconsole only displays a number 
> of messages per page will make it feasible to browse deep Queues.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Comment Edited] (AMQ-5024) Add paging of messages to the webconsole when viewing a deep queue

2014-02-06 Thread zmhassan (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894138#comment-13894138
 ] 

zmhassan edited comment on AMQ-5024 at 2/7/14 2:45 AM:
---

See this issue for more details of where this originated from:
https://issues.apache.org/jira/browse/AMQ-4994

So far I've setup pagination and I am running one more test with 200,000 jms 
messages in queue. I will then paginate through it and then once I am satisfied 
I'll put in a pull request.

 


was (Author: zmhassan):
See this issue for more details of where this originated from:
https://issues.apache.org/jira/browse/AMQ-4994

So far I've setup pagination and I am running on test send 200,000 jms messages 
to a queue. I will then paginate through it and then once I am satisfied I'll 
put in a pull request.

 

> Add paging of messages to the webconsole when viewing a deep queue
> --
>
> Key: AMQ-5024
> URL: https://issues.apache.org/jira/browse/AMQ-5024
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: webconsole
>Affects Versions: 5.9.0
>Reporter: Arthur Naseef
>Assignee: Arthur Naseef
>
> It is not feasible to browse a deep Queue via the webconsole: navigating to 
> the webconsole's Queue list, then browsing the Queue, if there are a large 
> number of messages stored, the webpage takes a very long time, and may 
> timeout.
> Adding pagination of messages so that the webconsole only displays a number 
> of messages per page will make it feasible to browse deep Queues.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues

2014-02-04 Thread zmhassan (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891626#comment-13891626
 ] 

zmhassan commented on AMQ-4994:
---

No we don't have an issue. Please create one and assign to me.

Thanks,
Zak


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: webconsole
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Assignee: Hadrian Zbarcea
>Priority: Blocker
> Attachments: AMQ-4994.patch
>
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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:1320)
>   at 
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
>   at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at 
> org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at 
> com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129){code}
> when trying to browse that queue.
> To reproduce it:
> 1. Start a broker with default configuration
> 2. Send 200k messages with
> {code}ant producer -Dmax=20 -Ddurable=true -Dsubject=TEST{code}
> 3. Try to browse the queue
> http://localhost:8161/admin/browse.jsp?JMSDestination=TEST
> The proper solution to this problem is to implement proper pagination while 
> browsing the messages, so users can browse through all messages showing 100 
> msgs (or so) at the time and not using all the available memory.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: Node.JS Client Library for Accessing Apache ActiveMQ

2014-02-02 Thread zmhassan

Hey Arthur,

Node.JS could replace the console and add many features that would enrich
the experience of users when using ActiveMQ. It's asynchronous in nature so
stuff like push notifications, web sockets, REST web services, and a world
of possibilities would be possible. We could still use the same java code
for ActiveMQ and have Node.JS running on a separate port. The ideal plan
would be to use this API or client library to communicate with ActiveMQ via
one of the following protocols: tcp, stomp, mqtt, etc.   

Here a high level view of the architecture and yes web sockets would be easy
to implement here:

 



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Node-JS-Client-Library-for-Accessing-Apache-ActiveMQ-tp4677269p4677293.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Commented] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888238#comment-13888238
 ] 

zmhassan commented on AMQ-4994:
---

@Hadrian,

Yes I guess we can move the pagination stuff to a separate issue. 

> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Assignee: Hadrian Zbarcea
>Priority: Blocker
> Attachments: AMQ-4994.patch
>
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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:1320)
>   at 
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
>   at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at 
> org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at 
> com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129){code}
> when trying to browse that queue.
> To reproduce it:
> 1. Start a broker with default configuration
> 2. Send 200k messages with
> {code}ant producer -Dmax=20 -Ddurable=true -Dsubject=TEST{code}
> 3. Try to browse the queue
> http://localhost:8161/admin/browse.jsp?JMSDestination=TEST
> The proper solution to this problem is to implement proper pagination while 
> browsing the messages, so users can browse through all messages showing 100 
> msgs (or so) at the time and not using all the available memory.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Comment Edited] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887988#comment-13887988
 ] 

zmhassan edited comment on AMQ-4994 at 1/31/14 7:14 PM:


Okay at this point I'm just testing the client side code. Every page will 
display 100 Jms Messages and as we paginate through it will show the next 100. 
I can do some optimizations but wanted  your input on the design of it. Changed 
a bit of the UI to look more modern using bootstrap and jQuery. 

See screenshoot:
https://www.dropbox.com/s/f8wgkae6vpgrc21/Screenshot%20from%202014-01-31%2013%3A35%3A31.png


This was done by utilizing Bootstrap 3.0 css + jQuery + teamwork  to get RSS 
feed data from  ActiveMQ for the first 100 messages in the queue. As we go 
deeper the slower it will be. I'm working on a way around that but still 
thinking at this point. Appreciate any feedback I'll be online at the usual 
times > 7pm (E.S.T).

I'll send in my pull request once I'm satisfied that everything is working 100% 
 test and fully functional. 

Best Regards,
Zak
“Empowerment of individuals is a key part of what makes open source work, since 
in the end, innovations tend to come from small groups, not from large, 
structured efforts.”
– Tim O’Reilly



was (Author: zmhassan):
Okay at this point I'm just testing the client side code. Every page will 
display 100 Jms Messages and as we paginate through it will show the next 100. 
I can do some optimizations but wanted  your input on the design of it. Changed 
a bit of the UI to look more modern using bootstrap and jQuery. 

See screenshoot:
https://www.dropbox.com/s/f8wgkae6vpgrc21/Screenshot%20from%202014-01-31%2013%3A35%3A31.png


This was done by utilizing Bootstrap 3.0 css + jQuery + teamwork  to get RSS 
feed data from the ActiveMQ for the first 100 in the queue. As we go deeper the 
slower it will be. Appreciate any feedback I'll be online at the usual times.

I'll send in my pull request once I'm satisfied that everything is working 100% 
 test and fully functional. 

Best Regards,
Zak
“Empowerment of individuals is a key part of what makes open source work, since 
in the end, innovations tend to come from small groups, not from large, 
structured efforts.”
– Tim O’Reilly


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Priority: Blocker
> Attachments: AMQ-4994.patch
>
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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)
>   a

[jira] [Comment Edited] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887988#comment-13887988
 ] 

zmhassan edited comment on AMQ-4994 at 1/31/14 7:12 PM:


Okay at this point I'm just testing the client side code. Every page will 
display 100 Jms Messages and as we paginate through it will show the next 100. 
I can do some optimizations but wanted  your input on the design of it. Changed 
a bit of the UI to look more modern using bootstrap and jQuery. 

See screenshoot:
https://www.dropbox.com/s/f8wgkae6vpgrc21/Screenshot%20from%202014-01-31%2013%3A35%3A31.png


This was done by utilizing Bootstrap 3.0 css + jQuery + teamwork  to get RSS 
feed data from the ActiveMQ for the first 100 in the queue. As we go deeper the 
slower it will be. Appreciate any feedback I'll be online at the usual times.

I'll send in my pull request once I'm satisfied that everything is working 100% 
 test and fully functional. 

Best Regards,
Zak
“Empowerment of individuals is a key part of what makes open source work, since 
in the end, innovations tend to come from small groups, not from large, 
structured efforts.”
– Tim O’Reilly



was (Author: zmhassan):
Okay at this point I'm just testing the client side code. Every page will 
display 100 Jms Messages and as we paginate through it will show the next 100. 
I can do some optimizations but wanted  your input on the design of it. Changed 
a bit of the UI to look more modern using bootstrap and jQuery. 

See screenshoot:
https://www.dropbox.com/s/f8wgkae6vpgrc21/Screenshot%20from%202014-01-31%2013%3A35%3A31.png


I used bootstrap 3.0 css and a bit of jQuery to get RSS feed data from the 
ActiveMQ for the first 100 in the queue. As we go deeper the slower it will be. 
Appreciate any feedback I'll be online at the usual times.


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Priority: Blocker
> Attachments: AMQ-4994.patch
>
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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:1320)
>   at 
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
>   at 
> org.springframework.web.filter.OncePerReque

[jira] [Commented] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887988#comment-13887988
 ] 

zmhassan commented on AMQ-4994:
---

Okay at this point I'm just testing the client side code. Every page will 
display 100 Jms Messages and as we paginate through it will show the next 100. 
I can do some optimizations but wanted  your input on the design of it. Changed 
a bit of the UI to look more modern using bootstrap and jQuery. 

See screenshoot:
https://www.dropbox.com/s/f8wgkae6vpgrc21/Screenshot%20from%202014-01-31%2013%3A35%3A31.png


I used bootstrap 3.0 css and a bit of jQuery to get RSS feed data from the 
ActiveMQ for the first 100 in the queue. As we go deeper the slower it will be. 
Appreciate any feedback I'll be online at the usual times.


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Priority: Blocker
> Attachments: AMQ-4994.patch
>
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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:1320)
>   at 
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
>   at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at 
> org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at 
> com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129){code}
> when trying to browse that queue.
> To reproduce it:
> 1. Start a broker with default configuration
> 2. Send 200k messages with
> {code}ant producer -Dmax=20 -Ddurable=true -Dsubject=TEST{code}
> 3. Try to browse the queue
> http://localhost:8161/admin/browse.jsp?JMSDestination=TEST
> The proper solution to this problem is to implement proper pagination while 
> browsing the messages, so users can browse through all messages showing 100 
> msgs (or so) at the time and not using all the available memory.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Comment Edited] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886224#comment-13886224
 ] 

zmhassan edited comment on AMQ-4994 at 1/30/14 4:22 AM:


I was originally planning on making a slight change in the design. I was 
planning on making a restful endpoint that will display the first hundred JMS 
messages in queue in JSON format (one argument 'page'). It would save time and 
resource because we don't loop through all 200,000 items in queue. However that 
would make a change in the design and I was thinking there must be a way that 
we can reuse existing code that does web service like functionality. 

One option I was looking at was that we could use the RSS/ATOM feed with xml 
data and pull from it via javascript on the client-side to get the messages in 
queue but when I tried this, it was a really large xml file and takes a long 
time to load. When the number of messages grow too large I was unsuccessful in 
requesting it and parsing it. Perhaps if we can just display 100 messages of 
the 200,000 in queue that would make it an easier problem to solve. 

http://localhost:8161/admin/queueBrowse/TEST?view=rss&feedType=atom_1.0


Here is an example of how I will get the xml data from JavaScript just in case 
anyone would like to see the code:

https://gist.github.com/zmhassan/8702385



was (Author: zmhassan):
I was originally planning on making a slight change in the design. I was 
planning on making a restful endpoint that will display the first hundred JMS 
messages in queue in JSON format (one argument 'page'). It would save time and 
resource because we don't loop through all 200,000 items in queue. However that 
would make a change in the design and I was thinking there must be a way that 
we can reuse existing code that does web service like functionality. 

One option I was looking at was that we could use the RSS/ATOM feed with xml 
data and pull from it via javascript on the client-side to get the messages in 
queue but when I tried this, it was a really large xml file and takes a long 
time to load. When the number of messages grow too large I was unsuccessful in 
requesting it and parsing it. Perhaps if we can just display 100 messages of 
the 200,000 in queue that would make it an easier problem to solve. 

http://localhost:8161/admin/queueBrowse/TEST?view=rss&feedType=atom_1.0


Here is an example of how I will get the xml data from Javascript just incase 
anyone would like to see the code:

https://gist.github.com/zmhassan/8702385


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Priority: Blocker
> Attachments: AMQ-4994.patch
>
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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)
>

[jira] [Comment Edited] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886224#comment-13886224
 ] 

zmhassan edited comment on AMQ-4994 at 1/30/14 4:22 AM:


I was originally planning on making a slight change in the design. I was 
planning on making a restful endpoint that will display the first hundred JMS 
messages in queue in JSON format (one argument 'page'). It would save time and 
resource because we don't loop through all 200,000 items in queue. However that 
would make a change in the design and I was thinking there must be a way that 
we can reuse existing code that does web service like functionality. 

One option I was looking at was that we could use the RSS/ATOM feed with xml 
data and pull from it via javascript on the client-side to get the messages in 
queue but when I tried this, it was a really large xml file and takes a long 
time to load. When the number of messages grow too large I was unsuccessful in 
requesting it and parsing it. Perhaps if we can just display 100 messages of 
the 200,000 in queue that would make it an easier problem to solve. 

http://localhost:8161/admin/queueBrowse/TEST?view=rss&feedType=atom_1.0


Here is an example of how I will get the xml data from Javascript just incase 
anyone would like to see the code:

https://gist.github.com/zmhassan/8702385



was (Author: zmhassan):
I was originally planning on making a slight change in the design. I was 
planning on making a restful endpoint that will display the first hundred JMS 
messages in queue in JSON format (one argument 'page'). It would save time and 
resource because we don't loop through all 200,000 items in queue. However that 
would make a change in the design and I was thinking there must be a way that 
we can reuse existing code that does web service like functionality. 

One option I was looking at was that we could use the RSS/ATOM feed with xml 
data and pull from it via javascript on the client-side to get the messages in 
queue but when I tried this, it was a really large xml file and takes a long 
time to load. When the number of messages grow too large I was unsuccessful in 
requesting it and parsing it. Perhaps if we can just display 100 messages of 
the 200,000 in queue that would make it an easier problem to solve. 

http://localhost:8161/admin/queueBrowse/TEST?view=rss&feedType=atom_1.0


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Priority: Blocker
> Attachments: AMQ-4994.patch
>
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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.serviceJs

[jira] [Comment Edited] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886224#comment-13886224
 ] 

zmhassan edited comment on AMQ-4994 at 1/30/14 3:54 AM:


I was originally planning on making a slight change in the design. I was 
planning on making a restful endpoint that will display the first hundred JMS 
messages in queue in JSON format (one argument 'page'). It would save time and 
resource because we don't loop through all 200,000 items in queue. However that 
would make a change in the design and I was thinking there must be a way that 
we can reuse existing code that does web service like functionality. 

One option I was looking at was that we could use the RSS/ATOM feed with xml 
data and pull from it via javascript on the client-side to get the messages in 
queue but when I tried this, it was a really large xml file and takes a long 
time to load. When the number of messages grow too large I was unsuccessful in 
requesting it and parsing it. Perhaps if we can just display 100 messages of 
the 200,000 in queue that would make it an easier problem to solve. 

http://localhost:8161/admin/queueBrowse/TEST?view=rss&feedType=atom_1.0



was (Author: zmhassan):
I was originally planning on making a slight change in the design. I was 
planning on making a restful endpoint that will display the first hundred JMS 
messages in queue in JSON format (one argument 'page'). It would save time and 
resource because we don't loop through all 200,000 items in queue. However that 
would make a change in the design and I was thinking there must be a way that 
we can reuse existing code that does web service like functionality. 

One option I was looking at was that we could use the RSS/ATOM feed with xml 
data and pull from it via javascript on the client-side to get the messages in 
queue but when I tried this it was a really large xml file filled with 200,000 
elements. Perhaps if we can just display 100 messages of the 200,000 in queue 
that would make it an easier problem to solve. 

http://localhost:8161/admin/queueBrowse/TEST?view=rss&feedType=atom_1.0


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Priority: Blocker
> Attachments: AMQ-4994.patch
>
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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(ServletHol

[jira] [Commented] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886224#comment-13886224
 ] 

zmhassan commented on AMQ-4994:
---

I was originally planning on making a slight change in the design. I was 
planning on making a restful endpoint that will display the first hundred JMS 
messages in queue in JSON format (one argument 'page'). It would save time and 
resource because we don't loop through all 200,000 items in queue. However that 
would make a change in the design and I was thinking there must be a way that 
we can reuse existing code that does web service like functionality. 

One option I was looking at was that we could use the RSS/ATOM feed with xml 
data and pull from it via javascript on the client-side to get the messages in 
queue but when I tried this it was a really large xml file filled with 200,000 
elements. Perhaps if we can just display 100 messages of the 200,000 in queue 
that would make it an easier problem to solve. 

http://localhost:8161/admin/queueBrowse/TEST?view=rss&feedType=atom_1.0


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Priority: Blocker
> Attachments: AMQ-4994.patch
>
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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:1320)
>   at 
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
>   at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at 
> org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
>   at 
> com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129){code}
> when trying to browse that queue.
> To reproduce it:
> 1. Start a broker with default conf

[jira] [Comment Edited] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885825#comment-13885825
 ] 

zmhassan edited comment on AMQ-4994 at 1/29/14 10:29 PM:
-

I'm able to generate pagination on the UI when the requests are small but I 
seem to be getting an error from the server-side "java.lang out of memory  
" when messages when the queue depth is large. I'm searching for where this bug 
is coming from. Pagination may sort of help but we still need to find some way 
of limiting the amount of messages that get displayed.
I narrowed down where the problem is coming from I suspect that is somewhere in:

https://github.com/apache/activemq/blob/trunk/activemq-web-console/src/main/java/org/apache/activemq/web/controller/SendMessage.java#L51-L79

Also I can imagine that there could me more messages being produced and 
consumed at the same time which we have to consider. Any suggestions on 
possible options? 




was (Author: zmhassan):
I'm able to generate pagination on the UI when the requests are small but I 
seem to be getting an error from the server-side "java.lang out of memory  
" when messages when the queue depth is large. I'm searching for where this bug 
is coming from. Pagination may sort of help but we still need to find some way 
of limiting the amount of messages that get displayed.
I narrowed down where the problem is coming from I suspect that is somewhere in:

https://github.com/apache/activemq/blob/trunk/activemq-web-console/src/main/java/org/apache/activemq/web/controller/SendMessage.java#L51-L79

Also I can imagine that there could me more messages being produced and 
consumed at the same time which we have to consider. Any suggestions on 
possible options? 

Note: Since the user is limited when using a single worker perhaps they can try 
a more scalable architecture and have multiple brokers on different hosts to 
share the load to avoid contending for the same resource.


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Priority: Blocker
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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:1320)
>   at 
> org.springframework.web.filter.RequestContextFilter.d

[jira] [Comment Edited] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885825#comment-13885825
 ] 

zmhassan edited comment on AMQ-4994 at 1/29/14 10:26 PM:
-

I'm able to generate pagination on the UI when the requests are small but I 
seem to be getting an error from the server-side "java.lang out of memory  
" when messages when the queue depth is large. I'm searching for where this bug 
is coming from. Pagination may sort of help but we still need to find some way 
of limiting the amount of messages that get displayed.
I narrowed down where the problem is coming from I suspect that is somewhere in:

https://github.com/apache/activemq/blob/trunk/activemq-web-console/src/main/java/org/apache/activemq/web/controller/SendMessage.java#L51-L79

Also I can imagine that there could me more messages being produced and 
consumed at the same time which we have to consider. Any suggestions on 
possible options? 

Note: Since the user is limited when using a single worker perhaps they can try 
a more scalable architecture and have multiple brokers on different hosts to 
share the load to avoid contending for the same resource.



was (Author: zmhassan):
I'm able to generate pagination on the UI when the requests are small but I 
seem to be getting an error from the server-side "java.lang out of memory  
" when messages when the queue depth is large. I'm searching for where this bug 
is coming from. Pagination may sort of help but we still need to find some way 
of limiting the amount of messages that get displayed.
I narrowed down where the problem is coming from I suspect that is somewhere in:

https://github.com/apache/activemq/blob/trunk/activemq-web-console/src/main/java/org/apache/activemq/web/controller/SendMessage.java#L51-L79

Also I can imagine that there could me more messages being produced and 
consumed at the same time which we have to consider. Any suggestions on 
possible options? 

Note: Since the user is limited when using a single worker perhaps they can try 
a more distributed architecture and have multiple brokers on different hosts to 
share the load to avoid contending for the same resource.


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Priority: Blocker
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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)
>

[jira] [Comment Edited] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues


[ 
https://issues.apache.org/jira/browse/AMQ-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885825#comment-13885825
 ] 

zmhassan edited comment on AMQ-4994 at 1/29/14 10:24 PM:
-

I'm able to generate pagination on the UI when the requests are small but I 
seem to be getting an error from the server-side "java.lang out of memory  
" when messages when the queue depth is large. I'm searching for where this bug 
is coming from. Pagination may sort of help but we still need to find some way 
of limiting the amount of messages that get displayed.
I narrowed down where the problem is coming from I suspect that is somewhere in:

https://github.com/apache/activemq/blob/trunk/activemq-web-console/src/main/java/org/apache/activemq/web/controller/SendMessage.java#L51-L79

Also I can imagine that there could me more messages being produced and 
consumed at the same time which we have to consider. Any suggestions on 
possible options? 

Note: Since the user is limited when using a single worker perhaps they can try 
a more distributed architecture and have multiple brokers on different hosts to 
share the load to avoid contending for the same resource.



was (Author: zmhassan):
I'm able to generate pagination on the UI when the requests are small but I 
seem to be getting an error from the server-side "java.lang out of memory  
" when messages when the queue depth is large. I'm searching for where this bug 
is coming from. Pagination may sort of help but we still need to find some way 
of limiting the amount of messages that get displayed.
I narrowed down where the problem is coming from I suspect that is somewhere in:

https://github.com/apache/activemq/blob/trunk/activemq-web-console/src/main/java/org/apache/activemq/web/controller/SendMessage.java#L51-L79

Also I can imagine that there could me more messages being produced and 
consumed at the same time which we have to consider. Any suggestions on 
possible options? 


> Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing 
> deep queues
> --
>
> Key: AMQ-4994
> URL: https://issues.apache.org/jira/browse/AMQ-4994
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Priority: Blocker
>
> When browsing a deep queue with large number of messages, broker throws 
> {code}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:412)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.writeEscapedXml(OutSupport.java:239)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.out(OutSupport.java:208)
>   at 
> org.apache.taglibs.standard.tag.common.core.OutSupport.doStartTag(OutSupport.java:128)
>   at 
> org.apache.jsp.browse_jsp._jspx_meth_c_out_6(org.apache.jsp.browse_jsp:323)
>   at org.apache.jsp.browse_jsp.access$8(org.apache.jsp.browse_jsp:314)
>   at 
> org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:426)
>   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:1320)
>   at 
> org.springframework.web.filter.RequestContextFilter.d

[jira] [Commented] (AMQ-4994) Web Console - java.lang.OutOfMemoryError: Java heap space - while browsing deep queues