You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Subrata Saha (JIRA)" <ji...@apache.org> on 2008/05/02 12:06:43 UTC
[jira] Created: (AMQ-1708) Memory Leak while sending Text/Stream
Message of size 512 kb or more with MySql persistance
Memory Leak while sending Text/Stream Message of size 512 kb or more with MySql persistance
-------------------------------------------------------------------------------------------
Key: AMQ-1708
URL: https://issues.apache.org/activemq/browse/AMQ-1708
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.0.0
Environment: My activeMQ is running on Linux box. I sees the gradual shoot up of Memory. which causes some exception.
Reporter: Subrata Saha
Attachments: BugAttachment.zip
steps to following to reproduce the problem::
1) ActiveMQ is running on Linux box . MySql is configured as persistance data base.
2) Write a simple producer and consumer program which produces/consumes from five different queue.
3) while producer and consumer running at the same time (send 1000000 messages in a for loop)
You can see its memory being eaten up in the Linux server.
4) after soem time consuming some 300 or so messages it will end up with an exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1708) Memory Leak while sending Text/Stream
Message of size 512 kb or more with MySql persistance
Posted by "Subrata Saha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42578#action_42578 ]
Subrata Saha commented on AMQ-1708:
-----------------------------------
And the memory limit never goes down , even if you stop the producer and consumer program.
> Memory Leak while sending Text/Stream Message of size 512 kb or more with MySql persistance
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-1708
> URL: https://issues.apache.org/activemq/browse/AMQ-1708
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0
> Environment: My activeMQ is running on Linux box. I sees the gradual shoot up of Memory. which causes some exception.
> Reporter: Subrata Saha
> Attachments: BugAttachment.zip
>
>
> steps to following to reproduce the problem::
> 1) ActiveMQ is running on Linux box . MySql is configured as persistance data base.
> 2) Write a simple producer and consumer program which produces/consumes from five different queue.
> 3) while producer and consumer running at the same time (send 1000000 messages in a for loop)
> You can see its memory being eaten up in the Linux server.
> 4) after soem time consuming some 300 or so messages it will end up with an exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1708) Memory Leak while sending Text/Stream
Message of size 512 kb or more with MySql persistance
Posted by "Subrata Saha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42577#action_42577 ]
Subrata Saha commented on AMQ-1708:
-----------------------------------
Sorry i forgot
the message size is starting from 16kb
> Memory Leak while sending Text/Stream Message of size 512 kb or more with MySql persistance
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-1708
> URL: https://issues.apache.org/activemq/browse/AMQ-1708
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0
> Environment: My activeMQ is running on Linux box. I sees the gradual shoot up of Memory. which causes some exception.
> Reporter: Subrata Saha
> Attachments: BugAttachment.zip
>
>
> steps to following to reproduce the problem::
> 1) ActiveMQ is running on Linux box . MySql is configured as persistance data base.
> 2) Write a simple producer and consumer program which produces/consumes from five different queue.
> 3) while producer and consumer running at the same time (send 1000000 messages in a for loop)
> You can see its memory being eaten up in the Linux server.
> 4) after soem time consuming some 300 or so messages it will end up with an exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (AMQ-1708) Memory Leak while sending
Text/Stream Message of size 512 kb or more with MySql persistance
Posted by "Subrata Saha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42577#action_42577 ]
subrata_saha_1208 edited comment on AMQ-1708 at 5/7/08 3:02 AM:
-----------------------------------------------------------
Sorry i forgot
the message size is starting from 16kb
and keep on increasing data size as 512 kb and then 1mb etc...
was (Author: subrata_saha_1208):
Sorry i forgot
the message size is starting from 16kb
> Memory Leak while sending Text/Stream Message of size 512 kb or more with MySql persistance
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-1708
> URL: https://issues.apache.org/activemq/browse/AMQ-1708
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0
> Environment: My activeMQ is running on Linux box. I sees the gradual shoot up of Memory. which causes some exception.
> Reporter: Subrata Saha
> Attachments: BugAttachment.zip
>
>
> steps to following to reproduce the problem::
> 1) ActiveMQ is running on Linux box . MySql is configured as persistance data base.
> 2) Write a simple producer and consumer program which produces/consumes from five different queue.
> 3) while producer and consumer running at the same time (send 1000000 messages in a for loop)
> You can see its memory being eaten up in the Linux server.
> 4) after soem time consuming some 300 or so messages it will end up with an exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.