Sterling Integrator JMS Adapter Issue in consuming messages

There is an issue that happens when an outside source sends a file with a “null” message inside the message body to the B2Bi JMS adapter: the Sterling JMS adapter process is going into an endless loop when receiving the Null value inside the body of a client file.

jms.log in debug showed messages stuck on JMS TIBCO queue are null messages. (Text=null)

The adapter is failing to read/understand how to handle the “null” messages, therefore produces the endless loop error. After a restart the adapter only has a few messages that are read/understood and processed. Is there any way to avoid the continual loop response that is currently how the application works (which can end up with so many error responses that it ends up crashing the system/database) and make it so that when the “null” message is received that a single error message is produced instead of the continual error loop?

Support has stated to work with the customer and the producing application which would change the incoming message body from “null” to empty as the fix. However, we would like to see this “null” in the message body treated as a bug with an alternate option for a “null” message body that would, instead of causing an endless loop of continually produced error messages, produce one single error message and possibly a notification alert that the error occurred