activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Badri <badrinarayanan.doraisw...@fxall.com>
Subject Re: Reference to 61616
Date Thu, 15 May 2008 17:56:27 GMT

Thanks Hiram for the reply. I commented out camel configuration. I am using
jetty for the web console. Is there some way to configure jetty not to
connect to the default port?



Hiram Chirino wrote:
> 
> Your broker is starting up and listening on 2506.. this is evident
> from the message:
> 008-05-09 14:41:27,794 INFO  TransportServerThreadSupport   -
> Listening for connections at: tcp://dcmpdevapp05:2506
> 
> The it looks like a failover client in the broker is trying to connect
> to tcp://localhost:61616 as seen by message:
> 2008-05-09 14:41:29,637 DEBUG FailoverTransport              -
> Attempting connect to: tcp://localhost:61616
> 
> So I'm thinking your config still has the default camel and jetty bits
> enabled in it.  The camel and jetty components connect to the broker
> as clients using the default ports.  If you disable these optional
> components those messages should go away.
> 
> On Fri, May 9, 2008 at 2:51 PM, Badri
> <badrinarayanan.doraiswamy@fxall.com> wrote:
>>
>> Hi
>> I am using tcp://localhost:2506 in transportConnector in activemq.xml
>> <transportConnectors>
>>      <transportConnector name="default" uri="tcp://localhost:2506"
>> discoveryUri="multicast://default"/>
>> </transportConnectors>
>>
>> <networkConnectors>
>>      <!-- by default just auto discover the other brokers -->
>>      <networkConnector name="default-nc" uri="multicast://default"/>
>> </networkConnectors>
>>
>> When i start active mq, I observe the following logs. I am not sure where
>> is
>> it picking tcp://localhost:61616?
>>
>> 2008-05-09 14:41:27,147 INFO  BrokerService                  - ActiveMQ
>> 5.1.0 JMS Message Broker (localhost) is starting
>> 2008-05-09 14:41:27,794 INFO  TransportServerThreadSupport   - Listening
>> for
>> connections at: tcp://dcmpdevapp05:2506
>> 2008-05-09 14:41:27,832 INFO  TransportConnector             - Connector
>> default Started
>> 2008-05-09 14:41:27,835 INFO  NetworkConnector               - Network
>> Connector default-nc Started
>> 2008-05-09 14:41:27,837 INFO  BrokerService                  - ActiveMQ
>> JMS
>> Message Broker (localhost, ID:dcmpdevapp05-41862-1210358487581-0:0)
>> started
>>
>> 2008-05-09 14:41:29,626 DEBUG FailoverTransport              - Waking up
>> reconnect task
>> 2008-05-09 14:41:29,637 DEBUG FailoverTransport              - Attempting
>> connect to: tcp://localhost:61616
>> 2008-05-09 14:41:29,709 DEBUG FailoverTransport              - Connect
>> fail
>> to: tcp://localhost:61616, reason: java.net.ConnectException: Connection
>> refused
>> 2008-05-09 14:41:29,709 DEBUG FailoverTransport              - Waiting 10
>> ms
>> before attempting connection.
>> 2008-05-09 14:41:29,715 DEBUG FailoverTransport              - Started.
>> 2008-05-09 14:41:29,715 DEBUG FailoverTransport              - Waking up
>> reconnect task
>> 2008-05-09 14:41:29,721 DEBUG FailoverTransport              - Attempting
>> connect to: tcp://localhost:61616
>> 2008-05-09 14:41:29,721 DEBUG FailoverTransport              - Connect
>> fail
>> to: tcp://localhost:61616, reason: java.net.ConnectException: Connection
>> refused
>> 2008-05-09 14:41:29,721 DEBUG FailoverTransport              - Waiting 20
>> ms
>> before attempting connection.
>>
>> Any help is appreciated.
>> Thanks
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Reference-to-61616-tp17154414s2354p17154414.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> 
> -- 
> Regards,
> Hiram
> 
> Blog: http://hiramchirino.com
> 
> Open Source SOA
> http://open.iona.com
> 
> 

-- 
View this message in context: http://www.nabble.com/Reference-to-61616-tp17154414s2354p17258959.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message