This document describes the message sequence for publishing a track and automatic internal subscription in the red5-moq-relay server.
%%{init: {'theme':'base', 'themeVariables': {'fontSize':'16px', 'fontFamily':'arial'}}}%%
sequenceDiagram
participant Publisher as Publisher Client
| <%@ page import=" | |
| org.apache.mina.core.buffer.IoBuffer, | |
| org.springframework.context.ApplicationContext, | |
| org.springframework.web.context.WebApplicationContext, | |
| com.red5pro.media.SourceType, | |
| com.red5pro.override.IProStream, | |
| com.red5pro.override.ISideStream, | |
| com.red5pro.override.ProStream, | |
| com.red5pro.override.io.ConnectorShell, | |
| com.red5pro.plugin.Red5ProPlugin, |
To provide exclusion for WISH URI, add this to your web.xml as well if you're adding security to live
<!-- Public resources: explicitly marked as accessible -->
<security-constraint>
<web-resource-collection>
<web-resource-name>No auth area</web-resource-name>
<url-pattern>/whip/*</url-pattern>
<url-pattern>/whep/*</url-pattern>
Change log for WsSession leak in Red5; new version 2.0.16 released 4/23/2025
The leak was primarily seen during regular use of Red5 Pro's RTC client which uses a WebSocket for the initial connection with a switch to DataChannel if accepted / configured in the RTC client during startup.
Classes modified:
WeakReference to the WebSocketScope itself and marked final. In the ctor the scope is also added to the WsSession user properties for consolidated access within Tomcat. Several timeout properties were also added from the latest Tomcat 11.x documentation: BLOCKING_SEND_TIMEOUT our default to 8000ms, ABNORMAL_SESSION_CLOSE_SEND_TIMEOUT our default 10000ms, SESSION_CLOSE_TIMEOUT our default 5000ms. The properties are standard for Tomcat and may be modified at-will via system property override; all values are long type in milliseconds. The maximum idle timeout is now configured to use the largest
Red5 updated its slf4j and logback libraries recently to address security vulnerabilities; in doing so, this broke the old code in Red5 open source logging that allowed the separation of logging into additional contexts such as those used by custom webapps and Red5 Pro cloudstorage. The symptom of which was difficult to catch since it just prevented logging without any indication. Currently, the only work-arounds are to replace the logger libraries with the older versions or replace every use of Red5LoggerFactory with the SLF4J default interface LoggerFactory; the SLF4J factory does not accept a context. Here is an example:
/*
* The recent updates for SLF4J prevents Red5 logger factory use of a context,
* it does not work in the latest Red5 open source libraries. We suggest a
* replacement in the interim.
*/
This document assumes that you've upgraded to 12.x of Red5 Pro prior to any patches addressing custom Red5 application scope handling. To get your application working, follow the steps below:
<dependency>
<groupId>com.red5pro</groupId>
<artifactId>red5pro-common</artifactId>
<version>12.0.1.0</version>
<scope>compile</version>
In conf/red5-common.xml the MP3 and M4A entries must be removed to prevent startup exceptions, unless an MP3/M4A support jar is included in the classpath (Not yet available). Remove or comment out the following entries from the streamableFileFactory bean:
<bean id="mp3FileService" class="org.red5.server.service.mp3.impl.MP3Service"/>
<bean id="m4aFileService" class="org.red5.server.service.m4a.impl.M4AService"/>Remove this entire bean entry: