[jira] [Updated] (ARTEMIS-264) NPE from Netty at Pub Sub tests with Topics

["Glaucio Melo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Glaucio Melo updated ARTEMIS-264:
---------------------------------
    Summary: NPE from Netty at Pub Sub tests with Topics  (was: NPE from Netty at Pub Suc tests with Topics)

> NPE from Netty at Pub Sub tests with Topics
> -------------------------------------------
>
>                 Key: ARTEMIS-264
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-264
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.1.1
>            Reporter: Glaucio Melo
>
> I was performing some tests using as basis the JMeter samples at
> https://github.com/apache/activemq-artemis/tree/master/examples/perf/jmeter
> And I've got an exception message from the client consumer:
> Oct 16, 2015 6:24:12 PM org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner run
> ERROR: AMQ214000: Failed to call onMessage
> java.lang.NullPointerException
> 	at io.netty.buffer.PoolChunk.initBufWithSubpage(PoolChunk.java:381)
> 	at io.netty.buffer.PoolChunk.initBufWithSubpage(PoolChunk.java:369)
> 	at io.netty.buffer.PoolArena.allocate(PoolArena.java:194)
> 	at io.netty.buffer.PoolArena.allocate(PoolArena.java:132)
> 	at io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:271)
> 	at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:155)
> 	at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:146)
> 	at org.apache.activemq.artemis.core.remoting.impl.netty.PartialPooledByteBufAllocator.directBuffer(PartialPooledByteBufAllocator.java:91)
> 	at org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnection.createTransportBuffer(NettyConnection.java:154)
> 	at org.apache.activemq.artemis.spi.core.protocol.AbstractRemotingConnection.createTransportBuffer(AbstractRemotingConnection.java:156)
> 	at org.apache.activemq.artemis.core.protocol.core.impl.PacketImpl.encode(PacketImpl.java:267)
> 	at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.send(ChannelImpl.java:225)
> 	at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBatched(ChannelImpl.java:205)
> 	at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.sendACK(ActiveMQSessionContext.java:400)
> 	at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.acknowledge(ClientSessionImpl.java:672)
> 	at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.doAck(ClientConsumerImpl.java:1035)
> 	at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.acknowledge(ClientConsumerImpl.java:702)
> 	at org.apache.activemq.artemis.core.client.impl.ClientMessageImpl.acknowledge(ClientMessageImpl.java:96)
> 	at org.apache.activemq.artemis.core.client.impl.ClientMessageImpl.acknowledge(ClientMessageImpl.java:38)
> 	at org.apache.activemq.artemis.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:120)
> 	at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:932)
> 	at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:47)
> 	at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1045)
> 	at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:94)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> This error only happened at my tests only one time, not sure on how to reproduce it. I was looking for a similar error from netty project and I've found this link:
> https://github.com/netty/netty/issues/4198
> From the discussion at this link, it seems that the guy who reports the issue said that he was using netty incorrectly (not sure exactly what he meant about that). I'm creating this ticket because it's possible to get something similar -  by using netty library unexpectedly.
> Thanks,
> Glaucio Melo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)