Class | Description |
---|---|
AbstractStreamingDownloadMule1389TestCase | |
AbstractTcpSocketToAddressBindingTestCase |
Tests how sockets are bound to addresses by the TCP transport.
|
AsynchMule1869TestCase | |
InputStreamSource | |
KeepSendSocketOpenMule1491TestCase | |
LengthProtocolLengthTestCase | |
LingerExperimentMule2067TestCase |
Are the "address already in use" errors coming from lingering sockets?
We see "address already in use" errors when trying to re-use sockets very quickly,
but the tests below don't give much information, except that:
- data needs to be sent
- explicitly setting or disabling the SO_LINGER value has little effect
|
LingerExperimentMule2067TestCase.Server | |
MultiConnectorMULE3669TestCase | |
MultiStreamMule1692TestCase | |
ReuseExperimentMule2067TestCase |
Can we avoid the "address already in use" errors by using SO_REUSEADDR?
Typical results are
|
ReuseExperimentMule2067TestCase.Server | |
ReuseMule2069TestCase |
This is just to check that the Boolean (rather than boolean) doesn't cause any problems
|
SafeProtocolMule2227TestCase | |
StreamingDownloadMule1389TestCase |
This fails to work as described in the issue, but isn't HTTP...
|
SynchStreamingMule1687TestCase | |
TcpSocketToAddressBindingTestCase |
Tests how sockets are bound to addresses by the TCP transport.
|
TcpSocketToAddressLegacyBindingTestCase |
Tests socket binding with legacy behaviour setting the MULE_TCP_BIND_LOCALHOST_TO_ALL_LOCAL_INTERFACES_PROPERTY to
true.
|
Copyright © 2003–2016 MuleSoft, Inc.. All rights reserved.