Hi Danshuka,
The message you are seeing is not the result of any sort of
warning/error it just happens to be at the WARN log level which probably is
incorrect. It should really have been done at the DEBUG level. The java client
uses slf4j internally so the way to get rid of the message is to simply adjust
the log level of whatever real logger you are using (log4j, java logging) to
disable warning messages which you can do by class if you simply just want to
remove this particular message.
Also, you could file a JIRA requesting the level for these particular messages
be changed which I think would be valid in this case.
Regards,
Weston
On Apr 25, 2011, at 8:03 AM, Danushka Menikkumbura wrote:
> Hi,
>
> I get the following warning message on the client side for each client call
> i make.
>
> [2011-04-25 13:25:10,177] WARN
> {org.apache.qpid.transport.ClientDelegate} - Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,178] WARN
> {org.apache.qpid.transport.SessionDelegate} - CLOSED:
> [ssn:"10bbf39e-3676-4205-a713-789b3a377cf3"]
>
> The reason for the first warning is that the default heartbeat value in
> client properties is 120 whereas the default min and max heartbeat values of
> a connection are 0. And it checks if the heartbeat value lies between the
> min and max.
>
> I do not quite understand the reason for the second warning. It just logs
> this warning in SessionDelegate.closed.
>
> Could you please tell me how to get rid of these warning?.
>
> Thanks,
> Danushka
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
