More > JRiver Media Center 31 for Linux

JRiver Panel/MCWS stops serving over HTTPS after a large amount of requests

(1/3) > >>

danrien:
When running MC31 on Linux, if I access a large playlist containing a few hundred to 1000 items over HTTPS in Panel and scroll quickly through it, MCWS stops serving requests until I restart MC. Over HTTP this works as expected. My host PC is running Ubuntu 22.04.3 LTS.

Hendrik:
Can you post a log of this happening?

danrien:
Sure... where can I find these log files?

Hendrik:
Enable logging in the Help menu, then reproduce the issue and you can find the log in ~/.jriver/Media Center 31

danrien:
There's a lot of initialization things going on, but I think the interesting piece is here:

0018053: 139774794913472: Sharing Plugins: JRWebService::Process: Finish (157 ms)
0018053: 139774794913472: Sharing Plugins: VHTTPMessage::Write: Wrote 2460 bytes
0018064: 139774794913472: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
0018064: 139774794913472: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (218 ms)
0018064: 139774794913472: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 26
0018333: 139775296251840: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 25
0018585: 139774794913472: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0018635: 139774794913472: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.1.73: GET: https://192.168.1.2:52200/MCWS/v1/File/GetInfo?File=6693057
0018637: 139774794913472: Sharing Plugins: JRWebService::Process: Start
0018637: 139774794913472: Sharing Plugins: JRWebService::Process: URL: /MCWS/v1/File/GetInfo?File=6693057
0018638: 139774794913472: Sharing Plugins: JRWebService::Process: Finish (1 ms)
0018638: 139774794913472: Sharing Plugins: VHTTPMessage::Write: Wrote 2330 bytes
0018660: 139774794913472: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
0018660: 139774794913472: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (74 ms)
0018660: 139774794913472: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 17
0018731: 139774794913472: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0018743: 139774794913472: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.1.73: GET: https://192.168.1.2:52200/MCWS/v1/File/GetInfo?File=6725319
0018745: 139774794913472: Sharing Plugins: JRWebService::Process: Start
0018745: 139774794913472: Sharing Plugins: JRWebService::Process: URL: /MCWS/v1/File/GetInfo?File=6725319
0018746: 139774794913472: Sharing Plugins: JRWebService::Process: Finish (1 ms)
0018746: 139774794913472: Sharing Plugins: VHTTPMessage::Write: Wrote 2572 bytes
0018773: 139774794913472: Sharing Plugins: CTCPSocketReader::Read: Read failed: Connection reset by peer (104) (socket: 25)
0018773: 139774794913472: Reader: CTLSSocketReader::Read: Read failed: The TLS connection was non-properly terminated.
0018773: 139774794913472: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
0018773: 139774794913472: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (41 ms)
0018773: 139774794913472: Sharing Plugins: CTCPSocketReader::Write: Write failed: Broken pipe (32) (socket: 25)
0018773: 139774794913472: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 25
0018814: 139775121405632: Sharing Plugins: CTCPSocketReader::Write: Write failed: Broken pipe (32) (socket: 26)
0018814: 139775121405632: Sharing Plugins: CTCPSocketReader::Write: Write failed: Broken pipe (32) (socket: 26)
0018814: 139775121405632: Sharing Plugins: CTCPSocketReader::Write: Write failed: Broken pipe (32) (socket: 26)
0018814: 139775121405632: Sharing Plugins: CTCPSocketReader::Write: Write failed: Broken pipe (32) (socket: 26)
0018814: 139775121405632: Sharing Plugins: CTCPSocketReader::Write: Write failed: Broken pipe (32) (socket: 26)
0018814: 139775121405632: Sharing Plugins: CTCPSocketReader::Write: Write failed: Broken pipe (32) (socket: 26)

The broken pipe message then repeats ad infinitum... I've attached the full log (sans the repeated broken pipe messages, which quickly goes into the many megabytes in size).

Navigation

[0] Message Index

[#] Next page