Re: Camel generating message with correlationid=null and tmp-queue null

[Tim Bain]

Was that error happening when you first saw the behavior you first asked
about? Are you saying that these are related, or that they're two unrelated
issues? I can't see anything obvious about this exception that I would
expect to result in the behavior you saw in your first post, so my starting
assumption is that the two are unrelated.

Tim

On Thu, Mar 8, 2018 at 9:58 PM, Rajesh Malla  wrote:

> following error messages we are seeing on client side :
> 2018-03-08 18:38:24,248 41319597 [Camel (jcsCoreCamelContext) thread #12 -
> JmsConsumer[uniquequename]]
> (org.apache.activemq.activemq-osgi:org.apache.activemq.jms.
> pool.PooledSession:126)
> WARN   - Caught exception trying close() when putting session back into the
> pool, will invalidate. javax.jms.JMSException: Cannot send, channel has
> already failed: https://URL
> javax.jms.JMSException: Cannot send, channel has already failed:
> https://URL
> at
> org.apache.activemq.util.JMSExceptionSupport.create(
> JMSExceptionSupport.java:72)[120:org.apache.activemq.activemq-osgi:5.12.3]
> at
> org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(
> ActiveMQConnection.java:1314)[120:org.apache.activemq.
> activemq-osgi:5.12.3]
> at
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(
> ActiveMQConnection.java:1306)[120:org.apache.activemq.
> activemq-osgi:5.12.3]
> at
> org.apache.activemq.ActiveMQSession.asyncSendPacket(
> ActiveMQSession.java:2074)[120:org.apache.activemq.activemq-osgi:5.12.3]
> at
> org.apache.activemq.ActiveMQMessageConsumer.doClose(
> ActiveMQMessageConsumer.java:728)[120:org.apache.activemq.
> activemq-osgi:5.12.3]
> at
> org.apache.activemq.ActiveMQMessageConsumer.close(
> ActiveMQMessageConsumer.java:715)[120:org.apache.activemq.
> activemq-osgi:5.12.3]
> at
> org.apache.activemq.jms.pool.PooledSession.close(
> PooledSession.java:108)[120:org.apache.activemq.activemq-osgi:5.12.3]
> at
> org.apache.activemq.jms.pool.PooledConnection.cleanupAllLoanedSessions(
> PooledConnection.java:257)[120:org.apache.activemq.activemq-osgi:5.12.3]
> at
> org.apache.activemq.jms.pool.PooledConnection.close(
> PooledConnection.java:85)[120:org.apache.activemq.activemq-osgi:5.12.3]
> at
> org.springframework.jms.connection.ConnectionFactoryUtils.
> releaseConnection(ConnectionFactoryUtils.java:
> 80)[140:org.apache.servicemix.bundles.spring-jms:3.2.14.RELEASE_1]
> at
> org.springframework.jms.listener.AbstractJmsListeningContainer.
> refreshSharedConnection(AbstractJmsListeningContainer.
> java:387)[140:org.apache.servicemix.bundles.spring-jms:3.2.14.RELEASE_1]
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer.
> refreshConnectionUntilSuccessful(DefaultMessageListenerContaine
> r.java:887)[140:org.apache.servicemix.bundles.spring-jms:3.2.14.RELEASE_1]
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer.
> recoverAfterListenerSetupFailure(DefaultMessageListenerContaine
> r.java:863)[140:org.apache.servicemix.bundles.spring-jms:3.2.14.RELEASE_1]
> at
> org.springframework.jms.listener.DefaultMessageListenerContaine
> r$AsyncMessageListenerInvoker.run(DefaultMessageListenerContaine
> r.java:1014)[140:org.apache.servicemix.bundles.spring-jms:
> 3.2.14.RELEASE_1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
> Source)[:1.8.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)[:1.8.0_60]
> at java.lang.Thread.run(Unknown Source)[:1.8.0_60]
> Caused by: org.apache.activemq.transport.InactivityIOException: Cannot
> send,
> channel has already failed: https://URL
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.doOnewaySend(
> AbstractInactivityMonitor.java:333)[120:org.apache.
> activemq.activemq-osgi:5.12.3]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.oneway(
> AbstractInactivityMonitor.java:322)[120:org.apache.
> activemq.activemq-osgi:5.12.3]
> at
> org.apache.activemq.transport.MutexTransport.oneway(
> MutexTransport.java:68)[120:org.apache.activemq.activemq-osgi:5.12.3]
> at
> org.apache.activemq.transport.ResponseCorrelator.oneway(
> ResponseCorrelator.java:60)[120:org.apache.activemq.activemq-osgi:5.12.3]
> at
> org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(
> ActiveMQConnection.java:1312)[120:org.apache.activemq.
> activemq-osgi:5.12.3]
> ... 15 more
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>

