Summary: | Migrate to Jetty6 for working AJP support | ||
---|---|---|---|
Product: | Lenya | Reporter: | J <nettings> |
Component: | Miscellaneous | Assignee: | Lenya Developers <dev> |
Status: | NEW --- | ||
Severity: | major | ||
Priority: | P2 | ||
Version: | Trunk | ||
Target Milestone: | 2.0.1 | ||
Hardware: | Other | ||
OS: | other | ||
Bug Depends on: | 43864 | ||
Bug Blocks: |
Description
J
2007-10-29 15:15:27 UTC
looks like it's a slightly different issue that has been fixed already: http://jira.codehaus.org/browse/JETTY-407 time to upgrade jetty i think... i'm setting this on the agenda for 2.0. the goal is to have a proxied testing environment using jetty and to provide apache httpd vhost configs that will enable users and developers to easily test in a proxy setting and to serve as example configs. currently, people are using wildly different proxy setups, there are no established best practices yet and thus it's very hard to compare symptoms and make sense of bug reports regarding proxying... confirmed. the ajp connector works with jetty 6.1. i've committed tools/proxytest, see jetty6.xml on how to run lenya with the new version. so far, everything seems to work, except the jetty6 configuration could use some polish. there is now a preliminary proxy testing scaffold, but it's quite broken atm. it would be great if some people could do some testing on jetty6. maybe we can up it before we go into code freeze? wdyt? I think it would be good to get it up and going with Jetty 6.1. In fact yesterday I was starting to weigh the pros and cons of Jetty vs Tomcat due to the fact I want to move to mod_proxy_ajp, and was going to test Jetty out today. Looks like I'll be testing with a new version when I get back from lunch. I've done some testing but am having issues. I get a bunch of redirects all over the place that eventually cause it to not work. I don't have Apache 2.2 on my machine, so I'm using different machine with different domains. So my test setup is a bit different from the reference. I can however tell you that Jetty 6.1 will listen via IPV6, and Apache will send it requests via V6. yeah, the proxy test setup is not working for me, either. still very much work in progress. the redirects is where i'm stuck, too. but did you test jetty6 w/o proxying? that works for me, flawlessly. i'd like to hear more about that. you don't need to change anything, jetty6 is configured both for ajp on port 8009 and for http on 8888, so you can pretty much drop it in for the current jetty. (In reply to comment #5) > but did you test jetty6 w/o proxying? that works for me, flawlessly. i'd like to > hear more about that. you don't need to change anything, jetty6 is configured > both for ajp on port 8009 and for http on 8888, so you can pretty much drop it > in for the current jetty. > I just did some testing there. I haven't had any issues with jetty6 in particular. Since it isn't in the root context, I've been having trouble there. I don't have a tomcat install so I'm not sure if this is a problem with jetty6 or a generic problem with not having lenya under the root context. i'd say let's try and release 2.0.1 with jetty6 included, but given the current code freeze for 2.0, it's probably better to postpone further work on it until after the release. just a quick summary: there have been some success reports with jetty6 in general, and using it as an ajp proxy in particular. proxy- and context-related bugs have mostly been fixed. one tricky issue remains: bug 43864 seems to be jetty-specific. at least jann and andreas can't reproduce it on tomcat. additionally, we need to provide a robust start script that will work on both linux and windows and ideally takes its configuration from local.build.properties, and then it should be ready for 2.0.1 |