[jira] [Commented] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816222#comment-17816222
]
daves commented on ARTEMIS-4217:
Thank you [~jbertram] and [~tabish] for finding the cause and helping me.
Changing amqpMinLargeMessageSize or journal-buffer-size works. I cannot
reproduce the problem with correct settings.
> AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
>
>
> Key: ARTEMIS-4217
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4217
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.28.0
> Environment: Windows Server 2022 21H2
> openjdk 19.0.1 2022-10-18
> OpenJDK Runtime Environment (build 19.0.1+10-21)
> OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing)
>Reporter: daves
>Priority: Major
> Attachments: ArtemisConvertError.zip, ArtemisReproMemory.zip,
> image-2023-06-16-15-59-25-689.png, image-2023-06-16-15-59-25-721.png
>
>
> Some of the AMQP messages sent by my client never arrive at the consumer. In
> the Artemis log I found the following exception:
> {noformat}
> 2023-03-23 18:06:58,084 WARN
> [org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to
> convert message. Sending it to Dead Letter Address.
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
> java.nio.channels.ClosedChannelException
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:318)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:79)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:561)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.server.impl.MessageReferenceImpl.run(MessageReferenceImpl.java:131)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
> ~[netty-transport-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> ~[artemis-commons-2.28.0.jar:?] Caused by: java.lang.RuntimeException:
> java.nio.channels.ClosedChannelException
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:293)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.getBodyBufferSize(LargeServerMessageImpl.java:263)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBodyLength(CoreBytesMessageWrapper.java:98)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBinaryFromMessageBody(CoreBytesMessageWrapper.java:68)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.createAMQPSection(CoreBytesMessageWrapper.java:78)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:106)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> ... 10 more
> Caused by: java.nio.channels.ClosedChannelException
> at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:165)
> ~[?:?]
> at sun.nio.ch.FileChannelImpl.size(FileChannelImpl.java:416) ~[?:?]
> at
> org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.size(NIOSequentialFile.java:339)
> ~[artemis-journal-2.28.0.jar:2.28.0]
[jira] [Comment Edited] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816194#comment-17816194
]
daves edited comment on ARTEMIS-4217 at 2/9/24 7:32 PM:
Hi [~jbertram]
I planned to upload the file together with a comment, but I got interrupted
while writing the comment, sorry.
I did some more testing and found a way to reproduce the problem rellably.
For the problem to occure the system running the broker must be in a low memory
state. I've added a small project to the issue to reproduce the problem.
Setup:
Broker: The problem exists since version 2.28 I used 2.31.2 for this test.
2.27.1 is the last version in which the problem never occurs.
Broker config:
{code:xml}
http://www.w3.org/2001/XMLSchema-instance;
xmlns:xi="http://www.w3.org/2001/XInclude; xsi:schemaLocation="urn:activemq
/schema/artemis-configuration.xsd">
http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="urn:activemq:core ">
Argos
true
NIO
C:/Data/Artemis/Argos/data/paging
C:/Data/Artemis/Argos/data/bindings
C:/Data/Artemis/Argos/data/journal
C:/Data/Artemis/Argos/data/large-messages
true
2
10
4096
10M
1404000
1
5000
99
true
12
6
HALT
1196000
tcp://0.0.0.0:5672?tcpSendBufferSize=2000;tcpReceiveBufferSize=2000;minLargeMessageSize=500;amqpMinLargeMessageSize=500;consumerWindowSize=10485760;directDeliver=false;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpMinCredits=300
0
-1
10
PAGE
true
true
true
true
1.5
5000
6
10
10485760
104857600
2
PAGE
10
true
true
true
true
false
false
false
false
{code}
Repro tool:
Extract ArtemisReproMemory.zip and run the project.
It is a .net application and should run on all major platforms, but I tested it
only on Windows (11) . To build and run it, you need the .net8.0 SDK from here:
https://dotnet.microsoft.com/en-us/download/visual-studio-sdks
Run this command to build the project (in the root of the extracted directory):
{code:bash}
dotnet build -c Release
{code}
Start the built application like this:
{code:bash}
cd .\ArtemisReproMemory\bin\Release\net8.0\
dotnet .\ArtemisReproMemory.dll -a amqp://admin:password@localhost:5672 -b 10
{code}
Use the -a switch to specify a broker URL (AMQP)
Use -b to allocate the specified number of bytes to simulate a high memory
state. (Only makes sense if the broker is running on the same machine)
The repro tool will send large messages to the specified broker using the AMQP
protocol and simultaneously consume the messages. The actions of the repro tool
trigger the problem (
Failed to convert message. Sending it to Dead Letter Address.) on all machines
I tested with.
In some cases, it took considerably longer for the problem to occur, if the
broker was started before the system memory was all "in use". So it can help to
start the broker after the repro tool is up and running (using the -b flag).
Artemis will, using this setup, generate the following log entries and loose
messages:
{code:java}
2024-02-09 10:30:17,320 WARN [org.apache.activemq.artemis.core.server]
AMQ222150: Sending message
Reference[8590002935]:NON-RELIABLE:LargeServerMessage[messageID=8590002935,durable=false,userID=d5f605da-c72d-11ee-891c-a059505d02d7,priority=4,
timestamp=0,expiration=0, durable=false, address=test-q,
properties=TypedProperties[NATIVE_MESSAGE_ID=ID:AMQP_NO_PREFIX:test-producer
#18, JMS_AMQP_ORIGINAL_ENCODING=6, _AMQ_LARGE_SIZE=1048576]]@964273977 to Dead
Letter Address, but there is no Dead Letter Address configured for queue test-q
so dropping it
2024-02-09 10:30:29,752 WARN
[org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to convert
message. Sending it to Dead Letter Address.
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
java.nio.channels.AsynchronousCloseException
at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:318)
~[artemis-amqp-protocol-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:79)
~[artemis-amqp-protocol-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:572)
~[artemis-amqp-protocol-2.31.2.jar:2.31.2]
at
[jira] [Comment Edited] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816194#comment-17816194
]
daves edited comment on ARTEMIS-4217 at 2/9/24 7:30 PM:
Hi [~jbertram]
I planned to upload the file together with a comment, but I got interrupted
while writing the comment, sorry.
I did some more testing and found a way to reproduce the problem rellably.
For the problem to occure the system running the broker must be in a low memory
state. I've added a small project to the issue to reproduce the problem.
Setup:
Broker: The problem exists since version 2.28 I used 2.31.2 for this test.
2.27.1 is the last version in which the problem never occurs.
Broker config:
{code:xml}
http://www.w3.org/2001/XMLSchema-instance;
xmlns:xi="http://www.w3.org/2001/XInclude; xsi:schemaLocation="urn:activemq
/schema/artemis-configuration.xsd">
http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="urn:activemq:core ">
Argos
true
NIO
C:/Data/Artemis/Argos/data/paging
C:/Data/Artemis/Argos/data/bindings
C:/Data/Artemis/Argos/data/journal
C:/Data/Artemis/Argos/data/large-messages
true
2
10
4096
10M
1404000
1
5000
99
true
12
6
HALT
1196000
tcp://0.0.0.0:5672?tcpSendBufferSize=2000;tcpReceiveBufferSize=2000;minLargeMessageSize=500;amqpMinLargeMessageSize=500;consumerWindowSize=10485760;directDeliver=false;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpMinCredits=300
0
-1
10
PAGE
true
true
true
true
1.5
5000
6
10
10485760
104857600
2
PAGE
10
true
true
true
true
false
false
false
false
{code}
Repro tool:
Extract ArtemisReproMemory.zip and run the project.
It is a .net application and should run on all major platforms, but I tested it
only on Windows (11) . To build and run it, you need the .net8.0 SDK from here:
https://dotnet.microsoft.com/en-us/download/visual-studio-sdks
Run this command to build the project (in the root of the extracted directory):
{code:cmd}
dotnet build -c Release
{code}
Start the built application like this:
{code:cmd}
cd .\ArtemisReproMemory\bin\Release\net8.0\
dotnet .\ArtemisReproMemory.dll -a amqp://admin:password@localhost:5672 -b 10
{code}
Use the -a switch to specify a broker URL (AMQP)
Use -b to allocate the specified number of bytes to simulate a high memory
state. (Only makes sense if the broker is running on the same machine)
The repro tool will send large messages to the specified broker using the AMQP
protocol and simultaneously consume the messages. The actions of the repro tool
trigger the problem (
Failed to convert message. Sending it to Dead Letter Address.) on all machines
I tested with.
In some cases, it took considerably longer for the problem to occur, if the
broker was started before the system memory was all "in use". So it can help to
start the broker after the repro tool is up and running (using the -b flag).
Artemis will, using this setup, generate the following log entries and loose
messages:
{code:java}
2024-02-09 10:30:17,320 WARN [org.apache.activemq.artemis.core.server]
AMQ222150: Sending message
Reference[8590002935]:NON-RELIABLE:LargeServerMessage[messageID=8590002935,durable=false,userID=d5f605da-c72d-11ee-891c-a059505d02d7,priority=4,
timestamp=0,expiration=0, durable=false, address=test-q,
properties=TypedProperties[NATIVE_MESSAGE_ID=ID:AMQP_NO_PREFIX:test-producer
#18, JMS_AMQP_ORIGINAL_ENCODING=6, _AMQ_LARGE_SIZE=1048576]]@964273977 to Dead
Letter Address, but there is no Dead Letter Address configured for queue test-q
so dropping it
2024-02-09 10:30:29,752 WARN
[org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to convert
message. Sending it to Dead Letter Address.
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
java.nio.channels.AsynchronousCloseException
at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:318)
~[artemis-amqp-protocol-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:79)
~[artemis-amqp-protocol-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:572)
~[artemis-amqp-protocol-2.31.2.jar:2.31.2]
at
[jira] [Commented] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816194#comment-17816194
]
daves commented on ARTEMIS-4217:
Hi [~jbertram]
I planned to upload the file together with a comment, but I got interrupted
while writing the comment, sorry.
I did some more testing and found a way to reproduce the problem rellably.
For the problem to occure the system running the broker must be in a low memory
state. I've added a small project to the issue to reproduce the problem.
Setup:
Broker: The problem exists since version 2.28 I used 2.31.2 for this test.
2.27.1 is the last version in which the problem never occurs.
Broker config:
{code:xml}
http://www.w3.org/2001/XMLSchema-instance;
xmlns:xi="http://www.w3.org/2001/XInclude; xsi:schemaLocation="urn:activemq
/schema/artemis-configuration.xsd">
http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="urn:activemq:core ">
Argos
true
NIO
C:/Logisoft/Data/Artemis/Argos/data/paging
C:/Logisoft/Data/Artemis/Argos/data/bindings
C:/Logisoft/Data/Artemis/Argos/data/journal
C:/Logisoft/Data/Artemis/Argos/data/large-messages
true
2
10
4096
10M
1404000
1
5000
99
true
12
6
HALT
1196000
tcp://0.0.0.0:5672?tcpSendBufferSize=2000;tcpReceiveBufferSize=2000;minLargeMessageSize=500;amqpMinLargeMessageSize=500;consumerWindowSize=10485760;directDeliver=false;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpMinCredits=300
0
-1
10
PAGE
true
true
true
true
1.5
5000
6
10
10485760
104857600
2
PAGE
10
true
true
true
true
false
false
false
false
{code}
Repro tool:
Extract ArtemisReproMemory.zip and run the project.
It is a .net application and should run on all major platforms, but I tested it
only on Windows (11) . To build and run it, you need the .net8.0 SDK from here:
https://dotnet.microsoft.com/en-us/download/visual-studio-sdks
Run this command to build the project (in the root of the extracted directory):
{code:cmd}
dotnet build -c Release
{code}
Start the built application like this:
{code:cmd}
cd .\ArtemisReproMemory\bin\Release\net8.0\
dotnet .\ArtemisReproMemory.dll -a amqp://admin:password@localhost:5672 -b 10
{code}
Use the -a switch to specify a broker URL (AMQP)
Use -b to allocate the specified number of bytes to simulate a high memory
state. (Only makes sense if the broker is running on the same machine)
The repro tool will send large messages to the specified broker using the AMQP
protocol and simultaneously consume the messages. The actions of the repro tool
trigger the problem (
Failed to convert message. Sending it to Dead Letter Address.) on all machines
I tested with.
In some cases, it took considerably longer for the problem to occur, if the
broker was started before the system memory was all "in use". So it can help to
start the broker after the repro tool is up and running (using the -b flag).
Artemis will, using this setup, generate the following log entries and loose
messages:
{code:java}
2024-02-09 10:30:17,320 WARN [org.apache.activemq.artemis.core.server]
AMQ222150: Sending message
Reference[8590002935]:NON-RELIABLE:LargeServerMessage[messageID=8590002935,durable=false,userID=d5f605da-c72d-11ee-891c-a059505d02d7,priority=4,
timestamp=0,expiration=0, durable=false, address=test-q,
properties=TypedProperties[NATIVE_MESSAGE_ID=ID:AMQP_NO_PREFIX:test-producer
#18, JMS_AMQP_ORIGINAL_ENCODING=6, _AMQ_LARGE_SIZE=1048576]]@964273977 to Dead
Letter Address, but there is no Dead Letter Address configured for queue test-q
so dropping it
2024-02-09 10:30:29,752 WARN
[org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to convert
message. Sending it to Dead Letter Address.
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
java.nio.channels.AsynchronousCloseException
at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:318)
~[artemis-amqp-protocol-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:79)
~[artemis-amqp-protocol-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:572)
~[artemis-amqp-protocol-2.31.2.jar:2.31.2]
at
[jira] [Updated] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
daves updated ARTEMIS-4217:
---
Attachment: ArtemisReproMemory.zip
> AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
>
>
> Key: ARTEMIS-4217
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4217
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.28.0
> Environment: Windows Server 2022 21H2
> openjdk 19.0.1 2022-10-18
> OpenJDK Runtime Environment (build 19.0.1+10-21)
> OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing)
>Reporter: daves
>Priority: Major
> Attachments: ArtemisConvertError.zip, ArtemisReproMemory.zip,
> image-2023-06-16-15-59-25-689.png, image-2023-06-16-15-59-25-721.png
>
>
> Some of the AMQP messages sent by my client never arrive at the consumer. In
> the Artemis log I found the following exception:
> {noformat}
> 2023-03-23 18:06:58,084 WARN
> [org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to
> convert message. Sending it to Dead Letter Address.
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
> java.nio.channels.ClosedChannelException
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:318)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:79)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:561)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.server.impl.MessageReferenceImpl.run(MessageReferenceImpl.java:131)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
> ~[netty-transport-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> ~[artemis-commons-2.28.0.jar:?] Caused by: java.lang.RuntimeException:
> java.nio.channels.ClosedChannelException
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:293)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.getBodyBufferSize(LargeServerMessageImpl.java:263)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBodyLength(CoreBytesMessageWrapper.java:98)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBinaryFromMessageBody(CoreBytesMessageWrapper.java:68)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.createAMQPSection(CoreBytesMessageWrapper.java:78)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:106)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> ... 10 more
> Caused by: java.nio.channels.ClosedChannelException
> at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:165)
> ~[?:?]
> at sun.nio.ch.FileChannelImpl.size(FileChannelImpl.java:416) ~[?:?]
> at
> org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.size(NIOSequentialFile.java:339)
> ~[artemis-journal-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:285)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
>
[jira] [Commented] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733522#comment-17733522
]
daves commented on ARTEMIS-4217:
[~jbertram] Thanks for looking at this and sorry for the long delay...
It looks like it is hard to reproduce it. I'm currently not able to reproduce
the problem on my local test machine. But I still see the problem on other
systems:
In this case, the problem occurred with a "large message". Could a large
message trigger some kind of conversion? Maybe during writing/reading from the
storage (file system)? The payload of the message is a 1mb chunk of a zip file.
The message also has some custom headers/properties which are visible in the
log below.
We only have AMQP consumers/producers on this system. I've also verified this
in the admin console:
!image-2023-06-16-15-59-25-689.png!!image-2023-06-16-15-59-25-721.png!
{code:java}
2023-06-16 15:44:48,301 WARN [org.apache.activemq.artemis.core.server]
AMQ222150: Sending message Reference[120978405]:NON-RELIABLE:LargeServerMessage
[messageID=120978405,durable=false,userID=f5eb19e9-0c4b-11ee-
8c25-f44d30e2ecf9,priority=4, timestamp=0,expiration=Mon Jun 19 15:44:46 CEST
2023, durable=false, address=MyQName,
properties=TypedProperties[content-length=100,JMS_AMQP_ORIGINAL_ENCODING=6,content-version=2.0,AtmCommandTaskResultId=25160,
filename=MyBroker_2023-06-15_2243_12.0.0.6_Logisoft.7z,content-type=multipart/byteranges,x-version=7.9.45.349,AtmCommandTaskId=-1,_AMQ_LARGE_SIZE=100,extensions=1,
checksumrange=F4861070CFDFC33B7D77A74420AF25DF1FAFF4F57A01D75A1E0FB03047BF38C7,NATIVE_MESSAGE_ID=ID:AMQP_NO_PREFIX:MyQName_2023-06-16T15:44:46.8290577+02:00_97089137-6edd-49cd-a81a-0b40441f6be5,Issued=2023-06-16
15:44:46.824
+02:00,AtmJobId=15065,content-status=200,range=600-699,1773052136,process-id=Job_15065_MonitoringDataExchange__2023-06-16T15:38:58.0607859+02:00,atmid=CHE8455,received-getrange=600-699,0]]@80507286
to Dead Letter Address, but there is no Dead Letter Address configured for
queue MyQName so dropping it 2023-06-16 15:44:48,338 WARN
[org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to convert
message. Sending it to Dead Letter Address.
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
java.nio.channels.AsynchronousCloseException at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:318)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:79)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:561)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.core.server.impl.MessageReferenceImpl.run(MessageReferenceImpl.java:131)
~[artemis-server-2.28.0.jar:2.28.0] at
io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
~[netty-transport-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
~[artemis-commons-2.28.0.jar:?] Caused by: java.lang.RuntimeException:
java.nio.channels.AsynchronousCloseException at
org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:293)
~[artemis-server-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.getBodyBufferSize(LargeServerMessageImpl.java:263)
~[artemis-server-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBodyLength(CoreBytesMessageWrapper.java:98)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBinaryFromMessageBody(CoreBytesMessageWrapper.java:68)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
[jira] [Updated] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
daves updated ARTEMIS-4217:
---
Attachment: image-2023-06-16-15-59-25-721.png
> AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
>
>
> Key: ARTEMIS-4217
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4217
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.28.0
> Environment: Windows Server 2022 21H2
> openjdk 19.0.1 2022-10-18
> OpenJDK Runtime Environment (build 19.0.1+10-21)
> OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing)
>Reporter: daves
>Priority: Major
> Attachments: ArtemisConvertError.zip,
> image-2023-06-16-15-59-25-689.png, image-2023-06-16-15-59-25-721.png
>
>
> Some of the AMQP messages sent by my client never arrive at the consumer. In
> the Artemis log I found the following exception:
> {noformat}
> 2023-03-23 18:06:58,084 WARN
> [org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to
> convert message. Sending it to Dead Letter Address.
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
> java.nio.channels.ClosedChannelException
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:318)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:79)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:561)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.server.impl.MessageReferenceImpl.run(MessageReferenceImpl.java:131)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
> ~[netty-transport-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> ~[artemis-commons-2.28.0.jar:?] Caused by: java.lang.RuntimeException:
> java.nio.channels.ClosedChannelException
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:293)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.getBodyBufferSize(LargeServerMessageImpl.java:263)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBodyLength(CoreBytesMessageWrapper.java:98)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBinaryFromMessageBody(CoreBytesMessageWrapper.java:68)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.createAMQPSection(CoreBytesMessageWrapper.java:78)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:106)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> ... 10 more
> Caused by: java.nio.channels.ClosedChannelException
> at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:165)
> ~[?:?]
> at sun.nio.ch.FileChannelImpl.size(FileChannelImpl.java:416) ~[?:?]
> at
> org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.size(NIOSequentialFile.java:339)
> ~[artemis-journal-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:285)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
>
[jira] [Updated] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
daves updated ARTEMIS-4217:
---
Attachment: image-2023-06-16-15-59-25-689.png
> AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
>
>
> Key: ARTEMIS-4217
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4217
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.28.0
> Environment: Windows Server 2022 21H2
> openjdk 19.0.1 2022-10-18
> OpenJDK Runtime Environment (build 19.0.1+10-21)
> OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing)
>Reporter: daves
>Priority: Major
> Attachments: ArtemisConvertError.zip,
> image-2023-06-16-15-59-25-689.png, image-2023-06-16-15-59-25-721.png
>
>
> Some of the AMQP messages sent by my client never arrive at the consumer. In
> the Artemis log I found the following exception:
> {noformat}
> 2023-03-23 18:06:58,084 WARN
> [org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to
> convert message. Sending it to Dead Letter Address.
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
> java.nio.channels.ClosedChannelException
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:318)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:79)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:561)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.server.impl.MessageReferenceImpl.run(MessageReferenceImpl.java:131)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
> ~[netty-transport-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> ~[artemis-commons-2.28.0.jar:?] Caused by: java.lang.RuntimeException:
> java.nio.channels.ClosedChannelException
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:293)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.getBodyBufferSize(LargeServerMessageImpl.java:263)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBodyLength(CoreBytesMessageWrapper.java:98)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBinaryFromMessageBody(CoreBytesMessageWrapper.java:68)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.createAMQPSection(CoreBytesMessageWrapper.java:78)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:106)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> ... 10 more
> Caused by: java.nio.channels.ClosedChannelException
> at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:165)
> ~[?:?]
> at sun.nio.ch.FileChannelImpl.size(FileChannelImpl.java:416) ~[?:?]
> at
> org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.size(NIOSequentialFile.java:339)
> ~[artemis-journal-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:285)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
>
[jira] [Created] (ARTEMIS-4307) AMQP ARtemis "hangs" on single message delivery
daves created ARTEMIS-4307:
--
Summary: AMQP ARtemis "hangs" on single message delivery
Key: ARTEMIS-4307
URL: https://issues.apache.org/jira/browse/ARTEMIS-4307
Project: ActiveMQ Artemis
Issue Type: Bug
Components: AMQP
Affects Versions: 2.28.0
Reporter: daves
My Setup:
- Multiple clients ~500 send messages to a queue in Artemis using AMQP
- A single application reads consumes the messages from the queue using AMQP
At some point - I sadly don't know how to reproduce it - my consuming client
does not receive messages anymore.
>From the perspective of my client the call to receiving new messages (AMQP.NET
>lite) just hands/waits for messages and never returns. Also, It still looks
>like the connection is open and healthy.
On the Artemis side I see two different pictures.
- In the Broker console I can see a consumer from my client, and it tells me
that 1 Messages is in Transit. ...as if Artemis is waiting for an ACK for the
message.
In the Artemis log is see this:
{code:java}
2023-06-09 15:11:37,934 WARN
[org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext]
Array must not be empty or null
java.lang.IllegalArgumentException: Array must not be empty or null
at
org.apache.qpid.proton.codec.CompositeReadableBuffer.append(CompositeReadableBuffer.java:691)
~[proton-j-0.34.0.jar:?]
at
org.apache.qpid.proton.engine.impl.DeliveryImpl.send(DeliveryImpl.java:345)
~[proton-j-0.34.0.jar:?]
at org.apache.qpid.proton.engine.impl.SenderImpl.send(SenderImpl.java:74)
~[proton-j-0.34.0.jar:?]
at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext$LargeMessageDeliveryContext.deliverInitialPacket(ProtonServerSenderContext.java:715)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext$LargeMessageDeliveryContext.deliver(ProtonServerSenderContext.java:622)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.deliverLarge(ProtonServerSenderContext.java:837)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:567)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
at
org.apache.activemq.artemis.core.paging.cursor.PagedReferenceImpl.run(PagedReferenceImpl.java:116)
~[artemis-server-2.28.0.jar:2.28.0]
at
io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
~[netty-common-4.1.86.Final.jar:4.1.86.Final]
at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
~[netty-common-4.1.86.Final.jar:4.1.86.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
~[netty-common-4.1.86.Final.jar:4.1.86.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:566)
~[netty-transport-4.1.86.Final.jar:4.1.86.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
~[netty-common-4.1.86.Final.jar:4.1.86.Final]
at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
~[netty-common-4.1.86.Final.jar:4.1.86.Final]
at
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
~[artemis-commons-2.28.0.jar:?]
2023-06-09 15:11:37,934 WARN [org.apache.activemq.artemis.core.server]
AMQ222151: removing consumer which did not handle a message,
consumer=ServerConsumerImpl [id=3, filter=null, binding=LocalQueueBinding
[address=MyQName, queue=QueueImpl[name=MyQName, postOffice=PostOfficeImpl
[server=ActiveMQServerImpl::name=MyApp], temp=false]@776d381a, filter=null,
name=MyQName, clusterName=MyQName431ed7e1-05dd-11ee-ade9-f44d30e2ecf9]],
message=PagedReferenceImpl [message=PagedMessageImpl [queueIDs=[47],
transactionID=-1, page=25, message=AMQPLargeMessage( [durable=false,
messageID=12940183, address=MyQName, size=0, scanningStatus=SCANNED,
applicationProperties={atmid=CHE8128, content-type=application/x-protobuf,
content-version=2.0,
process-id=FireAndForgetJob_AtmStatusRequest_CHE8128_ConfigurationRequest_f2eb7a14-fc1e-4439-8c83-4e836e83c818,
content-status=200, Issued=2023-06-08 19:46:55.862 +02:00,
x-version=7.9.44.348, AtmJobId=-1, AtmCommandTaskId=4,
AtmCommandTaskResultId=-1, extensions=1, content-length=8145690},
messageAnnotations={},
properties=Properties{messageId=MyQName_2023-06-08T19:46:55.8712925+02:00_208f699f-9636-493f-9bfd-af4317e3dc45,
userId=null, to='MyQName', subject='null', replyTo='null', correlationId=null,
contentType=null, contentEncoding=null, absoluteExpiryTime=Fri Jun 07 19:46:55
CEST 2024, creationTime=null, groupId='null', groupSequence=null,
[jira] [Commented] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[ https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705410#comment-17705410 ] daves commented on ARTEMIS-4217: [Justin Bertram|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jbertram] About the log. After I discovered that my client does not receive all messages, I took a look at the Artemis log and saw the stack/trace. I then changed the level to capture more details about the problem. This did NOT work... all messages were delivered when the log level was set to trace. I then checked if the problem occurs again when the log output is set to a higher level, which "worked", the stack-trace did appear again in the log. The clients both send and receive messages using AMQP. There are other clients on the same broker which use STOMP. But not for this queue. > AMQ111005: Failed to convert message. Sending it to Dead Letter Address. > > > Key: ARTEMIS-4217 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4217 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.28.0 > Environment: Windows Server 2022 21H2 > openjdk 19.0.1 2022-10-18 > OpenJDK Runtime Environment (build 19.0.1+10-21) > OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing) >Reporter: daves >Priority: Major > Attachments: ArtemisConvertError.zip, artemis-service.wrapper.log, > artemis.log, artemis.log.2023-03-23-1.log.gz, > artemis.log.2023-03-23-10.log.gz, artemis.log.2023-03-23-100.log.gz, > artemis.log.2023-03-23-11.log.gz, artemis.log.2023-03-23-12.log.gz, > artemis.log.2023-03-23-13.log.gz, artemis.log.2023-03-23-14.log.gz, > artemis.log.2023-03-23-15.log.gz, artemis.log.2023-03-23-16.log.gz, > artemis.log.2023-03-23-17.log.gz, artemis.log.2023-03-23-18.log.gz, > artemis.log.2023-03-23-19.log.gz, artemis.log.2023-03-23-2.log.gz, > artemis.log.2023-03-23-20.log.gz, artemis.log.2023-03-23-21.log.gz, > artemis.log.2023-03-23-22.log.gz, artemis.log.2023-03-23-23.log.gz, > artemis.log.2023-03-23-24.log.gz, artemis.log.2023-03-23-25.log.gz, > artemis.log.2023-03-23-26.log.gz, artemis.log.2023-03-23-27.log.gz, > artemis.log.2023-03-23-28.log.gz, artemis.log.2023-03-23-29.log.gz, > artemis.log.2023-03-23-3.log.gz, artemis.log.2023-03-23-30.log.gz, > artemis.log.2023-03-23-31.log.gz, artemis.log.2023-03-23-32.log.gz, > artemis.log.2023-03-23-33.log.gz, artemis.log.2023-03-23-34.log.gz, > artemis.log.2023-03-23-35.log.gz, artemis.log.2023-03-23-36.log.gz, > artemis.log.2023-03-23-37.log.gz, artemis.log.2023-03-23-38.log.gz, > artemis.log.2023-03-23-39.log.gz, artemis.log.2023-03-23-4.log.gz, > artemis.log.2023-03-23-40.log.gz, artemis.log.2023-03-23-41.log.gz, > artemis.log.2023-03-23-42.log.gz, artemis.log.2023-03-23-43.log.gz, > artemis.log.2023-03-23-44.log.gz, artemis.log.2023-03-23-45.log.gz, > artemis.log.2023-03-23-46.log.gz, artemis.log.2023-03-23-47.log.gz, > artemis.log.2023-03-23-48.log.gz, artemis.log.2023-03-23-49.log.gz, > artemis.log.2023-03-23-5.log.gz, artemis.log.2023-03-23-50.log.gz, > artemis.log.2023-03-23-51.log.gz, artemis.log.2023-03-23-52.log.gz, > artemis.log.2023-03-23-53.log.gz, artemis.log.2023-03-23-54.log.gz, > artemis.log.2023-03-23-55.log.gz, artemis.log.2023-03-23-56.log.gz, > artemis.log.2023-03-23-57.log.gz, artemis.log.2023-03-23-58.log.gz, > artemis.log.2023-03-23-59.log.gz, artemis.log.2023-03-23-6.log.gz, > artemis.log.2023-03-23-60.log.gz, artemis.log.2023-03-23-61.log.gz, > artemis.log.2023-03-23-62.log.gz, artemis.log.2023-03-23-63.log.gz, > artemis.log.2023-03-23-64.log.gz, artemis.log.2023-03-23-65.log.gz, > artemis.log.2023-03-23-66.log.gz, artemis.log.2023-03-23-67.log.gz, > artemis.log.2023-03-23-68.log.gz, artemis.log.2023-03-23-69.log.gz, > artemis.log.2023-03-23-7.log.gz, artemis.log.2023-03-23-70.log.gz, > artemis.log.2023-03-23-71.log.gz, artemis.log.2023-03-23-72.log.gz, > artemis.log.2023-03-23-73.log.gz, artemis.log.2023-03-23-74.log.gz, > artemis.log.2023-03-23-75.log.gz, artemis.log.2023-03-23-76.log.gz, > artemis.log.2023-03-23-77.log.gz, artemis.log.2023-03-23-78.log.gz, > artemis.log.2023-03-23-79.log.gz, artemis.log.2023-03-23-8.log.gz, > artemis.log.2023-03-23-80.log.gz, artemis.log.2023-03-23-81.log.gz, > artemis.log.2023-03-23-82.log.gz, artemis.log.2023-03-23-83.log.gz, > artemis.log.2023-03-23-84.log.gz, artemis.log.2023-03-23-85.log.gz, > artemis.log.2023-03-23-86.log.gz, artemis.log.2023-03-23-87.log.gz, > artemis.log.2023-03-23-88.log.gz, artemis.log.2023-03-23-89.log.gz, > artemis.log.2023-03-23-9.log.gz, artemis.log.2023-03-23-90.log.gz, > artemis.log.2023-03-23-91.log.gz, artemis.log.2023-03-23-92.log.gz, > artemis.log.2023-03-23-93.log.gz,
[jira] [Commented] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[ https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705313#comment-17705313 ] daves commented on ARTEMIS-4217: Hi [Justin Bertram|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jbertram] The log is all the traces I got from finding the problem to reproducing* it. I thought it's better to have too much log available than not enough. The use-case is this: Client A sends a AMQP message to client B via Artemis. Both clients use AMQP as protocol. The message is a proprietary structure serialized with protobuf. The payload contains 1-5 PNG images (therefore the large size). Sending the message works, all send attempts are successful, no errors. Consuming messages also does not produce any client side errors, BUT some messages are never "pushed" to the client. For all "lost" messages, I can find the stack trace (ticket description) in the Artemis log. Sadly, the problem occurs only on a test environment with real applications. Also, it only happens a few times a day. I tried to make a small consumer and producer example, but I could not reproduce the problem. I used a recorded message from the test environment as test data for my client, although I believe the problem has "nothing" to do with the payload. The real application sends the same data, just with a different client id, to multiple clients (100-2000) and typically only 1 or 2 messages do not arrive at the client. The problem does not always occur with the same client. If you want to try it for yourself, I've added my sample client as an attachment. You can change the connection string in the appsettings.json file. > AMQ111005: Failed to convert message. Sending it to Dead Letter Address. > > > Key: ARTEMIS-4217 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4217 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.28.0 > Environment: Windows Server 2022 21H2 > openjdk 19.0.1 2022-10-18 > OpenJDK Runtime Environment (build 19.0.1+10-21) > OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing) >Reporter: daves >Priority: Major > Attachments: ArtemisConvertError.zip, artemis-service.wrapper.log, > artemis.log, artemis.log.2023-03-23-1.log.gz, > artemis.log.2023-03-23-10.log.gz, artemis.log.2023-03-23-100.log.gz, > artemis.log.2023-03-23-11.log.gz, artemis.log.2023-03-23-12.log.gz, > artemis.log.2023-03-23-13.log.gz, artemis.log.2023-03-23-14.log.gz, > artemis.log.2023-03-23-15.log.gz, artemis.log.2023-03-23-16.log.gz, > artemis.log.2023-03-23-17.log.gz, artemis.log.2023-03-23-18.log.gz, > artemis.log.2023-03-23-19.log.gz, artemis.log.2023-03-23-2.log.gz, > artemis.log.2023-03-23-20.log.gz, artemis.log.2023-03-23-21.log.gz, > artemis.log.2023-03-23-22.log.gz, artemis.log.2023-03-23-23.log.gz, > artemis.log.2023-03-23-24.log.gz, artemis.log.2023-03-23-25.log.gz, > artemis.log.2023-03-23-26.log.gz, artemis.log.2023-03-23-27.log.gz, > artemis.log.2023-03-23-28.log.gz, artemis.log.2023-03-23-29.log.gz, > artemis.log.2023-03-23-3.log.gz, artemis.log.2023-03-23-30.log.gz, > artemis.log.2023-03-23-31.log.gz, artemis.log.2023-03-23-32.log.gz, > artemis.log.2023-03-23-33.log.gz, artemis.log.2023-03-23-34.log.gz, > artemis.log.2023-03-23-35.log.gz, artemis.log.2023-03-23-36.log.gz, > artemis.log.2023-03-23-37.log.gz, artemis.log.2023-03-23-38.log.gz, > artemis.log.2023-03-23-39.log.gz, artemis.log.2023-03-23-4.log.gz, > artemis.log.2023-03-23-40.log.gz, artemis.log.2023-03-23-41.log.gz, > artemis.log.2023-03-23-42.log.gz, artemis.log.2023-03-23-43.log.gz, > artemis.log.2023-03-23-44.log.gz, artemis.log.2023-03-23-45.log.gz, > artemis.log.2023-03-23-46.log.gz, artemis.log.2023-03-23-47.log.gz, > artemis.log.2023-03-23-48.log.gz, artemis.log.2023-03-23-49.log.gz, > artemis.log.2023-03-23-5.log.gz, artemis.log.2023-03-23-50.log.gz, > artemis.log.2023-03-23-51.log.gz, artemis.log.2023-03-23-52.log.gz, > artemis.log.2023-03-23-53.log.gz, artemis.log.2023-03-23-54.log.gz, > artemis.log.2023-03-23-55.log.gz, artemis.log.2023-03-23-56.log.gz, > artemis.log.2023-03-23-57.log.gz, artemis.log.2023-03-23-58.log.gz, > artemis.log.2023-03-23-59.log.gz, artemis.log.2023-03-23-6.log.gz, > artemis.log.2023-03-23-60.log.gz, artemis.log.2023-03-23-61.log.gz, > artemis.log.2023-03-23-62.log.gz, artemis.log.2023-03-23-63.log.gz, > artemis.log.2023-03-23-64.log.gz, artemis.log.2023-03-23-65.log.gz, > artemis.log.2023-03-23-66.log.gz, artemis.log.2023-03-23-67.log.gz, > artemis.log.2023-03-23-68.log.gz, artemis.log.2023-03-23-69.log.gz, > artemis.log.2023-03-23-7.log.gz, artemis.log.2023-03-23-70.log.gz, > artemis.log.2023-03-23-71.log.gz, artemis.log.2023-03-23-72.log.gz,
[jira] [Updated] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
daves updated ARTEMIS-4217:
---
Attachment: ArtemisConvertError.zip
> AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
>
>
> Key: ARTEMIS-4217
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4217
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.28.0
> Environment: Windows Server 2022 21H2
> openjdk 19.0.1 2022-10-18
> OpenJDK Runtime Environment (build 19.0.1+10-21)
> OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing)
>Reporter: daves
>Priority: Major
> Attachments: ArtemisConvertError.zip, artemis-service.wrapper.log,
> artemis.log, artemis.log.2023-03-23-1.log.gz,
> artemis.log.2023-03-23-10.log.gz, artemis.log.2023-03-23-100.log.gz,
> artemis.log.2023-03-23-11.log.gz, artemis.log.2023-03-23-12.log.gz,
> artemis.log.2023-03-23-13.log.gz, artemis.log.2023-03-23-14.log.gz,
> artemis.log.2023-03-23-15.log.gz, artemis.log.2023-03-23-16.log.gz,
> artemis.log.2023-03-23-17.log.gz, artemis.log.2023-03-23-18.log.gz,
> artemis.log.2023-03-23-19.log.gz, artemis.log.2023-03-23-2.log.gz,
> artemis.log.2023-03-23-20.log.gz, artemis.log.2023-03-23-21.log.gz,
> artemis.log.2023-03-23-22.log.gz, artemis.log.2023-03-23-23.log.gz,
> artemis.log.2023-03-23-24.log.gz, artemis.log.2023-03-23-25.log.gz,
> artemis.log.2023-03-23-26.log.gz, artemis.log.2023-03-23-27.log.gz,
> artemis.log.2023-03-23-28.log.gz, artemis.log.2023-03-23-29.log.gz,
> artemis.log.2023-03-23-3.log.gz, artemis.log.2023-03-23-30.log.gz,
> artemis.log.2023-03-23-31.log.gz, artemis.log.2023-03-23-32.log.gz,
> artemis.log.2023-03-23-33.log.gz, artemis.log.2023-03-23-34.log.gz,
> artemis.log.2023-03-23-35.log.gz, artemis.log.2023-03-23-36.log.gz,
> artemis.log.2023-03-23-37.log.gz, artemis.log.2023-03-23-38.log.gz,
> artemis.log.2023-03-23-39.log.gz, artemis.log.2023-03-23-4.log.gz,
> artemis.log.2023-03-23-40.log.gz, artemis.log.2023-03-23-41.log.gz,
> artemis.log.2023-03-23-42.log.gz, artemis.log.2023-03-23-43.log.gz,
> artemis.log.2023-03-23-44.log.gz, artemis.log.2023-03-23-45.log.gz,
> artemis.log.2023-03-23-46.log.gz, artemis.log.2023-03-23-47.log.gz,
> artemis.log.2023-03-23-48.log.gz, artemis.log.2023-03-23-49.log.gz,
> artemis.log.2023-03-23-5.log.gz, artemis.log.2023-03-23-50.log.gz,
> artemis.log.2023-03-23-51.log.gz, artemis.log.2023-03-23-52.log.gz,
> artemis.log.2023-03-23-53.log.gz, artemis.log.2023-03-23-54.log.gz,
> artemis.log.2023-03-23-55.log.gz, artemis.log.2023-03-23-56.log.gz,
> artemis.log.2023-03-23-57.log.gz, artemis.log.2023-03-23-58.log.gz,
> artemis.log.2023-03-23-59.log.gz, artemis.log.2023-03-23-6.log.gz,
> artemis.log.2023-03-23-60.log.gz, artemis.log.2023-03-23-61.log.gz,
> artemis.log.2023-03-23-62.log.gz, artemis.log.2023-03-23-63.log.gz,
> artemis.log.2023-03-23-64.log.gz, artemis.log.2023-03-23-65.log.gz,
> artemis.log.2023-03-23-66.log.gz, artemis.log.2023-03-23-67.log.gz,
> artemis.log.2023-03-23-68.log.gz, artemis.log.2023-03-23-69.log.gz,
> artemis.log.2023-03-23-7.log.gz, artemis.log.2023-03-23-70.log.gz,
> artemis.log.2023-03-23-71.log.gz, artemis.log.2023-03-23-72.log.gz,
> artemis.log.2023-03-23-73.log.gz, artemis.log.2023-03-23-74.log.gz,
> artemis.log.2023-03-23-75.log.gz, artemis.log.2023-03-23-76.log.gz,
> artemis.log.2023-03-23-77.log.gz, artemis.log.2023-03-23-78.log.gz,
> artemis.log.2023-03-23-79.log.gz, artemis.log.2023-03-23-8.log.gz,
> artemis.log.2023-03-23-80.log.gz, artemis.log.2023-03-23-81.log.gz,
> artemis.log.2023-03-23-82.log.gz, artemis.log.2023-03-23-83.log.gz,
> artemis.log.2023-03-23-84.log.gz, artemis.log.2023-03-23-85.log.gz,
> artemis.log.2023-03-23-86.log.gz, artemis.log.2023-03-23-87.log.gz,
> artemis.log.2023-03-23-88.log.gz, artemis.log.2023-03-23-89.log.gz,
> artemis.log.2023-03-23-9.log.gz, artemis.log.2023-03-23-90.log.gz,
> artemis.log.2023-03-23-91.log.gz, artemis.log.2023-03-23-92.log.gz,
> artemis.log.2023-03-23-93.log.gz, artemis.log.2023-03-23-94.log.gz,
> artemis.log.2023-03-23-95.log.gz, artemis.log.2023-03-23-96.log.gz,
> artemis.log.2023-03-23-97.log.gz, artemis.log.2023-03-23-98.log.gz,
> artemis.log.2023-03-23-99.log.gz
>
>
> Some of the AMQP messages sent by my client never arrive at the consumer. In
> the Artemis log I found the following exception:
> {noformat}
> 2023-03-23 18:06:58,084 WARN
> [org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to
> convert message. Sending it to Dead Letter Address.
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
> java.nio.channels.ClosedChannelException
> at
>
[jira] [Commented] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17704606#comment-17704606
]
daves commented on ARTEMIS-4217:
Thanks for the minLargeMessageSize idea. i will try this.
> AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
>
>
> Key: ARTEMIS-4217
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4217
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.28.0
> Environment: Windows Server 2022 21H2
> openjdk 19.0.1 2022-10-18
> OpenJDK Runtime Environment (build 19.0.1+10-21)
> OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing)
>Reporter: daves
>Priority: Major
> Attachments: artemis-service.wrapper.log, artemis.log,
> artemis.log.2023-03-23-1.log.gz, artemis.log.2023-03-23-10.log.gz,
> artemis.log.2023-03-23-100.log.gz, artemis.log.2023-03-23-11.log.gz,
> artemis.log.2023-03-23-12.log.gz, artemis.log.2023-03-23-13.log.gz,
> artemis.log.2023-03-23-14.log.gz, artemis.log.2023-03-23-15.log.gz,
> artemis.log.2023-03-23-16.log.gz, artemis.log.2023-03-23-17.log.gz,
> artemis.log.2023-03-23-18.log.gz, artemis.log.2023-03-23-19.log.gz,
> artemis.log.2023-03-23-2.log.gz, artemis.log.2023-03-23-20.log.gz,
> artemis.log.2023-03-23-21.log.gz, artemis.log.2023-03-23-22.log.gz,
> artemis.log.2023-03-23-23.log.gz, artemis.log.2023-03-23-24.log.gz,
> artemis.log.2023-03-23-25.log.gz, artemis.log.2023-03-23-26.log.gz,
> artemis.log.2023-03-23-27.log.gz, artemis.log.2023-03-23-28.log.gz,
> artemis.log.2023-03-23-29.log.gz, artemis.log.2023-03-23-3.log.gz,
> artemis.log.2023-03-23-30.log.gz, artemis.log.2023-03-23-31.log.gz,
> artemis.log.2023-03-23-32.log.gz, artemis.log.2023-03-23-33.log.gz,
> artemis.log.2023-03-23-34.log.gz, artemis.log.2023-03-23-35.log.gz,
> artemis.log.2023-03-23-36.log.gz, artemis.log.2023-03-23-37.log.gz,
> artemis.log.2023-03-23-38.log.gz, artemis.log.2023-03-23-39.log.gz,
> artemis.log.2023-03-23-4.log.gz, artemis.log.2023-03-23-40.log.gz,
> artemis.log.2023-03-23-41.log.gz, artemis.log.2023-03-23-42.log.gz,
> artemis.log.2023-03-23-43.log.gz, artemis.log.2023-03-23-44.log.gz,
> artemis.log.2023-03-23-45.log.gz, artemis.log.2023-03-23-46.log.gz,
> artemis.log.2023-03-23-47.log.gz, artemis.log.2023-03-23-48.log.gz,
> artemis.log.2023-03-23-49.log.gz, artemis.log.2023-03-23-5.log.gz,
> artemis.log.2023-03-23-50.log.gz, artemis.log.2023-03-23-51.log.gz,
> artemis.log.2023-03-23-52.log.gz, artemis.log.2023-03-23-53.log.gz,
> artemis.log.2023-03-23-54.log.gz, artemis.log.2023-03-23-55.log.gz,
> artemis.log.2023-03-23-56.log.gz, artemis.log.2023-03-23-57.log.gz,
> artemis.log.2023-03-23-58.log.gz, artemis.log.2023-03-23-59.log.gz,
> artemis.log.2023-03-23-6.log.gz, artemis.log.2023-03-23-60.log.gz,
> artemis.log.2023-03-23-61.log.gz, artemis.log.2023-03-23-62.log.gz,
> artemis.log.2023-03-23-63.log.gz, artemis.log.2023-03-23-64.log.gz,
> artemis.log.2023-03-23-65.log.gz, artemis.log.2023-03-23-66.log.gz,
> artemis.log.2023-03-23-67.log.gz, artemis.log.2023-03-23-68.log.gz,
> artemis.log.2023-03-23-69.log.gz, artemis.log.2023-03-23-7.log.gz,
> artemis.log.2023-03-23-70.log.gz, artemis.log.2023-03-23-71.log.gz,
> artemis.log.2023-03-23-72.log.gz, artemis.log.2023-03-23-73.log.gz,
> artemis.log.2023-03-23-74.log.gz, artemis.log.2023-03-23-75.log.gz,
> artemis.log.2023-03-23-76.log.gz, artemis.log.2023-03-23-77.log.gz,
> artemis.log.2023-03-23-78.log.gz, artemis.log.2023-03-23-79.log.gz,
> artemis.log.2023-03-23-8.log.gz, artemis.log.2023-03-23-80.log.gz,
> artemis.log.2023-03-23-81.log.gz, artemis.log.2023-03-23-82.log.gz,
> artemis.log.2023-03-23-83.log.gz, artemis.log.2023-03-23-84.log.gz,
> artemis.log.2023-03-23-85.log.gz, artemis.log.2023-03-23-86.log.gz,
> artemis.log.2023-03-23-87.log.gz, artemis.log.2023-03-23-88.log.gz,
> artemis.log.2023-03-23-89.log.gz, artemis.log.2023-03-23-9.log.gz,
> artemis.log.2023-03-23-90.log.gz, artemis.log.2023-03-23-91.log.gz,
> artemis.log.2023-03-23-92.log.gz, artemis.log.2023-03-23-93.log.gz,
> artemis.log.2023-03-23-94.log.gz, artemis.log.2023-03-23-95.log.gz,
> artemis.log.2023-03-23-96.log.gz, artemis.log.2023-03-23-97.log.gz,
> artemis.log.2023-03-23-98.log.gz, artemis.log.2023-03-23-99.log.gz
>
>
> Some of the AMQP messages sent by my client never arrive at the consumer. In
> the Artemis log I found the following exception:
>
>
> {code:java}
> 2023-03-23 18:06:58,084 WARN
> [org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to
> convert message. Sending it to Dead Letter Address.
> org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
> java.nio.channels.ClosedChannelException at
>
[jira] [Updated] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[ https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] daves updated ARTEMIS-4217: --- Attachment: artemis.log.2023-03-23-94.log.gz artemis.log.2023-03-23-95.log.gz artemis.log.2023-03-23-96.log.gz artemis.log.2023-03-23-97.log.gz artemis.log.2023-03-23-98.log.gz artemis.log.2023-03-23-99.log.gz artemis.log.2023-03-23-100.log.gz artemis-service.wrapper.log artemis.log.2023-03-23-15.log.gz artemis.log.2023-03-23-16.log.gz artemis.log.2023-03-23-17.log.gz artemis.log.2023-03-23-18.log.gz artemis.log.2023-03-23-19.log.gz artemis.log.2023-03-23-20.log.gz artemis.log.2023-03-23-21.log.gz artemis.log.2023-03-23-22.log.gz artemis.log.2023-03-23-23.log.gz artemis.log.2023-03-23-24.log.gz artemis.log.2023-03-23-25.log.gz artemis.log.2023-03-23-26.log.gz artemis.log.2023-03-23-27.log.gz artemis.log.2023-03-23-28.log.gz artemis.log.2023-03-23-29.log.gz artemis.log.2023-03-23-30.log.gz artemis.log.2023-03-23-31.log.gz artemis.log.2023-03-23-32.log.gz artemis.log.2023-03-23-33.log.gz artemis.log.2023-03-23-34.log.gz artemis.log.2023-03-23-35.log.gz artemis.log.2023-03-23-36.log.gz artemis.log.2023-03-23-37.log.gz artemis.log.2023-03-23-38.log.gz artemis.log.2023-03-23-39.log.gz artemis.log.2023-03-23-40.log.gz artemis.log.2023-03-23-41.log.gz artemis.log.2023-03-23-42.log.gz artemis.log.2023-03-23-43.log.gz artemis.log.2023-03-23-44.log.gz artemis.log.2023-03-23-45.log.gz artemis.log.2023-03-23-46.log.gz artemis.log.2023-03-23-47.log.gz artemis.log.2023-03-23-48.log.gz artemis.log.2023-03-23-49.log.gz artemis.log.2023-03-23-50.log.gz artemis.log.2023-03-23-51.log.gz artemis.log.2023-03-23-52.log.gz artemis.log.2023-03-23-53.log.gz artemis.log.2023-03-23-54.log.gz artemis.log.2023-03-23-55.log.gz artemis.log.2023-03-23-56.log.gz artemis.log.2023-03-23-57.log.gz artemis.log.2023-03-23-58.log.gz artemis.log.2023-03-23-59.log.gz artemis.log.2023-03-23-60.log.gz artemis.log.2023-03-23-61.log.gz artemis.log.2023-03-23-62.log.gz artemis.log.2023-03-23-63.log.gz artemis.log.2023-03-23-64.log.gz artemis.log.2023-03-23-65.log.gz artemis.log.2023-03-23-66.log.gz artemis.log.2023-03-23-67.log.gz artemis.log.2023-03-23-68.log.gz artemis.log.2023-03-23-69.log.gz artemis.log.2023-03-23-70.log.gz artemis.log.2023-03-23-71.log.gz artemis.log.2023-03-23-72.log.gz artemis.log.2023-03-23-73.log.gz artemis.log.2023-03-23-74.log.gz artemis.log.2023-03-23-75.log.gz artemis.log.2023-03-23-76.log.gz artemis.log.2023-03-23-77.log.gz artemis.log.2023-03-23-78.log.gz artemis.log.2023-03-23-79.log.gz artemis.log.2023-03-23-80.log.gz artemis.log.2023-03-23-81.log.gz artemis.log.2023-03-23-82.log.gz artemis.log.2023-03-23-83.log.gz artemis.log.2023-03-23-84.log.gz artemis.log.2023-03-23-85.log.gz artemis.log.2023-03-23-86.log.gz artemis.log.2023-03-23-87.log.gz artemis.log.2023-03-23-88.log.gz artemis.log.2023-03-23-89.log.gz artemis.log.2023-03-23-90.log.gz artemis.log.2023-03-23-91.log.gz artemis.log.2023-03-23-92.log.gz artemis.log.2023-03-23-93.log.gz > AMQ111005: Failed to convert message. Sending it to Dead Letter Address. > > > Key: ARTEMIS-4217 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4217 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.28.0 > Environment: Windows Server 2022 21H2 > openjdk 19.0.1 2022-10-18 > OpenJDK Runtime Environment (build 19.0.1+10-21) > OpenJDK 64-Bit Server VM (build
[jira] [Created] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
daves created ARTEMIS-4217:
--
Summary: AMQ111005: Failed to convert message. Sending it to Dead
Letter Address.
Key: ARTEMIS-4217
URL: https://issues.apache.org/jira/browse/ARTEMIS-4217
Project: ActiveMQ Artemis
Issue Type: Bug
Components: AMQP
Affects Versions: 2.28.0
Environment: Windows Server 2022 21H2
openjdk 19.0.1 2022-10-18
OpenJDK Runtime Environment (build 19.0.1+10-21)
OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing)
Reporter: daves
Attachments: artemis.log, artemis.log.2023-03-23-1.log.gz,
artemis.log.2023-03-23-10.log.gz, artemis.log.2023-03-23-11.log.gz,
artemis.log.2023-03-23-12.log.gz, artemis.log.2023-03-23-13.log.gz,
artemis.log.2023-03-23-14.log.gz, artemis.log.2023-03-23-2.log.gz,
artemis.log.2023-03-23-3.log.gz, artemis.log.2023-03-23-4.log.gz,
artemis.log.2023-03-23-5.log.gz, artemis.log.2023-03-23-6.log.gz,
artemis.log.2023-03-23-7.log.gz, artemis.log.2023-03-23-8.log.gz,
artemis.log.2023-03-23-9.log.gz
Some of the AMQP messages sent by my client never arrive at the consumer. In
the Artemis log I found the following exception:
{code:java}
2023-03-23 18:06:58,084 WARN
[org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to convert
message. Sending it to Dead Letter Address.
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
java.nio.channels.ClosedChannelException at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:318)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:79)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:561)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.core.server.impl.MessageReferenceImpl.run(MessageReferenceImpl.java:131)
~[artemis-server-2.28.0.jar:2.28.0] at
io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
~[netty-transport-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
~[artemis-commons-2.28.0.jar:?] Caused by: java.lang.RuntimeException:
java.nio.channels.ClosedChannelException at
org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:293)
~[artemis-server-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.getBodyBufferSize(LargeServerMessageImpl.java:263)
~[artemis-server-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBodyLength(CoreBytesMessageWrapper.java:98)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBinaryFromMessageBody(CoreBytesMessageWrapper.java:68)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.createAMQPSection(CoreBytesMessageWrapper.java:78)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:106)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] ... 10 more Caused by:
java.nio.channels.ClosedChannelException at
sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:165) ~[?:?] at
sun.nio.ch.FileChannelImpl.size(FileChannelImpl.java:416) ~[?:?] at
org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.size(NIOSequentialFile.java:339)
~[artemis-journal-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:285)
~[artemis-server-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.getBodyBufferSize(LargeServerMessageImpl.java:263)
~[artemis-server-2.28.0.jar:2.28.0] at
[jira] [Commented] (ARTEMIS-4047) Artemis does not send message to consumer AMQP
[
https://issues.apache.org/jira/browse/ARTEMIS-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17616971#comment-17616971
]
daves commented on ARTEMIS-4047:
I saw that there is a newer version 2.26. I’ve updated my broker to this
version, but the problem still exists. … Also, a new start of the broker does
not change anything. Restarting the client does not change anything either.
> Artemis does not send message to consumer AMQP
> --
>
> Key: ARTEMIS-4047
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4047
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, Broker
>Affects Versions: 2.25.0
>Reporter: daves
>Priority: Major
> Attachments: 1.PNG, 2.PNG, 3.PNG, 4.PNG, 5.PNG, All.zip
>
>
> The broker does not send messages from one of many existing queues to the
> connected consumer.
> According to the UI the queue does contain ~15k messages.
> I’m not able to consume any of these messages. I also tried to read a message
> using the browse function of the UI/console but that does not work eighter.
> The message was created by a AMQP client and should be consumed by another
> AMQP client.
> I tried to capture the situation in a few screenshots…
> I don’t know which data can help you to understand the situation, so I’ve
> collected everything:
> * Logs
> * Broker
> * Data
> Please let me know if there are any other data I should add to the ticket.
>
> I don’t think that the code of my client is relevant since the problem only
> exist for a single queue…but here it is anyway:
>
>
> {code:java}
> using Amqp;
> using Amqp.Framing;
> using Amqp.Types;
> namespace Test;
> public sealed class MessageConsumer
> {
> private readonly String _address;
> private readonly CancellationToken _cancellationToken;
> private readonly String _consumerName;
> private readonly String[] _destinations;
> public MessageConsumer( String address, String consumerName, String[]
> destinations, CancellationToken cancellationToken )
> {
> _address = address;
> _consumerName = consumerName;
> _destinations = destinations;
> _cancellationToken = cancellationToken;
> }
> public async Task StartReceivingMessages()
> {
> await Task.Yield();
> while ( !_cancellationToken.IsCancellationRequested )
> {
> var connectionFactory = new ConnectionFactory();
> var address = new Address( _address );
> try
> {
> var connection = await connectionFactory.CreateAsync( address
> );
> var session = ( (IConnection) connection ).CreateSession();
> var receivers = new List();
> foreach ( var destination in _destinations )
> {
> var receiver = session.CreateReceiver(
> $"{_consumerName}_{destination}",
> new Source
> {
> Address =
> destination,
> Capabilities =
> new[] { new Symbol( "queue" ) }
> } );
> receivers.Add( receiver );
> }
> while ( !_cancellationToken.IsCancellationRequested )
> foreach ( var receiver in receivers )
> {
> // ReceiveAsync( TimeSpan.Zero ); blocks forever and
> no messages will be received
> var message = await receiver.ReceiveAsync(
> TimeSpan.FromMilliseconds( 1 ) );
> if ( message == null )
> continue;
> receiver.Accept( message );
> Console.WriteLine( $"{_consumerName} - Received
> message with id: '{message.Properties.MessageId}'" );
> }
> }
> catch ( Exception ex )
> {
> Console.WriteLine( $"{_consumerName} - Connection error in
> producer '{_consumerName}' {ex.Message} => create new connection." );
> await Task.Delay( 1000, CancellationToken.None );
> }
> }
> }
> }
> {code}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4047) Artemis does not send message to consumer AMQP
[
https://issues.apache.org/jira/browse/ARTEMIS-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
daves updated ARTEMIS-4047:
---
Affects Version/s: 2.26.0
> Artemis does not send message to consumer AMQP
> --
>
> Key: ARTEMIS-4047
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4047
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, Broker
>Affects Versions: 2.25.0, 2.26.0
>Reporter: daves
>Priority: Major
> Attachments: 1.PNG, 2.PNG, 3.PNG, 4.PNG, 5.PNG, All.zip
>
>
> The broker does not send messages from one of many existing queues to the
> connected consumer.
> According to the UI the queue does contain ~15k messages.
> I’m not able to consume any of these messages. I also tried to read a message
> using the browse function of the UI/console but that does not work eighter.
> The message was created by a AMQP client and should be consumed by another
> AMQP client.
> I tried to capture the situation in a few screenshots…
> I don’t know which data can help you to understand the situation, so I’ve
> collected everything:
> * Logs
> * Broker
> * Data
> Please let me know if there are any other data I should add to the ticket.
>
> I don’t think that the code of my client is relevant since the problem only
> exist for a single queue…but here it is anyway:
>
>
> {code:java}
> using Amqp;
> using Amqp.Framing;
> using Amqp.Types;
> namespace Test;
> public sealed class MessageConsumer
> {
> private readonly String _address;
> private readonly CancellationToken _cancellationToken;
> private readonly String _consumerName;
> private readonly String[] _destinations;
> public MessageConsumer( String address, String consumerName, String[]
> destinations, CancellationToken cancellationToken )
> {
> _address = address;
> _consumerName = consumerName;
> _destinations = destinations;
> _cancellationToken = cancellationToken;
> }
> public async Task StartReceivingMessages()
> {
> await Task.Yield();
> while ( !_cancellationToken.IsCancellationRequested )
> {
> var connectionFactory = new ConnectionFactory();
> var address = new Address( _address );
> try
> {
> var connection = await connectionFactory.CreateAsync( address
> );
> var session = ( (IConnection) connection ).CreateSession();
> var receivers = new List();
> foreach ( var destination in _destinations )
> {
> var receiver = session.CreateReceiver(
> $"{_consumerName}_{destination}",
> new Source
> {
> Address =
> destination,
> Capabilities =
> new[] { new Symbol( "queue" ) }
> } );
> receivers.Add( receiver );
> }
> while ( !_cancellationToken.IsCancellationRequested )
> foreach ( var receiver in receivers )
> {
> // ReceiveAsync( TimeSpan.Zero ); blocks forever and
> no messages will be received
> var message = await receiver.ReceiveAsync(
> TimeSpan.FromMilliseconds( 1 ) );
> if ( message == null )
> continue;
> receiver.Accept( message );
> Console.WriteLine( $"{_consumerName} - Received
> message with id: '{message.Properties.MessageId}'" );
> }
> }
> catch ( Exception ex )
> {
> Console.WriteLine( $"{_consumerName} - Connection error in
> producer '{_consumerName}' {ex.Message} => create new connection." );
> await Task.Delay( 1000, CancellationToken.None );
> }
> }
> }
> }
> {code}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4047) Artemis does not send message to consumer AMQP
daves created ARTEMIS-4047:
--
Summary: Artemis does not send message to consumer AMQP
Key: ARTEMIS-4047
URL: https://issues.apache.org/jira/browse/ARTEMIS-4047
Project: ActiveMQ Artemis
Issue Type: Bug
Components: AMQP, Broker
Affects Versions: 2.25.0
Reporter: daves
Attachments: 1.PNG, 2.PNG, 3.PNG, 4.PNG, 5.PNG, All.zip
The broker does not send messages from one of many existing queues to the
connected consumer.
According to the UI the queue does contain ~15k messages.
I’m not able to consume any of these messages. I also tried to read a message
using the browse function of the UI/console but that does not work eighter.
The message was created by a AMQP client and should be consumed by another AMQP
client.
I tried to capture the situation in a few screenshots…
I don’t know which data can help you to understand the situation, so I’ve
collected everything:
* Logs
* Broker
* Data
Please let me know if there are any other data I should add to the ticket.
I don’t think that the code of my client is relevant since the problem only
exist for a single queue…but here it is anyway:
{code:java}
using Amqp;
using Amqp.Framing;
using Amqp.Types;
namespace Test;
public sealed class MessageConsumer
{
private readonly String _address;
private readonly CancellationToken _cancellationToken;
private readonly String _consumerName;
private readonly String[] _destinations;
public MessageConsumer( String address, String consumerName, String[]
destinations, CancellationToken cancellationToken )
{
_address = address;
_consumerName = consumerName;
_destinations = destinations;
_cancellationToken = cancellationToken;
}
public async Task StartReceivingMessages()
{
await Task.Yield();
while ( !_cancellationToken.IsCancellationRequested )
{
var connectionFactory = new ConnectionFactory();
var address = new Address( _address );
try
{
var connection = await connectionFactory.CreateAsync( address );
var session = ( (IConnection) connection ).CreateSession();
var receivers = new List();
foreach ( var destination in _destinations )
{
var receiver = session.CreateReceiver(
$"{_consumerName}_{destination}",
new Source
{
Address =
destination,
Capabilities =
new[] { new Symbol( "queue" ) }
} );
receivers.Add( receiver );
}
while ( !_cancellationToken.IsCancellationRequested )
foreach ( var receiver in receivers )
{
// ReceiveAsync( TimeSpan.Zero ); blocks forever and no
messages will be received
var message = await receiver.ReceiveAsync(
TimeSpan.FromMilliseconds( 1 ) );
if ( message == null )
continue;
receiver.Accept( message );
Console.WriteLine( $"{_consumerName} - Received message
with id: '{message.Properties.MessageId}'" );
}
}
catch ( Exception ex )
{
Console.WriteLine( $"{_consumerName} - Connection error in
producer '{_consumerName}' {ex.Message} => create new connection." );
await Task.Delay( 1000, CancellationToken.None );
}
}
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4027) Cannot access management API due to CORS problems (403)
[
https://issues.apache.org/jira/browse/ARTEMIS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612778#comment-17612778
]
daves edited comment on ARTEMIS-4027 at 10/4/22 8:05 PM:
-
Yes, I would like to build a small web based client to manage Artemis.
The current console contains many useful features, but at the same time is very
annoying to use.
Some problems I have with the current console:
* Constant logouts
* Collapse/open state of left navigation (black area) not persisted
* Too much space wasted on "non-content elements" like the header or the
#artemistree
* Tables like Queues do not persist items per page, filters and columns to
display
* Purging or deleting a Queue requires too many clicks and due to the
navigation filters on the Queue table get lost
* In general...Death by 1000 papercuts
My goal is to build a client which contains much less functionality but improve
on the UX. I was planing to learn blazor and evaluate it for other applications
for a long time...and the idea was to use this project for that purpose.
I don't know yet what functionality the client will contain, but I will focus
on a life updating Queue overview with easier functions to see subscribers and
manage the content of a Queue.
In the end, I only need the data from Artemis to display something in my UI. Is
Jalokia is the only way I know how to get the data...is there another way?
was (Author: daves):
Yes, I would like to build a small web based client to manage Artemis.
The current console contains many useful features, but at the same time is very
annoying to use.
Some problems I have with the current console:
* Constant logouts
* Collapse/open state of left navigation (black area) not persisted
* Too much space wasted on "non-content elements" like the header or the
#artemistree
* Tables like Queues do not persist items per page, filters and columns to
display
* Purging or deleting a Queue requires too many clicks and due to the
navigation filters on the Queue table get lost
* In general...Death by 1000 papercuts
My goal is to build a client which contains much less functionality but improve
on the UX. I was planing to learn blazor and evaluate it for other applications
for a long time...and the idea was to use this project for that purpose.
I don't know yet what functionality the client will contain, but I will focus
on a life updating Queue overview with easier functions to see subscribers and
manage the content of a Queue.
> Cannot access management API due to CORS problems (403)
> ---
>
> Key: ARTEMIS-4027
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4027
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: API
>Affects Versions: 2.25.0
>Reporter: daves
>Priority: Major
> Attachments: artemis.log, consoleError.JPG, etc.zip, f1.JPG, f2.JPG,
> options.JPG
>
>
> I try to access the management API from a client app running in chrome.
> This does not work because the preflight check fails.
> OPTIONS request:
>
> {code:java}
> fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
> {
> "headers": {
> "accept": "*/*",
> "accept-language": "en-US,en;q=0.9",
> "sec-fetch-dest": "empty",
> "sec-fetch-mode": "cors",
> "sec-fetch-site": "cross-site"
> },
> "referrerPolicy": "strict-origin-when-cross-origin",
> "body": null,
> "method": "OPTIONS",
> "mode": "cors",
> "credentials": "omit"
> });
>
> {code}
>
> The request fails with a 403 not authenticated... which is strange since
> preflight checks must not be authenticated.
> !options.JPG!
>
> I tried to configure CORS in the jolokia-access.xml file like so:
>
>
> {code:java}
>
>
>
> *://*
>
>
>
> {code}
>
>
> I also tried to specify the URL and port of my application explicitly. But
> this did not work either.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4027) Cannot access management API due to CORS problems (403)
[
https://issues.apache.org/jira/browse/ARTEMIS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612778#comment-17612778
]
daves commented on ARTEMIS-4027:
Yes, I would like to build a small web based client to manage Artemis.
The current console contains many useful features, but at the same time is very
annoying to use.
Some problems I have with the current console:
* Constant logouts
* Collapse/open state of left navigation (black area) not persisted
* Too much space wasted on "non-content elements" like the header or the
#artemistree
* Tables like Queues do not persist items per page, filters and columns to
display
* Purging or deleting a Queue requires too many clicks and due to the
navigation filters on the Queue table get lost
* In general...Death by 1000 papercuts
My goal is to build a client which contains much less functionality but improve
on the UX. I was planing to learn blazor and evaluate it for other applications
for a long time...and the idea was to use this project for that purpose.
I don't know yet what functionality the client will contain, but I will focus
on a life updating Queue overview with easier functions to see subscribers and
manage the content of a Queue.
> Cannot access management API due to CORS problems (403)
> ---
>
> Key: ARTEMIS-4027
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4027
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: API
>Affects Versions: 2.25.0
>Reporter: daves
>Priority: Major
> Attachments: artemis.log, consoleError.JPG, etc.zip, f1.JPG, f2.JPG,
> options.JPG
>
>
> I try to access the management API from a client app running in chrome.
> This does not work because the preflight check fails.
> OPTIONS request:
>
> {code:java}
> fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
> {
> "headers": {
> "accept": "*/*",
> "accept-language": "en-US,en;q=0.9",
> "sec-fetch-dest": "empty",
> "sec-fetch-mode": "cors",
> "sec-fetch-site": "cross-site"
> },
> "referrerPolicy": "strict-origin-when-cross-origin",
> "body": null,
> "method": "OPTIONS",
> "mode": "cors",
> "credentials": "omit"
> });
>
> {code}
>
> The request fails with a 403 not authenticated... which is strange since
> preflight checks must not be authenticated.
> !options.JPG!
>
> I tried to configure CORS in the jolokia-access.xml file like so:
>
>
> {code:java}
>
>
>
> *://*
>
>
>
> {code}
>
>
> I also tried to specify the URL and port of my application explicitly. But
> this did not work either.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4027) Cannot access management API due to CORS problems (403)
[
https://issues.apache.org/jira/browse/ARTEMIS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612726#comment-17612726
]
daves commented on ARTEMIS-4027:
[~jbertram] Thanks for looking at the issue!
I don't think the problem is Windows or environment specific...
To verify if a script from origin A is allowed to request anything from origin
B a browser performs a preflight request. A preflight request is an
unauthenticated HTTP OPTIONS request. If the server allows requests from origin
A it will indicate so to the browser with an HTTP header in the response
(Access-Control-Allow-Origin).
See: [https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request]
When I send the request from my browsers console I get the following error
(which tells me it's a CORS problem):
!consoleError.JPG!
The same problem also occurs when running the request from FireFox:
!f1.JPG!!f2.JPG!
I see the request in the Artemis log ,but I can't find anything helping to
understand what is happening. (I've added the log to the ticket). [^artemis.log]
While searching for CORS related problems like this one, I found this:
[https://gist.github.com/rhuss/e0c949f7564a47943460] But I don't understand
much of the Java specific part... not sure how helpful it is.
> Cannot access management API due to CORS problems (403)
> ---
>
> Key: ARTEMIS-4027
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4027
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: API
>Affects Versions: 2.25.0
>Reporter: daves
>Priority: Major
> Attachments: artemis.log, consoleError.JPG, etc.zip, f1.JPG, f2.JPG,
> options.JPG
>
>
> I try to access the management API from a client app running in chrome.
> This does not work because the preflight check fails.
> OPTIONS request:
>
> {code:java}
> fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
> {
> "headers": {
> "accept": "*/*",
> "accept-language": "en-US,en;q=0.9",
> "sec-fetch-dest": "empty",
> "sec-fetch-mode": "cors",
> "sec-fetch-site": "cross-site"
> },
> "referrerPolicy": "strict-origin-when-cross-origin",
> "body": null,
> "method": "OPTIONS",
> "mode": "cors",
> "credentials": "omit"
> });
>
> {code}
>
> The request fails with a 403 not authenticated... which is strange since
> preflight checks must not be authenticated.
> !options.JPG!
>
> I tried to configure CORS in the jolokia-access.xml file like so:
>
>
> {code:java}
>
>
>
> *://*
>
>
>
> {code}
>
>
> I also tried to specify the URL and port of my application explicitly. But
> this did not work either.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4027) Cannot access management API due to CORS problems (403)
[
https://issues.apache.org/jira/browse/ARTEMIS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
daves updated ARTEMIS-4027:
---
Attachment: f2.JPG
f1.JPG
> Cannot access management API due to CORS problems (403)
> ---
>
> Key: ARTEMIS-4027
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4027
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: API
>Affects Versions: 2.25.0
>Reporter: daves
>Priority: Major
> Attachments: artemis.log, consoleError.JPG, etc.zip, f1.JPG, f2.JPG,
> options.JPG
>
>
> I try to access the management API from a client app running in chrome.
> This does not work because the preflight check fails.
> OPTIONS request:
>
> {code:java}
> fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
> {
> "headers": {
> "accept": "*/*",
> "accept-language": "en-US,en;q=0.9",
> "sec-fetch-dest": "empty",
> "sec-fetch-mode": "cors",
> "sec-fetch-site": "cross-site"
> },
> "referrerPolicy": "strict-origin-when-cross-origin",
> "body": null,
> "method": "OPTIONS",
> "mode": "cors",
> "credentials": "omit"
> });
>
> {code}
>
> The request fails with a 403 not authenticated... which is strange since
> preflight checks must not be authenticated.
> !options.JPG!
>
> I tried to configure CORS in the jolokia-access.xml file like so:
>
>
> {code:java}
>
>
>
> *://*
>
>
>
> {code}
>
>
> I also tried to specify the URL and port of my application explicitly. But
> this did not work either.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4027) Cannot access management API due to CORS problems (403)
[
https://issues.apache.org/jira/browse/ARTEMIS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
daves updated ARTEMIS-4027:
---
Attachment: artemis.log
> Cannot access management API due to CORS problems (403)
> ---
>
> Key: ARTEMIS-4027
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4027
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: API
>Affects Versions: 2.25.0
>Reporter: daves
>Priority: Major
> Attachments: artemis.log, consoleError.JPG, etc.zip, options.JPG
>
>
> I try to access the management API from a client app running in chrome.
> This does not work because the preflight check fails.
> OPTIONS request:
>
> {code:java}
> fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
> {
> "headers": {
> "accept": "*/*",
> "accept-language": "en-US,en;q=0.9",
> "sec-fetch-dest": "empty",
> "sec-fetch-mode": "cors",
> "sec-fetch-site": "cross-site"
> },
> "referrerPolicy": "strict-origin-when-cross-origin",
> "body": null,
> "method": "OPTIONS",
> "mode": "cors",
> "credentials": "omit"
> });
>
> {code}
>
> The request fails with a 403 not authenticated... which is strange since
> preflight checks must not be authenticated.
> !options.JPG!
>
> I tried to configure CORS in the jolokia-access.xml file like so:
>
>
> {code:java}
>
>
>
> *://*
>
>
>
> {code}
>
>
> I also tried to specify the URL and port of my application explicitly. But
> this did not work either.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4027) Cannot access management API due to CORS problems (403)
[
https://issues.apache.org/jira/browse/ARTEMIS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
daves updated ARTEMIS-4027:
---
Attachment: consoleError.JPG
> Cannot access management API due to CORS problems (403)
> ---
>
> Key: ARTEMIS-4027
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4027
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: API
>Affects Versions: 2.25.0
>Reporter: daves
>Priority: Major
> Attachments: consoleError.JPG, etc.zip, options.JPG
>
>
> I try to access the management API from a client app running in chrome.
> This does not work because the preflight check fails.
> OPTIONS request:
>
> {code:java}
> fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
> {
> "headers": {
> "accept": "*/*",
> "accept-language": "en-US,en;q=0.9",
> "sec-fetch-dest": "empty",
> "sec-fetch-mode": "cors",
> "sec-fetch-site": "cross-site"
> },
> "referrerPolicy": "strict-origin-when-cross-origin",
> "body": null,
> "method": "OPTIONS",
> "mode": "cors",
> "credentials": "omit"
> });
>
> {code}
>
> The request fails with a 403 not authenticated... which is strange since
> preflight checks must not be authenticated.
> !options.JPG!
>
> I tried to configure CORS in the jolokia-access.xml file like so:
>
>
> {code:java}
>
>
>
> *://*
>
>
>
> {code}
>
>
> I also tried to specify the URL and port of my application explicitly. But
> this did not work either.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4027) Cannot access management API due to CORS problems (403)
[
https://issues.apache.org/jira/browse/ARTEMIS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612662#comment-17612662
]
daves edited comment on ARTEMIS-4027 at 10/4/22 4:05 PM:
-
[~jbertram] Sure here is how we create a broker:
*$artemisInstallDirectory* is the path to the extracted zip file. The script
should work with pwsh and powershell.
The builtin service account should work, but we use special user for the serive.
{code:bash}
$username = "admin"
$password = "password"
$brokerName = "MyBroker"
$datadir = "C:\Data\"
$instanceDirector = "C:\Apache\Artemis\MyBroker"
$artemisInstallDirectory = "C:\Apache\Artemis\apache-artemis-2.25.0"
$artemisCmdPath = Join-Path $artemisInstallDirectory "\bin\artemis.cmd"
Start-Process -Wait -WindowStyle Hidden -FilePath $artemisCmdPath
"create --data `"$datadir`" --name $brokerName --user $username --password
$password --require-login `"$instanceDirector`""
$instanceServiceExe = Join-Path $instanceDirector
"\bin\artemis-service.exe"
Start-Process -FilePath $instanceServiceExe -ArgumentList "install"
-RedirectStandardOutput "NUL" -Wait -NoNewWindow
sc.exe config $serviceNameArtemis start= delayed-auto | Out-Null
sc.exe failure $serviceNameArtemis actions=
restart/6/restart/6/restart/6 reset= 6 | Out-Null
sc.exe config $serviceNameArtemis obj= "UserName" password=
"UserPassword
{code}
(I've attached the config files of my broker to the ticket.)
For the request you can use the fetch request from the ticket and past it into
the chrome dev console.
Once the preflight check wors you can use this fetch to read some data:
{code:js}
fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
{
"headers": {
"authorization": "Basic YWRtaW46cGFzc3dvcmQ=",
"content-type": "text/json",
"sec-ch-ua": "\"Google Chrome\";v=\"105\", \"Not)A;Brand\";v=\"8\",
\"Chromium\";v=\"105\"",
"sec-ch-ua-mobile": "?0",
"sec-ch-ua-platform": "\"Windows\""
},
"referrer": "",
"referrerPolicy": "strict-origin-when-cross-origin",
"body":
"{\"type\":\"exec\",\"mbean\":\"org.apache.activemq.artemis:broker=\\u0022Argos\\u0022\",\"operation\":\"listQueues(java.lang.String,
int,
int)\",\"arguments\":[\"{\\u0022field\\u0022:\\u0022\\u0022,\\u0022operation\\u0022:\\u0022\\u0022,\\u0022value\\u0022:\\u0022\\u0022,\\u0022sortOrder\\u0022:\\u0022\\u0022,\\u0022sortColumn\\u0022:\\u0022\\u0022}\",\"1\",\"1000\"]}",
"method": "POST",
"mode": "cors",
"credentials": "include"
});
{code}
You may have to change the authorization based on your username/password.
was (Author: daves):
[~jbertram] Sure here is how we create a broker:
*$artemisInstallDirectory* is the path to the extracted zip file. The script
should work with pwsh and powershell.
The builtin service account should work, but we use special user for the serive.
{code:bash}
$username = "admin"
$password = "password"
$brokerName = "MyBroker"
$datadir = "C:\Data\"
$instanceDirector = "C:\Apache\Artemis\MyBroker"
$artemisInstallDirectory = "C:\Apache\Artemis\apache-artemis-2.25.0"
$artemisCmdPath = Join-Path $artemisInstallDirectory "\bin\artemis.cmd"
Start-Process -Wait -WindowStyle Hidden -FilePath $artemisCmdPath
"create --data `"$datadir`" --name $brokerName --user $username --password
$password --require-login `"$instanceDirector`""
$instanceServiceExe = Join-Path $instanceDirector
"\bin\artemis-service.exe"
Start-Process -FilePath $instanceServiceExe -ArgumentList "install"
-RedirectStandardOutput "NUL" -Wait -NoNewWindow
sc.exe config $serviceNameArtemis start= delayed-auto | Out-Null
sc.exe failure $serviceNameArtemis actions=
restart/6/restart/6/restart/6 reset= 6 | Out-Null
sc.exe config $serviceNameArtemis obj= "UserName" password=
"UserPassword
{code}
For the request you can use the fetch request from the ticket and past it into
the chrome dev console.
Once the preflight check wors you can use this fetch to read some data:
{code:js}
fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
{
"headers": {
"authorization": "Basic YWRtaW46cGFzc3dvcmQ=",
"content-type": "text/json",
"sec-ch-ua": "\"Google Chrome\";v=\"105\", \"Not)A;Brand\";v=\"8\",
\"Chromium\";v=\"105\"",
"sec-ch-ua-mobile": "?0",
"sec-ch-ua-platform": "\"Windows\""
},
"referrer": "",
"referrerPolicy": "strict-origin-when-cross-origin",
"body":
"{\"type\":\"exec\",\"mbean\":\"org.apache.activemq.artemis:broker=\\u0022Argos\\u0022\",\"operation\":\"listQueues(java.lang.String,
int,
[jira] [Updated] (ARTEMIS-4027) Cannot access management API due to CORS problems (403)
[
https://issues.apache.org/jira/browse/ARTEMIS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
daves updated ARTEMIS-4027:
---
Attachment: etc.zip
> Cannot access management API due to CORS problems (403)
> ---
>
> Key: ARTEMIS-4027
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4027
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: API
>Affects Versions: 2.25.0
>Reporter: daves
>Priority: Major
> Attachments: etc.zip, options.JPG
>
>
> I try to access the management API from a client app running in chrome.
> This does not work because the preflight check fails.
> OPTIONS request:
>
> {code:java}
> fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
> {
> "headers": {
> "accept": "*/*",
> "accept-language": "en-US,en;q=0.9",
> "sec-fetch-dest": "empty",
> "sec-fetch-mode": "cors",
> "sec-fetch-site": "cross-site"
> },
> "referrerPolicy": "strict-origin-when-cross-origin",
> "body": null,
> "method": "OPTIONS",
> "mode": "cors",
> "credentials": "omit"
> });
>
> {code}
>
> The request fails with a 403 not authenticated... which is strange since
> preflight checks must not be authenticated.
> !options.JPG!
>
> I tried to configure CORS in the jolokia-access.xml file like so:
>
>
> {code:java}
>
>
>
> *://*
>
>
>
> {code}
>
>
> I also tried to specify the URL and port of my application explicitly. But
> this did not work either.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4027) Cannot access management API due to CORS problems (403)
[
https://issues.apache.org/jira/browse/ARTEMIS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612662#comment-17612662
]
daves commented on ARTEMIS-4027:
[~jbertram] Sure here is how we create a broker:
*$artemisInstallDirectory* is the path to the extracted zip file. The script
should work with pwsh and powershell.
The builtin service account should work, but we use special user for the serive.
{code:bash}
$username = "admin"
$password = "password"
$brokerName = "MyBroker"
$datadir = "C:\Data\"
$instanceDirector = "C:\Apache\Artemis\MyBroker"
$artemisInstallDirectory = "C:\Apache\Artemis\apache-artemis-2.25.0"
$artemisCmdPath = Join-Path $artemisInstallDirectory "\bin\artemis.cmd"
Start-Process -Wait -WindowStyle Hidden -FilePath $artemisCmdPath
"create --data `"$datadir`" --name $brokerName --user $username --password
$password --require-login `"$instanceDirector`""
$instanceServiceExe = Join-Path $instanceDirector
"\bin\artemis-service.exe"
Start-Process -FilePath $instanceServiceExe -ArgumentList "install"
-RedirectStandardOutput "NUL" -Wait -NoNewWindow
sc.exe config $serviceNameArtemis start= delayed-auto | Out-Null
sc.exe failure $serviceNameArtemis actions=
restart/6/restart/6/restart/6 reset= 6 | Out-Null
sc.exe config $serviceNameArtemis obj= "UserName" password=
"UserPassword
{code}
For the request you can use the fetch request from the ticket and past it into
the chrome dev console.
Once the preflight check wors you can use this fetch to read some data:
{code:js}
fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
{
"headers": {
"authorization": "Basic YWRtaW46cGFzc3dvcmQ=",
"content-type": "text/json",
"sec-ch-ua": "\"Google Chrome\";v=\"105\", \"Not)A;Brand\";v=\"8\",
\"Chromium\";v=\"105\"",
"sec-ch-ua-mobile": "?0",
"sec-ch-ua-platform": "\"Windows\""
},
"referrer": "",
"referrerPolicy": "strict-origin-when-cross-origin",
"body":
"{\"type\":\"exec\",\"mbean\":\"org.apache.activemq.artemis:broker=\\u0022Argos\\u0022\",\"operation\":\"listQueues(java.lang.String,
int,
int)\",\"arguments\":[\"{\\u0022field\\u0022:\\u0022\\u0022,\\u0022operation\\u0022:\\u0022\\u0022,\\u0022value\\u0022:\\u0022\\u0022,\\u0022sortOrder\\u0022:\\u0022\\u0022,\\u0022sortColumn\\u0022:\\u0022\\u0022}\",\"1\",\"1000\"]}",
"method": "POST",
"mode": "cors",
"credentials": "include"
});
{code}
You may have to change the authorization based on your username/password.
> Cannot access management API due to CORS problems (403)
> ---
>
> Key: ARTEMIS-4027
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4027
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: API
>Affects Versions: 2.25.0
>Reporter: daves
>Priority: Major
> Attachments: options.JPG
>
>
> I try to access the management API from a client app running in chrome.
> This does not work because the preflight check fails.
> OPTIONS request:
>
> {code:java}
> fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
> {
> "headers": {
> "accept": "*/*",
> "accept-language": "en-US,en;q=0.9",
> "sec-fetch-dest": "empty",
> "sec-fetch-mode": "cors",
> "sec-fetch-site": "cross-site"
> },
> "referrerPolicy": "strict-origin-when-cross-origin",
> "body": null,
> "method": "OPTIONS",
> "mode": "cors",
> "credentials": "omit"
> });
>
> {code}
>
> The request fails with a 403 not authenticated... which is strange since
> preflight checks must not be authenticated.
> !options.JPG!
>
> I tried to configure CORS in the jolokia-access.xml file like so:
>
>
> {code:java}
>
>
>
> *://*
>
>
>
> {code}
>
>
> I also tried to specify the URL and port of my application explicitly. But
> this did not work either.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4027) Cannot access management API due to CORS problems (403)
daves created ARTEMIS-4027:
--
Summary: Cannot access management API due to CORS problems (403)
Key: ARTEMIS-4027
URL: https://issues.apache.org/jira/browse/ARTEMIS-4027
Project: ActiveMQ Artemis
Issue Type: Bug
Components: API
Affects Versions: 2.25.0
Reporter: daves
Attachments: options.JPG
I try to access the management API from a client app running in chrome.
This does not work because the preflight check fails.
OPTIONS request:
{code:java}
fetch("http://localhost:8161/console/jolokia/?maxDepth=7=5=false=false;,
{
"headers": {
"accept": "*/*",
"accept-language": "en-US,en;q=0.9",
"sec-fetch-dest": "empty",
"sec-fetch-mode": "cors",
"sec-fetch-site": "cross-site"
},
"referrerPolicy": "strict-origin-when-cross-origin",
"body": null,
"method": "OPTIONS",
"mode": "cors",
"credentials": "omit"
});
{code}
The request fails with a 403 not authenticated... which is strange since
preflight checks must not be authenticated.
!options.JPG!
I tried to configure CORS in the jolokia-access.xml file like so:
{code:java}
*://*
{code}
I also tried to specify the URL and port of my application explicitly. But this
did not work either.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-3437) java.lang.NumberFormatException STOMP/AMQP interop
daves created ARTEMIS-3437:
--
Summary: java.lang.NumberFormatException STOMP/AMQP interop
Key: ARTEMIS-3437
URL: https://issues.apache.org/jira/browse/ARTEMIS-3437
Project: ActiveMQ Artemis
Issue Type: Bug
Components: AMQP
Affects Versions: 2.18.0
Environment: win10 21h1 x64
jdk-15.0.1
Artemis 2.18.0
Reporter: daves
I’ve a client which sends STOMP messages to a Artemis broker (2.18.0).
The server is currently consuming the messages using STOMP as well.
I’m not happy with my STOMP library and there are no good alternatives.
Therefore, I would like to switch to AMQP for the server.
…as far as I understand the client and server can use a different
protocol…right?
Consuming messages with the new AMQP code works…but after a few messages the
broker stops sending new messages to my client. The current implementation
consumes one message at a time and sends a accept after each message…
In the Artemis Log I can find entry like this when the broker stops sending
messages to my AMQP client:
{code:java}
2021-08-20 19:40:54,946 DEBUG
[org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreMessageWrapper]
null: java.lang.NumberFormatException: nullat
java.base/java.lang.Integer.parseInt(Integer.java:614) [java.base:]at
java.base/java.lang.Short.parseShort(Short.java:130) [java.base:]at
java.base/java.lang.Short.valueOf(Short.java:186) [java.base:]at
java.base/java.lang.Short.valueOf(Short.java:212) [java.base:]at
org.apache.activemq.artemis.utils.collections.TypedProperties.getShortProperty(TypedProperties.java:257)
[artemis-commons-2.18.0.jar:2.18.0]at
org.apache.activemq.artemis.core.message.impl.CoreMessage.getShortProperty(CoreMessage.java:1044)
[artemis-core-client-2.18.0.jar:2.18.0]at
org.apache.activemq.artemis.core.message.impl.CoreMessage.getShortProperty(CoreMessage.java:1049)
[artemis-core-client-2.18.0.jar:2.18.0]at
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreMessageWrapper.getOrignalEncoding(CoreMessageWrapper.java:78)
[artemis-amqp-protocol-2.18.0.jar:2.18.0]at
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.createAMQPSection(CoreBytesMessageWrapper.java:77)
[artemis-amqp-protocol-2.18.0.jar:2.18.0]at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:108)
[artemis-amqp-protocol-2.18.0.jar:2.18.0]at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:83)
[artemis-amqp-protocol-2.18.0.jar:2.18.0]at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:537)
[artemis-amqp-protocol-2.18.0.jar:2.18.0]at
org.apache.activemq.artemis.core.server.impl.MessageReferenceImpl.run(MessageReferenceImpl.java:136)
[artemis-server-2.18.0.jar:2.18.0]at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
[netty-all-4.1.66.Final.jar:4.1.66.Final]at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
[netty-all-4.1.66.Final.jar:4.1.66.Final]at
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
[netty-all-4.1.66.Final.jar:4.1.66.Final]at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
[netty-all-4.1.66.Final.jar:4.1.66.Final]at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
[netty-all-4.1.66.Final.jar:4.1.66.Final]at
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
[artemis-commons-2.18.0.jar:2.18.0]{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2811) Component org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
[
https://issues.apache.org/jira/browse/ARTEMIS-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142854#comment-17142854
]
daves commented on ARTEMIS-2811:
[~jbertram] Thanks for your comment. I will look at the documentation.
I think the problem with the windows service is that the service is not
running the java process directly but uses a service wrapper called
"artemis-service.exe". I've used such wrappers before. My favorite is nssm
[https://nssm.cc/] which as far as is know detects if the "hosted" process
existed an is able to signal this exit to the service manager.
Sadly the broker is hosted in an environment not controlled by us. I don't have
any option to change the monitoring or check if everything is ok with the
filestystem… I know you can't do anything neither but maybe it would be an
option to take a look at "artemis-service.exe" and check if there is an option
to detect a stopped java process?
> Component org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired
> on path 0
> -
>
> Key: ARTEMIS-2811
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2811
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.11.0
> Environment: * Windows Server 2016
> * Artemis running as Windows Service
>Reporter: daves
>Assignee: Justin Bertram
>Priority: Major
> Attachments: broker.xml
>
>
> We run Artemis 2.11.0 on Windows Server 2016 as Windows Service. Suddenly
> Artemis stopped working. The Artemis process stopped but the Windows
> Service/Service wrapper was still running. We monitor all Services if they
> are running, but since the Artemis-Service was still running our monitoring
> did not detect that Artemis was not running anymore.
>
> # Is it possible to kill the Windows-Service together with the Artemis
> process? (would be very nice for monitoring etc.)
> # Is there a fix for this issue maybe in a newer version?
> Please see below stacktrace for more details. Please let me know if you need
> any additional information.
>
> {code:java}
> 2020-06-18 11:06:20,865 WARN
> [org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
> 2020-06-18 11:06:20,865 WARN
> [org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
> 2020-06-18 11:06:20,865 ERROR [org.apache.activemq.artemis.core.server]
> AMQ224079: The process for the virtual machine will be killed, as component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer@37d4349f is not
> responsive
> 2020-06-18 11:06:21,146 WARN [org.apache.activemq.artemis.core.server]
> AMQ222199: Thread dump:
> ***Complete
> Thread dump "qtp140224-69441" Id=69441 TIMED_WAITING on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@5b811449
> at sun.misc.Unsafe.park(Native Method) - waiting on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@5b811449
> at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown
> Source) at
> org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:392)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:564)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.access$800(QueuedThreadPool.java:49)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:627)
> at java.lang.Thread.run(Unknown Source)"Thread-11562
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@3cc1435c)"
> Id=69440 TIMED_WAITING on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@1e83815d
> at sun.misc.Unsafe.park(Native Method) - waiting on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@1e83815d
> at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown
> Source) at java.util.concurrent.LinkedBlockingQueue.poll(Unknown Source) at
> org.apache.activemq.artemis.utils.ActiveMQThreadPoolExecutor$ThreadPoolQueue.poll(ActiveMQThreadPoolExecutor.java:112)
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadPoolExecutor$ThreadPoolQueue.poll(ActiveMQThreadPoolExecutor.java:45)
> at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at
>
[jira] [Comment Edited] (ARTEMIS-2811) Component org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
[
https://issues.apache.org/jira/browse/ARTEMIS-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142854#comment-17142854
]
daves edited comment on ARTEMIS-2811 at 6/23/20, 11:32 AM:
---
[~jbertram] Thanks for your comment. I will look at the documentation.
I think the problem with the windows service is that the service is not
running the java process directly but uses a service wrapper called
"artemis-service.exe". I've used such wrappers before. My favorite is nssm
[https://nssm.cc/] which as far as is know detects if the "hosted" process
existed an is able to signal this exit to the service manager.
Sadly the broker is hosted in an environment not controlled by us. I don't have
any option to change the monitoring or check if everything is ok with the
filestystem… I know you can't do anything neither but maybe it would be an
option to take a look at "artemis-service.exe" and check if there is an option
to detect a stopped java process?
I’ve also attached our broker.xml file (if you want to take a look at the
content…)
was (Author: daves):
[~jbertram] Thanks for your comment. I will look at the documentation.
I think the problem with the windows service is that the service is not
running the java process directly but uses a service wrapper called
"artemis-service.exe". I've used such wrappers before. My favorite is nssm
[https://nssm.cc/] which as far as is know detects if the "hosted" process
existed an is able to signal this exit to the service manager.
Sadly the broker is hosted in an environment not controlled by us. I don't have
any option to change the monitoring or check if everything is ok with the
filestystem… I know you can't do anything neither but maybe it would be an
option to take a look at "artemis-service.exe" and check if there is an option
to detect a stopped java process?
> Component org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired
> on path 0
> -
>
> Key: ARTEMIS-2811
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2811
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.11.0
> Environment: * Windows Server 2016
> * Artemis running as Windows Service
>Reporter: daves
>Assignee: Justin Bertram
>Priority: Major
> Attachments: broker.xml
>
>
> We run Artemis 2.11.0 on Windows Server 2016 as Windows Service. Suddenly
> Artemis stopped working. The Artemis process stopped but the Windows
> Service/Service wrapper was still running. We monitor all Services if they
> are running, but since the Artemis-Service was still running our monitoring
> did not detect that Artemis was not running anymore.
>
> # Is it possible to kill the Windows-Service together with the Artemis
> process? (would be very nice for monitoring etc.)
> # Is there a fix for this issue maybe in a newer version?
> Please see below stacktrace for more details. Please let me know if you need
> any additional information.
>
> {code:java}
> 2020-06-18 11:06:20,865 WARN
> [org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
> 2020-06-18 11:06:20,865 WARN
> [org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
> 2020-06-18 11:06:20,865 ERROR [org.apache.activemq.artemis.core.server]
> AMQ224079: The process for the virtual machine will be killed, as component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer@37d4349f is not
> responsive
> 2020-06-18 11:06:21,146 WARN [org.apache.activemq.artemis.core.server]
> AMQ222199: Thread dump:
> ***Complete
> Thread dump "qtp140224-69441" Id=69441 TIMED_WAITING on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@5b811449
> at sun.misc.Unsafe.park(Native Method) - waiting on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@5b811449
> at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown
> Source) at
> org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:392)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:564)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.access$800(QueuedThreadPool.java:49)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:627)
> at java.lang.Thread.run(Unknown Source)"Thread-11562
>
[jira] [Updated] (ARTEMIS-2811) Component org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
[
https://issues.apache.org/jira/browse/ARTEMIS-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
daves updated ARTEMIS-2811:
---
Attachment: broker.xml
> Component org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired
> on path 0
> -
>
> Key: ARTEMIS-2811
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2811
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.11.0
> Environment: * Windows Server 2016
> * Artemis running as Windows Service
>Reporter: daves
>Assignee: Justin Bertram
>Priority: Major
> Attachments: broker.xml
>
>
> We run Artemis 2.11.0 on Windows Server 2016 as Windows Service. Suddenly
> Artemis stopped working. The Artemis process stopped but the Windows
> Service/Service wrapper was still running. We monitor all Services if they
> are running, but since the Artemis-Service was still running our monitoring
> did not detect that Artemis was not running anymore.
>
> # Is it possible to kill the Windows-Service together with the Artemis
> process? (would be very nice for monitoring etc.)
> # Is there a fix for this issue maybe in a newer version?
> Please see below stacktrace for more details. Please let me know if you need
> any additional information.
>
> {code:java}
> 2020-06-18 11:06:20,865 WARN
> [org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
> 2020-06-18 11:06:20,865 WARN
> [org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
> 2020-06-18 11:06:20,865 ERROR [org.apache.activemq.artemis.core.server]
> AMQ224079: The process for the virtual machine will be killed, as component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer@37d4349f is not
> responsive
> 2020-06-18 11:06:21,146 WARN [org.apache.activemq.artemis.core.server]
> AMQ222199: Thread dump:
> ***Complete
> Thread dump "qtp140224-69441" Id=69441 TIMED_WAITING on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@5b811449
> at sun.misc.Unsafe.park(Native Method) - waiting on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@5b811449
> at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown
> Source) at
> org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:392)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:564)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.access$800(QueuedThreadPool.java:49)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:627)
> at java.lang.Thread.run(Unknown Source)"Thread-11562
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@3cc1435c)"
> Id=69440 TIMED_WAITING on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@1e83815d
> at sun.misc.Unsafe.park(Native Method) - waiting on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@1e83815d
> at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown
> Source) at java.util.concurrent.LinkedBlockingQueue.poll(Unknown Source) at
> org.apache.activemq.artemis.utils.ActiveMQThreadPoolExecutor$ThreadPoolQueue.poll(ActiveMQThreadPoolExecutor.java:112)
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadPoolExecutor$ThreadPoolQueue.poll(ActiveMQThreadPoolExecutor.java:45)
> at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)"Thread-11561
>
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@3cc1435c)"
> Id=69439 TIMED_WAITING on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@1e83815d
> at sun.misc.Unsafe.park(Native Method) - waiting on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@1e83815d
> at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown
> Source) at java.util.concurrent.LinkedBlockingQueue.poll(Unknown Source) at
>
[jira] [Created] (ARTEMIS-2811) Component org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
daves created ARTEMIS-2811:
--
Summary: Component
org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 0
Key: ARTEMIS-2811
URL: https://issues.apache.org/jira/browse/ARTEMIS-2811
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker, STOMP
Affects Versions: 2.11.0
Environment: * Windows Server 2016
* Artemis running as Windows Service
Reporter: daves
Assignee: Justin Bertram
We run Artemis 2.11.0 on Windows Server 2016 as Windows Service. Suddenly
Artemis stopped working. The Artemis process stopped but the Windows
Service/Service wrapper was still running. We monitor all Services if they are
running, but since the Artemis-Service was still running our monitoring did not
detect that Artemis was not running anymore.
# Is it possible to kill the Windows-Service together with the Artemis
process? (would be very nice for monitoring etc.)
# Is there a fix for this issue maybe in a newer version?
#
Please see below stacktrace for more details. Please let me know if you need
any additional information.
{code:java}
2020-06-18 11:06:20,865 WARN
[org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path
02020-06-18 11:06:20,865 WARN
[org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path
02020-06-18 11:06:20,865 ERROR [org.apache.activemq.artemis.core.server]
AMQ224079: The process for the virtual machine will be killed, as component
org.apache.activemq.artemis.core.io.buffer.TimedBuffer@37d4349f is not
responsive2020-06-18 11:06:21,146 WARN
[org.apache.activemq.artemis.core.server] AMQ222199: Thread dump:
***Complete
Thread dump "qtp140224-69441" Id=69441 TIMED_WAITING on
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@5b811449
at sun.misc.Unsafe.park(Native Method) - waiting on
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@5b811449
at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown
Source) at
org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:392) at
org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:564)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.access$800(QueuedThreadPool.java:49)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:627)
at java.lang.Thread.run(Unknown Source)"Thread-11562
(ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@3cc1435c)"
Id=69440 TIMED_WAITING on
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@1e83815d
at sun.misc.Unsafe.park(Native Method) - waiting on
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@1e83815d
at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown
Source) at java.util.concurrent.LinkedBlockingQueue.poll(Unknown Source) at
org.apache.activemq.artemis.utils.ActiveMQThreadPoolExecutor$ThreadPoolQueue.poll(ActiveMQThreadPoolExecutor.java:112)
at
org.apache.activemq.artemis.utils.ActiveMQThreadPoolExecutor$ThreadPoolQueue.poll(ActiveMQThreadPoolExecutor.java:45)
at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) at
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)"Thread-11561
(ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@3cc1435c)"
Id=69439 TIMED_WAITING on
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@1e83815d
at sun.misc.Unsafe.park(Native Method) - waiting on
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@1e83815d
at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown
Source) at java.util.concurrent.LinkedBlockingQueue.poll(Unknown Source) at
org.apache.activemq.artemis.utils.ActiveMQThreadPoolExecutor$ThreadPoolQueue.poll(ActiveMQThreadPoolExecutor.java:112)
at
org.apache.activemq.artemis.utils.ActiveMQThreadPoolExecutor$ThreadPoolQueue.poll(ActiveMQThreadPoolExecutor.java:45)
at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) at
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