Re: Camel generating message with correlationid=null and tmp-queue null

[Rajesh Malla]

following error messages we are seeing on client side :
2018-03-08 18:38:24,248 41319597 [Camel (jcsCoreCamelContext) thread #12 -
JmsConsumer[uniquequename]]
(org.apache.activemq.activemq-osgi:org.apache.activemq.jms.pool.PooledSession:126)
WARN   - Caught exception trying close() when putting session back into the
pool, will invalidate. javax.jms.JMSException: Cannot send, channel has
already failed: https://URL
javax.jms.JMSException: Cannot send, channel has already failed: https://URL
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1314)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1306)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:2074)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.ActiveMQMessageConsumer.doClose(ActiveMQMessageConsumer.java:728)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.ActiveMQMessageConsumer.close(ActiveMQMessageConsumer.java:715)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.jms.pool.PooledSession.close(PooledSession.java:108)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.jms.pool.PooledConnection.cleanupAllLoanedSessions(PooledConnection.java:257)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.jms.pool.PooledConnection.close(PooledConnection.java:85)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.springframework.jms.connection.ConnectionFactoryUtils.releaseConnection(ConnectionFactoryUtils.java:80)[140:org.apache.servicemix.bundles.spring-jms:3.2.14.RELEASE_1]
at
org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:387)[140:org.apache.servicemix.bundles.spring-jms:3.2.14.RELEASE_1]
at
org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:887)[140:org.apache.servicemix.bundles.spring-jms:3.2.14.RELEASE_1]
at
org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:863)[140:org.apache.servicemix.bundles.spring-jms:3.2.14.RELEASE_1]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1014)[140:org.apache.servicemix.bundles.spring-jms:3.2.14.RELEASE_1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
Source)[:1.8.0_60]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
Source)[:1.8.0_60]
at java.lang.Thread.run(Unknown Source)[:1.8.0_60]
Caused by: org.apache.activemq.transport.InactivityIOException: Cannot send,
channel has already failed: https://URL
at
org.apache.activemq.transport.AbstractInactivityMonitor.doOnewaySend(AbstractInactivityMonitor.java:333)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.transport.AbstractInactivityMonitor.oneway(AbstractInactivityMonitor.java:322)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)[120:org.apache.activemq.activemq-osgi:5.12.3]
at
org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1312)[120:org.apache.activemq.activemq-osgi:5.12.3]
... 15 more



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Camel generating message with correlationid=null and tmp-queue null

[Tim Bain]

I'll start with the bad news. From what you've written, it could be either
product (Camel or ActiveMQ) that's causing the problem, and the people that
support the two products are both likely to initially assume it's the other
product's doing. So one of the best things you can do is to figure out
which product the problem is occurring in, so you can get the right people
involved in troubleshooting what's going on.

To that end, one thing you could do is try cycling the ActiveMQ Broker and
seeing whether the problem continues. Then wait for the problem to happen
again, and cycle the Camel producer and see whether the problem continues.
If cycling one product stops the problem from happening for a while and
cycling the other has no effect, then the problem is almost certainly in
the one that's fixed by cycling. If the behavior is the same no matter
which you cycle, then you'll have to look for another way to determine
where the problem lies.

