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
Simple (low volume) tests worked fine, but as I stressed the system Aeron started receiving corrupt UDP messages via the Goldy tunnel.
In an effort to verify correct operation of individual components, I used nc -ul 40123 > file to capture a file sent through Goldy with cat file | nc -u 127.0.0.1 50123. If this file was small, the shasum proved correct delivery. However larger files resulted in either corrupt delivery, Goldy Client segmentation faults, or Goldy Client assertion errors.
It is possible to produce the following segmentation fault using openssl rand 4027 |nc -u 127.0.0.1 50123. A random size of 4026 does not produce the fault.
I have been testing Goldy Client as an option to fronting Aeron, which uses UDP to transport and reassemble user messages. Configuration:
Simple (low volume) tests worked fine, but as I stressed the system Aeron started receiving corrupt UDP messages via the Goldy tunnel.
In an effort to verify correct operation of individual components, I used
nc -ul 40123 > file
to capture a file sent through Goldy withcat file | nc -u 127.0.0.1 50123
. If this file was small, theshasum
proved correct delivery. However larger files resulted in either corrupt delivery, Goldy Client segmentation faults, or Goldy Client assertion errors.It is possible to produce the following segmentation fault using
openssl rand 4027 |nc -u 127.0.0.1 50123
. A random size of 4026 does not produce the fault.In addition, running
openssl rand 4026 |nc -u 127.0.0.1 50123
with varying delays between each invocation will occasionally lead to:The above was compiled using Goldy Client 4f70c9f.
The text was updated successfully, but these errors were encountered: