activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From uma...@comcast.net
Subject Re: AMQ4.1.1: External broker drops transport connector for unknown reason
Date Mon, 21 Apr 2008 06:22:52 GMT

I had a couple of significant problems with 5.0.0 
due to which I chose to downgrade to 4.1.1.

My main problem now is that sporadically,
the messages on topics are not transported 
over the networkConnector to the rmeote broker, 
even though there are subscribers to the topic
on the remote broker.

The problme disappears when I restart the brokers.
I would like to trace this problem using the trace option.
However, as I explained in an earlier mail, I am not
sure where the trace messages are deposited.

Can you pl help?

Regards

/Ur


 -------------- Original message ----------------------
From: Rob Davies <rajdavies@gmail.com>
> ActiveMQ 4.1.3 isn't released  - can you move to ActiveMQ 5 ?
> 
> On 18 Apr 2008, at 01:51, uma_rk@comcast.net wrote:
> 
> >
> > I need to download ActiveMQ4.1.3. I do not see 4.1.3
> > on the download page. I see only 4.1.2.
> >
> > Could someone pl point me to 4.1.3 binaries?
> >
> > Regards
> >
> > /Ur
> >
> >
> > -------------- Original message ----------------------
> > From: uma_rk@comcast.net
> >> It  appears that U am running into the following
> >> problem:
> >>    https://issues.apache.org/activemq/browse/AMQ-1045
> >>
> >> Is there any way to increase the pool size while instantiating
> >> AMQ connection factory using Spring?
> >>
> >> Regards
> >>
> >> /U
> >>
> >>
> >>
> >> -------------- Original message ----------------------
> >> From: uma_rk@comcast.net
> >>> I have two peers A.xxx.com and B.xxx.com connected using external  
> >>> brokers
> >>> running on each.
> >>> A and B each have a number of applications that have transport  
> >>> connections to
> >>> the
> >>> respective brokers.
> >>>
> >>>    [clients] <--- tcpConnector ---> [ext Broker A] <===  
> >>> NetworkConnector ===>
> >>> <extBroker B] <--- tcpConn --> {clients]
> >>>
> >>> The brokers startup fine and the clients connect respectively as  
> >>> shown in this
> >>> log:
> >>>
> >>>      2008-04-17 10:23:53,097 [127.0.0.1:41762] DEBUG  
> >>> TransportConnection
> >>> - Setting up new connection:
> >>>                     
> >>> org.apache.activemq.broker.TransportConnection@1f04ea6
> >>>     2008-04-17 10:23:53,098 [127.0.0.1:41762] DEBUG AbstractRegion
> >>> - Adding consumer:
> >>>                   ID:A.xxx.com-41697-1208452947300-1:9:-1:1
> >>>     2008-04-17 10:23:53,140 [127.0.0.1:41762] DEBUG AbstractRegion
> >>> - Adding destination:
> >>>
> >>> topic:// 
> >>> ActiveMQ.Advisory.Producer.Topic.com.xxx.topic.configuration_change
> >>>
> >>> But as soon as a client on A publishes a message on a topic
> >>> (com.xxx.topic.configuration_change),
> >>> broker A seems to remove the transport connection to the client as  
> >>> follows:
> >>>
> >>>
> >>>     2008-04-17 10:23:53,188 [127.0.0.1:41762] DEBUG AbstractRegion
> >>> - Removing consumer:
> >>>                   ID:A.xxx.com-41697-1208452947300-1:9:-1:1
> >>>     2008-04-17 10:23:53,190 [127.0.0.1:41762] DEBUG  
> >>> TransportConnection
> >>> - Stopping connection:
> >>>                  /127.0.0.1:41762
> >>>     2008-04-17 10:23:53,190 [127.0.0.1:41762] DEBUG  
> >>> TransportConnection
> >>> - Stopped connection:
> >>>                  /127.0.0.1:41762
> >>>
> >>> Why does this occur? What would be the recommended way to  
> >>> troubleshoot this
> >>> problem?
> >>> Any hints appreciated...
> >>>
> >>> Regards
> >>>
> >>> /U
> >>
> >
> 


Mime
View raw message