Two years ago I’ve been to (page closed). It was amazing meeting with Luc Duponcheel sponsored by SUN. The topic was “what’s new in JEE6”. He was showing CDI, DI and Glassfish 3 and made an entrance to scala, saying it’s amazing future jvm language.

This year I will listen what Oracle is going to present 28 of March in Warsaw.
And I plan to go to Geecon in May this year!


Interesting thing about system.out.println how huge bottleneck it creates being used while asking db through RESTful webservice. This article pushed me to experiment by my own with VisualVM and JMeter. Both are great tools.

(About VisualVM, yesterday I’ve made a complaint about it, but today I’ve got notification to upgrade Visual sampler what really helped and turned this tool into very handy stuff;)


We put lately more attention to monitoring and tuning our systems – mainly db.  I tried to refresh in mind how to check active sessions on jvm for specified app. I’ve experimented with VisualVM, but it didn’t satisfied me. I simply does not work out-of-the-box. After registering jmx remote host, I could not expand apps list…

I need something more standard and working then that. I’ve run “jconsole”  (attached to each jdk copy).

Then I’ve connected to:

and under the path: com.sun.appserv/Manager/myAwesomeAppName/server/Attributes

I’ve found to variables: activeSessions and sessionCount. Take a look


A quick remark for the future that is worth to remember. I suppose there is one of good coding principles to keep your imported WSDL files up-to-date.

I was writing distributed ticket handling system. I needed some stateful service for this. I’ve implemented this storage with database behind and ejb-webservice as endpoint. While I was coding I’ve wrote module for creating, modifying and closing ticket in natural order. For every action I wrote separate module. During  implementation (after having done first two modules) I’ve implemented a new method in ejb-webservice what changed it’s WSDL file which I’ve used in the third module (but having not updated first two). You could imagine that this is wrong. My app server (glassfish) [I suppose] creates one wsdl file in memory for one endpoint so there is no possible way to keep two different versions of it (one with additional method and one without). Of course before that deployment and compilation were fine. This issue turned out while testers went through test scenarios.