Klaus Nossek

Subscribe to Klaus Nossek: eMailAlertsEmail Alerts
Get Klaus Nossek: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by Klaus Nossek

(This is the second part of a two-part article. The first part appeared in the September 2005 issue of WebSphere Journal.) Large session objects decrease the JVM memory available for creating and executing application objects. As a result, performance can degrade as the decreased available heap memory leads to more frequent garbage collection. Another factor is that the in-memory lifetime is always longer than the required usage lifetime, and so the number of sessions occupying space in the Java heap is usually greater than the number of active users. A session expiration time is configurable in WebSphere Application Server and is actually required to avoid a case when a user has to log in again after only a few seconds of inactivity. The release of a session is the responsibility of WebSphere Application Server and the portlet container. The serialized session size ... (more)

Creating Well Performing Custom Code

This article provides general guidance for creating well performing custom code for IBM WebSphere Portal. Custom code does not only refer to portlets (although they are the most common programming model for portals), but also includes code for WebSphere Portal themes and skins. Since these are implemented using the same basic technologies used for portlets, many performance considerations are applicable in the same way. Regarding portlets, this article focuses on standardized portlets following the Java Portlet Specification, JSR 168, and the corresponding implementation in WebS... (more)