Lloyd Hagemo

Subscribe to Lloyd Hagemo: eMailAlertsEmail Alerts
Get Lloyd Hagemo: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by Lloyd Hagemo

In a production environment, memory leaks can force organizations to add more memory and hardware resources. They can even cause an application to crash unexpectedly. In theory, Java memory leaks should not emerge as a development or production issue because the garbage collector is responsible for memory management. Built-in Java memory management enables developers to sidestep tedious memory management considerations and is a fundamental reason why Java is a relatively straightforward development environment. Practically, however, the garbage collector function is unable to accurately address all memory management considerations, due to programming oversights and Java language program loopholes that allow memory leaks. The garbage collector's job is to periodically collect unreferenced objects. Java memory leaks typically occur because the garbage collector reserv... (more)

Creating a Framework - J2EE pattern frameworks provide template for flexible and modular architecture

Many patterns have been published for J2EE applications. By developing and connecting multiple patterns, developers can create a framework that improves the stability, performance, and scalability of their J2EE application architectures. Because the number of patterns continues to expand, it can be difficult for developers to select the best combination of patterns to create frameworks that optimize J2EE applications and fulfill specific IT or business requirements. Similar to individual patterns, frameworks serve as development process templates that enable organizations to str... (more)

One Access Point to Rule Them All - Front Controller pattern simplifies integration challenges

The concept of a central point of access to an application or set of applications is not new. For more than 30 years, companies have been writing, enhancing, and maintaining applications written to transactional systems such as CICS and IMS for IBM OS/390 mainframes. These mature mainframe applications are similar to the J2EE applications developed today because they provide an environment for building customer transaction applications that support distributed enterprise computing. An effective application infrastructure must include a common point of access to perform applicati... (more)

J2EE Application Performance Analysis

How well does your application perform? It is probably one of the toughest questions to answer accurately. It is not only a question of how many requests your application serves per second or per minute, but also how your application scales with respect to other performance metrics. It remains challenging to quantify application health quickly because there are a number of variables to consider. This article outlines the key terminologies associated with measuring Java 2 Enterprise Edition (J2EE) application performance. Importantly, this article also outlines best practices for ... (more)

Dealing with Large Database Result Sets

When designing J2EE (Java 2 Platform, Enterprise Edition) applications, developers often find themselves challenged to create a display for large database result sets. Improper treatment of the large result set display can lead to poor response time and, ultimately, lost productivity and sales. Developers must be cautious when they deal with large results, particularly when they choose entity beans as a data access layer. Based on our experience, entity beans negatively impact performance when returning large result sets, due to the Enterprise JavaBean (EJB) container's extensive ... (more)