HornetQ ERROR ... HQ224006: Invalid filter: confEventQueue: java.lang.NullPointerException...FilterImpl.java 152

[skionsnow]

I am trying to send an object message or a text message on a JMS Queue that I have named confEventQueue without a lot of success.  I know that there is an issue with the message, but don't know how to address that issue.  Any insights would be appreciated.

I am running under jboss-eap6.1 AS-7 using hornetq version-2.3.1.Final.  The message bindings are as follows:

INFO  [org.hornetq.core.server] (MSC service thread 1-4) HQ221001: HornetQ Server version 2.3.1.Final (Wild Hornet, 123) [fefdbea7-4e5b-11e4-90de-b1e1fa221139]

17:18:21,130 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221003: trying to deploy queue jms.queue.confEventQueue

17:18:21,139 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:jboss/jms/confEventQueue

17:18:21,140 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/confEventQueue

17:18:21,155 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/EventConnectionFactory

17:18:21,156 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

I have attached the JcmDispatcher and ConfEventProducer classes that produce the following output:

[com.tatacommunications.tp.jcm.dispatcher.ConfEventProducer] (EJB default - 1) ConfEventProducer Start

17:18:27,697 INFO  [com...tp.jcm.dispatcher.ConfEventProducer] (EJB default - 1) confEventQueue: HornetQQueue[confEventQueue]

17:18:27,736 INFO  [com....tp.jcm.dispatcher.JcmDispatcher] (EJB default - 1) JcmDispatcher Start

17:18:27,738 INFO  [com....tp.jcm.dispatcher.JcmDispatcher] (EJB default - 1) JcmDispatcher: confEvent = ConferenceId=1timestamp=11sequence =1

17:18:27,739 INFO  [com.....tp.jcm.dispatcher.JcmDispatcher] (EJB default - 1) ConferenceProducer: com.tatacommunications.tp.jcm.dispatcher.ConfEventProducer@671ea673

17:18:27,752 INFO  [com....tp.jcm.dispatcher.JcmDispatcher] (EJB default - 1) JcmDispatcher Sending message: HornetQMessage[ID:fa14c52a-50c2-11e4-89ba-350a65b3679c]:PERSISTENT ConferenceId=1timestamp=11sequence =1

ERROR [org.hornetq.core.server] (Thread-3 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=fefdbea7-4e5b-11e4-90de-b1e1fa221139-849027611-1725707409)) HQ224006: Invalid filter: confEventQueue: java.lang.NullPointerException

  at org.hornetq.core.filter.impl.FilterImpl.match(FilterImpl.java:152) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.postoffice.impl.BindingsImpl.getNextBinding(BindingsImpl.java:366) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.postoffice.impl.BindingsImpl.route(BindingsImpl.java:299) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.postoffice.impl.PostOfficeImpl.route(PostOfficeImpl.java:633) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.postoffice.impl.PostOfficeImpl.route(PostOfficeImpl.java:593) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.server.impl.ServerSessionImpl.doSend(ServerSessionImpl.java:1590) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:1278) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:445) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]

  at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]

[jbertram]

The error looks to be with the filter itself, but you haven't specified any details about the actual filter.  What filter are you using?

[jbertram]

I see now.  The ERROR message specifies the filter as "confEventQueue" which is indeed invalid.  Where/how are you specifying this filter?

[skionsnow]

Well here is the thing.  I didn't set any filters that I am aware of.  I set some breakpoints in BindingsImpl.java and FilterImpl.java.  There appears to be a filter with a value of null(I have attached the variable readout from a breakpoint at line 366 in BindingsImpl.java which shows this).  I have also attached the diff of my standalone-full.xml and the original so you can see how I configured the queue there.  I am guessing that I need to specify a valid filter to get past this.  From the manual it looks like I have the choice of HQPriority, HQExpiration,HQDurable(the xml specified durable, but I guess that is not HQDurable), ...  So How do I set these?  I tried confMessage.setIntProperty("HQPriority", 7);  That didn't make a difference.  Please advise.

Thanks!

[jbertram]

You must be setting a filter somehow that you aren't aware of.  The value of the filter is represented by the "sFilterString" variable in org.hornetq.core.filter.impl.FilterImpl which does not appear to be null in the variables.txt you attached. 

