So, we have a WebRTC enabled app that is actually working in the sense that it's establishing sessions, we're able to connect to them, people are publishing streams, other people are subscribing and unsubscribing to those streams, etc. etc. But we keep getting errors from WebRTC which say 'PeerConnection.getStats. Already getting the stats!' The error occurs in the video stream itself. White text on a black background, instead of the video.
Also, in the console log, we're getting the following errors:
Uncaught TypeError: Cannot call method 'getStats' of undefined TB.min.js:208
PeerConnection.getStats: Already getting the stats! TB.min.js:54
Subscriber State Change Failed: 'Failed' cannot transition to 'NotSubscribing' TB.min.js:54
Object
TB.min.js:54
Sending WebSocket message: {"type":1016,"payload":{"streamId":"995827218","fromAddress":"d5e52bf2-03fb-4e3d-885f-297d4d243684","toAddresses":"d5c1a7d8-f70c-44f3-a42c-1c40bab803ca"}} TB.min.js:54
TB.exception :: title: Connection Failed (1013) msg: Subscriber PeerConnection Error: PeerConnection.getStats: Already getting the stats! TB.min.js:54
Subscriber State Change Failed: 'Failed' cannot transition to 'NotSubscribing' TB.min.js:54
Object
TB.min.js:54
Sending WebSocket message: {"type":1016,"payload":{"streamId":"995827218","fromAddress":"d5e52bf2-03fb-4e3d-885f-297d4d243684","toAddresses":"d5c1a7d8-f70c-44f3-a42c-1c40bab803ca"}} TB.min.js:54
TB.exception :: title: Connection Failed (1013) msg: Subscriber PeerConnection Error: PeerConnection.getStats: Already getting the stats! TB.min.js:54
Subscriber State Change Failed: 'Failed' cannot transition to 'NotSubscribing' TB.min.js:54
Object
TB.min.js:54
Sending WebSocket message: {"type":1016,"payload":{"streamId":"995827218","fromAddress":"d5e52bf2-03fb-4e3d-885f-297d4d243684","toAddresses":"d5c1a7d8-f70c-44f3-a42c-1c40bab803ca"}} TB.min.js:54
TB.exception :: title: Connection Failed (1013) msg: Subscriber PeerConnection Error: PeerConnection.getStats: Already getting the stats!
Any ideas on what might be causing this? How do we turn off PeerConnection from polling stats????? Thanks in advance for any suggestions!
I haven't seen this before, but if I were to guess this is probably because you were subscribing multiple times to the same stream before it was done subscribing.
Related
2022-09-14T07:37:21.040Z - error: [DiscoveryResultsProcessor]: parseDiscoveryResults[User] - Channel:mychannel received discovery error:failed constructing descriptor for chaincodes:<name:"User" >
Failed to submit transaction: Error: DiscoveryService: User error: failed constructing descriptor for chaincodes:<name:"User" >
when I hit API from post man i receive this error
This error usually comes when the chaincode name given is wrong. Make sure the chaincode('User' in this case) is committed to channel mychannel before sending transactions using SDK.
While making a network request with low connectivity very rarely I see that I get
<-- HTTP FAILED: java.net.UnknownHostException: Unable to resolve host ....
while my server seems to have got the request correctly. I found 1 instance of it with device logs which shows actually an SSLException happened
D/NativeCrypto: jniThrowException: javax/net/ssl/SSLException: Read error: ssl=0x7dc365f080: I/O error during system call, Software caused connection abort
D/NativeCrypto: jniThrowException: javax/net/ssl/SSLException: SSL shutdown failed: ssl=0x7dc365f080: I/O error during system call, Broken pipe
My question is why does okhttp and retrofit throw UnknownHostException and not SSLException, and is there a way to actually get the SSLException as currently my app thinks the request did not go while server processes that request.
I am using
okhttp:3.10.0
retrofit:2.2.0
adapter-rxjava2:2.2.0
I'm trying to get a Labview VI working. However, I'm getting an error on the KE6485 Multi-read sub-VI with the error "Driver Status: (Hex 0xBFFF004A) Error - A service request has not been received for the session". Does anyone have a suggestion on steps I could take to fix this?
We have seen much more SSL error than before when we move to a new server. The total SSL error rate is not high. Many of them are:
error:140943E8:SSL routines:SSL3_READ_BYTES:reason(1000):s3_pkt.c:1256:SSL alert number 0
We finally found these requests are actually successful requests. Why these error was generated is that openssl found these were fatal error. Add more debug info show that:
ssl_callback_info:SSL_CB_READ_ALERT fatal error close notify
But from rfc2246:
7.2.1. Closure alerts
The client and the server must share knowledge that the connection is
ending in order to avoid a truncation attack. Either party may
initiate the exchange of closing messages.
close_notify
This message notifies the recipient that the sender will not send
any more messages on this connection. The session becomes
unresumable if any connection is terminated without proper
close_notify messages with level equal to warning.
We are wondering if there some special clients send "alert 0" as fatal . Or this related some known issue of openssl. We are using openssl-1.0.1e now. Before migration we used openssl-1.0.0-25.
Any suggestions would be appreciated.
Update:
I investigated the access log and found almost all the "fatal alert 0" was sent by Safari on Apple devices(Mac, iPhone, iPad).
Through the code of libsecurity_ssl which the library of SSL engine. I found that this library would send "fatal alert 0" in sometimes that was totally different with other SSL libraries, for example openssl, NSS.
SSLFatalSessionAlert(SSL_AlertCloseNotify, ctx);
http://www.opensource.apple.com/source/libsecurity_ssl/libsecurity_ssl-32463/lib/sslRecord.c
This mostly occurred when Safari meet unexpected abort of the connection. As my server would not sent a "warning alert 0" to close the connection.
I have a receive port with a WCF-CustomIsolated receive location.
On receive port I checked "Enable routing for failed messages".
In pipeline settings I have set ValidateDocument to true.
When a client sends me an incorrect schema, it receives a validation error (that happened in pipeline) and it's OK.
But it's not routed as a fault message to message box.
Could you help me why does it happen?
Why "routing for failed messages" does not work in this case? And in what cases it should work?
Thank you!
On the Receive Location, go the Transport Properties, Messages, Error Handling, and check Suspend request message on failure.
Even though it says "Suspend" checking this in combination with the Routing for Failed Message on the Receive Port will actually create a FailedMessage that you are after. (If Routing for Failed Message isn't enabled it will suspend).
This applies to all the WCF adapters, not just the CustomIsolated one.
You need to subscribe to the error message. You could use a send port or orchestration with a filter set to the receive port, message type and/or message error.