Articles

High Performance Message Processing with BMT Message-Driven Beans and Spring
Addressing the traditional MDB-based message consumption model, Dmitri Maximovich and Eugene Kuleshov show how this scenario can be refactored to increase performance with non-transactional message retrieval while retaining once-and-only-once quality of service. Jan. 30, 2006

Peak performance tuning of CMP 2.0 Entity beans in WebLogic Server 8.1 and 9.0
Tuning CMP 2.0 EJBs is as much an art as it is a science. In this detailed article, Dmitri Maximovich takes the reader on a tour from concurrency strategies and caching between transactions, to the read-mostly pattern and choosing an optimal cache size. Nov. 14, 2005

Parallel task execution in J2EE using the Work Manager specification
As it stands, the J2EE specification provides no easy way to initiate the execution of parallel tasks. JSR 237, the Work Manager for Application Servers specification, changes this. In this article, Dmitri Maximovich introduces the specification, and provides an example of how to use it. His code runs on the current beta of WebLogic Server 9.0. May. 16, 2005

Weblogs

JMS messaging with Spring...nice but there is no magic: Some gotchas and things to keep in mind when using Spring's JMS support in J2EE server.
Posted by Dmitri Maximovich (maximdim) on October 19, 2005 at 16:56 PDT | Comments (2)  

Oracle nightmare? I think not yet.: Are open source databases ready to replase Oracle in the Enterprice applications? May be not now.
Posted by Dmitri Maximovich (maximdim) on September 22, 2005 at 12:22 PDT | Comments (5)  

What to do if your database doesn't support XA transactions?: If your database doesn't support XA transactions there are still a way to enlist it in XA transaction by using Last Resource Commit optimization available in WebLogic 9.
Posted by Dmitri Maximovich (maximdim) on May 24, 2005 at 12:23 PDT | Comments (5)  

Optimal configuration of EJB Entity cache in WebLogic: If you read my previos post you probably agree that choosing right size for the Entity cache is vitally important, and not only from performance optimization point of view. From one hand if cache size is too large your application memory consumption would be unnecessary high but if you go to other extreme and configure cache size too small we're risking running into CacheFullException. So how to choose optimal cache size for all your Entity beans?
Posted by Dmitri Maximovich (maximdim) on April 20, 2005 at 06:39 PDT | Comments (2)  

EJB Entity cache and transactions: Everybody know that EJB Container supports Entity Beans caching. Usually cache size is configured per Bean in vendor-specific deployment descriptor. Probably because it's described in documentation purely as performance-optimization parameter not all developers realize that there are some other implications which could dictate selection of proper cache size.
Posted by Dmitri Maximovich (maximdim) on April 14, 2005 at 11:50 PDT | Comments (5)