Comments on: Let’s play with OSGi, Spring and Maven, part 1 http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/ Short remarks from the Java world Fri, 21 Nov 2008 16:58:04 +0000 http://wordpress.org/?v=2.6.1 By: Honza Novotný http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/#comment-482 Honza Novotný Fri, 30 May 2008 06:12:20 +0000 http://blog.krecan.net/?p=74#comment-482 Thanks, that would be much interesting. Thanks, that would be much interesting.

]]> By: Lukáš Křečan http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/#comment-481 Lukáš Křečan Fri, 30 May 2008 05:58:09 +0000 http://blog.krecan.net/?p=74#comment-481 If you do not know, ask the machine. We can do a small experiment. I will try to write about it in part 3. If you do not know, ask the machine. We can do a small experiment. I will try to write about it in part 3.

]]> By: Honza Novotný http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/#comment-480 Honza Novotný Fri, 30 May 2008 04:26:14 +0000 http://blog.krecan.net/?p=74#comment-480 You have my copliment ;-) . It's nice short and well understandable article. I have been thinking about different thing since last CZJUG - and that is, whether OSGI could help to minimize classloader leak problems in web application. From the speech of Michal Malohlava I assume that it does not. OSGi is mostly about dynamic installing and uninstalling bundles - but when the bundle you are uninstalled haven't clear all its references and memory allocated for it could not be GCed, this principle goes in vain. And - leaking memory in web programming is SOOO easy. As I understand OSGi wouldn't help to solve this problem, more than that - by its nature OSGi will create dozens of classloaders, so it is possible much harder to find out what's going in. Finally, when you leak classloaders, you'll run out of PermGenSpace memory and you wouldn't be able to dynamicaly install/uninstall modules at all. Am I right or miles out? You have my copliment ;-) . It’s nice short and well understandable article.

I have been thinking about different thing since last CZJUG - and that is, whether OSGI could help to minimize classloader leak problems in web application. From the speech of Michal Malohlava I assume that it does not.

OSGi is mostly about dynamic installing and uninstalling bundles - but when the bundle you are uninstalled haven’t clear all its references and memory allocated for it could not be GCed, this principle goes in vain. And - leaking memory in web programming is SOOO easy. As I understand OSGi wouldn’t help to solve this problem, more than that - by its nature OSGi will create dozens of classloaders, so it is possible much harder to find out what’s going in. Finally, when you leak classloaders, you’ll run out of PermGenSpace memory and you wouldn’t be able to dynamicaly install/uninstall modules at all.

Am I right or miles out?

]]>