In my opinion the best way to fix this issue is to figure out why/how the filter is being set in the first place.  Typically this would be done in the XML through the "selector" attribute, e.g.:

                       <jms-queue name="confEventQueue">

                           <entry name="confEventQueue"/>

                           <selector string="myProperty=myValue"/>

                       </jms-queue>

But you don't appear to be doing that.

The filter/selector can also be set programmatically or administratively through either the AS7 or HornetQ management API.  Have you ever used either of these APIs?

Do you have a simple test-case I could use to reproduce the behavior you're seeing?

[skionsnow]

Justin,

I did not use the HornetQ API or JBOSS management to set up this queue.  I did look at the queue using the JBOSS management browser.  It shows the selector as blank.  I just noticed that I copied the ra.xml from a 2.4.0.Final download, and did not modify it at all.  Perhaps there is an issue with the the ra.xml being out of synch with the jar that I am building my workspace against?  I will create a simple test package for you from my EJB's as soon as I can it may be a few days.  In the meantime, would it be wise to upgrade my Hornetq version?

Thanks,

Jim

[jbertram]

I did look at the queue using the JBOSS management browser.

Did you use the CLI or the web-based application?

I just noticed that I copied the ra.xml from a 2.4.0.Final download, and did not modify it at all.  Perhaps there is an issue with the the ra.xml being out of synch with the jar that I am building my workspace against?

I wouldn't expect the ra.xml to play any role here.  That said, I'm curious as to why you would need the ra.xml at all.  What are you using it for?

In the meantime, would it be wise to upgrade my Hornetq version?

HornetQ is fairly tightly coupled to the messaging subsystem shipped with AS7/EAP/Wildfly.  If you want to upgrade you would probably need to upgrade the whole application server.

[skionsnow]

Justin,

I just removed the ra.xml and it didn't have an impact as you suggested.  There was no particular reason other than some blog mentioned it thought I would try it. 

I used the web based JBOSS management interface.

I cannot upgrade the whole application server at the moment so I will stay with what I have.

Jim

[skionsnow]

Justin,

I paired down the my ejb's to the bare minimum to show this issue and packaged the source and pom files in the attached zip.  I have also attached the standalone-full.xml file I am using.  Once the ear file is deployed in JBOSS a single timer will cause the jcm-dispatcher class to be executed and the exception will occur.

Thanks,

Jim

[jbertram]

I can't build your Maven project.  This is what I get when I execute 'mvn install':

$ mvn install
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR] 
[ERROR]  The project com.tatacommunications.tp:sdp-jcm:1.0.0.00-SNAPSHOT (/home/jbertram/Downloads/hornetqtest/pom.xml) has 1 error
[ERROR]    Non-resolvable parent POM: Failure to find com.tatacommunications.tp:tp-global-parent:pom:4 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

[skionsnow]

Justin,

Sorry, please replace the attached pom.xml file with the one attached.

Jim

[jbertram]

I saved your attached "standalone-full.xml" to "test.xml", built your EAR, deployed it to JBoss EAP 6.1, and it appears to be functioning without error.  Here's the log:

$ ./standalone.sh -c test.xml
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /home/jbertram/jboss/impl/forumTest

  JAVA: java

  JAVA_OPTS:  -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

