Pool runs out of packets in case of a high loaded server configuration

In case the stack is configured as Server and is configured to open more server sockets - in this case 16 - it might happen that the pool runs out of packet

The reason for the behavior is that when the stack send open requests to the tcp stack and the tcp stack returns a confirmation then the Omb immediately sends a wait connect request before releasing the packet from the open confirmation. In some heavy loaded situations this might lead to the pool being run out