[jira] [Updated] (ARTEMIS-2784) Could not decode properties for CoreMessage ... java.lang.IndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/ARTEMIS-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noah Zucker updated ARTEMIS-2784:
-
Description:
Our application is observing a large number of messages from Artemis
experiencing the following error
Server Version: ArtemisMQ 2.12.0
Client Version: org.hornetq hornetq-core 2.2.7.Final
{code}
Could not decode properties for
CoreMessage[messageID=0,durable=true,userID=null,priority=4, ti
mestamp=1590674773446,expiration=0,address=null, propertiesLocation=145:
java.lang.IndexOutOfBoundsException
activemq-artemis 2020-05-28 14:09:41,364 WARN
[org.apache.activemq.artemis.core.message.impl.CoreMessage] Failed message has
messageID=0 and the following buffer:
activemq-artemis +-+
activemq-artemis | 0 1 2 3 4 5 6 7 8 9 a b c d e f |
activemq-artemis
++-++
activemq-artemis || 00 00 00 7d 00 00 00 66 00 66 7b 20 22 74 22 20
|...}...f.f{ "t" |
activemq-artemis |0010| 3a 20 22 63 6f 6d 2e 6e 6f 76 75 73 2e 61 6e 61 |:
"com.novus.ana|
activemq-artemis |0020| 6c 79 74 69 63 73 2e 75 74 69 6c 2e 74 61 73 6b
|lytics.util.task|
activemq-artemis |0030| 73 2e 41 73 79 6e 63 43 6f 6e 73 75 6d 65 72 4d
|s.AsyncConsumerM|
activemq-artemis |0040| 65 73 73 61 67 65 22 20 2c 20 22 6d 73 67 22 20
|essage" , "msg" |
activemq-artemis |0050| 3a 20 22 66 65 61 74 75 72 65 46 6c 61 67 43 61 |:
"featureFlagCa|
activemq-artemis |0060| 63 68 65 2e 69 6e 76 61 6c 69 64 61 74 65 22 7d
|che.invalidate"}|
activemq-artemis |0070| 00 00 00 f2 00 00 00 00 00 00 00 00 00 00 03 ff
||
activemq-artemis |0080| 00 00 00 00 00 00 00 00 00 00 01 72 5b 9a d5 c6
|...r[...|
activemq-artemis |0090| 04 01 00 00 00 01 00 00 00 16 5f 00 48 00 51 00
|.._.H.Q.|
activemq-artemis |00a0| 5f 00 44 00 55 00 50 00 4c 00 5f 00 49 00 44 00
|_.D.U.P.L._.I.D.|
activemq-artemis |00b0| 0a 00 00 00 30 35 00 65 00 63 00 66 00 63 00 35
|05.e.c.f.c.5|
activemq-artemis |00c0| 00 35 00 35 00 64 00 39 00 31 00 33 00 62 00 32
|.5.5.d.9.1.3.b.2|
activemq-artemis |00d0| 00 34 00 65 00 66 00 30 00 32 00 32 00
|.4.e.f.0.2.2. |
activemq-artemis
++-++
{code}
Our client-side is also having trouble reading incoming text messages in its
onMessage callback. We encounter this with frequency: {{Unable to parse string
bodybuffer from Msg 'class org.hornetq.core.client.impl.ClientMessageImpl'
having id=4530593 !!! Details: java.lang.IndexOutOfBoundsException: Not enough
readable bytes - Need 24, maximum is 20}}
Apologies for being open ended on this, please let me know what additional
details to provide.
was:
Our application is observing a large number of messages from Artemis
experiencing the following error
Version: ArtemisMQ 2.12.0
{code}
Could not decode properties for
CoreMessage[messageID=0,durable=true,userID=null,priority=4, ti
mestamp=1590674773446,expiration=0,address=null, propertiesLocation=145:
java.lang.IndexOutOfBoundsException
activemq-artemis 2020-05-28 14:09:41,364 WARN
[org.apache.activemq.artemis.core.message.impl.CoreMessage] Failed message has
messageID=0 and the following buffer:
activemq-artemis +-+
activemq-artemis | 0 1 2 3 4 5 6 7 8 9 a b c d e f |
activemq-artemis
++-++
activemq-artemis || 00 00 00 7d 00 00 00 66 00 66 7b 20 22 74 22 20
|...}...f.f{ "t" |
activemq-artemis |0010| 3a 20 22 63 6f 6d 2e 6e 6f 76 75 73 2e 61 6e 61 |:
"com.novus.ana|
activemq-artemis |0020| 6c 79 74 69 63 73 2e 75 74 69 6c 2e 74 61 73 6b
|lytics.util.task|
activemq-artemis |0030| 73 2e 41 73 79 6e 63 43 6f 6e 73 75 6d 65 72 4d
|s.AsyncConsumerM|
activemq-artemis |0040| 65 73 73 61 67 65 22 20 2c 20 22 6d 73 67 22 20
|essage" , "msg" |
activemq-artemis |0050| 3a 20 22 66 65 61 74 75 72 65 46 6c 61 67 43 61 |:
"featureFlagCa|
activemq-artemis |0060| 63 68 65 2e 69 6e 76 61 6c 69 64 61 74 65 22 7d
|che.invalidate"}|
activemq-artemis |0070| 00 00 00 f2 00 00 00 00 00 00 00 00 00 00 03 ff
||
activemq-artemis |0080| 00 00 00 00 00 00 00 00 00 00 01 72 5b 9a d5 c6
|...r[...|
activemq-artemis |0090| 04 01 00 00 00 01 00 00 00 16 5f 00 48 00 51 00
|.._.H.Q.|
activemq-artemis |00a0| 5f 00 44 00 55 00 50 00 4c 00 5f 00 49 00 44 00
|_.D.U.P.L._.I.D.|
activemq-artemis |00b0| 0a 00 00 00 30 35 00 65 00 63 00 66 00 63 00 35
|05.e.c.f.c.5|
activemq-artemis |00c0| 00 35 00 35 00 64 00 39 00 31 00 33 00 62 00 32
|.5.5.d.9.1.3.b.2|
[jira] [Updated] (ARTEMIS-2784) Could not decode properties for CoreMessage ... java.lang.IndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/ARTEMIS-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noah Zucker updated ARTEMIS-2784:
-
Description:
Our application is observing a large number of messages from Artemis
experiencing the following error
Version: ArtemisMQ 2.12.0
{code}
Could not decode properties for
CoreMessage[messageID=0,durable=true,userID=null,priority=4, ti
mestamp=1590674773446,expiration=0,address=null, propertiesLocation=145:
java.lang.IndexOutOfBoundsException
activemq-artemis 2020-05-28 14:09:41,364 WARN
[org.apache.activemq.artemis.core.message.impl.CoreMessage] Failed message has
messageID=0 and the following buffer:
activemq-artemis +-+
activemq-artemis | 0 1 2 3 4 5 6 7 8 9 a b c d e f |
activemq-artemis
++-++
activemq-artemis || 00 00 00 7d 00 00 00 66 00 66 7b 20 22 74 22 20
|...}...f.f{ "t" |
activemq-artemis |0010| 3a 20 22 63 6f 6d 2e 6e 6f 76 75 73 2e 61 6e 61 |:
"com.novus.ana|
activemq-artemis |0020| 6c 79 74 69 63 73 2e 75 74 69 6c 2e 74 61 73 6b
|lytics.util.task|
activemq-artemis |0030| 73 2e 41 73 79 6e 63 43 6f 6e 73 75 6d 65 72 4d
|s.AsyncConsumerM|
activemq-artemis |0040| 65 73 73 61 67 65 22 20 2c 20 22 6d 73 67 22 20
|essage" , "msg" |
activemq-artemis |0050| 3a 20 22 66 65 61 74 75 72 65 46 6c 61 67 43 61 |:
"featureFlagCa|
activemq-artemis |0060| 63 68 65 2e 69 6e 76 61 6c 69 64 61 74 65 22 7d
|che.invalidate"}|
activemq-artemis |0070| 00 00 00 f2 00 00 00 00 00 00 00 00 00 00 03 ff
||
activemq-artemis |0080| 00 00 00 00 00 00 00 00 00 00 01 72 5b 9a d5 c6
|...r[...|
activemq-artemis |0090| 04 01 00 00 00 01 00 00 00 16 5f 00 48 00 51 00
|.._.H.Q.|
activemq-artemis |00a0| 5f 00 44 00 55 00 50 00 4c 00 5f 00 49 00 44 00
|_.D.U.P.L._.I.D.|
activemq-artemis |00b0| 0a 00 00 00 30 35 00 65 00 63 00 66 00 63 00 35
|05.e.c.f.c.5|
activemq-artemis |00c0| 00 35 00 35 00 64 00 39 00 31 00 33 00 62 00 32
|.5.5.d.9.1.3.b.2|
activemq-artemis |00d0| 00 34 00 65 00 66 00 30 00 32 00 32 00
|.4.e.f.0.2.2. |
activemq-artemis
++-++
{code}
Our client-side is also having trouble reading incoming text messages in its
onMessage callback. We encounter this with frequency: {{Unable to parse string
bodybuffer from Msg 'class org.hornetq.core.client.impl.ClientMessageImpl'
having id=4530593 !!! Details: java.lang.IndexOutOfBoundsException: Not enough
readable bytes - Need 24, maximum is 20}}
Apologies for being open ended on this, please let me know what additional
details to provide.
was:
Our application is observing a large number of messages from Artemis
experiencing the following error
Version: ArtemisMQ 2.12.0
{code}
Could not decode properties for
CoreMessage[messageID=0,durable=true,userID=null,priority=4, ti
mestamp=1590674773446,expiration=0,address=null, propertiesLocation=145:
java.lang.IndexOutOfBoundsException
activemq-artemis 2020-05-28 14:09:41,364 WARN
[org.apache.activemq.artemis.core.message.impl.CoreMessage] Failed message has
messageID=0 and the following buffer:
activemq-artemis +-+
activemq-artemis | 0 1 2 3 4 5 6 7 8 9 a b c d e f |
activemq-artemis
++-++
activemq-artemis || 00 00 00 7d 00 00 00 66 00 66 7b 20 22 74 22 20
|...}...f.f{ "t" |
activemq-artemis |0010| 3a 20 22 63 6f 6d 2e 6e 6f 76 75 73 2e 61 6e 61 |:
"com.novus.ana|
activemq-artemis |0020| 6c 79 74 69 63 73 2e 75 74 69 6c 2e 74 61 73 6b
|lytics.util.task|
activemq-artemis |0030| 73 2e 41 73 79 6e 63 43 6f 6e 73 75 6d 65 72 4d
|s.AsyncConsumerM|
activemq-artemis |0040| 65 73 73 61 67 65 22 20 2c 20 22 6d 73 67 22 20
|essage" , "msg" |
activemq-artemis |0050| 3a 20 22 66 65 61 74 75 72 65 46 6c 61 67 43 61 |:
"featureFlagCa|
activemq-artemis |0060| 63 68 65 2e 69 6e 76 61 6c 69 64 61 74 65 22 7d
|che.invalidate"}|
activemq-artemis |0070| 00 00 00 f2 00 00 00 00 00 00 00 00 00 00 03 ff
||
activemq-artemis |0080| 00 00 00 00 00 00 00 00 00 00 01 72 5b 9a d5 c6
|...r[...|
activemq-artemis |0090| 04 01 00 00 00 01 00 00 00 16 5f 00 48 00 51 00
|.._.H.Q.|
activemq-artemis |00a0| 5f 00 44 00 55 00 50 00 4c 00 5f 00 49 00 44 00
|_.D.U.P.L._.I.D.|
activemq-artemis |00b0| 0a 00 00 00 30 35 00 65 00 63 00 66 00 63 00 35
|05.e.c.f.c.5|
activemq-artemis |00c0| 00 35 00 35 00 64 00 39 00 31 00 33 00 62 00 32
|.5.5.d.9.1.3.b.2|
activemq-artemis |00d0| 00 34 00 65 00 66 00 30 00 32 0
[jira] [Created] (ARTEMIS-2784) Could not decode properties for CoreMessage ... java.lang.IndexOutOfBoundsException
Noah Zucker created ARTEMIS-2784:
Summary: Could not decode properties for CoreMessage ...
java.lang.IndexOutOfBoundsException
Key: ARTEMIS-2784
URL: https://issues.apache.org/jira/browse/ARTEMIS-2784
Project: ActiveMQ Artemis
Issue Type: Bug
Affects Versions: 2.12.0
Reporter: Noah Zucker
Our application is observing a large number of messages from Artemis
experiencing the following error
Version: ArtemisMQ 2.12.0
{code}
Could not decode properties for
CoreMessage[messageID=0,durable=true,userID=null,priority=4, ti
mestamp=1590674773446,expiration=0,address=null, propertiesLocation=145:
java.lang.IndexOutOfBoundsException
activemq-artemis 2020-05-28 14:09:41,364 WARN
[org.apache.activemq.artemis.core.message.impl.CoreMessage] Failed message has
messageID=0 and the following buffer:
activemq-artemis +-+
activemq-artemis | 0 1 2 3 4 5 6 7 8 9 a b c d e f |
activemq-artemis
++-++
activemq-artemis || 00 00 00 7d 00 00 00 66 00 66 7b 20 22 74 22 20
|...}...f.f{ "t" |
activemq-artemis |0010| 3a 20 22 63 6f 6d 2e 6e 6f 76 75 73 2e 61 6e 61 |:
"com.novus.ana|
activemq-artemis |0020| 6c 79 74 69 63 73 2e 75 74 69 6c 2e 74 61 73 6b
|lytics.util.task|
activemq-artemis |0030| 73 2e 41 73 79 6e 63 43 6f 6e 73 75 6d 65 72 4d
|s.AsyncConsumerM|
activemq-artemis |0040| 65 73 73 61 67 65 22 20 2c 20 22 6d 73 67 22 20
|essage" , "msg" |
activemq-artemis |0050| 3a 20 22 66 65 61 74 75 72 65 46 6c 61 67 43 61 |:
"featureFlagCa|
activemq-artemis |0060| 63 68 65 2e 69 6e 76 61 6c 69 64 61 74 65 22 7d
|che.invalidate"}|
activemq-artemis |0070| 00 00 00 f2 00 00 00 00 00 00 00 00 00 00 03 ff
||
activemq-artemis |0080| 00 00 00 00 00 00 00 00 00 00 01 72 5b 9a d5 c6
|...r[...|
activemq-artemis |0090| 04 01 00 00 00 01 00 00 00 16 5f 00 48 00 51 00
|.._.H.Q.|
activemq-artemis |00a0| 5f 00 44 00 55 00 50 00 4c 00 5f 00 49 00 44 00
|_.D.U.P.L._.I.D.|
activemq-artemis |00b0| 0a 00 00 00 30 35 00 65 00 63 00 66 00 63 00 35
|05.e.c.f.c.5|
activemq-artemis |00c0| 00 35 00 35 00 64 00 39 00 31 00 33 00 62 00 32
|.5.5.d.9.1.3.b.2|
activemq-artemis |00d0| 00 34 00 65 00 66 00 30 00 32 00 32 00
|.4.e.f.0.2.2. |
activemq-artemis
++-++
{code}
Apologies for being open ended on this, please direc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2784) Could not decode properties for CoreMessage ... java.lang.IndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/ARTEMIS-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noah Zucker updated ARTEMIS-2784:
-
Description:
Our application is observing a large number of messages from Artemis
experiencing the following error
Version: ArtemisMQ 2.12.0
{code}
Could not decode properties for
CoreMessage[messageID=0,durable=true,userID=null,priority=4, ti
mestamp=1590674773446,expiration=0,address=null, propertiesLocation=145:
java.lang.IndexOutOfBoundsException
activemq-artemis 2020-05-28 14:09:41,364 WARN
[org.apache.activemq.artemis.core.message.impl.CoreMessage] Failed message has
messageID=0 and the following buffer:
activemq-artemis +-+
activemq-artemis | 0 1 2 3 4 5 6 7 8 9 a b c d e f |
activemq-artemis
++-++
activemq-artemis || 00 00 00 7d 00 00 00 66 00 66 7b 20 22 74 22 20
|...}...f.f{ "t" |
activemq-artemis |0010| 3a 20 22 63 6f 6d 2e 6e 6f 76 75 73 2e 61 6e 61 |:
"com.novus.ana|
activemq-artemis |0020| 6c 79 74 69 63 73 2e 75 74 69 6c 2e 74 61 73 6b
|lytics.util.task|
activemq-artemis |0030| 73 2e 41 73 79 6e 63 43 6f 6e 73 75 6d 65 72 4d
|s.AsyncConsumerM|
activemq-artemis |0040| 65 73 73 61 67 65 22 20 2c 20 22 6d 73 67 22 20
|essage" , "msg" |
activemq-artemis |0050| 3a 20 22 66 65 61 74 75 72 65 46 6c 61 67 43 61 |:
"featureFlagCa|
activemq-artemis |0060| 63 68 65 2e 69 6e 76 61 6c 69 64 61 74 65 22 7d
|che.invalidate"}|
activemq-artemis |0070| 00 00 00 f2 00 00 00 00 00 00 00 00 00 00 03 ff
||
activemq-artemis |0080| 00 00 00 00 00 00 00 00 00 00 01 72 5b 9a d5 c6
|...r[...|
activemq-artemis |0090| 04 01 00 00 00 01 00 00 00 16 5f 00 48 00 51 00
|.._.H.Q.|
activemq-artemis |00a0| 5f 00 44 00 55 00 50 00 4c 00 5f 00 49 00 44 00
|_.D.U.P.L._.I.D.|
activemq-artemis |00b0| 0a 00 00 00 30 35 00 65 00 63 00 66 00 63 00 35
|05.e.c.f.c.5|
activemq-artemis |00c0| 00 35 00 35 00 64 00 39 00 31 00 33 00 62 00 32
|.5.5.d.9.1.3.b.2|
activemq-artemis |00d0| 00 34 00 65 00 66 00 30 00 32 00 32 00
|.4.e.f.0.2.2. |
activemq-artemis
++-++
{code}
Apologies for being open ended on this, please let me know what additional
details to provide.
was:
Our application is observing a large number of messages from Artemis
experiencing the following error
Version: ArtemisMQ 2.12.0
{code}
Could not decode properties for
CoreMessage[messageID=0,durable=true,userID=null,priority=4, ti
mestamp=1590674773446,expiration=0,address=null, propertiesLocation=145:
java.lang.IndexOutOfBoundsException
activemq-artemis 2020-05-28 14:09:41,364 WARN
[org.apache.activemq.artemis.core.message.impl.CoreMessage] Failed message has
messageID=0 and the following buffer:
activemq-artemis +-+
activemq-artemis | 0 1 2 3 4 5 6 7 8 9 a b c d e f |
activemq-artemis
++-++
activemq-artemis || 00 00 00 7d 00 00 00 66 00 66 7b 20 22 74 22 20
|...}...f.f{ "t" |
activemq-artemis |0010| 3a 20 22 63 6f 6d 2e 6e 6f 76 75 73 2e 61 6e 61 |:
"com.novus.ana|
activemq-artemis |0020| 6c 79 74 69 63 73 2e 75 74 69 6c 2e 74 61 73 6b
|lytics.util.task|
activemq-artemis |0030| 73 2e 41 73 79 6e 63 43 6f 6e 73 75 6d 65 72 4d
|s.AsyncConsumerM|
activemq-artemis |0040| 65 73 73 61 67 65 22 20 2c 20 22 6d 73 67 22 20
|essage" , "msg" |
activemq-artemis |0050| 3a 20 22 66 65 61 74 75 72 65 46 6c 61 67 43 61 |:
"featureFlagCa|
activemq-artemis |0060| 63 68 65 2e 69 6e 76 61 6c 69 64 61 74 65 22 7d
|che.invalidate"}|
activemq-artemis |0070| 00 00 00 f2 00 00 00 00 00 00 00 00 00 00 03 ff
||
activemq-artemis |0080| 00 00 00 00 00 00 00 00 00 00 01 72 5b 9a d5 c6
|...r[...|
activemq-artemis |0090| 04 01 00 00 00 01 00 00 00 16 5f 00 48 00 51 00
|.._.H.Q.|
activemq-artemis |00a0| 5f 00 44 00 55 00 50 00 4c 00 5f 00 49 00 44 00
|_.D.U.P.L._.I.D.|
activemq-artemis |00b0| 0a 00 00 00 30 35 00 65 00 63 00 66 00 63 00 35
|05.e.c.f.c.5|
activemq-artemis |00c0| 00 35 00 35 00 64 00 39 00 31 00 33 00 62 00 32
|.5.5.d.9.1.3.b.2|
activemq-artemis |00d0| 00 34 00 65 00 66 00 30 00 32 00 32 00
|.4.e.f.0.2.2. |
activemq-artemis
++-++
{code}
Apologies for being open ended on this, please direc
> Could not decode properties for CoreMessage ...
> java.lang.IndexOutOfBoundsException
>
[jira] [Work logged] (ARTEMIS-2783) User not set on shared queue
[ https://issues.apache.org/jira/browse/ARTEMIS-2783?focusedWorklogId=438428&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438428 ] ASF GitHub Bot logged work on ARTEMIS-2783: --- Author: ASF GitHub Bot Created on: 28/May/20 20:38 Start Date: 28/May/20 20:38 Worklog Time Spent: 10m Work Description: asfgit closed pull request #3150: URL: https://github.com/apache/activemq-artemis/pull/3150 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 438428) Time Spent: 20m (was: 10m) > User not set on shared queue > > > Key: ARTEMIS-2783 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2783 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.13.0 >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2783) User not set on shared queue
[ https://issues.apache.org/jira/browse/ARTEMIS-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119066#comment-17119066 ] ASF subversion and git services commented on ARTEMIS-2783: -- Commit 0443128b8145b4d0149bb2e6d1a139daabe93ff7 in activemq-artemis's branch refs/heads/master from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=0443128 ] ARTEMIS-2783 user not set on shared queue > User not set on shared queue > > > Key: ARTEMIS-2783 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2783 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.13.0 >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2781) Return only local queue names for AddressControl.getQueueNames()
[
https://issues.apache.org/jira/browse/ARTEMIS-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119064#comment-17119064
]
ASF subversion and git services commented on ARTEMIS-2781:
--
Commit 39b3dd1044138ea2a516b67fc6452f57358ea14d in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=39b3dd1 ]
ARTEMIS-2781 Adding getAllQueueNames; fixing tests
> Return only local queue names for AddressControl.getQueueNames()
>
>
> Key: ARTEMIS-2781
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2781
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> There is a discrepancy between what {{AddressControl.getQueueNames()}}
> returns and what {{ActiveMQServerControl.getQueueNames()}} returns. The
> former returns the names of both local and remote queue bindings whereas the
> latter only returns the names of local queue bindings. This is confusing for
> users. They return values should be consistent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2781) Return only local queue names for AddressControl.getQueueNames()
[
https://issues.apache.org/jira/browse/ARTEMIS-2781?focusedWorklogId=438427&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438427
]
ASF GitHub Bot logged work on ARTEMIS-2781:
---
Author: ASF GitHub Bot
Created on: 28/May/20 20:37
Start Date: 28/May/20 20:37
Worklog Time Spent: 10m
Work Description: asfgit closed pull request #3152:
URL: https://github.com/apache/activemq-artemis/pull/3152
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 438427)
Time Spent: 1h 20m (was: 1h 10m)
> Return only local queue names for AddressControl.getQueueNames()
>
>
> Key: ARTEMIS-2781
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2781
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> There is a discrepancy between what {{AddressControl.getQueueNames()}}
> returns and what {{ActiveMQServerControl.getQueueNames()}} returns. The
> former returns the names of both local and remote queue bindings whereas the
> latter only returns the names of local queue bindings. This is confusing for
> users. They return values should be consistent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2649) Auto-create DLQ message loss when moving messages between destinations
[ https://issues.apache.org/jira/browse/ARTEMIS-2649?focusedWorklogId=438402&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438402 ] ASF GitHub Bot logged work on ARTEMIS-2649: --- Author: ASF GitHub Bot Created on: 28/May/20 19:26 Start Date: 28/May/20 19:26 Worklog Time Spent: 10m Work Description: jbertram commented on pull request #3017: URL: https://github.com/apache/activemq-artemis/pull/3017#issuecomment-635548846 @clebertsuconic, I rebased. The problem here is that if we don't change the semantics then there can be message loss in use-cases involving, for example, diverts and auto-created dead-letter resources. I decided to implement the bread crumbs in order to preserve all the history. However, if we don't want to preserve the history then we should allow the existing `ORIG` properties to be overwritten as necessary. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 438402) Time Spent: 2h 40m (was: 2.5h) > Auto-create DLQ message loss when moving messages between destinations > -- > > Key: ARTEMIS-2649 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2649 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.12.0 > Environment: Centos 7 container in OKD with Java 8. >Reporter: Piotr Klimczak >Priority: Major > Time Spent: 2h 40m > Remaining Estimate: 0h > > [~jbertram], first of all thanks a lot for ARTEMIS-2587 implementation. > This was a must for me to switch to Artemis. > In past I have even tried to implement it in Artermis, but having no > previous experience with it, only with your PR I understood how nicely and > easily it can be implemented and how much I have overcomplicated it. > So I am testing 2.12.0 snapshot as I am really interested in work done under > ARTEMIS-2587. > I am connecting using open wire protocol using camel-jms component, having > replaced old AMQ5 with Artermis. > On failed consumption, I can see queue being created under DLQ address with > multicast and filter _AMQ_ORIG_ADDRESS = 'some.queue'. > However it is empty and message is lost. > Reproduction scenario: > # Sending message to address A > # Moving message from A queue to B using web console move function > # Consuming from B and failing consumption > Observed state: > # Queue is being created > # Message is lost and logs are not indicating anything > As a result this message being moved from A to be B queue, the header > "_AMQ_ORIG_ADDRESS" has value "A" instead of "B" and therefore it does not > match the filter "B" and is getting lost. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2778) AcceptorControl returns only transport parameters
[ https://issues.apache.org/jira/browse/ARTEMIS-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118996#comment-17118996 ] ASF subversion and git services commented on ARTEMIS-2778: -- Commit a7df87adf949e65a98b95939bce182fe46a12968 in activemq-artemis's branch refs/heads/master from brusdev [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=a7df87a ] ARTEMIS-2778 AcceptorControl returns only transport parameters Fix AcceptorControl to return all acceptor parameters. > AcceptorControl returns only transport parameters > - > > Key: ARTEMIS-2778 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2778 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Domenico Bruscino >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > The AcceptorControl returns only transport parameters and it doesn't return > the protocol parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2778) AcceptorControl returns only transport parameters
[ https://issues.apache.org/jira/browse/ARTEMIS-2778?focusedWorklogId=438396&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438396 ] ASF GitHub Bot logged work on ARTEMIS-2778: --- Author: ASF GitHub Bot Created on: 28/May/20 19:01 Start Date: 28/May/20 19:01 Worklog Time Spent: 10m Work Description: asfgit closed pull request #3147: URL: https://github.com/apache/activemq-artemis/pull/3147 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 438396) Time Spent: 50m (was: 40m) > AcceptorControl returns only transport parameters > - > > Key: ARTEMIS-2778 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2778 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Domenico Bruscino >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > The AcceptorControl returns only transport parameters and it doesn't return > the protocol parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ARTEMIS-2778) AcceptorControl returns only transport parameters
[ https://issues.apache.org/jira/browse/ARTEMIS-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-2778. - Fix Version/s: 2.14.0 Resolution: Fixed > AcceptorControl returns only transport parameters > - > > Key: ARTEMIS-2778 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2778 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Domenico Bruscino >Priority: Major > Fix For: 2.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The AcceptorControl returns only transport parameters and it doesn't return > the protocol parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2781) Return only local queue names for AddressControl.getQueueNames()
[
https://issues.apache.org/jira/browse/ARTEMIS-2781?focusedWorklogId=438372&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438372
]
ASF GitHub Bot logged work on ARTEMIS-2781:
---
Author: ASF GitHub Bot
Created on: 28/May/20 17:52
Start Date: 28/May/20 17:52
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on pull request #3149:
URL: https://github.com/apache/activemq-artemis/pull/3149#issuecomment-635500915
and then followed up with #3152
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 438372)
Time Spent: 1h 10m (was: 1h)
> Return only local queue names for AddressControl.getQueueNames()
>
>
> Key: ARTEMIS-2781
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2781
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> There is a discrepancy between what {{AddressControl.getQueueNames()}}
> returns and what {{ActiveMQServerControl.getQueueNames()}} returns. The
> former returns the names of both local and remote queue bindings whereas the
> latter only returns the names of local queue bindings. This is confusing for
> users. They return values should be consistent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2781) Return only local queue names for AddressControl.getQueueNames()
[
https://issues.apache.org/jira/browse/ARTEMIS-2781?focusedWorklogId=438362&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438362
]
ASF GitHub Bot logged work on ARTEMIS-2781:
---
Author: ASF GitHub Bot
Created on: 28/May/20 17:19
Start Date: 28/May/20 17:19
Worklog Time Spent: 10m
Work Description: clebertsuconic closed pull request #3151:
URL: https://github.com/apache/activemq-artemis/pull/3151
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 438362)
Time Spent: 1h (was: 50m)
> Return only local queue names for AddressControl.getQueueNames()
>
>
> Key: ARTEMIS-2781
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2781
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> There is a discrepancy between what {{AddressControl.getQueueNames()}}
> returns and what {{ActiveMQServerControl.getQueueNames()}} returns. The
> former returns the names of both local and remote queue bindings whereas the
> latter only returns the names of local queue bindings. This is confusing for
> users. They return values should be consistent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2781) Return only local queue names for AddressControl.getQueueNames()
[
https://issues.apache.org/jira/browse/ARTEMIS-2781?focusedWorklogId=438354&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438354
]
ASF GitHub Bot logged work on ARTEMIS-2781:
---
Author: ASF GitHub Bot
Created on: 28/May/20 17:06
Start Date: 28/May/20 17:06
Worklog Time Spent: 10m
Work Description: jbertram commented on pull request #3151:
URL: https://github.com/apache/activemq-artemis/pull/3151#issuecomment-635476574
To be clear, I don't think the original semantic should be restored due to
the discrepancy with `ActiveMQServerControl.getQueueNames()`. I updated the
Jira description to be more clear.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 438354)
Time Spent: 50m (was: 40m)
> Return only local queue names for AddressControl.getQueueNames()
>
>
> Key: ARTEMIS-2781
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2781
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> There is a discrepancy between what {{AddressControl.getQueueNames()}}
> returns and what {{ActiveMQServerControl.getQueueNames()}} returns. The
> former returns the names of both local and remote queue bindings whereas the
> latter only returns the names of local queue bindings. This is confusing for
> users. They return values should be consistent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2781) Return only local queue names for AddressControl.getQueueNames()
[
https://issues.apache.org/jira/browse/ARTEMIS-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-2781:
Description: There is a discrepancy between what
{{AddressControl.getQueueNames()}} returns and what
{{ActiveMQServerControl.getQueueNames()}} returns. The former returns the names
of both local and remote queue bindings whereas the latter only returns the
names of local queue bindings. This is confusing for users. They return values
should be consistent.
> Return only local queue names for AddressControl.getQueueNames()
>
>
> Key: ARTEMIS-2781
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2781
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> There is a discrepancy between what {{AddressControl.getQueueNames()}}
> returns and what {{ActiveMQServerControl.getQueueNames()}} returns. The
> former returns the names of both local and remote queue bindings whereas the
> latter only returns the names of local queue bindings. This is confusing for
> users. They return values should be consistent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2781) Return only local queue names for AddressControl.getQueueNames()
[ https://issues.apache.org/jira/browse/ARTEMIS-2781?focusedWorklogId=438349&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438349 ] ASF GitHub Bot logged work on ARTEMIS-2781: --- Author: ASF GitHub Bot Created on: 28/May/20 17:00 Start Date: 28/May/20 17:00 Worklog Time Spent: 10m Work Description: jbertram opened a new pull request #3152: URL: https://github.com/apache/activemq-artemis/pull/3152 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 438349) Time Spent: 0.5h (was: 20m) > Return only local queue names for AddressControl.getQueueNames() > > > Key: ARTEMIS-2781 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2781 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.14.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2781) Return only local queue names for AddressControl.getQueueNames()
[ https://issues.apache.org/jira/browse/ARTEMIS-2781?focusedWorklogId=438351&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438351 ] ASF GitHub Bot logged work on ARTEMIS-2781: --- Author: ASF GitHub Bot Created on: 28/May/20 17:00 Start Date: 28/May/20 17:00 Worklog Time Spent: 10m Work Description: jbertram commented on pull request #3151: URL: https://github.com/apache/activemq-artemis/pull/3151#issuecomment-635471908 Take a look at #3152. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 438351) Time Spent: 40m (was: 0.5h) > Return only local queue names for AddressControl.getQueueNames() > > > Key: ARTEMIS-2781 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2781 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.14.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7491) ActiveMQ illegal occupation vulnerability
[ https://issues.apache.org/jira/browse/AMQ-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118714#comment-17118714 ] wang Jessie commented on AMQ-7491: -- Thank you! > ActiveMQ illegal occupation vulnerability > - > > Key: AMQ-7491 > URL: https://issues.apache.org/jira/browse/AMQ-7491 > Project: ActiveMQ > Issue Type: Bug > Components: AMQP, Broker >Affects Versions: 5.15.12 > Environment: We build a script used JavaScript to interact with the > broker in ActiveMQ 5.15.12. > The experiment is performed on Windows10 1903 version. >Reporter: wang Jessie >Priority: Blocker > Labels: security > Attachments: 1590234052205.png > > > *Description:* Two client with the same Container-Id are not allowed to > connect to the broker. When we send *two OPEN packet with same the > Container-Id*, the broker will return error and the client will close the TCP > connection. The client with this Container-Id will *never be able to connect > with the broker* unless the broker resets. This vulnerability can be > exploited by the adversary to perform the aforementioned attacks on many > Container-Id to make a huge set of clients unable to connect with the broker. > As the ActiveMQ are widely adopted by the IoT vendors, this can be a > vulnerability affected a wide range. > Following are the details. > We send *two OPEN packets with the same Container-Id 1* and we can learn from > the log A in the attached picture in the broker side that the broker returned > close packets and the client closed this TCP connection with the broker. > Then we build a new client to connect with the broker using the same > Container-Id 1, we can learn from the log B in the attached pictur that the > broker returned errors as the broker believe the client with Container-Id 1 > already connected. > *Suggestion for repair:* May be the state of the broker after received two > OPEN packets could be checked and the connection state of the client could be > updated when the TCP connection is closed. > > :)I hope what I found can do some help and if you want further discussion, > please email me by [wangqiny...@zju.edu.cn|mailto:wangqiny...@zju.edu.cn]. > Thanks for spending your time on my issue. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7452) java.lang.IllegalStateException: Timer already cancelled.
[
https://issues.apache.org/jira/browse/AMQ-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118711#comment-17118711
]
Colm O hEigeartaigh commented on AMQ-7452:
--
Please give more details about how to reproduce the stacktrace above.
> java.lang.IllegalStateException: Timer already cancelled.
> -
>
> Key: AMQ-7452
> URL: https://issues.apache.org/jira/browse/AMQ-7452
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.15.3
>Reporter: wangxiaoqing
>Priority: Blocker
>
> 2020-03-24 12:54:47,990 | ERROR | Could not accept connection from
> tcp://10.0.1.5:41212 : {} | org.apache.activemq.broker.TransportConnector |
> ActiveMQ BrokerService[localhost] Task-174422020-03-24 12:54:47,990 | ERROR |
> Could not accept connection from tcp://10.0.1.5:41212 : {} |
> org.apache.activemq.broker.TransportConnector | ActiveMQ
> BrokerService[localhost] Task-17442java.lang.IllegalStateException: Timer
> already cancelled. at java.util.Timer.sched(Timer.java:397)[:1.8.0_191] at
> java.util.Timer.schedule(Timer.java:193)[:1.8.0_191] at
> org.apache.activemq.transport.AbstractInactivityMonitor.startConnectCheckTask(AbstractInactivityMonitor.java:425)[activemq-client-5.15.3.jar:5.15.3]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.startConnectCheckTask(AbstractInactivityMonitor.java:400)[activemq-client-5.15.3.jar:5.15.3]
> at
> org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:50)[activemq-client-5.15.3.jar:5.15.3]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)[activemq-client-5.15.3.jar:5.15.3]
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)[activemq-client-5.15.3.jar:5.15.3]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)[activemq-client-5.15.3.jar:5.15.3]
> at
> org.apache.activemq.broker.TransportConnection.start(TransportConnection.java:1066)[activemq-broker-5.15.3.jar:5.15.3]
> at
> org.apache.activemq.broker.TransportConnector$1$1.run(TransportConnector.java:218)[activemq-broker-5.15.3.jar:5.15.3]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_191]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_191]
> at java.lang.Thread.run(Thread.java:748)[:1.8.0_191]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AMQ-7491) ActiveMQ illegal occupation vulnerability
[ https://issues.apache.org/jira/browse/AMQ-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118709#comment-17118709 ] Colm O hEigeartaigh commented on AMQ-7491: -- I will contact you. > ActiveMQ illegal occupation vulnerability > - > > Key: AMQ-7491 > URL: https://issues.apache.org/jira/browse/AMQ-7491 > Project: ActiveMQ > Issue Type: Bug > Components: AMQP, Broker >Affects Versions: 5.15.12 > Environment: We build a script used JavaScript to interact with the > broker in ActiveMQ 5.15.12. > The experiment is performed on Windows10 1903 version. >Reporter: wang Jessie >Priority: Blocker > Labels: security > Attachments: 1590234052205.png > > > *Description:* Two client with the same Container-Id are not allowed to > connect to the broker. When we send *two OPEN packet with same the > Container-Id*, the broker will return error and the client will close the TCP > connection. The client with this Container-Id will *never be able to connect > with the broker* unless the broker resets. This vulnerability can be > exploited by the adversary to perform the aforementioned attacks on many > Container-Id to make a huge set of clients unable to connect with the broker. > As the ActiveMQ are widely adopted by the IoT vendors, this can be a > vulnerability affected a wide range. > Following are the details. > We send *two OPEN packets with the same Container-Id 1* and we can learn from > the log A in the attached picture in the broker side that the broker returned > close packets and the client closed this TCP connection with the broker. > Then we build a new client to connect with the broker using the same > Container-Id 1, we can learn from the log B in the attached pictur that the > broker returned errors as the broker believe the client with Container-Id 1 > already connected. > *Suggestion for repair:* May be the state of the broker after received two > OPEN packets could be checked and the connection state of the client could be > updated when the TCP connection is closed. > > :)I hope what I found can do some help and if you want further discussion, > please email me by [wangqiny...@zju.edu.cn|mailto:wangqiny...@zju.edu.cn]. > Thanks for spending your time on my issue. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7491) ActiveMQ illegal occupation vulnerability
[ https://issues.apache.org/jira/browse/AMQ-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118702#comment-17118702 ] wang Jessie commented on AMQ-7491: -- I am willing to share my script. Can I send you by email? Because I am not decided to make the script public. > ActiveMQ illegal occupation vulnerability > - > > Key: AMQ-7491 > URL: https://issues.apache.org/jira/browse/AMQ-7491 > Project: ActiveMQ > Issue Type: Bug > Components: AMQP, Broker >Affects Versions: 5.15.12 > Environment: We build a script used JavaScript to interact with the > broker in ActiveMQ 5.15.12. > The experiment is performed on Windows10 1903 version. >Reporter: wang Jessie >Priority: Blocker > Labels: security > Attachments: 1590234052205.png > > > *Description:* Two client with the same Container-Id are not allowed to > connect to the broker. When we send *two OPEN packet with same the > Container-Id*, the broker will return error and the client will close the TCP > connection. The client with this Container-Id will *never be able to connect > with the broker* unless the broker resets. This vulnerability can be > exploited by the adversary to perform the aforementioned attacks on many > Container-Id to make a huge set of clients unable to connect with the broker. > As the ActiveMQ are widely adopted by the IoT vendors, this can be a > vulnerability affected a wide range. > Following are the details. > We send *two OPEN packets with the same Container-Id 1* and we can learn from > the log A in the attached picture in the broker side that the broker returned > close packets and the client closed this TCP connection with the broker. > Then we build a new client to connect with the broker using the same > Container-Id 1, we can learn from the log B in the attached pictur that the > broker returned errors as the broker believe the client with Container-Id 1 > already connected. > *Suggestion for repair:* May be the state of the broker after received two > OPEN packets could be checked and the connection state of the client could be > updated when the TCP connection is closed. > > :)I hope what I found can do some help and if you want further discussion, > please email me by [wangqiny...@zju.edu.cn|mailto:wangqiny...@zju.edu.cn]. > Thanks for spending your time on my issue. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
