The first candidate release (CR1) for JBoss Application Server 5 has been released. There is a lot of good background from Sacha Labourey and feature details from project lead Dimitris Andreadis. Now that version 5 of the new application server has been through alpha and beta stages, this candidate release is a great opportunity for developers to get knowledge and practice on the next gen app server.
(Tip of the hat for Ales Justin’s post about the CR1. Ales also posts new information about SpringDeployer and VFS .)
This tip article has been edited and republished from the original source.
by Michael Juntao Yuan
LAMP and Java EE are two important middleware stacks for developing web applications. LAMP stands for Linux, Apache, MySQL, and PHP. They are all open source software included in Red Hat Enterprise Linux system. Java EE stands for Java Enterprise Edition. Red Hat chooses the open source JBoss Application Server (JBoss AS), which is an implementation of Java EE, as its official middleware stack.
This interview was edited and republished from the original location.
A Dev Fu Interview with Sacha Labourey
Back in April, Red Hat’s announcement of its intent to acquire JBoss began a lot of speculation about what this acquisition meant to both the companies, and to the industry as a whole. Now, three months after the transaction closed, Red Hat is announcing a combined offering of Red Hat Enterprise Linux and JBoss middleware called the Red Hat Application Stack. To find out more, we sat down with Sacha Labourey, Chief Technology Officer at JBoss, a division of Red Hat, to get his view on the Red Hat Application Stack offering and Red Hat’s acquisition of JBoss. Here’s what he had to say.
This article was edited and republished from the original source.
by Andrew C. Oliver
At JBoss, I was asked to help write some training materials for “performance tuning JBoss/Java on RHEL/Linux”. It wasn’t a very easy task because I knew the audience would primarily be composed of administrators who might not be interested in the whole system, compounded with the fact that most people mean performance and scalability when they say performance. What I would do to make one single client connect and perform its operations as quickly as possible on a single server is inherently very different from what I’d do for 10000 users connecting to a cluster. The type of performance tuning that I do for an application with no users and all messaging is very different from what I do for a standard web application-type system.
This tip article is edited and republished from the original source.
by Michael Juntao Yuan and Clebert Suconic
Memory leaks are one of the most common bugs in software engineering. A memory leak is created when a developer allocates memory space for an object but forgets to free the memory when the object is no longer in use. Memory leaks are hard to find. But they can cause application crashes, poor performance, or even open security holes if they are not fixed.
Compared with native programming languages such as C and C++, one of the major advantages of the Java platform is that Java has a built-in defense mechanism against memory leaks. The Java Virtual Machine (JVM) runs a Garbage Collector (GC) service periodically to free up memory for objects no long used by the application. So, the developer does not have to remember to the free the objects manually. Automatic memory management in Java is a great feature for improving developer productivity and application quality.
