Hello Sven, as mentioned before this has nothing to do with tomcat, your rmi servant inside tomcat will manage its threads by himself without tomcat manager having a chance to notice. For the second question, I highly doubt there is a servlet container there which cares for RMI, but why should there be any?
On an architectural note, you probably should take a look into embedded tomcat, since in your case tomcat is just a connector to your app with equal rights as rmi and others, and not the center of the universe it usually considers himself to be. regards Leon On Sun, Oct 26, 2008 at 1:40 PM, Sven A <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm looking at options in running our standalone RMI application within a > servlet container since we're planning to build support for http. I'm > currently testing our app on Tomcat 5.5 and my question is if Tomcat by > default actually dispatch incoming RMI calls to different threads. Looking > at the server stats in Tomcat manager it doesn't seem to be the case in > terms of active number of threads etc. > > My second question is if there are servlet containers out there that has > support for RMI connectivity and can dispatch incoming requests. > > Thanks > S > -- > View this message in context: > http://www.nabble.com/Tomcat-5.5-and-RMI-tp20173054p20173054.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