I'd also suggest turning on TRACE logging in both products to see if you
can see a log dump of each message that's sent by Camel and received by the
broker. If you can find a log line that's close to the sending of the
message, and it shows that the message is correct at the time it crosses
the wire to the broker, then the problem is likely in ActiveMQ; if it's
already incorrect by the time it goes across the wire, then it's likely a
Camel problem.

Can you reproduce this problem reliably (even if it takes a few hours)? Or
was this a one-time fluke that you've never seen happen again?

Tim

P.S. I also notice that the expiration is 0 in the message that's not
right, whereas it's got a non-zero value for the correct message.

On Thu, Mar 8, 2018 at 9:11 PM, Rajesh Malla  wrote:

>
> we are using activemq : 5.12.3
> apache camel : 2.16.2
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>

Re: Camel generating message with correlationid=null and tmp-queue null

[Rajesh Malla]

we are using activemq : 5.12.3 
apache camel : 2.16.2




--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: ERROR: javax.jms.InvalidSelectorException: (“JMSMessageID=

[Tim Bain]

Based on the error message in your original email, you appear to be using
Unicode pretty-print quote characters:

Lexical error at line
1, column 2.  Encountered: "\u201c" (8220), after : ""

On Mar 8, 2018 7:00 PM, "dhanasekar"  wrote:

> Hi,
>
> Yes, I tried removed ID: string in the message id as well.
>
> I found the 'root cause', still didn't find the solution.
>
> *Root cause:*
>
> ID:Dhanasekars-iMac.local-54880-1520061026486-1:1:1:1:1
>
> JMSMessageID is not accepting : and -, if I remove these 2 special
> character
> , Not getting error any more, but thats not correct message ID :)
>
> I tried various quotes option, but no luck.
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>

Re: It costs time when stopping ActiveMQ

[t-watana]

Thanks for reply.

I haven't investgate JVM yet.
I'm using AMQ as follows conditions, is there a factor that is likely to
take time?

Conditions: 
* Using MQTT (QoS=2) 
* MQTT Client is Eclipse Paho 1.0.0 
* Subscriber's CleanSession is false. 
* Number of Subscribers is 1 over. 
* Number of Topics is 1 over. 







--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: ERROR: javax.jms.InvalidSelectorException: (“JMSMessageID=

[dhanasekar]

Hi,

Yes, I tried removed ID: string in the message id as well.

I found the 'root cause', still didn't find the solution.

*Root cause:*

ID:Dhanasekars-iMac.local-54880-1520061026486-1:1:1:1:1

JMSMessageID is not accepting : and -, if I remove these 2 special character
, Not getting error any more, but thats not correct message ID :)

I tried various quotes option, but no luck.



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Camel generating message with correlationid=null and tmp-queue null

[Rajesh Malla]

Hi

we are using mesh n/w connectors A,B,C. and we have two consumers. upto some
hours system is working fine, after that when we are checking messages those
are generated by camel with correlationId as null

ActiveMQObjectMessage {commandId = 4, responseRequired = true, messageId =
ID:asdf-55403-1520511160238-20:1:1:1:1, originalDestination = null,
originalTransactionId = null, producerId =
ID:asdf-55403-1520511160238-20:1:1:1, destination = queue://uniquequeuename,
transactionId = null, expiration = 0, timestamp = 1520552897962, arrival =
0, brokerInTime = 1520552897962, brokerOutTime = 1520553651034,
correlationId = null, replyTo = null, persistent = true, type = null,
priority = 4, groupID = null, groupSequence = 0, targetConsumerId = null,
compressed = false, userID = admin, content =
org.apache.activemq.util.ByteSequence@6fa51cd4, marshalledProperties =
org.apache.activemq.util.ByteSequence@2767e23c, dataStructure = null,
redeliveryCounter = 0, size = 1607, properties =
{CamelAuthentication_Bytes=rO0ABXQAD2FkbWluCUFETUlOCUFMTA==,
breadcrumbId=ID-asdf-55404-1520511167186-2-14}, readOnlyProperties = true,
readOnlyBody = true, droppable = false, jmsXGroupFirstForConsumer = false}

and replyTo also become null. because of this, consumer is receiving [ from
test client ] and not able to respond to that message. 

upto some hours it is working properly, but this is happening after few
hours. Is this the problem with Camel ? activemq configuration please
suggest.
original message :

ActiveMQObjectMessage {commandId = 40, responseRequired = true, messageId =
ID:asdf-58894-1520512195342-12:1:10:1:57, originalDestination = null,
originalTransactionId = null, producerId =
new-broker->new-broker-58894-1520512195342-20:2:1:1, destination =
queue://uniquequeuename, transactionId = null, expiration = 1520555745459,
timestamp = 1520555685459, arrival = 0, brokerInTime = 1520555685462,
brokerOutTime = 1520555734467, correlationId =
Camel-ID-asdf-41356-1520512199669-2-203, replyTo =
temp-queue://ID:asdf-58894-1520512195342-12:1:2, persistent = true, type =
null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId =
null, compressed = false, userID = admin, content =
org.apache.activemq.util.ByteSequence@cc43f62, marshalledProperties =
org.apache.activemq.util.ByteSequence@5b218417, dataStructure = null,
redeliveryCounter = 0, size = 1488, properties =
{CamelAuthentication_Bytes=rO0ABXQAD2FkbWluCUFETUlOCUFMTA==,
breadcrumbId=ID-asdf-41356-1520512199669-2-201}, readOnlyProperties = true,
readOnlyBody = true, droppable = false, jmsXGroupFirstForConsumer = false}

Please help us.






--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

testRecoveryOnArchiveFailure failing test

[angelo.rlcosta]

Hello all,

I have just downloaded activemq-activemq-5.15.3 version of activemq and
trying to build the source code by running mvn clean install.

Problem is that there is a failing test:

testRecoveryOnArchiveFailure(org.apache.activemq.store.kahadb.JournalArchiveTest)
 
Time elapsed: 2.934 sec  <<< FAILURE!
java.lang.AssertionError: Failed to restart after failure to archive
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.activemq.store.kahadb.JournalArchiveTest.testRecoveryOnArchiveFailure(JournalArchiveTest.java:168)


testRecoveryOnArchiveFailure(org.apache.activemq.store.kahadb.JournalArchiveTest)
 
Time elapsed: 2.936 sec  <<< ERROR!

The process cannot access the file because it is being used by another
process.

at 
org.apache.activemq.util.IOHelper.moveFile(IOHelper.java:200)
at
org.apache.activemq.store.kahadb.disk.journal.DataFile.move(DataFile.java:107)

Not sure what i need to do in my environment to have this test pass.

Regards,
Ângelo Costa




--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Migratiion of Queue data from HornetQ to Artemis 2.x

[Clebert Suconic]

If this was fixed in 2.5 it will be closed as a non issue.  We can’t go
back in time and fix 2.4 ;)


Saying the obvious.  But I am now confused if this is an issue in 2.5 or
not.

On Thu, Mar 8, 2018 at 12:06 AM dharmendra  wrote:

> hi Clebert,
> Thanks for response . I am using Artemis 2.4.0 as we are going with this
> version in production so we didn't try on 2.5.0 . As you suggested i have
> raised JIRA for the same with broker.xml as well and all detail.
> If you need any more information then please let me know.
> JIRA id is : https://issues.apache.org/jira/browse/ARTEMIS-1735
> Thanks !
>
> -Dharmendra
>
>
>
> -
> DKumar
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
-- 
Clebert Suconic

