thanks, I've indeed changed the order of the transport protocol i.e. removed telnet from the list because the customer's network does use SSH. So It shouldn't report a connection refused. Is there a way to find out what devices in the DCR are causing this?

In the mean time I will setup a cronjob with logrot.

There isn't an easy way to determine this. But if you have disabled telnet from your allowed protocols, you should not enter this code path anymore.

What if there is certain devices such as the 3500 switch that can't run SSH? We must have the telnet active for that reason, and now our daemons.log is at 11GB after only 24 hours....

I did a

grep "java.net.ConnectException: Connection refused" daemons.log | wc

and got this, 5937014 <---!!!

That is almost 6 million occurrencies, and have in mind that this is only the firs row of 22. 6x22x1000000 rows of pure junk.

There must be a way to shut of this kind of java logging?

There is no way to disable this logging. However, I have developed a patch for bug CSCso57052 which will help reduce the amount of these connection refused exceptions. The patch doesn't actually address the logging issue, but it greatly cuts down on the number of connections attempted, and thus will reduce the logging.

For example, before the patch, you could get, say, 100 connections per device. After the patch there will never be more than three.

You can contact the TAC, and reference the above bug to get the patch.

Is this patch going to be in LMS 3.1?

Yes.