Based on your numbers it's probably not ephemeral port exhaustion. The
default TIME_WAIT is 4 minutes on Solaris, and to use up 32,767 sockets
within 4 minutes, you'd need you to be sending an average of 136 messages
per second.
Jim
On Fri, 11 Mar 2016 07:19:27 -0700, Tim Bain
wrote:
>I thought TIME_WAIT was the state after the application had closed the
>socket but before the OS had disposed it, so this may be a Solaris question.
My understanding (which may be wrong) is that the end which initiated
the closedown may end up
On Fri, 11 Mar 2016 14:53:09 +, "James A. Robinson"
wrote:
>The TIME_WAIT state indicates both sides of the connection have shut down
>the socket cleanly and now the OS is waiting for some period of time before
>it will allow that socket to be reused. This is to prevent the
>possibility of
The TIME_WAIT state indicates both sides of the connection have shut down
the socket cleanly and now the OS is waiting for some period of time before
it will allow that socket to be reused. This is to prevent the
possibility of a delayed packet on a previous session corrupting a
subsequent sessio
I thought TIME_WAIT was the state after the application had closed the
socket but before the OS had disposed it, so this may be a Solaris question.
On Mar 11, 2016 4:55 AM, "spamtrap"
wrote:
> On Thu, 10 Mar 2016 16:13:32 +, "James A. Robinson"
> wrote:
>
> It happens infrequently and unpred
On Thu, 10 Mar 2016 16:13:32 +, "James A. Robinson"
wrote:
It happens infrequently and unpredictibly. For example sometimes it
fails after 25 times and sometimes it works for several 100 before
going wrong.
Another thing is that program works OK on Linux. It's only on Solaris
that this pro
You don't say how frequently it performs this action? If it is frequent,
and I were debugging it, the first thing I would check for would be that
you haven't run out of socket filehandles. On a unix system running
something like "netstat -nt" can tell you what state the socket filehandles
are in.
On 03/10/2016 10:37 AM, spamtrap wrote:
[ActiveMQ-CPP v3.9.0]
We have a c++ program which connects to a broker, sends a message to a
topic and then closes the connections & exits. Every now and then it
fails to connect reporting a "Address already in use" exception
(based on ex.what()).
The co
[ActiveMQ-CPP v3.9.0]
We have a c++ program which connects to a broker, sends a message to a
topic and then closes the connections & exits. Every now and then it
fails to connect reporting a "Address already in use" exception
(based on ex.what()).
The code is like this:
- cut --
try
