Monday Aug 30, 2010

New GlassFish 3.1 Screencast: Application-scoped resources


This short screencast demonstrates the new application-scoped resources feature available starting with Milestone 4 of GlassFish 3.1 (the demo used promoted build #17). Such resources are bound to a module (war, ear, ejb) and as such they are created on deploy and destroyed when the module is undeployed. They are defined in a file called glassfish-resources.xml (schema-constrained) and shipped with the archive.

These resources are available only from the application they "belong" to which offers some level of security, more configuration flexibility (no resource name collision and different settings for different applications) as well as some level of performance isolation. They overall provide a single click/single deploy experience.

More details such as full demo description, application-scoped vs. module-scoped, location of glassfish-resources.xml and more are available from Feature one-pager (GlassFish Wiki) and Application Scoped Resources (Demo instructions).

Tuesday Sep 08, 2009

Towards SailFin 2.0 - SIP Session Replication and HCF


SailFin is closing on v2.0 which is aligned with GlassFish v2.1.1 (both scheduled for the end of October, see Roadmap) and the team has been highlighting new features in the release:

• Prasad Announces HCF, provides an overview and a List of Fixes since SCF.
• Shreedhar writes about the Support for SSR (SIP Session Replication).
• Ramesh describes the Configuration Options, including DNS failover and Converged LB.
• Prateek Announces a new AMIs for SailFin based on OpenSolaris.
  (also see EC2 Blog and Full List of Sun's AMIs)

Friday Oct 05, 2007

Grizzly secrets revealed

Performance image

If you've ever had to deal with Java performance tuning, you probably know about a few supported and maybe unsupported JVM tuning flags. Jeanfrancois "Grizzly" Arcand has a set of options for you when it comes to the Grizzly configuration (most are actually startup VM properties).

Here are my top picks (all apply to GlassFish v2):
• HTTP compression
• Comet support
• snooping support (I just like logging options)
• Asynchronous Request Processing
• Resource Consumption Management

As always and similarly to the JVM tuning case, the problem with having many options to choose from is to have methodology and good reasons to try them out. With greater power comes greater responsibility.

On the topic of Grizzly, there's a short article on JavaLobby for its 1.6.1 recent release.