You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.Why peer connect to other peer always report the Tomp2pCumulationTCP [ERROR] - exception in decoding TCP, not started decoding.
2.There are 3 peers connected and added file,when the fourth peer connect to the network, the Tomp2pCumulationTCP [ERROR] - OutOfMemroy : Direct buffer memory is reproted. And sometimes, there are Tomp2pCumulationTCP [ERROR] - exception in decoding TCP, Occurred bofore or after started decoding.
The text was updated successfully, but these errors were encountered:
This is most likely due to a "connection reset by peer". Since TomP2P
terminates connections with a RST, you'll see these exceptions.
Unfortunately in Java, its not possible to filter out those messages.
How big is the file?
On 08/28/2015 03:18 PM, Agony wrote:
1.Why peer connect to other peer always report the Tomp2pCumulationTCP
[ERROR] - exception in decoding TCP, not started decoding.
2.There are 3 peers connected and added file,when the fourth peer
connect to the network, the Tomp2pCumulationTCP [ERROR] - OutOfMemroy :
Direct buffer memory is reproted. And sometimes, there are
Tomp2pCumulationTCP [ERROR] - exception in decoding TCP, Occurred bofore
or after started decoding.
—
Reply to this email directly or view it on GitHub #108.
1.Why peer connect to other peer always report the Tomp2pCumulationTCP [ERROR] - exception in decoding TCP, not started decoding.
2.There are 3 peers connected and added file,when the fourth peer connect to the network, the Tomp2pCumulationTCP [ERROR] - OutOfMemroy : Direct buffer memory is reproted. And sometimes, there are Tomp2pCumulationTCP [ERROR] - exception in decoding TCP, Occurred bofore or after started decoding.
The text was updated successfully, but these errors were encountered: