Log message from IDACall after upgrading to 13.1p

[stonebranch3]

Isomorphic,

After upgrading from 12.1p to 13.1p, messages like the following are getting logged.

2025-02-07-15:05:51:990 -0500   INFO [http-nio-8180-exec-4] IDACall - Performing 1 operation(s) [UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36]

We extend IDACall and this message is logged by the logger for our subclass not the com.isomorphic logger.

Adding the following to our log4j2 configuration doesn't work.

<Logger name="com.isomorphic.servlet.IDACall" level="WARN" />

Using SmartClient Version: v13.1p_2025-02-04/Pro Deployment (built 2025-02-04)

Thanks

[Isomorphic]

Our loggers log based on the classname by default, so your subclass is going to log under your classname.

What are you hoping to do here? Get rid of just this one log, but retain other INFO-level logs? Or somehow change the category its being logged in?

[stonebranch3]

We would like to keep our logger level at INFO, but not see this one log (or any info messages from the IDACall class). We typically keep the com.isomorphic logger level at WARN. In other words, use the derived classname for our logging but not for IDACall logging.

[Isomorphic]

OK, that's clear, but we're not sure what we can do for you here.

The log in question is not logged by accident, and we don't want to remove it.

Logging to the className as a category instead of to some abstract category is also intentional, and used pervasively. In this case, it allows you to make a distinction between your special servlet subclass being called as opposed to the built-in servlet (as often, both are present).

Is there something you'd like to see here as a Feature Sponsorship? We're not sure what to suggest..

Outside of that, you should be able to configure some part of your logging system to squelch this particular log.