Wildfly 10 + JBoss OSGi + Spring + Gemini Blueprint startup is slow and fills memory [message #1736459] |
Wed, 29 June 2016 13:59 |
Hannu Lahtinen Messages: 1 Registered: June 2016 |
Junior Member |
|
|
Hi,
I have been migrating a large software project from Java 7 to Java 8. That meant I also had to migrate from JBoss AS 7.2 to Wildfly(10) as well as migrating from Spring 3.2 to Spring 4.2, which in turn caused the need to update Gemini Blueprint.
I have ran in to issues with slow startup time and am seeking for advice. I have created a thread about the same issue on JBoss OSGi but have not received any answers so far. (This is my first post so I can't link it to this post but I can link it later if someone is interested. It can also be found from Google with keywords: jboss osgi thread 270900)
I'm fairly certain the issue is with dependency lookup but it only appears after I add blueprint extender bundle as a capability.
I have attached an example standalone.xml that demonstrates the behavior. If Spring ORM or Blueprint Extender is commented out this configuration starts in less than 5 seconds. If both of the aforementioned bundles are included the startup takes anywhere from 15 to 70 seconds.
I'm aware Spring ORM and Spring Context have a cyclic dependency in their manifests and after I have removed that manually this configuration starts in 5 seconds with Spring ORM and Blueprint Extender included. The problem is similar issues arise throughout a huge stack of bundles that we currently deploy into our application server and tracking them down has proven to be very difficult.
|
|
|
Powered by
FUDForum. Page generated in 0.03746 seconds