Diagnosing Connection Problems

The most common connection problems are usually related to messages, and the methods in the previous section can be used. However, connection-related problems can also involve the improper use of callbacks. As discussed earlier, RTmon cannot be used to debug direct peer-to-peer connections that do not use RTserver.

Receiving Unwanted Messages

When a message is processed with TipcConnMsgProcess and there are no connection process callbacks for messages of that type and no connection default callbacks, TipcConnMsgProcess silently does nothing with the message. This is called an unwanted message. Receiving a large number of unwanted messages can noticeably slow processes. It is always a good practice to use TipcConnDefaultCbCreate to create a connection default callback that calls TipcMsgPrintError for unwanted messages. The output from TipcMsgPrintError is similar to:

WARNING: Received unwanted message at time 19. 
type = numeric_data 
sender = </_workstation.talarian.com_5031> 
sending server = </_workstation.talarian.com_4982> 
dest = </eps> 
max = 2048 
size = 64 
current = 0 
read_only = false 
priority = 0 
delivery_mode = best_effort 
ref_count = 1 
seq_num = 0 
resend_mode = false 
user_prop = 0 
data (num_fields = 4): 
  str "y" 
  real8 2 
  str "z" 
  real8 3