RE: Artemis 2.4.0 - Issues with memory leaks and JMS message redistribution

[Ilkka Virolainen]

An update: the errors were caused by a peculiarity in our environment. Anyway, 
looking at the nature of the changes between builds it is somewhat obvious this 
issue couldn't have been caused by the related commits. So far I've been unable 
to replicate the original issue, being the cluster connection dying to a 
concurrentmodificationexception so I remain optimistic.

Thank you!

Best regards,
- Ilkka

-Original Message-
From: Ilkka Virolainen [mailto:ilkka.virolai...@bitwise.fi] 
Sent: 8. maaliskuuta 2018 10:29
To: users@activemq.apache.org
Subject: RE: Artemis 2.4.0 - Issues with memory leaks and JMS message 
redistribution

Trying out master results in weird issues:

Broker A logs a very large amount of this:

10:06:37,292 ERROR [org.apache.activemq.artemis.core.client] AMQ214031: Failed 
to decode buffer, disconnect immediately.: java.lang.IllegalStateException: 
java.lang.IllegalArgumentException: AMQ119032: Invalid type: 1
at 
org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:378)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingBufferHandler.bufferReceived(ClientSessionFactoryImpl.java:1144)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:806)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:404) 
[netty-all-4.1.22.Final.jar:4.1.22.Final]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:304) 
[netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
 [artemis-commons-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
Caused by: java.lang.IllegalArgumentException: AMQ119032: Invalid type: 1
at 
org.apache.activemq.artemis.core.protocol.core.impl.PacketDecoder.decode(PacketDecoder.java:455)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.protocol.ClientPacketDecoder.decode(ClientPacketDecoder.java:67)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.protocol.ServerPacketDecoder.slowPathDecode(ServerPacketDecoder.java:253)
 [artemis-server-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.protocol.ServerPacketDecoder.decode(ServerPacketDecoder.java:133)
 [artemis-server-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 

RE: Artemis 2.4.0 - Issues with memory leaks and JMS message redistribution

[Ilkka Virolainen]

Trying out master results in weird issues:

Broker A logs a very large amount of this:

10:06:37,292 ERROR [org.apache.activemq.artemis.core.client] AMQ214031: Failed 
to decode buffer, disconnect immediately.: java.lang.IllegalStateException: 
java.lang.IllegalArgumentException: AMQ119032: Invalid type: 1
at 
org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:378)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingBufferHandler.bufferReceived(ClientSessionFactoryImpl.java:1144)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:806)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:404) 
[netty-all-4.1.22.Final.jar:4.1.22.Final]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:304) 
[netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886)
 [netty-all-4.1.22.Final.jar:4.1.22.Final]
at 
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
 [artemis-commons-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
Caused by: java.lang.IllegalArgumentException: AMQ119032: Invalid type: 1
at 
org.apache.activemq.artemis.core.protocol.core.impl.PacketDecoder.decode(PacketDecoder.java:455)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.protocol.ClientPacketDecoder.decode(ClientPacketDecoder.java:67)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.protocol.ServerPacketDecoder.slowPathDecode(ServerPacketDecoder.java:253)
 [artemis-server-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.protocol.ServerPacketDecoder.decode(ServerPacketDecoder.java:133)
 [artemis-server-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:365)
 [artemis-core-client-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
... 19 more


Broker B logs this once (note, no other process listens to addresses defined in 
its acceptors:

10:15:17,703 ERROR [org.apache.activemq.artemis.core.server] AMQ224000: Failure 
in initialisation: io.netty.channel.unix.Errors$NativeIoException: bind(..) 
failed: Address already in use
at io.netty.channel.unix.Errors.newIOException(Errors.java:122) 
[netty-all-4.1.22.Final.jar:4.1.22.Final]
at io.netty.channel.unix.Socket.bind(Socket.java:287) 
[netty-all-4.1.22.Final.jar:4.1.22.Final]
at