[ https://issues.apache.org/jira/browse/ARTEMIS-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruben Cala updated ARTEMIS-689: ------------------------------- Description: artemis.log message: WARN [org.apache.activemq.artemis.core.server] Sending unexpected exception to client: java.lang.NullPointerException at org.apache.activemq.artemis.core.postoffice.impl.WildcardAddressManager.addBinding(WildcardAddressManager.java:101) [artemis-server-1.1.0-jar:1.1.0] This happened after several successful calls to createTemporaryQueue() using the same address, using a test client running in Eclipse to consume messages. The address used has no wildcards. When the broker is in this state, I noticed in JConsole that the Address entry for it remains with failed queue names in the QueueNames and BindingNames attributes, yet there are no Queue entries for them. When I delete the queues (using JConsole), the Address entry goes away, and the createTemporaryQueue() call works again. Also, when in this state, the createTemporaryQueue() call works using a wildcard address. I suspect that running the test client in Eclipse is preventing a clean connection break from the broker, which is causing the broker to not clean up the queue/address from the test client correctly. was: artemis.log message: WARN [org.apache.activemq.artemis.core.server] Sending unexpected exception to client: java.lang.NullPointerException at org.apache.activemq.artemis.core.postoffice.impl.WildcardAddressManager.addBinding(WildcardAddressManager.java:101) [artemis-server-1.1.0-jar:1.1.0] This happened after several successful calls to createTemporaryQueue() using the same address, using a test client running in Eclipse to consume messages. The address used has no wildcards. When the broker is in this state, I noticed in JConsole that the Address entry for it remains with failed queue names in the QueueNames and BindingNames attributes, yet there are no Queue entries for them. When I delete the queues (using JConsole), the Address entry goes away, and the createTemporaryQueue() call works again. I suspect that running the test client in Eclipse is preventing a clean connection break from the broker, which is causing the broker to not clean up the queue/address from the test client correctly. > INTERNAL_ERROR reported on ClientSession createTemporaryQueue() > --------------------------------------------------------------- > > Key: ARTEMIS-689 > URL: https://issues.apache.org/jira/browse/ARTEMIS-689 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker > Affects Versions: 1.1.0 > Environment: Redhat Linux running on VM in Amazon Cloud > Reporter: Ruben Cala > > artemis.log message: > WARN [org.apache.activemq.artemis.core.server] Sending unexpected exception > to client: java.lang.NullPointerException > at > org.apache.activemq.artemis.core.postoffice.impl.WildcardAddressManager.addBinding(WildcardAddressManager.java:101) > [artemis-server-1.1.0-jar:1.1.0] > This happened after several successful calls to createTemporaryQueue() using > the same address, using a test client running in Eclipse to consume messages. > The address used has no wildcards. > When the broker is in this state, I noticed in JConsole that the Address > entry for it remains with failed queue names in the QueueNames and > BindingNames attributes, yet there are no Queue entries for them. When I > delete the queues (using JConsole), the Address entry goes away, and the > createTemporaryQueue() call works again. > Also, when in this state, the createTemporaryQueue() call works using a > wildcard address. > I suspect that running the test client in Eclipse is preventing a clean > connection break from the broker, which is causing the broker to not clean up > the queue/address from the test client correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)