Testing SSE not working

[digitalml]

Trying to test a node js express service that I've implement server-sent events in but I am not getting any results and I'm not sure why.

During the test I can see siege connect 10 connections to the sse service and the node js log shows that the node service is sending data through the open sse connections. When the siege ends I see the node sse service close the connections.

If I connect with curl or browser then everything works as expected and data from the node sse service is received.

siege does not seem to output any verbose data. i would assume that means it isn't receiving anything?

i've tried changing connection = keep-alive in the siege.config file thinking that might do something but it did not.

This is the siege command I am using:
siege --verbose -b -t30s -c10 http://192.168.1.20:3000/sse

The results are:
Lifting the server siege...
Transactions: 0 hits
Availability: 0.00 %
Elapsed time: 29.80 secs
Data transferred: 0.00 MB
Response time: 0.00 secs
Transaction rate: 0.00 trans/sec
Throughput: 0.00 MB/sec
Concurrency: 0.00
Successful transactions: 0
Failed transactions: 0
Longest transaction: 0.00
Shortest transaction: 0.00

The log shows:
Date & Time, Trans, Elap Time, Data Trans, Resp Time, Trans Rate, Throughput, Concurrent, OKAY, Failed
2021-12-12 21:43:30, 0, 29.83, 0, nan, 0.00, 0.00, 0.00, 0, 0

Any help would be greatly appreciated. Thank you.

[jg33]

any updates on this front?

[JoeDog]

Try -p/--print to see the content siege --print www.google.com

…

On Mon, Dec 13, 2021 at 12:49 AM digitalml ***@***.***> wrote: Trying to test a node js express service that I've implement server-sent events in but I am not getting any results and I'm not sure why. During the test I can see siege connect 10 connections to the sse service and the node js log shows that the node service is sending data through the open sse connections. When the siege ends I see the node sse service close the connections. If I connect with curl or browser then everything works as expected and data from the node sse service is received. siege does not seem to output any verbose data. i would assume that means it isn't receiving anything? i've tried changing connection = keep-alive in the siege.config file thinking that might do something but it did not. This is the siege command I am using: siege --verbose -b -t30s -c10 http://192.168.1.20:3000/sse The results are: Lifting the server siege... Transactions: 0 hits Availability: 0.00 % Elapsed time: 29.80 secs Data transferred: 0.00 MB Response time: 0.00 secs Transaction rate: 0.00 trans/sec Throughput: 0.00 MB/sec Concurrency: 0.00 Successful transactions: 0 Failed transactions: 0 Longest transaction: 0.00 Shortest transaction: 0.00 The log shows: Date & Time, Trans, Elap Time, Data Trans, Resp Time, Trans Rate, Throughput, Concurrent, OKAY, Failed 2021-12-12 21:43:30, 0, 29.83, 0, nan, 0.00, 0.00, 0.00, 0, 0 Any help would be greatly appreciated. Thank you. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#202>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJRHZU5BZ5J6P4XVMYOQQTUQWCNZANCNFSM5J5IJDBA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- Jeff Fulmer 1-717-799-8226 https://www.joedog.org/ He codes