EJB 3.1 - Initialize your application

EJB 3.1's spec is out for community's review. It is primarily targeted to solve EJB 3 problems but among the new specs I personally like container initialization and shutdown callbacks, asynchronous stateless session bean calls and cron-like EJB timers. It also include other (great) features like stateful web services.

Book

A good friend of mine recommended me to read this. I do recommend reading it for people with no so amazing negotiation skills :)

WebSphere vs JBoss

At the moment of time I am working to improve an application that suffers high memory consumption. So, my basic choice is to profile application with WebSphere (production environment), but that sucks WebSphere is slow. After a while I change to profile the application on JBoss and my life is whole easier now. However, after profiling I started observing memory allocation behavior when the application is running in JBoss against WebSphere. Result is that with a couple of clicks WebSphere allocated 1G memory. The same amount of clicks on JBoss will use 600M of memory and even pounding JBoss with more clicks does not make a huge difference. The difference might be easily the JDKs used on JBoss and WAS; JBoss was running on Sun JDK 1.4 and WAS was running on IBM JDK. I have no clue at the moment.

 

I also tried to use WebSphere Application Developer Suit to profile my application. At the end of the day, it just wrecked my installation. It must be me. No seriously, I haven't been patient enough to work with WebSphere recently. Maybe because JBoss is there :)

JProfiler 3, WebSphere 5

JProfiler 3 wrecked WebSphere 5's installation. I still don't know what the problem is, but WAS now only starts from JProfiler. Damn! I still don't know why one should pay for WAS while there is a JBoss. Just wondering...