On Jan 30, 2018 2:20 PM, "pypen" <py...@gmx.net> wrote: Bad day? Relax Tim. Not trying to offend anyone here.
I wasn't intending for the response to come across sharply; sorry that it did. It's not about me not wanting to tweak the log4j. I just didn't want to suppress the TransportDisposedIOException (or DemandForwardingBridgeSupport) if it happens for a different reason. Unfortunately I don't know of a way to prevent that; the only thing I can think of that even comes close is to use a custom Log4J stack trace renderer to strip out the lines if they match any exception you've seen recently (you'd have to keep a cache of recent exceptions to compare against), something like https://www.igorkromin.net/index.php/2017/08/21/filtering-exception-stack-trace-logging-with-log4j-and-a-custom-throwablerenderer/ with some tweaks like the cache. And I was not clear enough about the previous versions: It used to be a warning without exception. Also, I don't understand why this is a non-standard environment if the multi-cast discovery setup seems to be fine with brokers joining and leaving the network . The reason this works differently between those two configurations is that multicast discovery networks have a broadcast mechanism that allows new brokers to announce their presence, which means that the existing ones don't have to poll looking for them. But with static TCP connections, the only reliable way for the existing brokers to check whether a missing broker has come up is to poll for it by trying to connect repeatedly, and that generates these log messages. As for the non-standardness of this configuration, that's simply a statement of my perception that very few people seem to do what you're doing (a mesh network where its normal for some brokers in the network to be down for extended periods of time), but not to imply that it's unsupported or wrong. But it does mean that the default logging settings, which are streamlined for the more common cases, might not be optimal right out of the box in your environment. That's why I asked to see if my setup is correct (maybe there is parameter for the static configuration that makes the brokers "optional"). There's nothing about the pieces of your configuration that you've posted that's wrong, and no option I'm aware of to make brokers "optional" when defined statically. So I believe your only option is adjusting the Log4J configuration to make the logging more closely meet your needs. Tim
