We are seeing the following warning:

2018-03-26 11:50:45.703-0700 [RingBufferThread - default] WARN c.s.s.a.liveview.LiveViewDelete - dropPreviousControversyHistoryData: QueryName: dropPreviousControversyHistoryData got exception: Max queries per session '100' exceeded

What is it and how to get rid of it?

We are getting "2018-03-26 11:50:45.703-0700 [RingBufferThread - default] WARN c.s.s.a.liveview.LiveViewDelete - dropPreviousControversyHistoryData: QueryName: dropPreviousControversyHistoryData got exception: Max queries per session '100' exceeded " What is it and how to get rid of it

All supported platforms

There is a limit of maximum number of queries from single client on server side. This limit protects the server from a single client issuing a huge number of queries.
The default maximum number of queries is 100. It is unusual to hit this limit. User should first identify if it is expected a single client to have 100 queries.

There are many other ways to organize deletion activity in a LV table. Please see our KB article:
https://community.tibco.com/wiki/what-are-all-possible-ways-delete-rows-liveview-table

If it is expected a single client to issue X queries in a session, the server limit can be raised by setting:
       liveview.max.queries.per.session=X
You can set this in the LiveView project's sbd.sbconf under the java-vm section, where X is an integer value. For example:

<java-vm>
         <sysproperty name="liveview.max.queries.per.session" value="1000"/>
</java-vm>

You can also throttle your delete activity to fewer events by grouping deletes into a query with a predicate like:

id_column IN ['id1','id6','id92']

where the list of ID's may be 100s of elements long.