Closed GoogleCodeExporter closed 9 years ago
This problem is now has dirty workaround:
log.debug("Context initialized: {}", servletContext.getContextPath());
ctx.setPrivileged(true); <===add this line in TomcatLoader
//set the hosts id
servletContext.setAttribute("red5.host.id", getHostId());
I believe that it should be replaced with ctx.setDefaultContextXml to load
correct context.xml under META-INF folder of a certain webapp
Original comment by Stif...@gmail.com
on 9 Jun 2013 at 8:14
This has to do with using the Tomcat manager, which we have never supported.
Its great that you have a workaround, but its not something we will add at this
time. Be aware that the tomcat manager has no understanding of a red5
application nor does it know that the red5 app has to be initialized prior to
starting its own context.
Original comment by mondain
on 9 Jun 2013 at 4:26
I update to the latest red5 from trunk (August 29th) and the war files in the
webapps directory are extracted (the directory for the app is created) but the
launcher doesn't launch the apps. The war files don't get deleted as well. I
have to stop and restart the red5 server for it to work and I'll get the
message the app is already installed. logs is attached. Issue occurs even with
the oflaDemo app. To reproduce drop the war files to the webapps directory and
start red5. I would appreciate any help.
2013-09-13 11:27:52,471 [main] INFO o.a.catalina.core.StandardEngine -
Starting Servlet Engine: Apache Tomcat/7.0.41
2013-09-13 11:28:11,129 [Red5_Scheduler_Worker-2] WARN
org.red5.server.service.WarDeployer - Loader not found
Original comment by jdn...@gmail.com
on 13 Sep 2013 at 9:23
Attachments:
We don't support tomcat manager see #2
Original comment by mondain
on 13 Sep 2013 at 9:53
Original issue reported on code.google.com by
Stif...@gmail.com
on 8 Jun 2013 at 2:09