![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• The "bottom-up" approach generally seems best. That is, get the lowest layers of the network stack working first.
•
•
• Ensure that the channel's ttl is large enough for data to cross all of your switches and routers.
•
• When the multicast daemon detects excessive loss, the multicast connection exception IO Failed is generated in the application. Usually, this means that the server is sending too fast, and maxrate for the channel needs to be decreased. The multicast daemon will report an error, similar to the following:You will also notice in the multicast statistics that the particular channel's rcv_losses are growing.
• If a consumer receives a multicast exception of TIBEMS_TIMEOUT with a message similar to Timeout reached which may indicate a configuration or hardware problem, this indicates a lack of multicast connectivity. While unicast connectivity exists between the client and server and the multicast channel was set up, multicast data cannot get from the server to the local multicast daemon. Note that this may take more than a minute to detect.
• Start a subscriber listening to $sys.monitor.multicast.stats monitoring messages to receive multicast-related statistics.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |