[activemq-user] Occasionally ActiveMQ does not deliver the message on dynamically created Topic

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[activemq-user] Occasionally ActiveMQ does not deliver the message on dynamically created Topic

gklyuzner
The consumer is up and running and listen on dynamicly created topic. The
message successfully sent by publisher to the same topic, but message never
delivers to the consumer. If I restart all components, then it start working
as expected.

Once message is delivered to the consumer it replies to temporary created
topic (JMSReplyTo).

I am using not Durable, but persistent messages.

Wonder how can I find out what did happen to undelivered message?
From the log below it is unclear what was wrong or right from ActiveMQ
perspective.


Application trace:
SiteServer cs.login : Company = TUTFUS31, UserName = SS, InetAddress =
ny-cap-33/170.198.120.104, payload = null, SessionID = null cs : Random:
[com.tullib.core.message.jms.JMS_MSC@1b158db ] s_cms_cs : null
INFO 2005-06-21 17:21:13,812 - Sent login msg = ACTIVEMQ_OBJECT_MESSAGE: id
= 0 ActiveMQMessage{ , jmsMessageID = null, bodyAsBytes =
org.activemq.io.util.ByteArray@a56214, readOnlyMessage = false, jmsClientID
= 'null' , jmsCorrelationID =
'CSLoginTopic.c446f3b44a1f28ed:8fce95:104a0c6a205:-8000' , jmsDestination =
null, jmsReplyTo = null, jmsDeliveryMode = 2, jmsRedelivered = false,
jmsType = 'null' , jmsExpiration = 0, jmsPriority = 9, jmsTimestamp = 0,
properties = {OTCCore.LoginMessage.LoginTime=2005.06.21 17:21:13.750 EDT,
OTCCore.LoginMessage.InetAddress=ny-cap-33/170.198.120.104,
OTCCore.LoginMessage.UserName=SS,
OTCCore.LoginMessage.CompanyName=TUTFUS31}, readOnlyProperties = false,
entryBrokerName = 'null' , entryClusterName = 'null' , consumerNos = null,
transactionId = 'null' , xaTransacted = false, consumerIdentifer = 'null' ,
messageConsumed = false, transientConsumed = false, sequenceNumber = 0,
deliveryCount = 1, dispatchedFromDLQ = false, messageAcknowledge = null,
jmsMessageIdentity = null, producerKey = null } ActiveMQObjectMessage{
object = Company = TUTFUS31, UserName = SS, InetAddress =
ny-cap-33/170.198.120.104, payload = null, SessionID = null }
         to Destination : CSLoginTopic
         wait duration : 600 sec
INFO 2005-06-21 17:21:13,906 - ### SendAndWait publishing on
destination : CSLoginTopic
        waiting on temporary destination
:TemporaryTopic-{TD{ID:ny-cap-33-1796-1119388873109-6:0}TD}ID:ny-cap-33-1796
-1119388873109-21:0
        message : ACTIVEMQ_OBJECT_MESSAGE: id = 0 ActiveMQMessage{ ,
jmsMessageID = null, bodyAsBytes = org.activemq.io.util.ByteArray@a56214,
readOnlyMessage = false, jmsClientID = 'null' , jmsCorrelationID =
'CSLoginTopic.c446f3b44a1f28ed:8fce95:104a0c6a205:-8000' , jmsDestination =
null, jmsReplyTo =
TemporaryTopic-{TD{ID:ny-cap-33-1796-1119388873109-6:0}TD}ID:ny-cap-33-1796-
1119388873109-21:0, jmsDeliveryMode = 2, jmsRedelivered = false, jmsType =
'null' , jmsExpiration = 0, jmsPriority = 9, jmsTimestamp = 0, properties =
{OTCCore.LoginMessage.LoginTime=2005.06.21 17:21:13.750 EDT,
OTCCore.LoginMessage.InetAddress=ny-cap-33/170.198.120.104,
OTCCore.LoginMessage.UserName=SS,
OTCCore.LoginMessage.CompanyName=TUTFUS31}, readOnlyProperties = false,
entryBrokerName = 'null' , entryClusterName = 'null' , consumerNos = null,
transactionId = 'null' , xaTransacted = false, consumerIdentifer = 'null' ,
messageConsumed = false, transientConsumed = false, sequenceNumber = 0,
deliveryCount = 1, dispatchedFromDLQ = false, messageAcknowledge = null,
jmsMessageIdentity = null, producerKey = null } ActiveMQObjectMessage{
object = Company = TUTFUS31, UserName = SS, InetAddress =
ny-cap-33/170.198.120.104, payload = null, SessionID = null }
INFO 2005-06-21 17:21:13,906 - ### SendAndWait 600000 ms ... waiting for
reply on destination :
TemporaryTopic-{TD{ID:ny-cap-33-1796-1119388873109-6:0}TD}ID:ny-cap-33-1796-
1119388873109-21:0
INFO 2005-06-21 17:31:13,906 - Did not receive the reply on login message
sent to CSLoginTopic
         wait duration : 600 sec

ActiveMQ trace :

2005-06-21 17:21:02,262 [Cleanup Timmer ] DEBUG JDBCPersistenceAdapter
- Cleanup done.
2005-06-21 17:21:13,403 [/nyotc023:61616] DEBUG BrokerClientImpl
- brokerConnectorConnector client initialized
2005-06-21 17:21:13,419 [/nyotc023:61616] DEBUG BrokerConnectorImpl
- Starting new client: brokerConnector-client:(12804275) :
TcpTransportChannel: Socket[addr=/170.198.120.104,port=1797,localport=61616]
2005-06-21 17:21:13,450 [ocalport=61616]] DEBUG TcpTransportChannel
- TCP consumer thread starting
2005-06-21 17:21:13,450 [ocalport=61616]] DEBUG TransportChannelSupport
- TcpTransportChannel:
Socket[addr=/170.198.120.104,port=1797,localport=61616] using wire format
version: 3
2005-06-21 17:21:13,575 [ocalport=61616]] INFO  BrokerContainerImpl
- Adding new client: ID:ny-cap-33-1796-1119388873109-6:0 on transport:
TcpTransportChannel: Socket[addr=/170.198.120.104,port=1797,localport=61616]
2005-06-21 17:21:13,575 [ocalport=61616]] DEBUG BrokerClientImpl
- brokerConnector-client:(12804275) ID:ny-cap-33-1796-1119388873109-6:0:
TcpTransportChannel: Socket[addr=/170.198.120.104,port=1797,localport=61616]
has started running client version 3.1-SNAPSHOT , wire format = 3
2005-06-21 17:21:13,590 [/nyotc023:61616] DEBUG BrokerClientImpl
- brokerConnectorConnector client initialized
2005-06-21 17:21:13,590 [/nyotc023:61616] DEBUG BrokerConnectorImpl
- Starting new client: brokerConnector-client:(7067210) :
TcpTransportChannel: Socket[addr=/170.198.120.104,port=1798,localport=61616]
2005-06-21 17:21:13,590 [ocalport=61616]] DEBUG TcpTransportChannel
- TCP consumer thread starting
2005-06-21 17:21:13,590 [ocalport=61616]] DEBUG TransportChannelSupport
- TcpTransportChannel:
Socket[addr=/170.198.120.104,port=1798,localport=61616] using wire format
version: 3
2005-06-21 17:21:13,778 [ocalport=61616]] INFO  BrokerContainerImpl
- Adding new client: ID:ny-cap-33-1796-1119388873109-16:0 on transport:
TcpTransportChannel: Socket[addr=/170.198.120.104,port=1798,localport=61616]
2005-06-21 17:21:13,778 [ocalport=61616]] DEBUG BrokerClientImpl
- brokerConnector-client:(7067210) ID:ny-cap-33-1796-1119388873109-16:0:
TcpTransportChannel: Socket[addr=/170.198.120.104,port=1798,localport=61616]
has started running client version 3.1-SNAPSHOT , wire format = 3
2005-06-21 17:21:13,997 [ocalport=61616]] DEBUG
ientTopicBoundedMessageManager - Adding consumer: CONSUMER_INFO: id = 6
ConsumerInfo{ browser = false, destination =
TemporaryTopic-{TD{ID:ny-cap-33-1796-1119388873109-6:0}TD}ID:ny-cap-33-1796-
1119388873109-21:0, consumerIdentifier =
'ID:ny-cap-33-1796-1119388873109-6:0.1.1' , clientId =
'ID:ny-cap-33-1796-1119388873109-6:0' , sessionId = '1' , consumerName = ''
, selector = '' , startTime = 1119388873890, started = true, consumerNo = 1,
noLocal = false, prefetchNumber = 1000, consumerKey =
'[ID:ny-cap-33-1796-1119388873109-6:0:]'  }
2005-06-21 17:23:31,875 [eckpoint Worker] DEBUG JournalPersistenceAdapter
- Checkpoint started.
2005-06-21 17:23:31,907 [eckpoint Worker] DEBUG JournalPersistenceAdapter
- Checkpoint done.

-----Original Message-----
From: news [mailto:[hidden email]]On Behalf Of Lutz Mueller
Sent: Tuesday, June 14, 2005 4:10 PM
To: [hidden email]
Subject: [activemq-user] receiving old messages again after restart


hi all,

i am using 3.1M2 to send ptp messages to a message queue on a broker on
tcp://localhost. the queue uses derby-db persistence. it seems the messages
are not deleted from the persistence store after i received and
acknowledged them. after a restart of the broker i am getting the same old
messages i acknowledged before again. this can not be right?
what am i doing wrong? i see no error messages, just some warnings at
startup that some database tables could not be created, because they are
already there.

--
gmane



----------------------------------------------------------------------------
----------------------------------------------------------------------------
-------------------------
The information contained in this email is confidential and may also contain
privileged information. Sender does not waive confidentiality or legal
privilege. If you are not the intended recipient please notify the sender
immediately; you should not retain this message or disclose its content to
anyone.
Internet communications are not secure or error free and the sender does not
accept any liability for the content of the email. Although emails are
routinely screened for viruses, the sender does not accept responsibility
for any damage caused. Replies to this email may be monitored.
For more information about the Collins Stewart Tullett group of companies
please visit the following web site: www.cstplc.com
----------------------------------------------------------------------------
----------------------------------------------------------------------------
--------------------------

Reply | Threaded
Open this post in threaded view
|

Re: [activemq-user] Occasionally ActiveMQ does not deliver the message on dynamically created Topic

jstrachan
I wonder do you have a test case for this we could look at?

Are you positive that the consumer is definitely created for the  
temporary topic before the send occurs? We use temporary topic/queues  
fairly heavily in other projects (such as Lingo) and we've never hit  
this issue yet. Any chance you could create a test case that  
demonstrates this issue?


On 21 Jun 2005, at 14:59, [hidden email] wrote:

