The Apache Wicket team is proud to announce the availability of the third maintenance release: Apache Wicket 1.3.3. A lot of bugs have been squashed and several improvements implemented. PLEASE NOTE: We have fixed a bug related to the order of the rendered links in <wicket:head>, which might have influence on how your stylesheets are loaded. See WICKET-1487 (https://issues.apache.org/jira/browse/WICKET-1487) for details. Eager people click here to download the distribution, others can read further: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3 We thank you for your patience and support. - The Wicket Team Apache Wicket Apache Wicket is a component oriented Java web application framework. With proper mark-up/logic separation, a POJO data model, and a refreshing lack of XML, Apache Wicket makes developing web-apps simple and enjoyable again. Swap the boilerplate, complex debugging and brittle code for powerful, reusable components written with plain Java and HTML. You can find out more about Apache Wicket on our website: http://wicket.apache.org This release This release is the second maintenance release for the Wicket 1.3 product. Development for a new version of Wicket will commence soon. This release fixes several bugs and adds some minor improvements. You can find out about the changes at the bottom of this announcement. Migrating from 1.2 If you are coming from Wicket 1.2, you really want to read our migration guide, found on the wiki: http://cwiki.apache.org/WICKET/migrate-13.html Downloading the release You can download the release from the official Apache mirror system, and you can find it through the following link: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3/ For the Maven and Ivy fans out there: update your pom's to the following, and everything will be downloaded automatically: <dependency> <groupId>org.apache.wicket</groupId> <artifactId>wicket</artifactId> <version>1.3.3</version> </dependency> Substitute the artifact ID with the projects of your liking to get the other projects. Please note that we don't prescribe a Logging implementation for SLF4J. You need to specify yourself which one you prefer. Read more about SLF4J here: http://slf4j.org Validating the release The release has been signed by Frank Bille, your release manager for today. The public key can be found in the KEYS file in the download area. Download the KEYS file only from the Apache website. http://www.apache.org/dist/wicket/1.3.3/KEYS Instructions on how to validate the release can be found here: http://www.apache.org/dev/release-signing.html#check-integrity Reporting bugs In case you do encounter a bug, we would appreciate a report in our JIRA: http://issues.apache.org/jira/browse/WICKET The distribution In the distribution you will find a README. The README contains instructions on how to build from source yourself. You also find a CHANEGELOG-1.3 which contains a list of all things that have been fixed, added and/or removed since Wicket 1.3.0. Release Notes - Wicket - Version 1.3.3 Bug * WICKET-310 - AutoCompleteTextField does not invoke post call handlers * WICKET-860 - GoAndClearFilter doesn't reset filter form fields * WICKET-932 - BaseWicketTester support for SubmitLink * WICKET-1105 - Missing javascript header referencies when there are no body or head tags. * WICKET-1265 - Close ModalWindow in IE with scrollbars scrolls to bottom * WICKET-1268 - Form inside VelocityPanel throws WicketRuntimeException: Unable to find the markup for the component. * WICKET-1280 - Autocomplete onchange event gets fired twice when selecting with mouse click * WICKET-1329 - AutoCompleteTextField's suggestion list disappeared when it is used inside a ModalWindow * WICKET-1332 - AjaxFormChoiceComponentUpdatingBehavior just updates the group "grandchildren" * WICKET-1350 - AutoCompleteTextField's scrollable suggestion list disappeared when a mouse pointing to the scroll bar in IE6/7 * WICKET-1372 - Input field with autocomplete behavior does not submit the form via enter key in some cases * WICKET-1391 - <wicket:enclosure> bug: setObject(null) called for excplicitly invisible fields in a non-visible enclosure * WICKET-1408 - ComponentFeedbackMessageFilter should use equals() method to determine equality * WICKET-1411 - FormTester doesn't initialise values for RadioGroups * WICKET-1414 - findSubmittingButton will fail when button without form is added before form * WICKET-1415 - BundleStringResourceLoader throws NPE if component is null * WICKET-1416 - WIcket Filter ignoring query parameters on redirect * WICKET-1417 - AjaxFormChoiceComponentUpdatingBehavior does not iterate over immediate children * WICKET-1423 - AuthenticatedWebApplication uses deprecated constructor of AuthenticatedWebSession * WICKET-1430 - Form processing throws NPE if button.onsubmit() moves the button or its parents out of the component hierarchy * WICKET-1433 - MarkupCache NPEs when null (never cache) cacheKey is returned from IMarkupCacheKeyProvider * WICKET-1434 - WicketTester.startPage(Class) does not trigger WebRequestCycle.onBeginRequest * WICKET-1435 - WicketTester.clickLink(String) only triggers the WebRequestCycle.onEndRequest * WICKET-1438 - detach behavior * WICKET-1440 - AbstractDefaultAjaxBehavior doesn't work when added directly to page * WICKET-1442 - nested forms inside a multipart form can't be submitted via ajax * WICKET-1444 - AbstractDecimalConverter has a numberFormats fields that holds NumberFormats, But those are not thread save... * WICKET-1445 - StreamCorruptedException/PageStore/Serialization broken because ObjectOutputStream was not flushed * WICKET-1446 - Lazy registration in SharedResourceRequestTarget fails * WICKET-1452 - Error in javadoc class description in MySignInPage * WICKET-1454 - Enter in AutoCompleteTextField with AjaxFormSubmitBehavior on change-event submits form multiple times * WICKET-1455 - Session. requestDetached() does not replicate dirty pages to session in some situations, breaking application clustering * WICKET-1457 - modalwindow with panel doesn't resize properly on IE * WICKET-1458 - Changing tag name and expanding open-close to open-body-close prints old tag name * WICKET-1462 - Problem with ajax form submission inside model window in IE and Safari * WICKET-1467 - StringResourceModel should implement IComponentAssignedModel * WICKET-1470 - DiskPageStore may cause memory leaks when the files can't be written * WICKET-1487 - Bug in order of rendered links within <wicket:head> Improvement * WICKET-1288 - Make Cookie-Detection possible without JavaScript * WICKET-1338 - enclosures on nested components within wicket:extends * WICKET-1351 - AutoCompleteTextField's scrollable suggestion list can be better if it can be scrolled using KEY_UP and KEY_DOWN * WICKET-1406 - CheckGroupSelector should implement ILabelProvider * WICKET-1410 - WicketTester and temporary sessions * WICKET-1420 - Allow to change charset in StringRequestTarget * WICKET-1421 - DecimalConverter with grouping disabled needed * WICKET-1422 - request to make RadioChoice getPrefix() and getSuffix() non-final * WICKET-1461 - Javadoc error with parent in constructor style * WICKET-1464 - Stop dumping stack trace in PropertyResolver when a field or set method is not found * WICKET-1465 - AjaxRequestTarget shouldn't throw exception when component is already removed from page (but log warning) * WICKET-1472 - JavaDoc enhancements in FileUpload API New Feature * WICKET-1428 - AutoLinkResolver and Parent-Relative (../) Links

View original post | Add to del.icio.us| Updated 5 months ago | Share

This is the Iron Mongrel release. It is the result of trying to trash Mongrel until it can’t move and then fixing anything that comes up. The testing methods used are:

1. Increased the number of unit tests against the main C parts.
2. Write several tests against Mongrel’s parser which throw it tons of random data.
3. Use Peach Fuzz to thrash several live apps with randomness.
4. Wrote several extensive little scripts to explore the edges of death for Mongrel.
5. Heavy code audits covering as much code as possible to find any possible loose ends.

The end result is a lot of little fixes which make Mongrel more robust against badly behaving clients and possibly against many potential security risks in the future. In general Mongrel 0.3.12.2 behaves more consistently compared to past releases when given random data or maliciously formatted data.

The main changes are related to how IO is processed and how the HTTP parser rejects “bad” input. What the parser now blocks is:

• Any header over 112k.
• Any query string over 10k.
• Any header field value over 80k.
• Any header field name over 256 bytes.
• Any request URI greater than 512 bytes.

As soon as these conditions are detected the client is disconnected immediately and a log message is printed out listing the IP address, the exact cause, and the data that caused it. I’ll remove the data dump later, but I want people to shoot me valid requests that cause parser errors.

That’s not all though. I’ve started a security page where I’ll publish the results of security threats, tests, and improvements as well as any advice for folks.

This release also features a few little features here and there:

• Initial support for a “config script”. I’ll be documenting this more, but it basically lets you use the Mongrel::RailsConfigurator to augment your application’s config via a small script. Just pass “-S config/mongrel.rb” and put any Mongrel::RailsConfigurator statements that are reasonable.
• Mongrel will report the correct REMOTE_ADDR variable, but it does a little trick where if there is an X-FORWARDED-FOR header then it sets REMOTE_ADDR to that.
• Fixes for little bugs like double log messages, but not a lot of changes to the overall core.

Go ahead and install the usual way: gem install mongrel or gem upgrade

The logo is courtesy court3nay from caboose

-- Delivered by Feed43 service

View original post | Add to del.icio.us| Updated 9 months ago | Share

The Apache Archiva team is pleased to announce the release of Archiva 1.0.2 Archiva is a build artifact repository manager for use with build tools such as Maven, Continuum and Ant. It has features like repository search and browse, securing repositories, identifying unknown artifacts and reporting of repository problems. Aside from these, it can also act as a nearby (proxy) cache of popular global repositories. The latest release is now available here: http://maven.apache.org/archiva/download.html If you have any questions, please consult: - the web site: http://maven.apache.org/archiva/ - the archiva-user mailing list: http://maven.apache.org/archiva/mail-lists.html New in Archiva 1.0.2 ================ * Configurable Proxy Error Handling Two new options have been added to the proxy connector configuration page: - On remote error - gives control over whether to stop immediately, continue to try for a successful proxy, or ignore an error - Return error when - gives control over whether to return an existing artifact if present or fail regardless if a remote error occurs when updating an artifact Change Log for Archiva 1.0.2 ======================= * [MRM-159] - should not respond with a 404 if proxying a file results in a remote error * [MRM-532] - Unable to specify the location of the index files through the web ui * [MRM-598] - Validation error on new repository creation and other fields under certain conditions * [MRM-608] - Unable to find project model for [...] if the initial import of the POM failed * [MRM-617] - Reporting does not work due to bug in client-side JavaScript validation * [MRM-618] - PLEXUS_BASE does not work for local databases * [MRM-622] - database not being updated with project model information * [MRM-626] - ClassCastException when saving proxy connector with property defined * [MRM-627] - Archiva doesn't download SNAPSHOTs for proxied repositories. * [MRM-642] - archiva-common tests rely on relative paths * [MRM-655] - The logs are duplicated in the archiva.log and wrapper.log file. * [MRM-659] - archiva cannot serve ejb artifacts from a maven1 repository * [MRM-661] - remote repository removals are not saved after restart * [MRM-664] - Cannot download a strut-module artifact in a Legacy repository * [MRM-674] - LayoutException when downloading SNAPSHOT test-sources * [MRM-683] - Archiva version missing from pages and logs * [MRM-687] - Project model cannot be added to database if it inherits groupId and/or version from parent POM * [MRM-689] - Incorrect war name in example for tomcat * [MRM-690] - using undefined appserver.base * [MRM-691] - Can't get any of the consumers to work without through a NPE * [MRM-701] - Buggy documentation on "separating the base from the installation" * [MRM-703] - Artifacts with extensions longer than fours characters breaks repository scanning. * [MRM-713] - extensionPattern in FilenameParser is incorrect * [MRM-715] - error adding artifacts to Lucene under some circumstances * [MRM-719] - NPE during repository scan * [MRM-725] - /archiva/browse URL does not work on WebSphere * [MRM-727] - Archiva does not download plugin artifacts in Geronimo * [MRM-734] - Unable to update metadata - No versions found for reference * [MRM-746] - unable to include *.xml in artifacts list as it picks up maven-metadata.xml * [MRM-750] - Adding a network proxy doesn't require an identifier * [MRM-755] - No content type for .pom files denoted in file "archiva-mime-types.txt" - workaround included * [MRM-758] - unable to schedule cron expressions that contain a comma * [MRM-761] - Exception when trying to retrieve a Maven 1 artifact of type zip * [MRM-762] - Footer doesn't stretch across repositoryScanning and database pages * [MRM-763] - Default cron expression for database update is invalid * [MRM-764] - default policies are not selected in the add proxy connector page * [MRM-504] - Find Artifact page needs more onscreen information/ instructions * [MRM-656] - Admin guide for installing WAR needs updating * [MRM-666] - Edit Managed Repository page should indicate the repo id being edited * [MRM-700] - Review the documentation on deploying to Archiva for inconsistent repository ids * [MRM-720] - Upgrade Lucene from 2.0 to 2.3.1 Thanks, The Apache Archiva team

View original post | Add to del.icio.us| Updated 4 months ago | Share

The Apache MyFaces Orchestra team is pleased to announce the release of Apache MyFaces Orchestra Core 1.2. Get a full overview at Orchestra's homepage [1]. The distribution is available at * http://myfaces.apache.org/orchestra/download.html Apache MyFaces Orchestra is available in the central Maven repository under Group ID "org.apache.myfaces.orchestra". Have fun! Regards, Simon [1] http://myfaces.apache.org/orchestra

View original post | Add to del.icio.us| Updated 8 d and 14 h ago | Share

The Apache Harmony team are pleased to announce the immediate availability of Apache Harmony 5.0M7. Apache Harmony is the Java platform project of the Apache Software Foundation. Apache Harmony 5.0M7 is the latest stable build with numerous enhancements and bug fixes including: * new performance improvements, especially in object serialization and pack200 decoding, * a new 'javap' the class file disassembler tool, and alpha version of 'policytool' the security policy management tool. * bug fixes and functional enhancements throughout the class libraries, especially in the Swing widget toolkit, * ...and many more We would particularly like to thank our Google Summer of Code students András Belicza (policytool) and Tharindu Mathew (Swing enhancements), and welcome them to the project! Source code and binary builds are available from the project download site: http://harmony.apache.org/download.cgi Apache Harmony welcomes your help. For more information on how to report problems, successes, and to get involved in Apache Harmony visit the project website at http://harmony.apache.org The Apache Harmony Team

View original post | Add to del.icio.us| Updated 8 d and 12 h ago | Share

The Apache JAMES Project http://james.apache.org is pround to announce that Apache JSieve 0.2 is now available. Apache JSieve is a Java implementation of RFC 3028 Sieve: A Mail Filtering Language. A prime (though not the only) use case for Sieve is rule-based filtering into mailboxes after delivery to a server. JAMES server uses JSieve for this purpose. For more information see http://james.apache.org/jsieve. This is the first release of JSieve though the code base is reasonably mature. It can be downloaded from ������http://james.apache.org/download.cgi. Please remember to check the signature or sum. Robert Burrell Donkin

View original post | Add to del.icio.us| Updated 9 d and 3 h ago | Share

The development version of Ruby on Rails has cool new internationalization features. Although the framework itself doesn’t provide a lot of I18N functionality, it does provide the necessary hooks for plugins to implement I18N however they see fit. Simon Tokumine has written an I18N demo application to show you what Rails is capable of, when used in combination with the localized_dates plugin.

We’ve deployed the demo application at http://i18n-demo.phusion.nl/. Check it out.

[Ruby on Rails ]
View original post | Add to del.icio.us| Updated 9 d and 0 h ago | Share

2.0.3 is a minor release containing non-intrusive bug fixes and optimizations.

Changes Vendor Rails optimization Some people vendorize Ruby on Rails. In previous versions, Phusion Passenger creates a new framework spawner which caches the code for the vendorized Rails framework. This step has now been removed because it’s redundant. As a result, Phusion Passenger now uses less memory when serving applications that have vendorized Rails. It is therefore especially adviced that shared hosts upgrade to this version. ‘passenger-memory-stats’ now works on non-Linux systems The ‘passenger-memory-stats’ didn’t work correctly on non-Linux platforms. This has been fixed. However, ‘passenger-memory-stats’ is only capable of displaying the real memory usage of processes when running on Linux. Other operating systems don’t provide a way to query the real memory usage, unfortunately. So on non-Linux platforms, ‘passenger-memory-stats’ will display the Resident Set Size instead. WSGI fixes WSGI support in Phusion Passenger is mostly a proof of concept. Nevertheless, we find it worthwhile to fix any WSGI-related bugs that we may encounter. 2.0.3 fixes Python 2.4 compatibility (previous versions require at least Python 2.5), and fixes some WSGI compliance bugs. Thanks to Weyert de Boer for contributing the latter fix. How do I upgrade to 2.0.3? Via a gem

Please install it with the following command:

gem install passenger

Next, run:

passenger-install-apache2-module

Please don’t forget to copy & paste the Apache config snippet that the installer gives you.

Via a native Linux package

Neil Wilson from Brightbox has kindly provided an Ubuntu 8.04 package for Phusion Passenger. The package is available from the Brightbox repository which you can find at:

http://apt.brightbox.net

Add the following line to the Third Party Software Sources:

deb http://apt.brightbox.net hardy main

(The simplest way to do that is to create a file in /etc/apt/sources.list.d/ containing the deb instruction, and then run ‘apt-get update‘).

Once you’ve done this then you can install Phusion Passenger by running:

apt-get install libapache2-mod-passenger

(Note that Neil is currently packaging 2.0.3, so it might take a while before this release shows up in the apt repository.)

[General ]
View original post | Add to del.icio.us| Updated 27 d and 4 h ago | Share

Phusion Passenger’s development continues on. A few bugs have been found and fixed. These fixes are deemed to be important enough to backport to the 2.0.x series, so today we present you with Phusion Passenger 2.0.2.

Changes Fixed a file descriptor leak If a system error occurs while receiving the response data from a Rails application, then the file descriptor that connects Apache to the Rails application is not properly cleaned up. This has been fixed. Thanks to TonyLa for reporting and analyzing this problem. Fixed a memory leak Due to an unfortunate little mistake, each time a client disconnects from the ApplicationPoolServerExecutable will result in a small memory leak. In practice, it means this: if your Apache is configured to restart* worker threads or worker processes often (say, every 10 requests or so), then each time that happens, a small memory leak will occur. For most people this is not a problem, because by far most Apache servers are configured to never restart worker threads/processes, or only restart a worker thread/process after several hundred thousand requests. This leak didn’t catch our attention because we used a standard Apache configuration (Ubuntu default).
Once again, many thanks to TonyLa for reporting and analyzing this problem.
(* = This has got nothing to do with the ‘apachectl restart’ or ‘apachectl graceful’ command. These commands restart Phusion Passenger entirely, and will not result in any memory leaks. We were only referring to Apache’s internal process of restarting worker threads and worker processes.) Fixed a compilation problem for some people This has been fixed. How do I upgrade to 2.0.2? Via a gem

Please install it with the following command:

gem install passenger

Next, run:

passenger-install-apache2-module

Please don’t forget to copy & paste the Apache config snippet that the installer gives you.

Via a native Linux package

Neil Wilson from Brightbox has kindly provided an Ubuntu 8.04 package for Phusion Passenger. The package is available from the Brightbox repository which you can find at:

http://apt.brightbox.net

Add the following line to the Third Party Software Sources:

deb http://apt.brightbox.net hardy main

(The simplest way to do that is to create a file in /etc/apt/sources.list.d/ containing the deb anstruction, and then run ‘apt-get update‘).

Once you’ve done this then you can install Phusion Passenger by running:

apt-get install libapache2-mod-passenger

(Note that Neil is currently packaging 2.0.2, so it might take a while before this release shows up in the apt repository.)

[Phusion Passenger ]
View original post | Add to del.icio.us| Updated 53 d ago | Share

This is a small release that fixes a little bug, some of the documentation, and adds the new RedirectHandler code and a redirect call for the mongrel.conf files. It’s fresh so don’t rely on it. Everyone should upgrade with the usual gem update command (which tells you it’s “Upgrading…”) and tell me how it works.

This release fixes:

The -C configure file option was busted because of an errant line move. Adds RedirectHandler thanks to Jonas Pfenniger and a new redirect call to Configurator. Fixes mongrel_service documentation which was referring to -r instead of -c and -C instead of -u. Using RedirectHandler

Redirects are pretty simple. You simply have either a new RedirectHandler class you can use or you can put this in a mongrel.conf and pass that to -S:

redirect "/from", "/to"

It also accepts regex for the from parameter and can take a block. Play with it if you’re interested.

Deflate And Safari

It looks like Safari does not honor the Content-Encoding: deflate response, so avoid using DeflateFilter until I can find out why. This is why you don’t hand code network protocol parsers.

-- Delivered by Feed43 service

View original post | Add to del.icio.us| Updated 9 months ago | Share

This is the release that came out of RailsConf hacking with folks like Rick Olsen, Why The Luck Stiff and other incredibly cool folks. The conference was great, so lets hope this release is good too. The big thing it adds is upload progress in Mongrel. That’s right, Why and Rick pinned me down and made me put it in Mongrel. They worked up the mongrel_upload_progress plugin and are now working on Rails and Camping code to make it happen.

Install from the gem servers with your usual commands:

gem update or gem update mongrel or gem install mongrel

But if you can’t wait for the gem mirrors to update, then you can also do:

gem install mongrel --source=http://mongrel.rubyforge.org/releases

To get around it all.

-- Delivered by Feed43 service

View original post | Add to del.icio.us| Updated 9 months ago | Share

The Apache MINA project team is proud to announce the new minor point releases of Apache MINA, a Java network application framework, version 1.0.10 and 1.1.7. Apache MINA is a network application framework which helps users develop high performance and high scalability network applications easily by providing an abstract, event-driven, asynchronous API over various transports such as TCP/IP and UDP/IP via Java NIO. Please refer to the release note for the changelog: http://tinyurl.com/6hxvec The Apache MINA project website includes resources such as introductory presentation slides, tutorials, and examples to help you learn MINA as soon as possible. Quick links: ============ * Homepage - http://mina.apache.org/ * FAQ - http://mina.apache.org/faq.html * Testimonials - http://mina.apache.org/testimonials.html * Documentation - http://mina.apache.org/documentation.html * Performance - http://mina.apache.org/performance-test-reports.html * Downloads - http://mina.apache.org/downloads.html The Apache MINA project team is always open for your feedback. Please let us know what you think about MINA via our mailing list: http://mina.apache.org/contact.html Thank you, -- The Apache MINA Project Team -- http://mina.apache.org/

View original post | Add to del.icio.us| Updated 4 months ago | Share

A few days ago, the Ruby core team has announced several newly discovered security vulnerabilities. Ruby versions prior to 1.8.6-p285 and 1.8.7-p70 are vulnerable. The previous version of Ruby Enterprise Edition is also vulnerable because it’s based on 1.8.6-p114.

Earlier Ruby releases had some crash bugs and incompatibility problems. It goes without saying that such problems are unacceptable in production environments, so we’ve been careful and took the time to test 1.8.6-p286 against various test suites:

• We tested it against the Ruby on Rails test suite (edge). All tests passed.
• We tested it against the RubySpec test suite (git HEAD from yesterday). All tests passed. In fact, Ruby 1.8.6-p114 fails a few tests, so p286 is more Ruby-compliant.
• We tested it against Typo 5.0.3’s test suite. All tests passed.
• We tested it against the test suite of various of our internal applications. All tests passed.

So our conclusion is that Ruby 1.8.6-p286 is indeed stable and compatible. Kudos to the Ruby core developers for this excellent release!

We’ve prepared a new Ruby Enterprise Edition release, based on Ruby 1.8.6-p286. The official Ruby on Rails wiki has been running on this Ruby Enterprise Edition version since yesterday (in addition to Phusion Passenger git HEAD), and everything seems to be rock-solid so far.

This Ruby Enterprise Edition release not only includes upstream Ruby’s security vulnerability fixes and other bug fixes, but also some Ruby Enterprise Edition-specific improvements and fixes:

MySQL headers are autodetected Many people have problems installing the MySQL gem, especially on non-Linux platforms. That’s because the gem cannot find the MySQL development headers. The Ruby Enterprise Edition installer now autodetects the MySQL headers, for much better MySQL gem installation success rate. Bug fix: don’t overwrite shebang lines for non-Ruby scripts Normally, the installer changes the shebang lines of all scripts in $PREFIX/bin to the correct location of the Ruby Enterprise Edition binary. ($PREFIX is the location that one installs Ruby Enterprise Edition to) However, this would change all shebang lines, even for non-Ruby scripts. This has been fixed: only the shebang lines of Ruby scripts will now be changed. sqlite3-ruby gem permissions fixed The sqlite3-ruby gem installed itself with the wrong permissions. Its files would be world-writable by default. The installer now fixes this problem. ‘PassengerRuby’ instead of ‘RailsRuby’ The installer used to instruct the user to change the ‘RailsRuby’ option for Phusion Passenger. ‘RailsRuby’ has been deprecated since Phusion Passenger 2.0 in favor of ‘PassengerRuby’, so the installer now instructs the user to change ‘PassengerRuby’ instead. Upgrade instructions Via the source tarball

Please download the source tarball from the download page and run the built in installer, as instructed on the download page. To upgrade, please install Ruby Enterprise Edition to the same location that you specified last time.

Via the Debian package

Please install the Debian package by downloading it from the download page. (click on the “Linux” tab)

[Ruby Enterprise Edition ]
View original post | Add to del.icio.us| Updated 26 d and 10 h ago | Share

After talking with various people deep inside the Ruby machine, I’ve decided to release Mongrel Ruby licensed as of 0.3.13.3. This release should make quite a few people happy. It also means that contributors will hopefully feel better about their contributions and people using Mongrel have more freedom.

This release also fixes a problem with the -B option not actually logging object counts. The object count logging isn’t perfect, but some folks use it.

This release also will print the access log to the screen when you run it in your console. This was requested by a few folks, but I’m not convinced I like it. Try it out and if you do or don’t then mention it in the mailing list.

As usual, do your:

gem install mongrel

To get the release, and if it doesn’t show up then you have to wait for the ruby gems mirror to sync up.

-- Delivered by Feed43 service

View original post | Add to del.icio.us| Updated 9 months ago | Share

Alright folks, after nearly a month of pounding and beating up the Mongrel 1.0 RC1 release we’re putting out the official 1.0.1 release. It’s official, so let the chaos spread across the 2.0 web in a destructive blaze viewable from the buckle of Orion’s Belt.

Or, you could just install it with:

$ gem install mongrel

It should properly pull all the required dependencies, and updating your gems should get all the new cool stuff.

What happened to 1.0?

We decided to follow official Rails Configuration Management Board Standards and do a silent 1.0 followed by an official 1.0.1. There weren’t any bugs in 1.0 but we didn’t want to break with tradition by not offering a 1.0.1. (Yes, this is a joke.)

Also, this forces the upgrade even for people who grabbed 1.0 from the releases directory.

Information RDoc Coverage Report Report Bugs Documentation Adoptions Books Are You Using It?

I want to build up a good list of people who are using Mongrel, no matter what you use it for or where. Any use is a good use. I’ll be filling in documentation and collecting up all the pictures of people’s dogs that I’ve collected, so adding more “mongrel success stories” would be a great addition.

If you wrote a book or mentioned Mongrel in a book then tell me that too. I want to make sure more than just my book is mentioned. I’ll be adding to that list as well.

You can post to the mailing list or email one of the project members. If you ask us to keep the company secret then we won’t post your usage, just keep it for our own records and smug self-satisfaction.

-- Delivered by Feed43 service

View original post | Add to del.icio.us| Updated 9 months ago | Share

Mongrel 1.0.3 is finally out with an asspile of bug fixes. It’s now a signed gem, so add the Mongrel public certificate via:

$ wget http://rubyforge.org/frs/download.php/25325/mongrel-public_cert.pem $ gem cert --add mongrel-public_cert.pem

Now install via:

$ gem install mongrel --include-dependencies -P HighSecurity

Manual downloads (gems and tarballs) are at http://mongrel.rubyforge.org/releases/.

Mongrel 1.1 is coming real soon now with JRuby support and a few other things.

-- Delivered by Feed43 service

View original post | Add to del.icio.us| Updated 9 months ago | Share

Mongrel 1.0.4 is out. It fixes three bugs that were introduced in 1.0.3.

-- Delivered by Feed43 service

View original post | Add to del.icio.us| Updated 9 months ago | Share

Mongrel 1.1 is out, with JRuby support. Mongrel_cluster is also updated to 1.0.4, with fixes for a Capistrano recipe bug. The URIClassifier has been updated; if you still need the old one (you don’t), it’s available in the mongrel_experimental gem.

-- Delivered by Feed43 service

View original post | Add to del.icio.us| Updated 9 months ago | Share

Hi guys.

RailsConf 2008 was great, and our talk on Phusion Passenger and Ruby Enterprise Edition went really well. Fabio Akita has some pictures of our talk. For other pictures, see Fabio’s .mac gallery!

We promised to release Passenger 2.0 and Ruby Enterprise Edition on the same day. Unfortunately we’ve been too optimistic about Internet access. We’re currently at the airport and we have limited internet access until we are back in the Netherlands (which should be in about 4 days or so), but in the meantime, the Passenger version with Rack and WSGI support has already been pushed to github, so feel free to tinker around with it. We’ve also put the latest Users Guide (with Rack support) online.
Thanks for the support Chad!

We’re trying our best to find a way to push out Ruby Enterprise Edition as well, and ask the hardcopy guys to not release it prior to the moment that we’re able to push it (which should be in about 4 days). This launch will also be accompanied by a site etc… Feel free to blog about it though, and the reason why we’re asking this is because we want to keep the support at Phusion related places. This will prevent any ‘noise’ in communication.

Thanks for the support mateys!

Cheers,
Hongli Lai
Tinco Andringa
Ninh Bui

[Phusion Passenger RailsConf Ruby Enterprise Edition ]
View original post | Add to del.icio.us| Updated 3 months ago | Share

It’s a little bit late (this should have been done during RailsConf, sorry), but it’s finally here. We’re pleased to announce Phusion Passenger 2.0, release candidate 1. If no major issues are found, this will become version 2.0.1. We’re also pleased to announce the long-awaited Ruby Enterprise Edition.

RailsConf 2008 presentation

Our RailsConf 2008 presentation about Phusion Passenger and Ruby Enterprise Edition went extremely well. The sheets are available in the following formats:

• PDF (15 MB)
• Flash, with animations (32 MB)

The presentation includes a screencast (23 MB) created by Soocial.

Some people have been distributing our old, outdated sheets, which contain lots and lots of bullet points and almost no graphics. Please download the sheets on this page instead: these are the sheets that we used during the presentation.

Introducing Rack support

2 months after the release of Phusion Passenger 1.0, we present you with Rack support. It is now possible to host arbitrary Ruby web applications (e.g. Merb and Camping) on Phusion Passenger! We provide this feature with the same ease of use that many people have come to love.

The following screencast, created by Ryan Bates of RailsCasts fame, demonstrates the ease of deploying a Rack application on Phusion Passenger:

But that’s not all. We’ve done our homework. Our Users guide provides a comprehensive list of Rackup specifications for all Ruby web frameworks that we could find, so that you don’t have to hunt this information down yourself!

We received some Rack-related contributions shortly after Rack support had been pushed to the public git repository. We’d like to thank _why and remi for contributing documentation and full Rackup DSL support.

Introduction Python WSGI support

Not only do we support Rack, we now also support Python WSGI! In theory, Phusion Passenger can now run Django.

Don’t get us wrong. Phusion Passenger’s main focus is still on Ruby and Ruby on Rails. WSGI support is meant to be a show case of Phusion Passenger’s flexible architecture.

Optimizations Much better stability This new release is much more stable than the 1.0.x series. Many stability issues have been fixed. In fact, Dreamhost and iLike are using this version in production environments. So if you were experiencing stability problems, please upgrade to this version, as it may solve your problem. Much faster graceful restart Some hosts gracefully restart Apache often, so to them, high graceful restart speed is essential. Phusion Passenger 2.0 RC 1 is much, much faster at graceful restarts. Less memory usage: reduced VM size

Process monitoring tools tend to use the “VM size” of a process as an indication of the actual memory usage. This is not correct, because the VM size only indicates the amount of memory that a process can access, not the amount of memory that it actually uses.

Nevertheless, having a large VM size poses problems. Some servers, virtual private servers in particular, have artificial VM size limits in order to prevent processes from using too much memory. Phusion Passenger 1.0 makes Apache’s VM size very large (more than 100 MB), even though the actual memory usage is only several MB.

In Phusion Passenger 2.0, the VM size has been reduced by ten fold, as shown by the following diagram:

Fair load balancing (as opposed to round-robin load balancing)

One of the traditional problems of Mongrel Cluster behind Nginx is, in Ezra’s words:

“My only complaint was that the proxy modue was round robin only. This means that if you had 3 mongrels and one of them performed and action that took say 20 seconds, for that 20 seconds every 3rd request would get stuck in line behind the mongrel doing the long blocking request. This is because nginx was merrily doing round robin and didn’t care if a mongrel was busy or not.”

Phusion Passenger now supports fair load balancing. It will forward a request to the Rails instance with the least number of requests in its queue. Fair load balancing is turned on by default, without the need to configure anything.

See also page 53 of the presentation sheets.

Upload buffering

In Phusion Passenger 1.0, a (long) file upload will block a Rails application instance. Usually this is not a big problem, because Phusion Passenger will spawn more Rails instances if existing ones are blocked. But it becomes a problem if your website handles many simultaneous file uploads (read: more than 10 concurrent file uploads at any time).

Phusion Passenger 2.0 supports upload buffering. File uploads that are sufficiently large, are stored into a temporary file. Only when the file upload is done, will it be forwarded to the Rails application. This means that your Rails applications will not be blocked while a large file upload is in progress.

See slide 86 of the presentation sheets.

Default timeouts changed, in favor of virtual private servers

The default timeout values in Phusion Passenger 1.0 were optimized for shared hosts, which host many applications and need to free resources quickly. But most of our users seem to be using virtual private servers. These servers usually don’t get a lot of traffic, so the default timeouts are easily reached. So we’ve changed the default timeout values in favor of virtual private servers. Shared hosts and people running Phusion Passenger on dedicated servers should adjust the timeouts.

What Default in Phusion Passenger 1.0 Default in Phusion Passenger 2.0

RailsMaxPoolSize	20	6
RailsPoolIdleTime	120	300
ApplicationSpawner server idle time	120	600

Other improvements Ruby on Rails 1.0 compatibility Phusion Passenger is now compatible with Rails 1.0 applications as well. Improved application compatibility: conservative spawning

By default, Phusion Passenger preloads the Ruby on Rails framework and application code. This allows Phusion Passenger to reduce the startup time of Ruby on Rails applications and to save memory. Using this technique, startup time can be decreased by as much as 90%!

Unfortunately, some applications and/or plugins don’t expect to be preloaded, and even assumes that no code is being preloaded. soap4r is one such plugin. Until recently, these applications/plugins didn’t work with Phusion Passenger.

Phusion Passenger 2.0 implements so-called conservative spawning. In conservative spawning mode, Phusion Passenger will not preload any code. In other words, it will emulate the way Mongrel loads Rails applications. Conservative spawning allows Phusion Passenger to be 100% compatible with all Rails applications.

Conservative spawning is less efficient than the default spawning strategy, though no less efficient than Mongrel Cluster. You should only use conservative spawning if you’re experiencing compatibility problems.

‘RailsEnv’ is now per-virtual host The RailsEnv configuration option used to be a global option. It’s now a per-virtual host option, so you can define a different environment for every Rails application. New resource control option: ‘PassengerMaxInstancesPerApp’

The PassengerMaxInstancesPerApp option allows you to define the maximum number of pool slots that a single application may use. This will prevent a single application from getting out of control and taking over the entire server.

Many thanks to Jochen Tuchbreiter for contributing this feature.

Support for worker MPM The Apache worker MPM is now supported. Analysis and system maintenance tools Phusion Passenger 2.0 includes new analysis and system maintenance tools. If you’re experiencing stability problems with Phusion Passenger or your Rails application, then please try these tools. How do I upgrade to 2.0 RC 1? Via a gem

Please download the 2.0 RC 1 gem, then install it with the command:

gem install passenger-1.9.0.gem

Next, run:

passenger-install-apache2-module

Please don’t forget to copy & paste the Apache config snippet that the installer gives you.

Via a native Linux package

Neil Wilson from Brightbox has kindly provided an Ubuntu 8.04 package for Phusion Passenger. The package is available from the Brightbox repository which you can find at:

http://apt.brightbox.net

Add the following line to the Third Party Software Sources:

deb http://apt.brightbox.net hardy main

(The simplest way to do that is to create a file in /etc/apt/sources.list.d/ containing the deb anstruction, and then run ‘apt-get update‘).

Once you’ve done this then you can install Phusion Passenger by running:

apt-get install libapache2-mod-passenger

Finally, run the following command. This will tell you how to configure Apache.

passenger-install-apache2-module Ruby Enterprise Edition

Ruby Enterprise Edition has been officially launched. Check out http://www.rubyenterpriseedition.com/

So far, Ruby Enterprise Edition has mostly been tested on Linux (both 32-bit and 64-bit). MacOS X is not yet supported: support for it is planned for a future version.

That’s all folks

A lot of work has been put into this release. Enjoy. If you like our work, please consider getting an “enterprise license”.

[Phusion Passenger Ruby Enterprise Edition ]
View original post | Add to del.icio.us| Updated 88 d ago | Share

A new version of Ruby Enterprise Edition has been released, with the following changes:

MacOS X support A number of people have been waiting for this. Upgraded to RubyGems 1.2.0 A number of VPS users have reported that RubyGems 1.1.1 uses an excessive amount of memory, which causes their servers to swap to death. RubyGems 1.2.0 should solve this problem. No need to reinstall already-installed gems The RubyGems installation provided by Ruby Enterprise Edition will now reuse the gems that you have already installed (with regular Ruby). So if you have lots of gems installed, then you don’t need to reinstall them separately for Ruby Enterprise Edition. Merged with Ruby 1.8.6-p230 This solves the recent security vulnerabilities. How do I upgrade?

Go to the download page and follow the installation instructions. (*note*: RubyForge is still updating their mirrors, so the download might not be immediately available. In that case, please wait a few hours before trying again.)

[Ruby Enterprise Edition ]
View original post | Add to del.icio.us| Updated 74 d ago | Share

Phusion Passenger version 2.0.1 has been officially released. Not much has changed since 2.0 RC 2: only some documentation has been updated.

See the announcements for versions 2.0 RC 1 and 2.0 RC 2 for a full list of changes compared to version 1.0.x.

How do I upgrade to 2.0.1?

Please install it with the following command:

gem install passenger

Next, run:

passenger-install-apache2-module

Please don’t forget to copy & paste the Apache config snippet that the installer gives you.

[Phusion Passenger ]
View original post | Add to del.icio.us| Updated 72 d ago | Share

We are days away from the official 0.3.13 release, which will be followed quickly by 0.4 code named Enterprisey Edition 1.2. This latest pre-release update closes off the last of the annoying bugs, and adds one very nasty feature people should check out before we release. Read about Katanas below.

This release doesn't have win32 yet. That'll be uploaded Monday.

GETTING IT

Best thing to do is this:

$ gem install daemons $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/ WHAT’S FIXED Fixes a failure of -P to find PID files. Changes the RailsHandler so that only passes GET or HEAD requests to the DirHandler for page caching. Confirms that the new send_file and upload to tempfile works on win32. More tests with big files uploaded on win32 are needed. Lots of documentation on installing, with more to come. Full Apache documentation and information on writing your own snazzy handlers and filters. François SIMOND suggested a check for allow_concurrency and to avoid locking Rails if that’s set to true. I tried it, had to change the patch but I left it in. Read below. Moved some of the “change to user/group” code around so that any Mongrel command can use it. Various code clean-ups and big improvements on the unit test coverage and reporting. Check out the coverage report Lots of thrashing and code review, not much more will come for 0.3.13 unless an obviously broken piece needs work. KATANA SUICIDE CONCURRENCY

I resisted doing this, but it’s going to come down sooner or later now that François SIMOND figured it out. Mongrel was protecting the world from the allow_concurrency “feature” but now it lets you kill yourself in obscenely horrible ways.

If you set ActionController::Base.allow_concurrency=true in your config/environments/* then Mongrel will NOT guard the Rails Dispatcher. This means that you’ll get full threaded madness thrashing your Rails controllers until they die horribly slicing themselves into tiny little bits leaving you breathless with the destruction.

Mongrel will obnoxiously warn you about this, and people who try it will NOT get support from me without mad amounts of dough. If you turn this on, and your world comes crashing around your head, then I warned you. Otherwise, go ahead and give it a try and see if that improves things for you.

Enjoy the release, and report those bugs

-- Delivered by Feed43 service

View original post | Add to del.icio.us| Updated 9 months ago | Share

After a huge push, tons of delays to fix bugs and add enhancements, and lots of feedback and contributions from many great people, I’m happy to announce the official release of Mongrel 0.3.13.

This release features lots of documentation, cleaned status output, improved IO processing, a major bug fix for a thread leak, and an improvement in the win32 support.

Read below from past news for all the stuff that was fixed. The main change that win32 folks should be aware of is they have to install a second little gem to get the services support. This is slightly annoying, but the change makes it possible to work independently on the services support and not hold back future Mongrel releases.

Getting The Release

For normal people you should do this:

$ sudo gem install mongrel

Of use update. If update don’t work then remove mongrel and re-install.

Win32: Getting The Release

For win32 people, you just do this:

$ gem install mongrel $ gem install mongrel_service

When you do the install, pick the mswin32 version. After you install the mongrel_service you now just use mongrel_rails like everyone else, but you get some new fancy service:: commands.

Reporting Bugs

Send them to the mailing list and make sure you have your OS, versions, web server, etc.

-- Delivered by Feed43 service

View original post | Add to del.icio.us| Updated 9 months ago | Share

Just in case you haven’t noticed yet, http://wiki.rubyonrails.org/ is now running Phusion Passenger and Ruby Enterprise Edition. We migrated them a few days ago, and other than a MySQL failure yesterday, it had been rock solid ever since. People have complained about wiki.rubyonrails.org being down often, but the uptime should be a lot better now.

[General ]
View original post | Add to del.icio.us| Updated 43 d ago | Share