You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/06/13 16:53:00 UTC

[jira] [Work logged] (ARTEMIS-2803) NPE when trying to configure clustering

     [ https://issues.apache.org/jira/browse/ARTEMIS-2803?focusedWorklogId=445383&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-445383 ]

ASF GitHub Bot logged work on ARTEMIS-2803:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Jun/20 16:52
            Start Date: 13/Jun/20 16:52
    Worklog Time Spent: 10m 
      Work Description: jbertram opened a new pull request #3182:
URL: https://github.com/apache/activemq-artemis/pull/3182


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 445383)
    Remaining Estimate: 0h
            Time Spent: 10m

> NPE when trying to configure clustering
> ---------------------------------------
>
>                 Key: ARTEMIS-2803
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2803
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.13.0
>            Reporter: Alexander Trauzzi
>            Assignee: Justin Bertram
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> I've encountered an exception during a bit of exploratory/PoC work I'm doing around clustering.
> I'm making this report mostly on the basis that I haven't been able to infer any cause or course of action from the exception messages. Even if this is a result of a misconfiguration, perhaps the feedback can be improved to make it easier to troubleshoot?
> I have already collated the details over at a question of Stack Overflow, which I've also attached as an external issue URL. 
> Here's the config of broker A:
> {code:xml}
> <?xml version='1.0'?>
> <configuration xmlns="urn:activemq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xi="http://www.w3.org/2001/XInclude" xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd">
>     <core xmlns="urn:activemq:core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:activemq:core ">
>         <name>0.0.0.0</name>
>         <persistence-enabled>true</persistence-enabled>
>         <!-- this could be ASYNCIO, MAPPED, NIO
>             ASYNCIO: Linux Libaio
>             MAPPED: mmap files
>             NIO: Plain Java Files
>         -->
>         <journal-type>ASYNCIO</journal-type>
>         <paging-directory>data/paging</paging-directory>
>         <bindings-directory>data/bindings</bindings-directory>
>         <journal-directory>data/journal</journal-directory>
>         <large-messages-directory>data/large-messages</large-messages-directory>
>         <journal-datasync>true</journal-datasync>
>         <journal-min-files>2</journal-min-files>
>         <journal-pool-files>10</journal-pool-files>
>         <journal-device-block-size>4096</journal-device-block-size>
>         <journal-file-size>10M</journal-file-size>
>         <!--
>         This value was determined through a calculation.
>         Your system could perform 50 writes per millisecond
>         on the current journal configuration.
>         That translates as a sync write every 20000 nanoseconds.
>         Note: If you specify 0 the system will perform writes directly to the disk.
>                 We recommend this to be 0 if you are using journalType=MAPPED and journal-datasync=false.
>         -->
>         <journal-buffer-timeout>20000</journal-buffer-timeout>
>         <!--
>         When using ASYNCIO, this will determine the writing queue depth for libaio.
>         -->
>         <journal-max-io>4096</journal-max-io>
>         <!--
>         You can verify the network health of a particular NIC by specifying the <network-check-NIC> element.
>             <network-check-NIC>theNicName</network-check-NIC>
>         -->
>         <!--
>         Use this to use an HTTP server to validate the network
>             <network-check-URL-list>http://www.apache.org</network-check-URL-list> -->
>         <!-- <network-check-period>10000</network-check-period> -->
>         <!-- <network-check-timeout>1000</network-check-timeout> -->
>         <!-- this is a comma separated list, no spaces, just DNS or IPs
>             it should accept IPV6
>             Warning: Make sure you understand your network topology as this is meant to validate if your network is valid.
>                     Using IPs that could eventually disappear or be partially visible may defeat the purpose.
>                     You can use a list of multiple IPs, and if any successful ping will make the server OK to continue running -->
>         <!-- <network-check-list>10.0.0.1</network-check-list> -->
>         <!-- use this to customize the ping used for ipv4 addresses -->
>         <!-- <network-check-ping-command>ping -c 1 -t %d %s</network-check-ping-command> -->
>         <!-- use this to customize the ping used for ipv6 addresses -->
>         <!-- <network-check-ping6-command>ping6 -c 1 %2$s</network-check-ping6-command> -->
>         <!-- how often we are looking for how many bytes are being used on the disk in ms -->
>         <disk-scan-period>5000</disk-scan-period>
>         <!-- once the disk hits this limit the system will block, or close the connection in certain protocols
>             that won't support flow control. -->
>         <max-disk-usage>90</max-disk-usage>
>         <!-- should the broker detect dead locks and other issues -->
>         <critical-analyzer>true</critical-analyzer>
>         <critical-analyzer-timeout>120000</critical-analyzer-timeout>
>         <critical-analyzer-check-period>60000</critical-analyzer-check-period>
>         <critical-analyzer-policy>HALT</critical-analyzer-policy>
>         <page-sync-timeout>1020000</page-sync-timeout>
>         <acceptors>
>             <!-- Acceptor for every supported protocol -->
>             <acceptor name="artemis">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true</acceptor>
>             <!-- STOMP Acceptor. -->
>             <acceptor name="stomp">tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true</acceptor>
>         </acceptors>
>         <cluster-user>cluster</cluster-user>
>         <cluster-password>REDACTED</cluster-password>
>         <addresses>
>             <address name="/queue/global.regional">
>                 <multicast>
>                     <queue name="/queue/global.regional">
>                         <durable>true</durable>
>                     </queue>
>                 </multicast>
>             </address>
>         </addresses>
>         <address-settings>
>             <!-- if you define auto-create on certain queues, management has to be auto-create -->
>             <address-setting match="activemq.management#">
>             <dead-letter-address>DLQ</dead-letter-address>
>             <expiry-address>ExpiryQueue</expiry-address>
>             <redelivery-delay>0</redelivery-delay>
>             <!-- with -1 only the global-max-size is in use for limiting -->
>             <max-size-bytes>-1</max-size-bytes>
>             <message-counter-history-day-limit>10</message-counter-history-day-limit>
>             <address-full-policy>PAGE</address-full-policy>
>             <auto-create-queues>true</auto-create-queues>
>             <auto-create-addresses>true</auto-create-addresses>
>             <auto-create-jms-queues>true</auto-create-jms-queues>
>             <auto-create-jms-topics>true</auto-create-jms-topics>
>             </address-setting>
>             <!--default for catch all-->
>             <address-setting match="#">
>                 <!-- <dead-letter-address>DLQ</dead-letter-address>
>                 <expiry-address>ExpiryQueue</expiry-address>
>                 <redelivery-delay>0</redelivery-delay> -->
>                 <!-- with -1 only the global-max-size is in use for limiting -->
>                 <!-- <max-size-bytes>-1</max-size-bytes>
>                 <message-counter-history-day-limit>10</message-counter-history-day-limit>
>                 <address-full-policy>PAGE</address-full-policy>
>                 <auto-create-queues>true</auto-create-queues>
>                 <auto-create-addresses>true</auto-create-addresses>
>                 <auto-create-jms-queues>true</auto-create-jms-queues>
>                 <auto-create-jms-topics>true</auto-create-jms-topics> -->
>             </address-setting>
>         </address-settings>
>         <security-settings>
>             <security-setting match="#">
>             <permission type="createNonDurableQueue" roles="amq"/>
>             <permission type="deleteNonDurableQueue" roles="amq"/>
>             <permission type="createDurableQueue" roles="amq"/>
>             <permission type="deleteDurableQueue" roles="amq"/>
>             <permission type="createAddress" roles="amq"/>
>             <permission type="deleteAddress" roles="amq"/>
>             <permission type="consume" roles="amq"/>
>             <permission type="browse" roles="amq"/>
>             <permission type="send" roles="amq"/>
>             <!-- we need this otherwise ./artemis data imp wouldn't work -->
>             <permission type="manage" roles="amq"/>
>             </security-setting>
>         </security-settings>
>     </core>
> </configuration>
> {code}
> Here's the config of broker B:
> {code:xml}
> <?xml version='1.0'?>
> <configuration xmlns="urn:activemq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xi="http://www.w3.org/2001/XInclude" xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd">
>     <core xmlns="urn:activemq:core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:activemq:core ">
>         <name>0.0.0.0</name>
>         <persistence-enabled>true</persistence-enabled>
>         <!-- this could be ASYNCIO, MAPPED, NIO
>             ASYNCIO: Linux Libaio
>             MAPPED: mmap files
>             NIO: Plain Java Files
>         -->
>         <journal-type>ASYNCIO</journal-type>
>         <paging-directory>data/paging</paging-directory>
>         <bindings-directory>data/bindings</bindings-directory>
>         <journal-directory>data/journal</journal-directory>
>         <large-messages-directory>data/large-messages</large-messages-directory>
>         <journal-datasync>true</journal-datasync>
>         <journal-min-files>2</journal-min-files>
>         <journal-pool-files>10</journal-pool-files>
>         <journal-device-block-size>4096</journal-device-block-size>
>         <journal-file-size>10M</journal-file-size>
>         <!--
>         This value was determined through a calculation.
>         Your system could perform 50 writes per millisecond
>         on the current journal configuration.
>         That translates as a sync write every 20000 nanoseconds.
>         Note: If you specify 0 the system will perform writes directly to the disk.
>                 We recommend this to be 0 if you are using journalType=MAPPED and journal-datasync=false.
>         -->
>         <journal-buffer-timeout>20000</journal-buffer-timeout>
>         <!--
>         When using ASYNCIO, this will determine the writing queue depth for libaio.
>         -->
>         <journal-max-io>4096</journal-max-io>
>         <!--
>         You can verify the network health of a particular NIC by specifying the <network-check-NIC> element.
>             <network-check-NIC>theNicName</network-check-NIC>
>         -->
>         <!--
>         Use this to use an HTTP server to validate the network
>             <network-check-URL-list>http://www.apache.org</network-check-URL-list> -->
>         <!-- <network-check-period>10000</network-check-period> -->
>         <!-- <network-check-timeout>1000</network-check-timeout> -->
>         <!-- this is a comma separated list, no spaces, just DNS or IPs
>             it should accept IPV6
>             Warning: Make sure you understand your network topology as this is meant to validate if your network is valid.
>                     Using IPs that could eventually disappear or be partially visible may defeat the purpose.
>                     You can use a list of multiple IPs, and if any successful ping will make the server OK to continue running -->
>         <!-- <network-check-list>10.0.0.1</network-check-list> -->
>         <!-- use this to customize the ping used for ipv4 addresses -->
>         <!-- <network-check-ping-command>ping -c 1 -t %d %s</network-check-ping-command> -->
>         <!-- use this to customize the ping used for ipv6 addresses -->
>         <!-- <network-check-ping6-command>ping6 -c 1 %2$s</network-check-ping6-command> -->
>         <!-- how often we are looking for how many bytes are being used on the disk in ms -->
>         <disk-scan-period>5000</disk-scan-period>
>         <!-- once the disk hits this limit the system will block, or close the connection in certain protocols
>             that won't support flow control. -->
>         <max-disk-usage>90</max-disk-usage>
>         <!-- should the broker detect dead locks and other issues -->
>         <critical-analyzer>true</critical-analyzer>
>         <critical-analyzer-timeout>120000</critical-analyzer-timeout>
>         <critical-analyzer-check-period>60000</critical-analyzer-check-period>
>         <critical-analyzer-policy>HALT</critical-analyzer-policy>
>         <page-sync-timeout>1020000</page-sync-timeout>
>         <acceptors>
>             <acceptor name="stomp">tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true</acceptor>
>         </acceptors>
>         <connectors>
>             <connector name="global">tcp://172.17.0.1:61616</connector>
>         </connectors>
>         <cluster-user>cluster</cluster-user>
>         <cluster-password>REDACTED</cluster-password>
>         <cluster-connections>
>             <cluster-connection name="global">
>                 <address>/queue/global.regional</address>
>                 <connector-ref>global</connector-ref>
>                 <forward-when-no-consumers>false</forward-when-no-consumers>
>                 <static-connectors allow-direct-connections-only="true">
>                     <connector-ref>global</connector-ref>
>                 </static-connectors>
>             </cluster-connection>
>         </cluster-connections>
>         <addresses>
>         </addresses>
>         <address-settings>
>             <address-setting match="/queue/global.regional">
>                 <redistribution-delay>0</redistribution-delay>
>             </address-setting>
>             <!-- if you define auto-create on certain queues, management has to be auto-create -->
>             <address-setting match="activemq.management#">
>                 <dead-letter-address>DLQ</dead-letter-address>
>                 <expiry-address>ExpiryQueue</expiry-address>
>                 <redelivery-delay>0</redelivery-delay>
>                 <!-- with -1 only the global-max-size is in use for limiting -->
>                 <max-size-bytes>-1</max-size-bytes>
>                 <message-counter-history-day-limit>10</message-counter-history-day-limit>
>                 <address-full-policy>PAGE</address-full-policy>
>                 <auto-create-queues>true</auto-create-queues>
>                 <auto-create-addresses>true</auto-create-addresses>
>                 <auto-create-jms-queues>true</auto-create-jms-queues>
>                 <auto-create-jms-topics>true</auto-create-jms-topics>
>             </address-setting>
>             <!--default for catch all-->
>             <address-setting match="#">
>                 <!-- <dead-letter-address>DLQ</dead-letter-address>
>                 <expiry-address>ExpiryQueue</expiry-address>
>                 <redelivery-delay>0</redelivery-delay> -->
>                 <!-- with -1 only the global-max-size is in use for limiting -->
>                 <!-- <max-size-bytes>-1</max-size-bytes>
>                 <message-counter-history-day-limit>10</message-counter-history-day-limit>
>                 <address-full-policy>PAGE</address-full-policy>
>                 <auto-create-queues>true</auto-create-queues>
>                 <auto-create-addresses>true</auto-create-addresses>
>                 <auto-create-jms-queues>true</auto-create-jms-queues>
>                 <auto-create-jms-topics>true</auto-create-jms-topics> -->
>             </address-setting>
>         </address-settings>
>         <security-settings>
>             <security-setting match="#">
>             <permission type="createNonDurableQueue" roles="amq"/>
>             <permission type="deleteNonDurableQueue" roles="amq"/>
>             <permission type="createDurableQueue" roles="amq"/>
>             <permission type="deleteDurableQueue" roles="amq"/>
>             <permission type="createAddress" roles="amq"/>
>             <permission type="deleteAddress" roles="amq"/>
>             <permission type="consume" roles="amq"/>
>             <permission type="browse" roles="amq"/>
>             <permission type="send" roles="amq"/>
>             <!-- we need this otherwise ./artemis data imp wouldn't work -->
>             <permission type="manage" roles="amq"/>
>             </security-setting>
>         </security-settings>
>     </core>
> </configuration>
> {code}
> Following are the two exception messages I'm getting from the broker I'm trying to _connect to_:
> {noformat}
> 2020-06-12 14:08:00,524 ERROR [org.apache.activemq.artemis.core.client] AMQ214013: Failed to decode packet: java.lang.NullPointerException
>     at org.apache.activemq.artemis.core.server.cluster.ClusterController$ClusterControllerChannelHandler.handlePacket(ClusterController.java:364) [artemis-server-2.13.0.jar:2.13.0]
>     at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:720) [artemis-core-client-2.13.0.jar:2.13.0]
>     at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:408) [artemis-core-client-2.13.0.jar:2.13.0]
>     at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:385) [artemis-core-client-2.13.0.jar:2.13.0]
>     at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:667) [artemis-server-2.13.0.jar:2.13.0]
>     at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73) [artemis-core-client-2.13.0.jar:2.13.0]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:321) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:295) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.handlerRemoved(ByteToMessageDecoder.java:253) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:505) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:437) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.channelRead(ProtocolHandler.java:142) [artemis-server-2.13.0.jar:2.13.0]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:792) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:475) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:378) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118) [artemis-commons-2.13.0.jar:2.13.0]
> 2020-06-12 14:08:00,525 WARN  [org.apache.activemq.artemis.core.server] AMQ222218: Server disconnecting: Error decoding buffer: java.lang.IllegalStateException: java.lang.NullPointerException
>     at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:390) [artemis-core-client-2.13.0.jar:2.13.0]
>     at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:667) [artemis-server-2.13.0.jar:2.13.0]
>     at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73) [artemis-core-client-2.13.0.jar:2.13.0]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:321) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:295) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.handlerRemoved(ByteToMessageDecoder.java:253) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:505) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:437) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.channelRead(ProtocolHandler.java:142) [artemis-server-2.13.0.jar:2.13.0]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:792) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:475) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:378) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-all-4.1.48.Final.jar:4.1.48.Final]
>     at org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118) [artemis-commons-2.13.0.jar:2.13.0]
> Caused by: java.lang.NullPointerException
>     at org.apache.activemq.artemis.core.server.cluster.ClusterController$ClusterControllerChannelHandler.handlePacket(ClusterController.java:364) [artemis-server-2.13.0.jar:2.13.0]
>     at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:720) [artemis-core-client-2.13.0.jar:2.13.0]
>     at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:408) [artemis-core-client-2.13.0.jar:2.13.0]
>     at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:385) [artemis-core-client-2.13.0.jar:2.13.0]
>     ... 28 more
> 2020-06-12 14:08:00,528 WARN  [org.apache.activemq.artemis.core.client] AMQ212037: Connection failure to /172.31.0.5:52646 has been detected: java.lang.NullPointerException [code=GENERIC_EXCEPTION]
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)