> The consumer is up and running and listen on dynamicly created  
> topic. The
> message successfully sent by publisher to the same topic, but  
> message never
> delivers to the consumer. If I restart all components, then it  
> start working
> as expected.
>
> Once message is delivered to the consumer it replies to temporary  
> created
> topic (JMSReplyTo).
>
> I am using not Durable, but persistent messages.
>
> Wonder how can I find out what did happen to undelivered message?
> From the log below it is unclear what was wrong or right from ActiveMQ
> perspective.
>
>
> Application trace:
> SiteServer cs.login : Company = TUTFUS31, UserName = SS, InetAddress =
> ny-cap-33/170.198.120.104, payload = null, SessionID = null cs :  
> Random:
> [com.tullib.core.message.jms.JMS_MSC@1b158db ] s_cms_cs : null
> INFO 2005-06-21 17:21:13,812 - Sent login msg =  
> ACTIVEMQ_OBJECT_MESSAGE: id
> = 0 ActiveMQMessage{ , jmsMessageID = null, bodyAsBytes =
> org.activemq.io.util.ByteArray@a56214, readOnlyMessage = false,  
> jmsClientID
> = 'null' , jmsCorrelationID =
> 'CSLoginTopic.c446f3b44a1f28ed:8fce95:104a0c6a205:-8000' ,  
> jmsDestination =
> null, jmsReplyTo = null, jmsDeliveryMode = 2, jmsRedelivered = false,
> jmsType = 'null' , jmsExpiration = 0, jmsPriority = 9, jmsTimestamp  
> = 0,
> properties = {OTCCore.LoginMessage.LoginTime=2005.06.21  
> 17:21:13.750 EDT,
> OTCCore.LoginMessage.InetAddress=ny-cap-33/170.198.120.104,
> OTCCore.LoginMessage.UserName=SS,
> OTCCore.LoginMessage.CompanyName=TUTFUS31}, readOnlyProperties =  
> false,
> entryBrokerName = 'null' , entryClusterName = 'null' , consumerNos  
> = null,
> transactionId = 'null' , xaTransacted = false, consumerIdentifer =  
> 'null' ,
> messageConsumed = false, transientConsumed = false, sequenceNumber  
> = 0,
> deliveryCount = 1, dispatchedFromDLQ = false, messageAcknowledge =  
> null,
> jmsMessageIdentity = null, producerKey = null } ActiveMQObjectMessage{
> object = Company = TUTFUS31, UserName = SS, InetAddress =
> ny-cap-33/170.198.120.104, payload = null, SessionID = null }
>      to Destination :     CSLoginTopic
>      wait duration :     600 sec
> INFO 2005-06-21 17:21:13,906 - ###    SendAndWait publishing on
> destination : CSLoginTopic
>     waiting on temporary destination
> :TemporaryTopic-{TD{ID:ny-cap-33-1796-1119388873109-6:0}TD}ID:ny-
> cap-33-1796
> -1119388873109-21:0
>     message : ACTIVEMQ_OBJECT_MESSAGE: id = 0 ActiveMQMessage{ ,
> jmsMessageID = null, bodyAsBytes =  
> org.activemq.io.util.ByteArray@a56214,
> readOnlyMessage = false, jmsClientID = 'null' , jmsCorrelationID =
> 'CSLoginTopic.c446f3b44a1f28ed:8fce95:104a0c6a205:-8000' ,  
> jmsDestination =
> null, jmsReplyTo =
> TemporaryTopic-{TD{ID:ny-cap-33-1796-1119388873109-6:0}TD}ID:ny-
> cap-33-1796-
> 1119388873109-21:0, jmsDeliveryMode = 2, jmsRedelivered = false,  
> jmsType =
> 'null' , jmsExpiration = 0, jmsPriority = 9, jmsTimestamp = 0,  
> properties =
> {OTCCore.LoginMessage.LoginTime=2005.06.21 17:21:13.750 EDT,
> OTCCore.LoginMessage.InetAddress=ny-cap-33/170.198.120.104,
> OTCCore.LoginMessage.UserName=SS,
> OTCCore.LoginMessage.CompanyName=TUTFUS31}, readOnlyProperties =  
> false,
> entryBrokerName = 'null' , entryClusterName = 'null' , consumerNos  
> = null,
> transactionId = 'null' , xaTransacted = false, consumerIdentifer =  
> 'null' ,
> messageConsumed = false, transientConsumed = false, sequenceNumber  
> = 0,
> deliveryCount = 1, dispatchedFromDLQ = false, messageAcknowledge =  
> null,
> jmsMessageIdentity = null, producerKey = null } ActiveMQObjectMessage{
> object = Company = TUTFUS31, UserName = SS, InetAddress =
> ny-cap-33/170.198.120.104, payload = null, SessionID = null }
> INFO 2005-06-21 17:21:13,906 - ### SendAndWait 600000 ms ...  
> waiting for
> reply on destination :
> TemporaryTopic-{TD{ID:ny-cap-33-1796-1119388873109-6:0}TD}ID:ny-
> cap-33-1796-
> 1119388873109-21:0
> INFO 2005-06-21 17:31:13,906 - Did not receive the reply on login  
> message
> sent to CSLoginTopic
>      wait duration :     600 sec
>
> ActiveMQ trace :
>
> 2005-06-21 17:21:02,262 [Cleanup Timmer ] DEBUG JDBCPersistenceAdapter
> - Cleanup done.
> 2005-06-21 17:21:13,403 [/nyotc023:61616] DEBUG BrokerClientImpl
> - brokerConnectorConnector client initialized
> 2005-06-21 17:21:13,419 [/nyotc023:61616] DEBUG BrokerConnectorImpl
> - Starting new client: brokerConnector-client:(12804275) :
> TcpTransportChannel: Socket[addr=/
> 170.198.120.104,port=1797,localport=61616]
> 2005-06-21 17:21:13,450 [ocalport=61616]] DEBUG TcpTransportChannel
> - TCP consumer thread starting
> 2005-06-21 17:21:13,450 [ocalport=61616]] DEBUG  
> TransportChannelSupport
> - TcpTransportChannel:
> Socket[addr=/170.198.120.104,port=1797,localport=61616] using wire  
> format
> version: 3
> 2005-06-21 17:21:13,575 [ocalport=61616]] INFO  BrokerContainerImpl
> - Adding new client: ID:ny-cap-33-1796-1119388873109-6:0 on transport:
> TcpTransportChannel: Socket[addr=/
> 170.198.120.104,port=1797,localport=61616]
> 2005-06-21 17:21:13,575 [ocalport=61616]] DEBUG BrokerClientImpl
> - brokerConnector-client:(12804275) ID:ny-
> cap-33-1796-1119388873109-6:0:
> TcpTransportChannel: Socket[addr=/
> 170.198.120.104,port=1797,localport=61616]
> has started running client version 3.1-SNAPSHOT , wire format = 3
> 2005-06-21 17:21:13,590 [/nyotc023:61616] DEBUG BrokerClientImpl
> - brokerConnectorConnector client initialized
> 2005-06-21 17:21:13,590 [/nyotc023:61616] DEBUG BrokerConnectorImpl
> - Starting new client: brokerConnector-client:(7067210) :
> TcpTransportChannel: Socket[addr=/
> 170.198.120.104,port=1798,localport=61616]
> 2005-06-21 17:21:13,590 [ocalport=61616]] DEBUG TcpTransportChannel
> - TCP consumer thread starting
> 2005-06-21 17:21:13,590 [ocalport=61616]] DEBUG  
> TransportChannelSupport
> - TcpTransportChannel:
> Socket[addr=/170.198.120.104,port=1798,localport=61616] using wire  
> format
> version: 3
> 2005-06-21 17:21:13,778 [ocalport=61616]] INFO  BrokerContainerImpl
> - Adding new client: ID:ny-cap-33-1796-1119388873109-16:0 on  
> transport:
> TcpTransportChannel: Socket[addr=/
> 170.198.120.104,port=1798,localport=61616]
> 2005-06-21 17:21:13,778 [ocalport=61616]] DEBUG BrokerClientImpl
> - brokerConnector-client:(7067210) ID:ny-
> cap-33-1796-1119388873109-16:0:
> TcpTransportChannel: Socket[addr=/
> 170.198.120.104,port=1798,localport=61616]
> has started running client version 3.1-SNAPSHOT , wire format = 3
> 2005-06-21 17:21:13,997 [ocalport=61616]] DEBUG
> ientTopicBoundedMessageManager - Adding consumer: CONSUMER_INFO: id  
> = 6
> ConsumerInfo{ browser = false, destination =
> TemporaryTopic-{TD{ID:ny-cap-33-1796-1119388873109-6:0}TD}ID:ny-
> cap-33-1796-
> 1119388873109-21:0, consumerIdentifier =
> 'ID:ny-cap-33-1796-1119388873109-6:0.1.1' , clientId =
> 'ID:ny-cap-33-1796-1119388873109-6:0' , sessionId = '1' ,  
> consumerName = ''
> , selector = '' , startTime = 1119388873890, started = true,  
> consumerNo = 1,
> noLocal = false, prefetchNumber = 1000, consumerKey =
> '[ID:ny-cap-33-1796-1119388873109-6:0:]'  }
> 2005-06-21 17:23:31,875 [eckpoint Worker] DEBUG  
> JournalPersistenceAdapter
> - Checkpoint started.
> 2005-06-21 17:23:31,907 [eckpoint Worker] DEBUG  
> JournalPersistenceAdapter
> - Checkpoint done.
>
> -----Original Message-----
> From: news [mailto:[hidden email]]On Behalf Of Lutz Mueller
> Sent: Tuesday, June 14, 2005 4:10 PM
> To: [hidden email]
> Subject: [activemq-user] receiving old messages again after restart
>
>
> hi all,
>
> i am using 3.1M2 to send ptp messages to a message queue on a  
> broker on
> tcp://localhost. the queue uses derby-db persistence. it seems the  
> messages
> are not deleted from the persistence store after i received and
> acknowledged them. after a restart of the broker i am getting the  
> same old
> messages i acknowledged before again. this can not be right?
> what am i doing wrong? i see no error messages, just some warnings at
> startup that some database tables could not be created, because  
> they are
> already there.
>
> --
> gmane
>
>
>
> ----------------------------------------------------------------------
> ------
> ----------------------------------------------------------------------
> ------
> -------------------------
> The information contained in this email is confidential and may  
> also contain
> privileged information. Sender does not waive confidentiality or legal
> privilege. If you are not the intended recipient please notify the  
> sender
> immediately; you should not retain this message or disclose its  
> content to
> anyone.
> Internet communications are not secure or error free and the sender  
> does not
> accept any liability for the content of the email. Although emails are
> routinely screened for viruses, the sender does not accept  
> responsibility
> for any damage caused. Replies to this email may be monitored.
> For more information about the Collins Stewart Tullett group of  
> companies
> please visit the following web site: www.cstplc.com
> ----------------------------------------------------------------------
> ------
> ----------------------------------------------------------------------
> ------
> --------------------------
>
>


James
-------
http://radio.weblogs.com/0112098/