Home › Blogs › Christoph C. Cemper's blog
Java

J2EE and JBoss optimizations article

<< Aspect-Oriented Programming (AOP) a paradigm introduction | JBoss 4.0 DR 2 released - notable new features >>
Wed, 07/30/2003 - 01:11 — Christoph C. Cemper

While we are at it – crying about poor performance is one thing – but maybe this article on JBoss Optimizations lights some bulbs in terms of your wacky J2EE server performance ...

What I appreciate is that this article is no dusty theroetics but based on a fictitious application to show some basic configuration mistakes, frequently made by new J2EE developers, that lead to bad application performance. While the application is fictious, all surrounding issues and optimizations covered are said to originate from real-life consulting experiences in the J2EE and JBoss fields.

Average rating
 
 
 
 
 
(0 votes)

Similar entries

  • J2EE clustering with JBoss

    JBoss clustering, JBoss J2EE compliance, J2EE IDE

  • JBoss 3.2.2 RC 2 (Development Releases) and Jboss 3.0.8 production release

    Released some hours ago: JBoss 3.2.2 RC 2 (3.2.x Development Releases) and Jboss 3.0.8, from the JBoss 3.0.x production release branch variant. They say the new versions only have minor feature enhancements… JBoss is an Open Source, standards-compliant, Enterprise JavaBeans…

  • JBoss 4 Release available - AOP still not performing, hibernate usage simplified

    Seid points me to the official JBoss 4 roll out. Did you know ? It is the first J2EE certified open source application server. Jgroups for Clustering features, usage of Hibernate simplified, but according to Seid the delivered AOP (Aspect…

  • JBoss 4.0 DR 2 released - notable new features

    That sounds nice: the JBoss 4.0 DR 2 from the JBoss 4.0.x Development Releases that was released today aswell a few minutes later features a JBoss JDO implementation for standard Java object persistence a JMS rewrite of the Message service…

  • Aspect-Oriented Programming (AOP) a paradigm introduction

    Aspect-oriented programming (AOP) is an exciting new paradigm that should have the same effect on software development that object-oriented programming (OOP) had 15-20 years ago. AOP and OOP are not competing technologies, but actually complement each other quite nicely. OOP is great for modeling common behavior on a hierarchy of objects. Its weakness is in applying common behavior that spans multiple non-related object models; this is where AOP comes in.