TIBCO Streaming UDP Receiver Adapter message "Timeout waiting for packet, continuing with run loop"
Article ID: KB0073506
Updated On:
| Products | Versions |
|---|---|
| TIBCO Streaming | 10.x |
Description
Our streaming application is deployed on PaaS(Openshift) environment using a UDPReceiver adapter in our streaming application. In the console logs, with logs set at Trace level, we see messages like "Timeout waiting for a packet, continuing with run loop" continuously. We see a continuous increase in this message in the logs and also an increased receive Buffer Size from 1024 to 16777216. It didn't help us to solve the issue as these messages filled the logs.
Issue/Introduction
When UDP receiver adapter waits for incoming data, It prints message as "Timeout waiting for packet, continuing with run loop" in logs continuously
Environment
Production
Resolution
The issue here is that the application was run at TRACE level instead applications should only be run at INFO level logging, even when troubleshooting. You may set a few adapters to DEBUG logging for more information when troubleshooting an issue. TRACE level logging in TIBCO Streaming is very verbose and should only be used when advised by TIBCO Technical Support. Specifically for this issue, the problem was that TRACE level logging was used inappropriately and the repeated message does not indicate a problem but correct functioning of the adapter.
As seen below, Whenever you run the application at the TRACE level, You would see the below message which states that the adapter is not receiving the incoming data for the timeframe as per its functionality. Hence as mentioned above, Please run the applications at the INFO level.
As seen below, Whenever you run the application at the TRACE level, You would see the below message which states that the adapter is not receiving the incoming data for the timeframe as per its functionality. Hence as mentioned above, Please run the applications at the INFO level.
Feedback
Yes
No
Powered by