16:07:02,424 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
16:07:02,708 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
16:07:02,796 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
16:07:04,031 INFO  [org.xnio] (MSC service thread 1-8) XNIO Version 3.0.7.GA-redhat-1
16:07:04,034 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
16:07:04,037 INFO  [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
16:07:04,108 INFO  [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 3.2.16.GA-redhat-1
16:07:04,139 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 35) JBAS016300: Activating JacORB Subsystem
16:07:04,155 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) JBAS010280: Activating Infinispan subsystem.
16:07:04,210 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-7) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.17.Final-redhat-1)
16:07:04,244 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 50) JBAS013171: Activating Security Subsystem
16:07:04,261 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 42) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
16:07:04,279 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 46) JBAS011800: Activating Naming Subsystem
16:07:04,319 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension
16:07:04,319 INFO  [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.17.Final-redhat-1
16:07:04,409 INFO  [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service
16:07:04,435 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
16:07:04,444 INFO  [org.jboss.jaxr] (MSC service thread 1-7) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
16:07:04,532 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:07:04,595 INFO  [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final-redhat-3
16:07:04,818 INFO  [org.apache.coyote.http11] (MSC service thread 1-5) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080
16:07:04,856 INFO  [org.apache.coyote.http11] (MSC service thread 1-5) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080
16:07:05,029 INFO  [org.hornetq.core.server] (MSC service thread 1-3) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/jbertram/jboss/impl/forumTest/standalone/data/messagingjournal,bindingsDirectory=/home/jbertram/jboss/impl/forumTest/standalone/data/messagingbindings,largeMessagesDirectory=/home/jbertram/jboss/impl/forumTest/standalone/data/messaginglargemessages,pagingDirectory=/home/jbertram/jboss/impl/forumTest/standalone/data/messagingpaging)
16:07:05,032 INFO  [org.hornetq.core.server] (MSC service thread 1-3) HQ221006: Waiting to obtain live lock
16:07:05,066 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016330: CORBA ORB Service started
16:07:05,106 INFO  [org.hornetq.core.server] (MSC service thread 1-3) HQ221013: Using NIO Journal
16:07:05,212 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
16:07:05,259 INFO  [org.jboss.as.jacorb] (MSC service thread 1-1) JBAS016328: CORBA Naming Service started
16:07:05,280 INFO  [org.hornetq.core.server] (MSC service thread 1-3) HQ221034: Waiting to obtain live lock
16:07:05,282 INFO  [org.hornetq.core.server] (MSC service thread 1-3) HQ221035: Live Server Obtained live lock
16:07:05,330 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /home/jbertram/jboss/impl/forumTest/standalone/deployments
16:07:05,344 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:4447
16:07:05,344 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on 127.0.0.1:9999
16:07:05,347 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "sdp-jcm-ear-1.0.0.00-SNAPSHOT.ear" (runtime-name: "sdp-jcm-ear-1.0.0.00-SNAPSHOT.ear")
16:07:06,355 INFO  [org.hornetq.core.server] (MSC service thread 1-3) HQ221020: Started Netty Acceptor version 3.6.2.Final-redhat-1-c0d783c 127.0.0.1:5455 for CORE protocol
16:07:06,358 INFO  [org.hornetq.core.server] (MSC service thread 1-3) HQ221020: Started Netty Acceptor version 3.6.2.Final-redhat-1-c0d783c 127.0.0.1:5445 for CORE protocol
16:07:06,361 INFO  [org.hornetq.core.server] (MSC service thread 1-3) HQ221007: Server is now live
16:07:06,361 INFO  [org.hornetq.core.server] (MSC service thread 1-3) HQ221001: HornetQ Server version 2.3.1.Final (Wild Hornet, 123) [e2597330-531c-11e4-97d3-953a74c8f8d6]
16:07:06,423 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/EventConnectionFactory
16:07:06,425 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221003: trying to deploy queue jms.queue.confEventQueue
16:07:06,483 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-8) JBAS010406: Registered connection factory java:/JmsXA
16:07:06,507 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/confEventQueue
16:07:06,511 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
16:07:06,537 INFO  [org.hornetq.ra] (MSC service thread 1-8) HornetQ resource adaptor started
16:07:06,538 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) IJ020002: Deployed: file://RaActivatorhornetq-ra
16:07:06,541 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-5) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
16:07:06,631 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "null" (runtime-name: "sdp-jcm-listener.jar")
16:07:06,632 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "sdp-jcm-xmpp.jar")
16:07:06,631 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "null" (runtime-name: "sdp-jcm-dispatcher.jar")
16:07:06,679 WARN  [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014218: [EJB3.1 spec, section 4.9.2] Session bean implementation class MUST NOT be a interface - com.tatacommunications.tp.jcm.dispatcher.JcmDispatcherInterface is an interface, hence won't be considered as a session bean
16:07:06,911 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named JcmDispatcher in deployment unit subdeployment "sdp-jcm-dispatcher.jar" of deployment "sdp-jcm-ear-1.0.0.00-SNAPSHOT.ear" are as follows:

  java:global/sdp-jcm-ear-1.0.0.00-SNAPSHOT/sdp-jcm-dispatcher/JcmDispatcher!com.tatacommunications.tp.jcm.dispatcher.JcmDispatcherInterface
  java:app/sdp-jcm-dispatcher/JcmDispatcher!com.tatacommunications.tp.jcm.dispatcher.JcmDispatcherInterface
  java:module/JcmDispatcher!com.tatacommunications.tp.jcm.dispatcher.JcmDispatcherInterface
  java:global/sdp-jcm-ear-1.0.0.00-SNAPSHOT/sdp-jcm-dispatcher/JcmDispatcher
  java:app/sdp-jcm-dispatcher/JcmDispatcher
  java:module/JcmDispatcher

16:07:06,911 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named PubSubAdaptorBean in deployment unit subdeployment "sdp-jcm-xmpp.jar" of deployment "sdp-jcm-ear-1.0.0.00-SNAPSHOT.ear" are as follows:

  java:global/sdp-jcm-ear-1.0.0.00-SNAPSHOT/sdp-jcm-xmpp/PubSubAdaptorBean!com.tatacommunications.tp.jcm.xmpp.PubSubAdaptorBean
  java:app/sdp-jcm-xmpp/PubSubAdaptorBean!com.tatacommunications.tp.jcm.xmpp.PubSubAdaptorBean
  java:module/PubSubAdaptorBean!com.tatacommunications.tp.jcm.xmpp.PubSubAdaptorBean
  java:global/sdp-jcm-ear-1.0.0.00-SNAPSHOT/sdp-jcm-xmpp/PubSubAdaptorBean
  java:app/sdp-jcm-xmpp/PubSubAdaptorBean
  java:module/PubSubAdaptorBean

16:07:07,381 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) JBAS014142: Started message driven bean 'confEventQueue' with 'hornetq-ra' resource adapter
16:07:07,410 INFO  [com.tatacommunications.tp.jcm.xmpp.PubSubAdaptorBean] (ServerService Thread Pool -- 56) Starting timer
16:07:07,421 INFO  [com.tatacommunications.tp.jcm.xmpp.PubSubAdaptorBean] (ServerService Thread Pool -- 56) Init Completed
16:07:07,545 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "sdp-jcm-ear-1.0.0.00-SNAPSHOT.ear" (runtime-name : "sdp-jcm-ear-1.0.0.00-SNAPSHOT.ear")
16:07:07,698 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
16:07:07,699 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:07:07,699 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started in 5985ms - Started 299 of 370 services (70 services are passive or on-demand)
16:07:12,422 INFO  [com.tatacommunications.tp.jcm.xmpp.PubSubAdaptorBean] (EJB default - 1) thread=EJB default - 1
16:07:12,424 INFO  [com.tatacommunications.tp.jcm.xmpp.PubSubAdaptorBean] (EJB default - 1) timerHandler: ConferenceId=1timestamp=11sequence =1
16:07:12,427 INFO  [com.tatacommunications.tp.jcm.dispatcher.ConfEventProducer] (EJB default - 1) ConfEventProducer Start
16:07:12,428 INFO  [com.tatacommunications.tp.jcm.dispatcher.ConfEventProducer] (EJB default - 1) confEventQueue: HornetQQueue[confEventQueue]
16:07:12,451 INFO  [com.tatacommunications.tp.jcm.dispatcher.JcmDispatcher] (EJB default - 1) JcmDispatcher Start
16:07:12,452 INFO  [com.tatacommunications.tp.jcm.dispatcher.JcmDispatcher] (EJB default - 1) JcmDispatcher: confEvent = ConferenceId=1timestamp=11sequence =1
16:07:12,453 INFO  [com.tatacommunications.tp.jcm.dispatcher.JcmDispatcher] (EJB default - 1) ConferenceProducer: com.tatacommunications.tp.jcm.dispatcher.ConfEventProducer@84badc2
16:07:12,490 INFO  [com.tatacommunications.tp.jcm.dispatcher.JcmDispatcher] (EJB default - 1) JcmDispatcher Sending message: HornetQMessage[ID:e6d5368f-531c-11e4-97d3-953a74c8f8d6]:PERSISTENT ConferenceId=1timestamp=11sequence =1

[jbertram]

BTW, I left it running for another 20 minutes or so and never saw an error.

[skionsnow]

Justin,

Thanks,  I am looking at my environment to see what may be different. I have been running this out of eclipse on a windows PC.  I am going to try some experiments like running the jboss server indepentently and on linux.  If you can think of anything else I might try would appreciate it.

Thanks,

Jim

[jbertram]

I'd start with removing the <JBOSS_HOME>/standalone/data directory so that the bindings are re-initialized when the server is re-started.  My guess is that a filter got set on the queue at some point during its life and was persisted to the bindings journal and is still being used.