Community
Participate
Working Groups
The code to run Jetty and Tomcat in embedded mode, uses constructs that won't work when running in OSGi. One prominent example is passing class names as strings. We should try to replace these passages with API from Jetty/Tomcat that accepts classes or instances (if any).
Both Jetty and Tomcat run on Eclipse Virgo with no problems, you could try running on top of Virgo.
(In reply to comment #1) > Both Jetty and Tomcat run on Eclipse Virgo with no problems, you could try > running on top of Virgo. Christopher, thanks for your hint. We are aware that Jetty and Tomcat run on Virgo. However, with 'cluster' in this context, we mean transparent session failover. Do Jetty and/or Tomcat on Virgo support this? Is there a some sort of documentation how to set this up?
Hi, We've never tried it with Jetty so I don't know but Tomcat clustering on Virgo is supported and configured in the normal way. The Tomcat config file is located in the config directory. Just refer to the Tomcat documentation for it, essentially Virgo isn't involved and doesn't get in the way. Chris.
(In reply to comment #3) > We've never tried it with Jetty so I don't know but Tomcat clustering on Virgo > is supported and configured in the normal way. The Tomcat config file is located > in the config directory. Just refer to the Tomcat documentation for it, > essentially Virgo isn't involved and doesn't get in the way. There seems to be a misunderstanding. We deployed an RFC 66 web bundle on Virgo-Tomcat with clustering configured (SimpleTcpCluster). In this scenario we also get a ClassNotFoundException. The first class from the web bundle cannot be found. A similar setup (plain Jetty on OSGi running a web bundle), is described in bug 361554. If you think this should work on Virgo, we can file a bug and provide details and a setup to reproduce the exception.
Hi, I suspect it might be down to configuration in Virgo but please do raise a bug on us and we will have a look. It should work even if a little config change is needed. Thanks, Chris.
(In reply to comment #5) > Hi, > > I suspect it might be down to configuration in Virgo but please do raise a bug > on us and we will have a look. It should work even if a little config change is > needed. > > Thanks, Chris. Thanks for looking into this, I filed bug 361971