+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 16

Thread: "Attempted to send unsupported ClientMessage to RTMP client" [ES 5.3.2]

  1. #1
    Member
    Join Date
    Mar 2012
    Posts
    44
    Thanks
    8
    Thanked 1 Time in 1 Post

    "Attempted to send unsupported ClientMessage to RTMP client" [ES 5.3.2]

    Already posted at http://www.electrotank.com/forums/sh...ight=RTMP+WARN

    I'm having a similar issue. In my software, a client streams the webcam video and audio to multiple clients.

    When I'm playing the stream in a client I'm getting this warning for each message sent to that client (I only send messages at the server level):

    14:03:02,439 [New I/O server worker #1-19] WARN com.electrotank.electroserver5.protocol.rtmp.Clien tMessageSupportFilter - Attempted to send unsupported ClientMessage to RTMP client. com.electrotank.electroserver5.messages.client.eve nt.ClientPluginMessageEvent@15bab52 to (SOCKET, R: /127.0.0.1:50079, L: /127.0.0.1:1935, S: /0.0.0.0:1935)

    However, if nobody is playing the stream, the messages sent to the client publishing it don't print warnings.

    ElectroServer 5.3.2

  2. #2
    Administrator tcarr's Avatar
    Join Date
    Dec 2007
    Posts
    7,214
    Thanks
    80
    Thanked 1,087 Times in 1,076 Posts
    Thanks for the bug report. I'll add a ticket to our system. Would you be willing to send me a zip of your project so that I can reproduce the issue quickly?
    Teresa Carrigan
    Senior Engineer
    Electrotank, Inc.

  3. #3
    Member
    Join Date
    Mar 2012
    Posts
    44
    Thanks
    8
    Thanked 1 Time in 1 Post
    My project has a very complicated setup... and I don't know if my client would like the idea of sending it... :\

    It is easer to make a simple test with two clients. Let both of them join a persistent room with a plugin. One of the clients should publish the camera video in a stream named "something" and in the other play the stream "something". In the server, just send a plugin message to the room, every second or so.

    I'm kind of busy now, otherwise I would have provided you with an example.

    Hope it helps.

  4. #4
    Administrator tcarr's Avatar
    Join Date
    Dec 2007
    Posts
    7,214
    Thanks
    80
    Thanked 1,087 Times in 1,076 Posts
    It sounds as if the plugin might be sending plugin messages using RTMP instead of using TCP.

    It's going to be quite some time before we can address this bug unless we have a client to use to test it with.
    Teresa Carrigan
    Senior Engineer
    Electrotank, Inc.

  5. #5
    Member
    Join Date
    Mar 2012
    Posts
    44
    Thanks
    8
    Thanked 1 Time in 1 Post
    1) At the server side, I'm sending the messages as usual (using the plugin methods). Should I setup something at the server side?

    2) At the client side, I'm using the method send(message:EsMessage, con:Connection) with 'con' being a BinaryTCP connection.

    3) You have the RecordExample to test.

  6. #6
    Administrator tcarr's Avatar
    Join Date
    Dec 2007
    Posts
    7,214
    Thanks
    80
    Thanked 1,087 Times in 1,076 Posts
    I'll see what I can do.
    Teresa Carrigan
    Senior Engineer
    Electrotank, Inc.

  7. #7
    Administrator tcarr's Avatar
    Join Date
    Dec 2007
    Posts
    7,214
    Thanks
    80
    Thanked 1,087 Times in 1,076 Posts
    Question: is your plugin sending a plugin message to the room, or to individual users?
    Teresa Carrigan
    Senior Engineer
    Electrotank, Inc.

  8. #8
    Member
    Join Date
    Mar 2012
    Posts
    44
    Thanks
    8
    Thanked 1 Time in 1 Post
    1) I'm sending plugin messages to a room.

    2) I also send public messages to a room from a client (I'm using this to implement chat), which causes the warning too.

  9. #9
    Administrator tcarr's Avatar
    Join Date
    Dec 2007
    Posts
    7,214
    Thanks
    80
    Thanked 1,087 Times in 1,076 Posts
    Thanks! I'll see if we can figure out how to fix it.
    Teresa Carrigan
    Senior Engineer
    Electrotank, Inc.

  10. #10
    Administrator tcarr's Avatar
    Join Date
    Dec 2007
    Posts
    7,214
    Thanks
    80
    Thanked 1,087 Times in 1,076 Posts
    I have reproduced this bug in part. I'm not seeing any problem with plugin messages, but both with and without a plugin attached to the room, if a user sends a public message request, the warning appears in the server logs. The message does go out; I have to assume that the server is trying to send it on both TCP and RTMP channels (or possibly first on the RTMP channel and then on TCP).

    Still haven't found the part of the server code that decides which channel to use for sending.
    Teresa Carrigan
    Senior Engineer
    Electrotank, Inc.

+ Reply to Thread

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts