On 29/09/11 16:28, Steve Loughran wrote: > > I am pleased to announce release 3.18.012 of SmartFrog.
One other big change I should mention is > ** Bug > * [SFOS-676] - Jetty component should not block in sfStart/sfDeploy http://jira.smartfrog.org/jira/browse/SFOS-676 Jetty components now start on a separate thread, stopping ping() operations thinking there is a problem when in fact slow-starting servlets are causing it to take a while to come up. While this change is needed, I'm not sure what's gone is complete. -I'm starting to suspect that errors in servlet creation don't propagate up -that's not something I test for yet, so I'll add the test and see what happens. -It may be good to add a switch to say "use blocking startup", though the ping() operation will still be fixed to not worry about slow startup, which was half the problem. If anyone is having problems with Jetty, email the list and I'll have a look. I may well push out a new release at the end of October to deal with any Jetty-related problems, though I need better tests first ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Smartfrog-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/smartfrog-users
