TIBCO LogLogic LMI - How to enable and process Jumbo Messages
Article ID: KB0072062
Updated On:
| Products | Versions |
|---|---|
| TIBCO LogLogic Enterprise Virtual Appliance | 6.3.0 and higher |
Description
We can see in some use cases where TIBCO LogLogic Universal Collector 2.9 (or OIAG 3.0.0) - have a Real Time File collector with "Maximum message length" up to 1048576. In this scenario we can see in the LMI messages from that device source that appear incomplete or even with unreadable characters. This will break Customer's reports.
Environment
Linux RHEL
Resolution
To fix this issue, Administrators need to enable Jumbo Messages support in LMI. To do so - Administrators need to edit a configuration file under '/loglogic/conf' folder. The name of the file is 'tcpcoll.conf' and Administrators need to add in a couple of configurations parameters:
UseTcpCollectorQueue
And
MaxMsgLength
The first one - UseTcpCollectorQueue - is a flag that can hold a couple of values, 1 for jumbo messages enabled or 0 for jumbo messages disabled. The second parameter - MaxMsgLength- will hold the max message length value. It should match at least the same value set in Universal Collector. The maximum value supported is 1048576. In UC 2.9 the default value is 64000.
Below is how it looks like the 'tcpcoll.conf' after enabling jumbo messages:
After saving settings we need to restart engines:
For further details check documentation at:
Processing Jumbo Messages
UseTcpCollectorQueue
And
MaxMsgLength
The first one - UseTcpCollectorQueue - is a flag that can hold a couple of values, 1 for jumbo messages enabled or 0 for jumbo messages disabled. The second parameter - MaxMsgLength- will hold the max message length value. It should match at least the same value set in Universal Collector. The maximum value supported is 1048576. In UC 2.9 the default value is 64000.
Below is how it looks like the 'tcpcoll.conf' after enabling jumbo messages:
# cat /loglogic/conf/tcpcoll.conf
#TLSCert=<file_name>
TLSCert=/loglogic/conf/certs/cert1
#TLSKey=<file_name>
TLSKey=/loglogic/conf/certs/key1
#TLSDefaultClientCA=<file_name>
TLSDefaultClientCA=/loglogic/conf/certs/client179.ca
#0100
TLSVerFlags=4
ListenOnPort=4321
# jumbo messages settings
UseTcpCollectorQueue=1
MaxMsgLength=1048576
After saving settings we need to restart engines:
# mtask stop; mtask start
For further details check documentation at:
Processing Jumbo Messages
Issue/Introduction
If jumbo messages are disabled while one source is sending big data Administrator may notice issues in LMI reports.
Feedback
Yes
No
Powered by
