Troubleshooting: TCP UDP sockets

Review the common questions and issues that can arise when you are using TCP and UDP transports.

No messages are received

Verify the packetizer settings. If they are wrong, then the incoming stream of data cannot be broken up properly and it cannot be presented to the subscriber.

The last message is not received

If no end token is specified when you are using the token-based packetizer, packets will be determined by awaiting the next start token. This means that each message is presented to the subscriber when a subsequent message is received.

Bind error

When run as a server, the transport opens a listener on the specified port. If another process or another transport is started listening on this port, then a collision occurs. This results in a bind error that is reported to the user.

You need to stop the other process that is using the port or configure the other transport to use a different value.


Feedback