[jira] [Commented] (QPIDJMS-327) QPid JMS has no support for the content-type AMQP properties
[ https://issues.apache.org/jira/browse/QPIDJMS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350562#comment-16350562 ] Leo Riguspi commented on QPIDJMS-327: - Maybe I am over-simplifying, but content-type and content-encoding are AMQP standard properties. A library that claims to support AMQP 1.0 should offer a way to set these standard message properties. Like AMQP.NET Lite does. > QPid JMS has no support for the content-type AMQP properties > > > Key: QPIDJMS-327 > URL: https://issues.apache.org/jira/browse/QPIDJMS-327 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Reporter: Leo Riguspi >Priority: Major > > The content-type AMQP property cannot be set. According to the specifications > it should be set via the Jms property JMS_AMQP_ContentType, however this > results in nothing being set. > NOTE: there is a similar issue (albeit different) for the content-encoding > property (see [https://issues.apache.org/jira/browse/QPIDJMS-295]) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDJMS-327) QPid JMS has no support for the content-type AMQP properties
[ https://issues.apache.org/jira/browse/QPIDJMS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leo Riguspi updated QPIDJMS-327: Description: The content-type AMQP property cannot be set. According to the specifications it should be set via the Jms property JMS_AMQP_ContentType, however this results in nothing being set. NOTE: there is a similar issue (albeit different) for the content-encoding property (see [https://issues.apache.org/jira/browse/QPIDJMS-295]) was: The content-type AMQP property cannot be set. According to the specifications it should be set via the Jms property JMS_AMQP_ContentType, however this results in nothing being set. NOTE: there is a similar issue (albeit different) for the content-encoding property (see ) > QPid JMS has no support for the content-type AMQP properties > > > Key: QPIDJMS-327 > URL: https://issues.apache.org/jira/browse/QPIDJMS-327 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Reporter: Leo Riguspi > > The content-type AMQP property cannot be set. According to the specifications > it should be set via the Jms property JMS_AMQP_ContentType, however this > results in nothing being set. > NOTE: there is a similar issue (albeit different) for the content-encoding > property (see [https://issues.apache.org/jira/browse/QPIDJMS-295]) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDJMS-327) QPid JMS has no support for the content-type AMQP properties
Leo Riguspi created QPIDJMS-327: --- Summary: QPid JMS has no support for the content-type AMQP properties Key: QPIDJMS-327 URL: https://issues.apache.org/jira/browse/QPIDJMS-327 Project: Qpid JMS Issue Type: Bug Components: qpid-jms-client Reporter: Leo Riguspi The content-type AMQP property cannot be set. According to the specifications it should be set via the Jms property JMS_AMQP_ContentType, however this results in nothing being set. NOTE: there is a similar issue (albeit different) for the content-encoding property (see ) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDJMS-295) AMQP property content-encoding cannot be retrieved via JMS_AMQP_ContentEncoding
Leo Riguspi created QPIDJMS-295: --- Summary: AMQP property content-encoding cannot be retrieved via JMS_AMQP_ContentEncoding Key: QPIDJMS-295 URL: https://issues.apache.org/jira/browse/QPIDJMS-295 Project: Qpid JMS Issue Type: Bug Components: qpid-jms-client Affects Versions: 0.23.0 Reporter: Leo Riguspi The AMQP property content-encoding can be set but not retrieved: 1. Create a message and set the vendor property JMS_AMQP_ContentEncoding=gzip using QPid JMS 2. Send the message to an ActiveMQ broker via AMQP 1.0 with transport.transformer=jms (native does not work!) 3. Retrieve the message with QPid JMS: the property JMS_AMQP_ContentEncoding does not exist anymore in the message and there seem to be no other way of retrieving the content-encoding. Note that when consuming the same message with a python client the property seems to be set and accessible via the message.content_encoding field. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6935) Infinite recursion resulting in huge number of Transfer objects created in Delivery, until OutOfMemory
[ https://issues.apache.org/jira/browse/QPID-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15062404#comment-15062404 ] Leo Riguspi commented on QPID-6935: --- Hi Rob, the content in each transfer object seems to be different, at least for the ones we looked at. But there were 49000 Transfer objects in the previous heap dump and 115000 in the new one so it is not possible to say. The problem is that we can't even reproduce the error. We tried to inject several messages, even larger than 10MB. We took heap dumps after each message but can't see anything abnormal. Could the issue be in Camel's code? > Infinite recursion resulting in huge number of Transfer objects created in > Delivery, until OutOfMemory > -- > > Key: QPID-6935 > URL: https://issues.apache.org/jira/browse/QPID-6935 > Project: Qpid > Issue Type: Bug > Components: JMS AMQP 1.0 Client >Affects Versions: 0.32 > Environment: Linux RedHat 7 >Reporter: Leo Riguspi >Priority: Blocker > Attachments: Heap.png, Heap2.png, memory_dump.txt, snapshot1.png, > snapshot2.png > > > We have an Apache ActiveMQ 5.12 running for 2 months now and a Java AMQP > client publishing a few messages every few minutes. Messages are small, less > than 1K and are immediately consumed. > For the second time in two months the client exploded with an OutOfMemory > error. By analysing the memory the culprit seems to be the ArrayList of > Trasfer objects in the Delivery. All of a sudden, for some reason it just > keeps creating new Trasfers until the memory is full. > We have a screenshot of the memory dump in which there are more than 49000 > Trasfer objects in the same Delivery. Unfortunately there seems to be no way > to attach it to this issue. > We did not find a way to reproduce the problem but it looks like some > combination of conditions cause the SessionEndpoint::sendTransfer recursive > method to call itself over and over, each time adding a new Transfer object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6935) Infinite recursion resulting in huge number of Transfer objects created in Delivery, until OutOfMemory
[ https://issues.apache.org/jira/browse/QPID-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leo Riguspi updated QPID-6935: -- Attachment: Heap.png Heap2.png Hi, it just happened for the third time. By looking more closely at the heap dump we have identified the queues where this happens. It looks like the problem occurs when using Apache Camel to automatically forward messages from one queue to other queues. I have attached two additional screenshots, don't know if they can help. > Infinite recursion resulting in huge number of Transfer objects created in > Delivery, until OutOfMemory > -- > > Key: QPID-6935 > URL: https://issues.apache.org/jira/browse/QPID-6935 > Project: Qpid > Issue Type: Bug > Components: JMS AMQP 1.0 Client >Affects Versions: 0.32 > Environment: Linux RedHat 7 >Reporter: Leo Riguspi >Priority: Blocker > Attachments: Heap.png, Heap2.png, memory_dump.txt, snapshot1.png, > snapshot2.png > > > We have an Apache ActiveMQ 5.12 running for 2 months now and a Java AMQP > client publishing a few messages every few minutes. Messages are small, less > than 1K and are immediately consumed. > For the second time in two months the client exploded with an OutOfMemory > error. By analysing the memory the culprit seems to be the ArrayList of > Trasfer objects in the Delivery. All of a sudden, for some reason it just > keeps creating new Trasfers until the memory is full. > We have a screenshot of the memory dump in which there are more than 49000 > Trasfer objects in the same Delivery. Unfortunately there seems to be no way > to attach it to this issue. > We did not find a way to reproduce the problem but it looks like some > combination of conditions cause the SessionEndpoint::sendTransfer recursive > method to call itself over and over, each time adding a new Transfer object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6935) Infinite recursion resulting in huge number of Transfer objects created in Delivery, until OutOfMemory
[ https://issues.apache.org/jira/browse/QPID-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15050972#comment-15050972 ] Leo Riguspi commented on QPID-6935: --- We still have the heap dump but it's too large to post it. Anyway, the largest message we have is 6.5MB which cannot account for the 2,3GB used by the Delivery object. There are three key If statements in the SessionEndpoint::sendTransfer method. Could it be that for some reason it falls in a loop in which it keeps adding a new tranfer and then calls itself again? > Infinite recursion resulting in huge number of Transfer objects created in > Delivery, until OutOfMemory > -- > > Key: QPID-6935 > URL: https://issues.apache.org/jira/browse/QPID-6935 > Project: Qpid > Issue Type: Bug > Components: JMS AMQP 1.0 Client >Affects Versions: 0.32 > Environment: Linux RedHat 7 >Reporter: Leo Riguspi >Priority: Blocker > Attachments: memory_dump.txt, snapshot1.png, snapshot2.png > > > We have an Apache ActiveMQ 5.12 running for 2 months now and a Java AMQP > client publishing a few messages every few minutes. Messages are small, less > than 1K and are immediately consumed. > For the second time in two months the client exploded with an OutOfMemory > error. By analysing the memory the culprit seems to be the ArrayList of > Trasfer objects in the Delivery. All of a sudden, for some reason it just > keeps creating new Trasfers until the memory is full. > We have a screenshot of the memory dump in which there are more than 49000 > Trasfer objects in the same Delivery. Unfortunately there seems to be no way > to attach it to this issue. > We did not find a way to reproduce the problem but it looks like some > combination of conditions cause the SessionEndpoint::sendTransfer recursive > method to call itself over and over, each time adding a new Transfer object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6935) Infinite recursion resulting in huge number of Transfer objects created in Delivery, until OutOfMemory
[ https://issues.apache.org/jira/browse/QPID-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leo Riguspi updated QPID-6935: -- Attachment: snapshot2.png snapshot1.png First screenshot shows the stack. Second screenshot shows the total number of Transfer objects. > Infinite recursion resulting in huge number of Transfer objects created in > Delivery, until OutOfMemory > -- > > Key: QPID-6935 > URL: https://issues.apache.org/jira/browse/QPID-6935 > Project: Qpid > Issue Type: Bug > Components: JMS AMQP 1.0 Client >Affects Versions: 0.32 > Environment: Linux RedHat 7 >Reporter: Leo Riguspi >Priority: Blocker > Attachments: snapshot1.png, snapshot2.png > > > We have an Apache ActiveMQ 5.12 running for 2 months now and a Java AMQP > client publishing a few messages every few minutes. Messages are small, less > than 1K and are immediately consumed. > For the second time in two months the client exploded with an OutOfMemory > error. By analysing the memory the culprit seems to be the ArrayList of > Trasfer objects in the Delivery. All of a sudden, for some reason it just > keeps creating new Trasfers until the memory is full. > We have a screenshot of the memory dump in which there are more than 49000 > Trasfer objects in the same Delivery. Unfortunately there seems to be no way > to attach it to this issue. > We did not find a way to reproduce the problem but it looks like some > combination of conditions cause the SessionEndpoint::sendTransfer recursive > method to call itself over and over, each time adding a new Transfer object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-6935) Infinite recursion resulting in huge number of Transfer objects created in Delivery, until OutOfMemory
[ https://issues.apache.org/jira/browse/QPID-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15048277#comment-15048277 ] Leo Riguspi edited comment on QPID-6935 at 12/9/15 8:25 AM: Here's the heap dump. Thanks. was (Author: leorigu): Here's the heap dump. > Infinite recursion resulting in huge number of Transfer objects created in > Delivery, until OutOfMemory > -- > > Key: QPID-6935 > URL: https://issues.apache.org/jira/browse/QPID-6935 > Project: Qpid > Issue Type: Bug > Components: JMS AMQP 1.0 Client >Affects Versions: 0.32 > Environment: Linux RedHat 7 >Reporter: Leo Riguspi >Priority: Blocker > Attachments: memory_dump.txt, snapshot1.png, snapshot2.png > > > We have an Apache ActiveMQ 5.12 running for 2 months now and a Java AMQP > client publishing a few messages every few minutes. Messages are small, less > than 1K and are immediately consumed. > For the second time in two months the client exploded with an OutOfMemory > error. By analysing the memory the culprit seems to be the ArrayList of > Trasfer objects in the Delivery. All of a sudden, for some reason it just > keeps creating new Trasfers until the memory is full. > We have a screenshot of the memory dump in which there are more than 49000 > Trasfer objects in the same Delivery. Unfortunately there seems to be no way > to attach it to this issue. > We did not find a way to reproduce the problem but it looks like some > combination of conditions cause the SessionEndpoint::sendTransfer recursive > method to call itself over and over, each time adding a new Transfer object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6935) Infinite recursion resulting in huge number of Transfer objects created in Delivery, until OutOfMemory
[ https://issues.apache.org/jira/browse/QPID-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leo Riguspi updated QPID-6935: -- Attachment: memory_dump.txt Here's the heap dump. > Infinite recursion resulting in huge number of Transfer objects created in > Delivery, until OutOfMemory > -- > > Key: QPID-6935 > URL: https://issues.apache.org/jira/browse/QPID-6935 > Project: Qpid > Issue Type: Bug > Components: JMS AMQP 1.0 Client >Affects Versions: 0.32 > Environment: Linux RedHat 7 >Reporter: Leo Riguspi >Priority: Blocker > Attachments: memory_dump.txt, snapshot1.png, snapshot2.png > > > We have an Apache ActiveMQ 5.12 running for 2 months now and a Java AMQP > client publishing a few messages every few minutes. Messages are small, less > than 1K and are immediately consumed. > For the second time in two months the client exploded with an OutOfMemory > error. By analysing the memory the culprit seems to be the ArrayList of > Trasfer objects in the Delivery. All of a sudden, for some reason it just > keeps creating new Trasfers until the memory is full. > We have a screenshot of the memory dump in which there are more than 49000 > Trasfer objects in the same Delivery. Unfortunately there seems to be no way > to attach it to this issue. > We did not find a way to reproduce the problem but it looks like some > combination of conditions cause the SessionEndpoint::sendTransfer recursive > method to call itself over and over, each time adding a new Transfer object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-6935) Infinite recursion resulting in huge number of Transfer objects created in Delivery, until OutOfMemory
Leo Riguspi created QPID-6935: - Summary: Infinite recursion resulting in huge number of Transfer objects created in Delivery, until OutOfMemory Key: QPID-6935 URL: https://issues.apache.org/jira/browse/QPID-6935 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.32 Environment: Linux RedHat 7 Reporter: Leo Riguspi Priority: Blocker We have an Apache ActiveMQ 5.12 running for 2 months now and a Java AMQP client publishing a few messages every few minutes. Messages are small, less than 1K and are immediately consumed. For the second time in two months the client exploded with an OutOfMemory error. By analysing the memory the culprit seems to be the ArrayList of Trasfer objects in the Delivery. All of a sudden, for some reason it just keeps creating new Trasfers until the memory is full. We have a screenshot of the memory dump in which there are more than 49000 Trasfer objects in the same Delivery. Unfortunately there seems to be no way to attach it to this issue. We did not find a way to reproduce the problem but it looks like some combination of conditions cause the SessionEndpoint::sendTransfer recursive method to call itself over and over, each time adding a new Transfer object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
