Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.1-rc1
-
Component/s: Transport: TCP / UDP / SSL / Multicast
-
Labels:None
-
Environment:
Mule 1.1-SNAPSHOT, JDK 1.4.1
-
Similar Issues:None
Description
From Guillaume's research;
"I made some tests yesterday and found some problems.
These problems with huge data tranfer comes from the fact
that there is no defined protocol above the tcp socket.
The TcpReceiver / TcpDispatcher#receive read data from
the socket as long as there are some data available. When there
is no data left, it routes the received data into mule.
If there is a delay, the whole data will not be received and it will be
truncated.
I think the solution is to be able to plug a user-defined mechanism to
detect
the end of messages. The simpliest way would be to send the length of
the content
first, and for the receiver to read it.
I'll trying some more tests to configure the socket (buffer size,
so_linger ...) and see
if it changes.
"
All old Resolved issues transitioned into a Closed state.