Yes, the timeout is negociated, as you have not set it you got warned that the broker default time out is assumed.
On Tue, Nov 9, 2010 at 4:49 AM, [email protected] <[email protected]> wrote: > > I am using qpid-0.6 java broker and JMS client. When I start a connection I > will get this warning message: > WARN ClientDelegate - Ignoring the idle timeout 0 set by the connection, > using the brokers max value 65535 > > Below is my JMS configuration: > > java.naming.factory.initial = > org.apache.qpid.jndi.PropertiesFileInitialContextFactory > connectionfactory.qpidConnectionfactory = > amqp://guest:gu...@clientid/test?brokerlist='tcp://localhost:5672' > destination.directQueue = > direct://amq.direct//message_queue?routingkey='routing_key' > > Below is my code: > > context = new InitialContext(properties); > ConnectionFactory conFac = (ConnectionFactory) context > .lookup("qpidConnectionfactory"); > connection = conFac.createConnection(); > > -- > View this message in context: > http://apache-qpid-users.2158936.n2.nabble.com/A-warning-message-when-creating-a-connection-tp5719658p5719658.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Sorin S --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
