You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by kieran1 <KM...@herzumsoftware.com> on 2006/10/03 00:05:10 UTC
Null JMS Destination
Today it appears we have gotten a case where messages made it to ActiveMQ
with a null JMS destination.
The trace below appeared in activemq.log for every message sent. Has anyone
seen anything similar?
2006-10-02 21:11:37,781 [ocalport=61616]] WARN BrokerClientImpl
- caught exception consuming packet: ACTIVEMQ_OBJECT_MESSAGE: id = 0
ActiveMQMessage{ , jmsMessageID =
ID:whreal1.alleanzasalute.it-59045-1159814047343-68318:0, bodyAsBytes =
org.activemq.message.util.ByteArray@1592469, readOnlyMessage = false,
jmsClientID = 'ID:whreal1.alleanzasalute.it-59045-1159814047343-68223:' ,
jmsCorrelationID = 'null' , jmsDestination = null, jmsReplyTo = null,
jmsDeliveryMode = 2, jmsRedelivered = false, jmsType = 'null' ,
jmsExpiration = 0, jmsPriority = 4, jmsTimestamp = 1159816297767, properties
= null, readOnlyProperties = false, entryBrokerName = 'reporting2' ,
entryClusterName = 'default' , consumerNos = null, transactionId = 'null' ,
xaTransacted = false, consumerIdentifer = 'null' , messageConsumed = false,
transientConsumed = false, sequenceNumber = 0, deliveryCount = 1,
dispatchedFromDLQ = false, messageAcknowledge = null, jmsMessageIdentity =
null, producerKey = ID:whreal1.alleanzasalute.it-59045-1159814047343-68318:
} ActiveMQObjectMessage{ object = null }
java.lang.NullPointerException
at
org.activemq.broker.impl.DefaultBroker.sendMessage(DefaultBroker.java:283)
at
org.activemq.broker.impl.BrokerContainerImpl.sendMessage(BrokerContainerImpl.java:462)
at
org.activemq.broker.impl.BrokerConnectorImpl.sendMessage(BrokerConnectorImpl.java:271)
at
org.activemq.broker.impl.BrokerClientImpl.consumeActiveMQMessage(BrokerClientImpl.java:693)
at
org.activemq.broker.impl.BrokerClientImpl.consume(BrokerClientImpl.java:306)
at
org.activemq.transport.TransportChannelSupport.doConsumePacket(TransportChannelSupport.java:374)
at
org.activemq.transport.TransportChannelSupport.doConsumePacket(TransportChannelSupport.java:368)
at
org.activemq.transport.tcp.TcpTransportChannel.run(TcpTransportChannel.java:310)
at java.lang.Thread.run(Unknown Source)
--
View this message in context: http://www.nabble.com/Null-JMS-Destination-tf2372770.html#a6610593
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Null JMS Destination
Posted by kieran1 <KM...@herzumsoftware.com>.
We are using AMQ 3.0 and the Java client. I've also tested every way I can
imagine to get a null destination through our code to AMQ, and it so far it
seems that our code catches the nulls before they are sent to AMQ code.
>From my logs, it appears that this is happening on every message.
I'm still researching our code on this...seems strange to me that we would
suddenly have this problem after using AMQ 3.0 for over a year.
I will update with my findings.
James.Strachan wrote:
>
> Yeah I've seen this when using a non-Java client. Were you using the
> Java client? Am wondering how to reproduce. I've just added an
> explicit check into the Java client to make absolutely sure a
> destination is specified & if not give a meaningful exception
>
> On 10/2/06, kieran1 <KM...@herzumsoftware.com> wrote:
>>
>> Today it appears we have gotten a case where messages made it to ActiveMQ
>> with a null JMS destination.
>>
>> The trace below appeared in activemq.log for every message sent. Has
>> anyone
>> seen anything similar?
>>
>> 2006-10-02 21:11:37,781 [ocalport=61616]] WARN BrokerClientImpl
>> - caught exception consuming packet: ACTIVEMQ_OBJECT_MESSAGE: id = 0
>> ActiveMQMessage{ , jmsMessageID =
>> ID:whreal1.alleanzasalute.it-59045-1159814047343-68318:0, bodyAsBytes =
>> org.activemq.message.util.ByteArray@1592469, readOnlyMessage = false,
>> jmsClientID = 'ID:whreal1.alleanzasalute.it-59045-1159814047343-68223:' ,
>> jmsCorrelationID = 'null' , jmsDestination = null, jmsReplyTo = null,
>> jmsDeliveryMode = 2, jmsRedelivered = false, jmsType = 'null' ,
>> jmsExpiration = 0, jmsPriority = 4, jmsTimestamp = 1159816297767,
>> properties
>> = null, readOnlyProperties = false, entryBrokerName = 'reporting2' ,
>> entryClusterName = 'default' , consumerNos = null, transactionId = 'null'
>> ,
>> xaTransacted = false, consumerIdentifer = 'null' , messageConsumed =
>> false,
>> transientConsumed = false, sequenceNumber = 0, deliveryCount = 1,
>> dispatchedFromDLQ = false, messageAcknowledge = null, jmsMessageIdentity
>> =
>> null, producerKey =
>> ID:whreal1.alleanzasalute.it-59045-1159814047343-68318:
>> } ActiveMQObjectMessage{ object = null }
>> java.lang.NullPointerException
>> at
>> org.activemq.broker.impl.DefaultBroker.sendMessage(DefaultBroker.java:283)
>> at
>> org.activemq.broker.impl.BrokerContainerImpl.sendMessage(BrokerContainerImpl.java:462)
>> at
>> org.activemq.broker.impl.BrokerConnectorImpl.sendMessage(BrokerConnectorImpl.java:271)
>> at
>> org.activemq.broker.impl.BrokerClientImpl.consumeActiveMQMessage(BrokerClientImpl.java:693)
>> at
>> org.activemq.broker.impl.BrokerClientImpl.consume(BrokerClientImpl.java:306)
>> at
>> org.activemq.transport.TransportChannelSupport.doConsumePacket(TransportChannelSupport.java:374)
>> at
>> org.activemq.transport.TransportChannelSupport.doConsumePacket(TransportChannelSupport.java:368)
>> at
>> org.activemq.transport.tcp.TcpTransportChannel.run(TcpTransportChannel.java:310)
>> at java.lang.Thread.run(Unknown Source)
>> --
>> View this message in context:
>> http://www.nabble.com/Null-JMS-Destination-tf2372770.html#a6610593
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
>
--
View this message in context: http://www.nabble.com/Null-JMS-Destination-tf2372770.html#a6623138
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Null JMS Destination
Posted by James Strachan <ja...@gmail.com>.
Yeah I've seen this when using a non-Java client. Were you using the
Java client? Am wondering how to reproduce. I've just added an
explicit check into the Java client to make absolutely sure a
destination is specified & if not give a meaningful exception
On 10/2/06, kieran1 <KM...@herzumsoftware.com> wrote:
>
> Today it appears we have gotten a case where messages made it to ActiveMQ
> with a null JMS destination.
>
> The trace below appeared in activemq.log for every message sent. Has anyone
> seen anything similar?
>
> 2006-10-02 21:11:37,781 [ocalport=61616]] WARN BrokerClientImpl
> - caught exception consuming packet: ACTIVEMQ_OBJECT_MESSAGE: id = 0
> ActiveMQMessage{ , jmsMessageID =
> ID:whreal1.alleanzasalute.it-59045-1159814047343-68318:0, bodyAsBytes =
> org.activemq.message.util.ByteArray@1592469, readOnlyMessage = false,
> jmsClientID = 'ID:whreal1.alleanzasalute.it-59045-1159814047343-68223:' ,
> jmsCorrelationID = 'null' , jmsDestination = null, jmsReplyTo = null,
> jmsDeliveryMode = 2, jmsRedelivered = false, jmsType = 'null' ,
> jmsExpiration = 0, jmsPriority = 4, jmsTimestamp = 1159816297767, properties
> = null, readOnlyProperties = false, entryBrokerName = 'reporting2' ,
> entryClusterName = 'default' , consumerNos = null, transactionId = 'null' ,
> xaTransacted = false, consumerIdentifer = 'null' , messageConsumed = false,
> transientConsumed = false, sequenceNumber = 0, deliveryCount = 1,
> dispatchedFromDLQ = false, messageAcknowledge = null, jmsMessageIdentity =
> null, producerKey = ID:whreal1.alleanzasalute.it-59045-1159814047343-68318:
> } ActiveMQObjectMessage{ object = null }
> java.lang.NullPointerException
> at
> org.activemq.broker.impl.DefaultBroker.sendMessage(DefaultBroker.java:283)
> at
> org.activemq.broker.impl.BrokerContainerImpl.sendMessage(BrokerContainerImpl.java:462)
> at
> org.activemq.broker.impl.BrokerConnectorImpl.sendMessage(BrokerConnectorImpl.java:271)
> at
> org.activemq.broker.impl.BrokerClientImpl.consumeActiveMQMessage(BrokerClientImpl.java:693)
> at
> org.activemq.broker.impl.BrokerClientImpl.consume(BrokerClientImpl.java:306)
> at
> org.activemq.transport.TransportChannelSupport.doConsumePacket(TransportChannelSupport.java:374)
> at
> org.activemq.transport.TransportChannelSupport.doConsumePacket(TransportChannelSupport.java:368)
> at
> org.activemq.transport.tcp.TcpTransportChannel.run(TcpTransportChannel.java:310)
> at java.lang.Thread.run(Unknown Source)
> --
> View this message in context: http://www.nabble.com/Null-JMS-Destination-tf2372770.html#a6610593
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/