[jira] [Updated] (ARTEMIS-3598) Sending text message non-UTF-8 containing special characters from OpenWire
[ https://issues.apache.org/jira/browse/ARTEMIS-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Henry Brasseur updated ARTEMIS-3598: --- Affects Version/s: 2.17.0 > Sending text message non-UTF-8 containing special characters from OpenWire > --- > > Key: ARTEMIS-3598 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3598 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native, OpenWire >Affects Versions: 2.16.0, 2.17.0 >Reporter: Pierre-Henry Brasseur >Assignee: Gary Tully >Priority: Major > Attachments: Re Question about charset supported by Artemis.msg, > main.c, verifyUtf.patch > > > When a text message non-UTF-8 (ISO-8859-15) containing special characters is > sent from OpenWire, this raised an exception > :"java.io.UTFDataFormatException" which is not correctly handle and prevent > the sending of the text message. > See email from ActiveMQ Community in attachment for more details. > [^Re Question about charset supported by Artemis.msg] > > This was working with previous ActiveMQ version (v5.15.9). > > Identified during following test : > Text message sent from a C program using the Fuse ActiveMQ-Client C library > to Artemis v2.16. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARTEMIS-3598) Sending text message non-UTF-8 containing special characters from OpenWire
[ https://issues.apache.org/jira/browse/ARTEMIS-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456216#comment-17456216 ] Pierre-Henry Brasseur commented on ARTEMIS-3598: Hello, it is working with ActiveMQ 5.x, but did you test my example main.c with Artemis 2.17? > Sending text message non-UTF-8 containing special characters from OpenWire > --- > > Key: ARTEMIS-3598 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3598 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native, OpenWire >Affects Versions: 2.16.0 >Reporter: Pierre-Henry Brasseur >Assignee: Gary Tully >Priority: Major > Attachments: Re Question about charset supported by Artemis.msg, > main.c, verifyUtf.patch > > > When a text message non-UTF-8 (ISO-8859-15) containing special characters is > sent from OpenWire, this raised an exception > :"java.io.UTFDataFormatException" which is not correctly handle and prevent > the sending of the text message. > See email from ActiveMQ Community in attachment for more details. > [^Re Question about charset supported by Artemis.msg] > > This was working with previous ActiveMQ version (v5.15.9). > > Identified during following test : > Text message sent from a C program using the Fuse ActiveMQ-Client C library > to Artemis v2.16. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQNET-745) Apache.NMS has an exception for application launched in single file mode
[
https://issues.apache.org/jira/browse/AMQNET-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iuliia Fatkullina updated AMQNET-745:
-
Description:
Apache.NMS library version 1.8.0 and higher has an exception,
when trying to instantiate the NMSConnectionFactory class,
if the application is launched in single file mode.
An example of an exception can be seen when using Apache.NMS.ActiveMQ
[https://github.com/i7nfinity/apache-nms-singlefile-error]
Need to fix GetConfigSearchPaths method because
Path.GetDirectoryName(executingAssembly.Location) returns null in the file
[https://github.com/apache/activemq-nms-api/blob/main/src/nms-api/NMSConnectionFactory.cs]
You can read more about the problem here
[https://docs.microsoft.com/en-us/dotnet/core/deploying/single-file]
{code:bash}
Could not create the IConnectionFactory implementation: Value cannot be null.
(Parameter 'path1')
at Apache.NMS.NMSConnectionFactory.CreateConnectionFactory(Uri uriProvider,
Object[] constructorParams)
at Apache.NMS.NMSConnectionFactory..ctor(Uri uriProvider, Object[]
constructorParams)
at Apache.NMS.NMSConnectionFactory..ctor(String providerURI, Object[]
constructorParams)
at ApacheNmsSingleAppError.Program.Main()
{code}
was:
Apache.NMS library version 1.8.0 and higher has an exception,
when trying to instantiate the NMSConnectionFactory class,
if the application is launched in single file mode.
An example of an exception can be seen when using Apache.NMS.ActiveMQ
https://github.com/i7nfinity/apache-nms-singlefile-error
Need to fix GetConfigSearchPaths method because
Path.GetDirectoryName(executingAssembly.Location) returns null in the file
https://github.com/apache/activemq-nms-api/blob/main/src/nms-api/NMSConnectionFactory.cs
You can read more about the problem here
https://docs.microsoft.com/en-us/dotnet/core/deploying/single-file
> Apache.NMS has an exception for application launched in single file mode
>
>
> Key: AMQNET-745
> URL: https://issues.apache.org/jira/browse/AMQNET-745
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ, NMS
>Affects Versions: OpenWire-1.8.0
>Reporter: Iuliia Fatkullina
>Priority: Critical
>
> Apache.NMS library version 1.8.0 and higher has an exception,
> when trying to instantiate the NMSConnectionFactory class,
> if the application is launched in single file mode.
> An example of an exception can be seen when using Apache.NMS.ActiveMQ
> [https://github.com/i7nfinity/apache-nms-singlefile-error]
> Need to fix GetConfigSearchPaths method because
> Path.GetDirectoryName(executingAssembly.Location) returns null in the file
> [https://github.com/apache/activemq-nms-api/blob/main/src/nms-api/NMSConnectionFactory.cs]
> You can read more about the problem here
> [https://docs.microsoft.com/en-us/dotnet/core/deploying/single-file]
>
> {code:bash}
> Could not create the IConnectionFactory implementation: Value cannot be null.
> (Parameter 'path1')
>at Apache.NMS.NMSConnectionFactory.CreateConnectionFactory(Uri
> uriProvider, Object[] constructorParams)
>at Apache.NMS.NMSConnectionFactory..ctor(Uri uriProvider, Object[]
> constructorParams)
>at Apache.NMS.NMSConnectionFactory..ctor(String providerURI, Object[]
> constructorParams)
>at ApacheNmsSingleAppError.Program.Main()
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (AMQNET-745) Apache.NMS has an exception for application launched in single file mode
Iuliia Fatkullina created AMQNET-745: Summary: Apache.NMS has an exception for application launched in single file mode Key: AMQNET-745 URL: https://issues.apache.org/jira/browse/AMQNET-745 Project: ActiveMQ .Net Issue Type: Bug Components: ActiveMQ, NMS Affects Versions: OpenWire-1.8.0 Reporter: Iuliia Fatkullina Apache.NMS library version 1.8.0 and higher has an exception, when trying to instantiate the NMSConnectionFactory class, if the application is launched in single file mode. An example of an exception can be seen when using Apache.NMS.ActiveMQ https://github.com/i7nfinity/apache-nms-singlefile-error Need to fix GetConfigSearchPaths method because Path.GetDirectoryName(executingAssembly.Location) returns null in the file https://github.com/apache/activemq-nms-api/blob/main/src/nms-api/NMSConnectionFactory.cs You can read more about the problem here https://docs.microsoft.com/en-us/dotnet/core/deploying/single-file -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Deleted] (AMQ-8424) used furniture buyers in sharjah
[ https://issues.apache.org/jira/browse/AMQ-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon deleted AMQ-8424: > used furniture buyers in sharjah > > > Key: AMQ-8424 > URL: https://issues.apache.org/jira/browse/AMQ-8424 > Project: ActiveMQ > Issue Type: Wish > Environment: We buy all type of used furniture in Dubai, used bedroom > sets, used dining tables, used leather sofa sets, used fabric sofa sets, used > cupboards, used. > [used furniture buyers in > sharjah|https://www.usedfurniturebuyerdubai.furniture] >Reporter: IHSAN NOOR >Priority: Major > Original Estimate: 2,628h > Remaining Estimate: 2,628h > > We buy all type of used furniture in Dubai, used bedroom sets, used dining > tables, used leather sofa sets, used fabric sofa sets, used cupboards, used. > [used furniture buyers in > sharjah|https://www.usedfurniturebuyerdubai.furniture] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (ARTEMIS-3598) Sending text message non-UTF-8 containing special characters from OpenWire
[ https://issues.apache.org/jira/browse/ARTEMIS-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned ARTEMIS-3598: --- Assignee: Gary Tully (was: Clebert Suconic) > Sending text message non-UTF-8 containing special characters from OpenWire > --- > > Key: ARTEMIS-3598 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3598 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native, OpenWire >Affects Versions: 2.16.0 >Reporter: Pierre-Henry Brasseur >Assignee: Gary Tully >Priority: Major > Attachments: Re Question about charset supported by Artemis.msg, > main.c, verifyUtf.patch > > > When a text message non-UTF-8 (ISO-8859-15) containing special characters is > sent from OpenWire, this raised an exception > :"java.io.UTFDataFormatException" which is not correctly handle and prevent > the sending of the text message. > See email from ActiveMQ Community in attachment for more details. > [^Re Question about charset supported by Artemis.msg] > > This was working with previous ActiveMQ version (v5.15.9). > > Identified during following test : > Text message sent from a C program using the Fuse ActiveMQ-Client C library > to Artemis v2.16. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (ARTEMIS-3598) Sending text message non-UTF-8 containing special characters from OpenWire
[ https://issues.apache.org/jira/browse/ARTEMIS-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455902#comment-17455902 ] Gary Tully edited comment on ARTEMIS-3598 at 12/8/21, 5:41 PM: --- [~phbrasseur] I cannot reproduce this, with main/trunk in java and with a local build of main cms. It works ok. See the attached little java unit test that verifies from the main line. When that worked I build cms and ran your example main.c and it works too. Not sure what you are seeing but maybe verify with the latest 5.19.0 or main. was (Author: gtully): [~phbrasseur] I cannot reproduce this, with main in java and with a local build of main cms. It works ok. See the attached little java unit test that verifies from the main line. When that worked I build cms and ran your example main.c and it works too. Not sure what you are seeing but maybe verify with the latest 5.19.0 or main. > Sending text message non-UTF-8 containing special characters from OpenWire > --- > > Key: ARTEMIS-3598 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3598 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native, OpenWire >Affects Versions: 2.16.0 >Reporter: Pierre-Henry Brasseur >Assignee: Clebert Suconic >Priority: Major > Attachments: Re Question about charset supported by Artemis.msg, > main.c, verifyUtf.patch > > > When a text message non-UTF-8 (ISO-8859-15) containing special characters is > sent from OpenWire, this raised an exception > :"java.io.UTFDataFormatException" which is not correctly handle and prevent > the sending of the text message. > See email from ActiveMQ Community in attachment for more details. > [^Re Question about charset supported by Artemis.msg] > > This was working with previous ActiveMQ version (v5.15.9). > > Identified during following test : > Text message sent from a C program using the Fuse ActiveMQ-Client C library > to Artemis v2.16. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARTEMIS-3598) Sending text message non-UTF-8 containing special characters from OpenWire
[ https://issues.apache.org/jira/browse/ARTEMIS-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455902#comment-17455902 ] Gary Tully commented on ARTEMIS-3598: - [~phbrasseur] I cannot reproduce this, with main in java and with a local build of main cms. It works ok. See the attached little java unit test that verifies from the main line. When that worked I build cms and ran your example main.c and it works too. Not sure what you are seeing but maybe verify with the latest 5.19.0 or main. > Sending text message non-UTF-8 containing special characters from OpenWire > --- > > Key: ARTEMIS-3598 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3598 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native, OpenWire >Affects Versions: 2.16.0 >Reporter: Pierre-Henry Brasseur >Assignee: Clebert Suconic >Priority: Major > Attachments: Re Question about charset supported by Artemis.msg, > main.c, verifyUtf.patch > > > When a text message non-UTF-8 (ISO-8859-15) containing special characters is > sent from OpenWire, this raised an exception > :"java.io.UTFDataFormatException" which is not correctly handle and prevent > the sending of the text message. > See email from ActiveMQ Community in attachment for more details. > [^Re Question about charset supported by Artemis.msg] > > This was working with previous ActiveMQ version (v5.15.9). > > Identified during following test : > Text message sent from a C program using the Fuse ActiveMQ-Client C library > to Artemis v2.16. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARTEMIS-3598) Sending text message non-UTF-8 containing special characters from OpenWire
[ https://issues.apache.org/jira/browse/ARTEMIS-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3598: Attachment: verifyUtf.patch > Sending text message non-UTF-8 containing special characters from OpenWire > --- > > Key: ARTEMIS-3598 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3598 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native, OpenWire >Affects Versions: 2.16.0 >Reporter: Pierre-Henry Brasseur >Assignee: Clebert Suconic >Priority: Major > Attachments: Re Question about charset supported by Artemis.msg, > main.c, verifyUtf.patch > > > When a text message non-UTF-8 (ISO-8859-15) containing special characters is > sent from OpenWire, this raised an exception > :"java.io.UTFDataFormatException" which is not correctly handle and prevent > the sending of the text message. > See email from ActiveMQ Community in attachment for more details. > [^Re Question about charset supported by Artemis.msg] > > This was working with previous ActiveMQ version (v5.15.9). > > Identified during following test : > Text message sent from a C program using the Fuse ActiveMQ-Client C library > to Artemis v2.16. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker
[
https://issues.apache.org/jira/browse/ARTEMIS-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455368#comment-17455368
]
Justin Bertram commented on ARTEMIS-3509:
-
[~Elodie], can you elaborate on how you were able to reproduce the exception? I
need sufficient detail to reproduce the failure for myself. Thanks!
> STOMP Websocket client disconnected after ConcurrentModificationException in
> Broker
> ---
>
> Key: ARTEMIS-3509
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3509
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.16.0
>Reporter: Elodie Vandromme
>Priority: Major
>
> Web clients connected through WebSocket are randomly disconnected from
> artemis broker without notification of the disconnection.
> A ConcurrentModificationException is raised;
> {noformat}
> [2021-09-28 10:26:53,591] - [WILDFLY] - [WARN ] - [Thread-11
> ([ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@444dc7ba|mailto:ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@444dc7ba])]
> - [org.apache.activemq.artemis.core.server] : *AMQ222151: removing consumer
> which did not handle a message*, consumer=ServerConsumerImpl [id=1990,
> filter=null, binding=LocalQueueBinding [address=jms.topic.defended_assetFull,
> queue=QueueImpl[name=d1586796-2035-11ec-8d2e-00505689a76b,
> postOffice=PostOfficeImpl
> [server=ActiveMQServerImpl::serverUUID=2f00c36f-2034-11ec-8d2e-00505689a76b],
> temp=true]@4180826b, filter=null, name=d1586796-2035-11ec-8d2e-00505689a76b,
> clusterName=d1586796-2035-11ec-8d2e-00505689a76b2f00c36f-2034-11ec-8d2e-00505689a76b]],
>
> message=Reference[2019]:RELIABLE:CoreMessage[messageID=2019,durable=true,userID=d5e2d1c3-2035-11ec-8d2e-00505689a76b,priority=4,
> timestamp=Tue Sep 28 10:26:53 CEST 2021,expiration=0, durable=true,
> address=jms.topic.defended_assetFull,size=6520,properties=TypedProperties[__AMQ_CID=f9eab79a-2034-11ec-8d2e-00505689a76b,_AMQ_ROUTING_TYPE=0]]@155890432:
> java.util.ConcurrentModificationException
> at
> java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)
> at java.util.ArrayList$Itr.next(ArrayList.java:859)
> at
> org.apache.activemq.artemis.core.server.impl.RefsOperation.afterCommit(RefsOperation.java:179)
> at
> org.apache.activemq.artemis.core.transaction.impl.TransactionImpl.afterCommit(TransactionImpl.java:579)
> at
> org.apache.activemq.artemis.core.transaction.impl.TransactionImpl.access$100(TransactionImpl.java:40)
> at
> org.apache.activemq.artemis.core.transaction.impl.TransactionImpl$2.done(TransactionImpl.java:322)
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.OperationContextImpl.executeOnCompletion(OperationContextImpl.java:190)
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.OperationContextImpl.executeOnCompletion(OperationContextImpl.java:128)
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.afterCompleteOperations(AbstractJournalStorageManager.java:321)
> at
> org.apache.activemq.artemis.core.transaction.impl.TransactionImpl.commit(TransactionImpl.java:313)
> at
> org.apache.activemq.artemis.core.transaction.impl.TransactionImpl.commit(TransactionImpl.java:264)
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.commit(ServerSessionImpl.java:1284)
> at
> org.apache.activemq.artemis.core.protocol.stomp.StompSession$1.run(StompSession.java:164)
> at
> org.apache.activemq.artemis.core.protocol.stomp.StompSession.afterDelivery(StompSession.java:116)
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:511)
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.proceedDeliver(QueueImpl.java:3744)
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.deliver(QueueImpl.java:3048)
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.access$2400(QueueImpl.java:125)
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:4119)
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> at
>
[jira] [Commented] (ARTEMIS-3066) Upgrade JGroups from 3.x to 5.x
[
https://issues.apache.org/jira/browse/ARTEMIS-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455341#comment-17455341
]
Stephan Austermühle commented on ARTEMIS-3066:
--
I just noticed that I could not pass {{useNotReadyAddresses}} because JGroups
are outdated, so that I cannot integrate a more recent {{{}KUBE_PING{}}}.
> Upgrade JGroups from 3.x to 5.x
> ---
>
> Key: ARTEMIS-3066
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3066
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Reporter: Martin Kralicek
>Priority: Minor
>
> I know, that artemis is using JGroups only for discovery purpose, but it
> would be very helpful to be able use project
> [https://github.com/jgroups-extras/jgroups-kubernetes] to assembly cluster
> using kubernetes api.
> Project requires JGroups 5.0.1 for recent version 2.0.0 and JGroups 4.2.0 for
> 1.15.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (AMQ-8424) used furniture buyers in sharjah
IHSAN NOOR created AMQ-8424: --- Summary: used furniture buyers in sharjah Key: AMQ-8424 URL: https://issues.apache.org/jira/browse/AMQ-8424 Project: ActiveMQ Issue Type: Wish Environment: We buy all type of used furniture in Dubai, used bedroom sets, used dining tables, used leather sofa sets, used fabric sofa sets, used cupboards, used. [used furniture buyers in sharjah|https://www.usedfurniturebuyerdubai.furniture] Reporter: IHSAN NOOR We buy all type of used furniture in Dubai, used bedroom sets, used dining tables, used leather sofa sets, used fabric sofa sets, used cupboards, used. [used furniture buyers in sharjah|https://www.usedfurniturebuyerdubai.furniture] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARTEMIS-2716) Implements pluggable Quorum Vote
[ https://issues.apache.org/jira/browse/ARTEMIS-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455302#comment-17455302 ] ASF subversion and git services commented on ARTEMIS-2716: -- Commit de7a1805a4918c18dd911083f4f44972adb4645a in activemq-artemis's branch refs/heads/main from gtully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=de7a180 ] ARTEMIS-2716 - fix up test regression in OpenWireProtocolManagerTest > Implements pluggable Quorum Vote > > > Key: ARTEMIS-2716 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2716 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.18.0 > > Attachments: backup.png, primary.png > > Time Spent: 28h 50m > Remaining Estimate: 0h > > This task aim to ideliver a new Quorum Vote mechanism for artemis with the > objectives: > # to make it pluggable > # to cleanly separate the election phase and the cluster member states > # to simplify most common setups in both amount of configuration and > requirements (eg "witness" nodes could be implemented to support single > master-slave pairs) > Post-actions to help people adopt it, but need to be thought upfront: > # a clean upgrade path for current HA replication users > # deprecate or integrate the current HA replication into the new version -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARTEMIS-3602) Cluster connection not distribution messages
[
https://issues.apache.org/jira/browse/ARTEMIS-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455252#comment-17455252
]
Tobias Månsson commented on ARTEMIS-3602:
-
Here are logs from a failed delivery
December 8th 2021, 13:47:59.234 artemis-r4xg7 2021-12-08 12:47:59,234 DEBUG
[org.apache.activemq.artemis.core.server.impl.QueueMessageMetrics]
QueuePendingMessageMetrics[queue=$.artemis.internal.sf.artemis.994daab0-51e4-11ec-bfd9-9ab74d93b535,
name=pending] increment messageCount to 825:
Reference[180276]:NON-RELIABLE:AMQPStandardMessage( [durable=false,
messageID=180276, address=test.amqp.websocket.in, size=583,
applicationProperties=\{msgType=test},
messageAnnotations=\{x-opt-ORIG-QUEUE=test-amqp-websocket-1,
x-opt-ORIG-ADDRESS=test.amqp.websocket.out, x-opt-ORIG-MESSAGE-ID=180275},
properties=Properties\{messageId=null, userId=null,
to='test.amqp.websocket.in', subject='null', replyTo='null',
correlationId=null, contentType=null, contentEncoding=null,
absoluteExpiryTime=Wed Dec 08 12:48:09 UTC 2021, creationTime=null,
groupId='null', groupSequence=null, replyToGroupId='null'}, extraProperties =
TypedProperties[_AMQ_ROUTE_TO$.artemis.internal.sf.artemis.994daab0-51e4-11ec-bfd9-9ab74d93b535=[
0087),bytesAsLongs(135],_AMQ_ORIG_ADDRESS=test.amqp.websocket.out,_AMQ_ORIG_MESSAGE_ID=180275,_AMQ_ORIG_QUEUE=test-amqp-websocket-1,_AMQ_AD=test.amqp.websocket.in]]
December 8th 2021, 13:47:59.234 artemis-r4xg7 2021-12-08 12:47:59,234 DEBUG
[org.apache.activemq.artemis.core.server.impl.QueueImpl] Queue
$.artemis.internal.sf.artemis.994daab0-51e4-11ec-bfd9-9ab74d93b535 doing
deliver. messageReferences=824 with consumers=0
December 8th 2021, 13:47:59.233 artemis-r4xg7 2021-12-08 12:47:59,233 INFO
[com.husqvarnagroup.dss.husqiot.broker.interceptor.MessageInterceptor] INCOMING
interceptor accepted message with
MessageAnnotations\{{x-opt-websocketConnections=hib:husqtest:KB9rqflVDoECJ0Q=}}
and ApplicationProperties\{{msgType=test}} at test.amqp.websocket.out in 0 ms
December 8th 2021, 13:47:59.193 artemis-r4xg7 2021-12-08 12:47:59,192 DEBUG
[org.apache.activemq.artemis.core.server.impl.QueueMessageMetrics]
QueuePendingMessageMetrics[queue=test.amqp.websocket.in, name=delivering]
decrement messageCount to 0:
Reference[180273]:NON-RELIABLE:AMQPStandardMessage( [durable=false,
messageID=180273, address=test.amqp.websocket.in, size=583,
applicationProperties=\{msgType=test},
messageAnnotations=\{x-opt-ORIG-QUEUE=test-amqp-websocket-1,
x-opt-ORIG-ADDRESS=test.amqp.websocket.out, x-opt-ORIG-MESSAGE-ID=180272},
properties=Properties\{messageId=null, userId=null,
to='test.amqp.websocket.in', subject='null', replyTo='null',
correlationId=null, contentType=null, contentEncoding=null,
absoluteExpiryTime=Wed Dec 08 12:48:09 UTC 2021, creationTime=null,
groupId='null', groupSequence=null, replyToGroupId='null'}, extraProperties =
TypedProperties[_AMQ_ORIG_ADDRESS=test.amqp.websocket.out,_AMQ_ORIG_MESSAGE_ID=180272,_AMQ_ORIG_QUEUE=test-amqp-websocket-1,_AMQ_AD=test.amqp.websocket.in]]
December 8th 2021, 13:47:59.190 artemis-r4xg7 2021-12-08 12:47:59,190 DEBUG
[org.apache.activemq.artemis.core.server.impl.QueueMessageMetrics]
QueuePendingMessageMetrics[queue=test.amqp.websocket.in, name=pending]
decrement messageCount to 0:
Reference[180273]:NON-RELIABLE:AMQPStandardMessage( [durable=false,
messageID=180273, address=test.amqp.websocket.in, size=583,
applicationProperties=\{msgType=test},
messageAnnotations=\{x-opt-ORIG-QUEUE=test-amqp-websocket-1,
x-opt-ORIG-ADDRESS=test.amqp.websocket.out, x-opt-ORIG-MESSAGE-ID=180272},
properties=Properties\{messageId=null, userId=null,
to='test.amqp.websocket.in', subject='null', replyTo='null',
correlationId=null, contentType=null, contentEncoding=null,
absoluteExpiryTime=Wed Dec 08 12:48:09 UTC 2021, creationTime=null,
groupId='null', groupSequence=null, replyToGroupId='null'}, extraProperties =
TypedProperties[_AMQ_ORIG_ADDRESS=test.amqp.websocket.out,_AMQ_ORIG_MESSAGE_ID=180272,_AMQ_ORIG_QUEUE=test-amqp-websocket-1,_AMQ_AD=test.amqp.websocket.in]]
December 8th 2021, 13:47:59.190 artemis-r4xg7 2021-12-08 12:47:59,190 DEBUG
[org.apache.activemq.artemis.core.server.impl.QueueMessageMetrics]
QueuePendingMessageMetrics[queue=test.amqp.websocket.in, name=delivering]
increment messageCount to 1:
Reference[180273]:NON-RELIABLE:AMQPStandardMessage( [durable=false,
messageID=180273, address=test.amqp.websocket.in, size=583,
applicationProperties=\{msgType=test},
messageAnnotations=\{x-opt-ORIG-QUEUE=test-amqp-websocket-1,
x-opt-ORIG-ADDRESS=test.amqp.websocket.out, x-opt-ORIG-MESSAGE-ID=180272},
properties=Properties\{messageId=null, userId=null,
to='test.amqp.websocket.in', subject='null', replyTo='null',
correlationId=null, contentType=null, contentEncoding=null,
absoluteExpiryTime=Wed Dec 08 12:48:09 UTC 2021, creationTime=null,
groupId='null',
[jira] [Deleted] (ARTEMIS-3603) Movers And Packers In Sharjah
[ https://issues.apache.org/jira/browse/ARTEMIS-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram deleted ARTEMIS-3603: > Movers And Packers In Sharjah > - > > Key: ARTEMIS-3603 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3603 > Project: ActiveMQ Artemis > Issue Type: Wish > Environment: MOVERS AND PACKERS DUBAI Can Help With Anything. One of > the leading packers and movers in Sharjah is the fist removalists. > [Movers And Packers In Sharjah|https://www.packersmoversdubai.com] >Reporter: ihsan >Priority: Minor > Original Estimate: 2,628h > Remaining Estimate: 2,628h > > MOVERS AND PACKERS DUBAI Can Help With Anything. One of the leading packers > and movers in Sharjah is the fist removalists. > [Movers And Packers In Sharjah|https://www.packersmoversdubai.com] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARTEMIS-3603) Movers And Packers In Sharjah
ihsan created ARTEMIS-3603: --- Summary: Movers And Packers In Sharjah Key: ARTEMIS-3603 URL: https://issues.apache.org/jira/browse/ARTEMIS-3603 Project: ActiveMQ Artemis Issue Type: Wish Environment: MOVERS AND PACKERS DUBAI Can Help With Anything. One of the leading packers and movers in Sharjah is the fist removalists. [Movers And Packers In Sharjah|https://www.packersmoversdubai.com] Reporter: ihsan Attachments: download (1).jpg MOVERS AND PACKERS DUBAI Can Help With Anything. One of the leading packers and movers in Sharjah is the fist removalists. [Movers And Packers In Sharjah|https://www.packersmoversdubai.com] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Deleted] (AMQCLI-55) Movers And Packers In Al Ain
[ https://issues.apache.org/jira/browse/AMQCLI-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram deleted AMQCLI-55: - > Movers And Packers In Al Ain > > > Key: AMQCLI-55 > URL: https://issues.apache.org/jira/browse/AMQCLI-55 > Project: ActiveMQ CLI Tools > Issue Type: Wish >Reporter: ehsan noor >Priority: Major > > As Movers and Packers in Al Ain is one of the most professional relocation > companies in Al-Ain (and All over the United Arab Emirates), HereMovers and > Packers in Al Ain in Al Ain that is the only reason we have always 98% > satisfied clients. > [Movers And Packers In Al Ain|https://www.moverspackersinalain.com/] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (AMQCLI-55) Movers And Packers In Al Ain
ehsan noor created AMQCLI-55: Summary: Movers And Packers In Al Ain Key: AMQCLI-55 URL: https://issues.apache.org/jira/browse/AMQCLI-55 Project: ActiveMQ CLI Tools Issue Type: Wish Reporter: ehsan noor As Movers and Packers in Al Ain is one of the most professional relocation companies in Al-Ain (and All over the United Arab Emirates), HereMovers and Packers in Al Ain in Al Ain that is the only reason we have always 98% satisfied clients. [Movers And Packers In Al Ain|https://www.moverspackersinalain.com/] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARTEMIS-3602) Cluster connection not distribution messages
[ https://issues.apache.org/jira/browse/ARTEMIS-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Månsson updated ARTEMIS-3602: Description: The cluster is set up as a ON_DEMAND cluster with two nodes, were only one node is exposed to the external load-balancer and receiving new connections. This creates a online failover setup by switching over new connections to the other node, before taking down the current for maintenance. During one deployment, the active broker node was failed over without shutting down the passive node. This left the current connection on the passive node, while new connections were created against the now active one. If message were sent to the now passive node, they were synchronized correctly to both nodes and to all connections. But if the messages were sent to then now active node (the intended behavior), they were not sent to clients currently connected to the now passive node. The logs and message counters confirm this, but no cause has been found. Since the cluster synchronization work one way, but not the other, I don't know where to search for errors. I've enabled debug logs on both servers, but don't see any issues. The messages are committed to the correct queues, but nothing is received on the other node in the failure scenario. was: The cluster is set up as a ON_DEMAND cluster with two nodes, were only one node is exposed to the external load-balancer and receiving new connections. This creates a online failover setup by switching over new connections to the other node, before taking down the current for maintenance. During one deployment, the active broker node was failed over without shutting down the passive node. This left the current connection on the passive node, while new connections were created against the now active one. If message were sent to the now passive node, they were synchronized correctly to both nodes and to all connections. But if the messages were sent to then now active node (the intended behavior), they were not sent to clients currently connected to the now passive node. The logs and message counters confirm this, but no cause has been found. > Cluster connection not distribution messages > > > Key: ARTEMIS-3602 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3602 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.18.0 >Reporter: Tobias Månsson >Priority: Major > > The cluster is set up as a ON_DEMAND cluster with two nodes, were only one > node is exposed to the external load-balancer and receiving new connections. > This creates a online failover setup by switching over new connections to the > other node, before taking down the current for maintenance. > During one deployment, the active broker node was failed over without > shutting down the passive node. This left the current connection on the > passive node, while new connections were created against the now active one. > If message were sent to the now passive node, they were synchronized > correctly to both nodes and to all connections. But if the messages were sent > to then now active node (the intended behavior), they were not sent to > clients currently connected to the now passive node. > The logs and message counters confirm this, but no cause has been found. > Since the cluster synchronization work one way, but not the other, I don't > know where to search for errors. I've enabled debug logs on both servers, but > don't see any issues. The messages are committed to the correct queues, but > nothing is received on the other node in the failure scenario. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARTEMIS-3602) Cluster connection not distribution messages
Tobias Månsson created ARTEMIS-3602: --- Summary: Cluster connection not distribution messages Key: ARTEMIS-3602 URL: https://issues.apache.org/jira/browse/ARTEMIS-3602 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Tobias Månsson The cluster is set up as a ON_DEMAND cluster with two nodes, were only one node is exposed to the external load-balancer and receiving new connections. This creates a online failover setup by switching over new connections to the other node, before taking down the current for maintenance. During one deployment, the active broker node was failed over without shutting down the passive node. This left the current connection on the passive node, while new connections were created against the now active one. If message were sent to the now passive node, they were synchronized correctly to both nodes and to all connections. But if the messages were sent to then now active node (the intended behavior), they were not sent to clients currently connected to the now passive node. The logs and message counters confirm this, but no cause has been found. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARTEMIS-3602) Cluster connection not distribution messages
[ https://issues.apache.org/jira/browse/ARTEMIS-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Månsson updated ARTEMIS-3602: Affects Version/s: 2.18.0 > Cluster connection not distribution messages > > > Key: ARTEMIS-3602 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3602 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.18.0 >Reporter: Tobias Månsson >Priority: Major > > The cluster is set up as a ON_DEMAND cluster with two nodes, were only one > node is exposed to the external load-balancer and receiving new connections. > This creates a online failover setup by switching over new connections to the > other node, before taking down the current for maintenance. > During one deployment, the active broker node was failed over without > shutting down the passive node. This left the current connection on the > passive node, while new connections were created against the now active one. > If message were sent to the now passive node, they were synchronized > correctly to both nodes and to all connections. But if the messages were sent > to then now active node (the intended behavior), they were not sent to > clients currently connected to the now passive node. > The logs and message counters confirm this, but no cause has been found. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Deleted] (AMQCLI-54) Water Filter
[ https://issues.apache.org/jira/browse/AMQCLI-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon deleted AMQCLI-54: - > Water Filter > > > Key: AMQCLI-54 > URL: https://issues.apache.org/jira/browse/AMQCLI-54 > Project: ActiveMQ CLI Tools > Issue Type: Wish >Reporter: ahsan noor >Priority: Major > Original Estimate: 2,628h > Remaining Estimate: 2,628h > > Water purification, process by which undesired chemical compounds, organic > and inorganic materials, and biological contaminants are removed from water. > ... The purification procedure reduces the concentration of contaminants such > as suspended particles, parasites, bacteria, algae, viruses, > [Water Filter|https://kentuae.ae/] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Deleted] (AMQ-8423) India Cargo
[ https://issues.apache.org/jira/browse/AMQ-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon deleted AMQ-8423: > India Cargo > --- > > Key: AMQ-8423 > URL: https://issues.apache.org/jira/browse/AMQ-8423 > Project: ActiveMQ > Issue Type: Wish > Environment: Book Your Freight Shipping Online to India from > everywhere. Visit Now! With Deep Tracking Options, track your Cargo Shipment > effortlessly. 24/7 Support. Secure Payments. Deep Tracking Available. > Seamless & Safe. Transparent Pricing. Instant Booking. > [India Cargo|https://www.indiacarg.com/] >Reporter: ahsan noor >Priority: Minor > Original Estimate: 2,628h > Remaining Estimate: 2,628h > > Book Your Freight Shipping Online to India from everywhere. Visit Now! With > Deep Tracking Options, track your Cargo Shipment effortlessly. 24/7 Support. > Secure Payments. Deep Tracking Available. Seamless & Safe. Transparent > Pricing. Instant Booking. > [India Cargo|https://www.indiacarg.com/] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (AMQCLI-54) Water Filter
ahsan noor created AMQCLI-54: Summary: Water Filter Key: AMQCLI-54 URL: https://issues.apache.org/jira/browse/AMQCLI-54 Project: ActiveMQ CLI Tools Issue Type: Wish Reporter: ahsan noor Water purification, process by which undesired chemical compounds, organic and inorganic materials, and biological contaminants are removed from water. ... The purification procedure reduces the concentration of contaminants such as suspended particles, parasites, bacteria, algae, viruses, [Water Filter|https://kentuae.ae/] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (AMQ-8423) India Cargo
ahsan noor created AMQ-8423: --- Summary: India Cargo Key: AMQ-8423 URL: https://issues.apache.org/jira/browse/AMQ-8423 Project: ActiveMQ Issue Type: Wish Environment: Book Your Freight Shipping Online to India from everywhere. Visit Now! With Deep Tracking Options, track your Cargo Shipment effortlessly. 24/7 Support. Secure Payments. Deep Tracking Available. Seamless & Safe. Transparent Pricing. Instant Booking. [India Cargo|https://www.indiacarg.com/] Reporter: ahsan noor Attachments: india cargo.pdf Book Your Freight Shipping Online to India from everywhere. Visit Now! With Deep Tracking Options, track your Cargo Shipment effortlessly. 24/7 Support. Secure Payments. Deep Tracking Available. Seamless & Safe. Transparent Pricing. Instant Booking. [India Cargo|https://www.indiacarg.com/] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker
[
https://issues.apache.org/jira/browse/ARTEMIS-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455030#comment-17455030
]
Elodie Vandromme commented on ARTEMIS-3509:
---
Tested on 2.19.0 version of Artemis in standalone mode with the same result :
{noformat}
2021-12-07 15:08:50,017 WARN [org.apache.activemq.artemis.core.server]
AMQ222151: removing consumer which did not handle a message,
consumer=ServerConsumerImpl [id=2147502803, filter=null,
binding=LocalQueueBinding [address=jms.topic.acmFull,
queue=QueueImpl[name=26d11fd1-5767-11ec-bc7c-3024a9823a44,
postOffice=PostOfficeImpl [server=ActiveMQServerImpl::name=127.0.0.1],
temp=true]@44b4401b, filter=null, name=26d11fd1-5767-11ec-bc7c-3024a9823a44,
clusterName=26d11fd1-5767-11ec-bc7c-3024a9823a4415fd2ebf-5735-11ec-828b-3024a9823a44]],
message=Reference[2147502950]:RELIABLE:CoreMessage[messageID=2147502950,durable=true,userID=338e89a1-5767-11ec-b3a8-3024a9823a44,priority=4,
timestamp=Tue Dec 07 15:08:49 CET 2021,expiration=0, durable=true,
address=jms.topic.acmFull,size=3664,properties=TypedProperties[__AMQ_CID=fe63a897-5765-11ec-b3a8-3024a9823a44,_AMQ_ROUTING_TYPE=0]]@2056760686:
java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)
[rt.jar:1.8.0_222-4-redhat]
at java.util.ArrayList$Itr.next(ArrayList.java:859)
[rt.jar:1.8.0_222-4-redhat]
at
org.apache.activemq.artemis.core.server.impl.RefsOperation.afterCommit(RefsOperation.java:174)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.transaction.impl.TransactionImpl.afterCommit(TransactionImpl.java:564)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.transaction.impl.TransactionImpl$2.done(TransactionImpl.java:305)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.persistence.impl.journal.OperationContextImpl.executeOnCompletion(OperationContextImpl.java:195)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.persistence.impl.journal.OperationContextImpl.executeOnCompletion(OperationContextImpl.java:141)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.afterCompleteOperations(AbstractJournalStorageManager.java:329)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.transaction.impl.TransactionImpl.commit(TransactionImpl.java:296)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.transaction.impl.TransactionImpl.commit(TransactionImpl.java:247)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.commit(ServerSessionImpl.java:1320)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.protocol.stomp.StompSession$1.run(StompSession.java:164)
[artemis-stomp-protocol-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.protocol.stomp.StompSession.afterDelivery(StompSession.java:116)
[artemis-stomp-protocol-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:518)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl.proceedDeliver(QueueImpl.java:3840)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl.deliver(QueueImpl.java:3142)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl.access$2400(QueueImpl.java:129)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:4207)
[artemis-server-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
[artemis-commons-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
[artemis-commons-2.19.0.jar:2.19.0]
at
org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:65)
[artemis-commons-2.19.0.jar:2.19.0]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[rt.jar:1.8.0_222-4-redhat]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[rt.jar:1.8.0_222-4-redhat]
at
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
[artemis-commons-2.19.0.jar:2.19.0]{noformat}
> STOMP Websocket client disconnected after ConcurrentModificationException in
> Broker
> ---
>
> Key: ARTEMIS-3509
> URL:
