I looked again, I was wrong, the log level for this specific message is "severe".
That might be a bit high, but the question is how come you don't pass in any params?
The param values might be null, but of there are no params at all, the method shouldn't be called.
Can you check the task flow for a managed bean that uses the QueryBindParams class and see how the params are configured?
all of these are domains in JHS (upgraded to 11.1.13 from 10), used for dropDownList items, so I'm pulling them from the AppService-Domains-beans.xml file. There are several that are throwing the same error, all of them are nested lists (they depend on the value in another dropdown list). All of them have roughly the same managed-bean definition. We do have plans to change these over to adf-model choicelists instead, so this may become a moot issue, but that could be a couple of months out.
Actually, come to think of it, this could be a data issue. We have records in the database that were imported from legacy systems and they do not have values that match anything in the code set for the parent dropdown, causing the parent dropdown to display as blank. Would that cause the child dropdown to not get it's appropriate bind parameter. If so, this will be fixed in the next few weeks as we are planning a data audit and update on the legacy records.