2 Replies Latest reply on Nov 22, 2010 5:41 PM by charmed1130

Invalid Filter String Bad Object Type

charmed1130 Nov 19, 2010 11:03 AM

Hi please check this error.

We recently migrated to jboss 6. Add the necessary jar files on the client side to connect to the queues and topics on the new jboss.

The client was able to send the message to the Jboss. On Jboss the error is this: (Note: jar files that was included on the client is

hornetq-jms-client-java5.jar, hornetq-core-client-java5.jar, netty.jar, hornetq-logging.jar and just change the port to connect on to.)

We're doing some testings, some are successful. This one is not.

[org.hornetq.core.filter.impl.FilterImpl] Invalid filter string: TRUE: java.lang.Exception: Bad object type: true
        at org.hornetq.core.filter.impl.FilterImpl.match(FilterImpl.java:164) [:6.0.0.20100911-M5]
        at org.hornetq.core.postoffice.impl.BindingsImpl.getNextBinding(BindingsImpl.java:319) [:6.0.0.20100911-M5]
        at org.hornetq.core.postoffice.impl.BindingsImpl.route(BindingsImpl.java:266) [:6.0.0.20100911-M5]
        at org.hornetq.core.postoffice.impl.PostOfficeImpl.route(PostOfficeImpl.java:634) [:6.0.0.20100911-M5]
        at org.hornetq.core.server.impl.ServerSessionImpl.doSend(ServerSessionImpl.java:1175) [:6.0.0.20100911-M5]
        at org.hornetq.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:1000) [:6.0.0.20100911-M5]
        at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:461) [:6.0.0                                      .20100911-M5]
        at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:471) [:6.0.0.20100911-M5]
        at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:451) [:6.0.                                      0.20100911-M5]
        at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:412) [:6.0.0.                                      20100911-M5]
        at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImp                                      l.java:459) [:6.0.0.20100911-M5]
        at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:67) [:6.0.0.2                                      0100911-M5]
        at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100) [:6.0.0.20100911-M5]
        at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:362) [:6.0.0.20100911-M5]
        at org.jboss.netty.channel.StaticChannelPipeline$StaticChannelHandlerContext.sendUpstream(StaticChannelPipeline.java:5                                      14) [:6.0.0.20100911-M5]
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:287) [:6.0.0.20100911-M5]
        at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169) [:6.0.0.20100911-M5                                      ]
        at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134) [:6.0.0.20                                      100911-M5]
        at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) [:6.0.0.2                                      0100911-M5]
        at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:362) [:6.0.0.20100911-M5]
        at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:357) [:6.0.0.20100911-M5]
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) [:6.0.0.20100911-M5]
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) [:6.0.0.20100911-M5]
        at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:90) [:6.0.0.20100911-M5]
        at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [:6.0.0.20100911-M5]
        at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) [:6.0.0.20100911-M5]
        at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:181) [:6.0.0.2010                                      0911-M5]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
        at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]

CLIENT LOG is this:

DEBUG 2010-11-19 10:13:31,166 [V2JMSConnector.dispatcher.1] org.mule.providers.jms.transformers.ObjectToJMSMessage: The transformed object is of expected type. Type is: HornetQObjectMessage
DEBUG 2010-11-19 10:13:31,166 [V2JMSConnector.dispatcher.1] org.mule.providers.jms.JmsMessageDispatcher: Sending message of type HornetQObjectMessage

Thanks,

1. Re: Invalid Filter String Bad Object Type

clebert.suconic Nov 20, 2010 4:12 PM (in response to charmed1130)

It seems a Mule error to me
Actions
2. Re: Invalid Filter String Bad Object Type

charmed1130 Nov 22, 2010 5:41 PM (in response to clebert.suconic)

Hi, the client which is the Mule was able to send the message out successfully to Jboss. Upon receiving, Jboss encountered an error. Also, if we connect it to the old version of Jboss everything works fine.
For this error that we have encountered, we used a topic. I changed this to use queue instead and everything works fine. Any idea, where the error originated from? Would the content of the message being passed caused an error on the Jboss side? Connection/binding to topic on Jboss6 is successful. What condition could possibly cause an error on hornet -> Invalid filter string/Bad object type.

Thanks,
Actions

Go to original post