Slow startup time of DM Server

Hi all,

It is taking almost a minute to deploy and start my application. It used to take a second or 2 to start the application before when it was just a regular Java application. Here are some of the log files:

[2009-06-18 11:37:56.720] main <SPKB0001I> Server starting.
[2009-06-18 11:37:59.467] main <SPOF0001I> OSGi telnet console available on port 2402.
[2009-06-18 11:38:03.470] main <SPKE0000I> Boot subsystems installed.
[2009-06-18 11:38:06.458] main <SPKE0001I> Base subsystems installed.
[2009-06-18 11:38:07.707] server-dm-3 <SPPM0000I> Installing profile 'web'.
[2009-06-18 11:38:07.713] server-dm-3 <SPPM0001I> Installed profile 'web'.
[2009-06-18 11:38:12.579] server-dm-6 <SPPM0002I> Server open for business with profile 'web'.
[2009-06-18 11:38:29.394] onnection(2)-10.10.3.197 <SPDE0010I> Deployment of 'core.common' version '1' completed.
[2009-06-18 11:38:31.001] onnection(2)-10.10.3.197 <SPDE0010I> Deployment of 'event.common' version '1' completed.
[2009-06-18 11:38:33.204] onnection(2)-10.10.3.197 <SPDE0010I> Deployment of 'alert.common' version '1' completed.
[2009-06-18 11:38:34.787] onnection(2)-10.10.3.197 <SPDE0010I> Deployment of 'channel.common' version '1' completed.
[2009-06-18 11:38:36.062] onnection(2)-10.10.3.197 <SPDE0010I> Deployment of 'codetemplate.common' version '1' completed.
[2009-06-18 11:38:37.716] onnection(2)-10.10.3.197 <SPDE0010I> Deployment of 'config.common' version '1' completed.
[2009-06-18 11:38:39.058] onnection(2)-10.10.3.197 <SPDE0010I> Deployment of 'connector.common' version '1' completed.
[2009-06-18 11:38:40.528] onnection(2)-10.10.3.197 <SPDE0010I> Deployment of 'extension.common' version '1' completed.
[2009-06-18 11:38:41.937] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'message.common' version '1' completed.
[2009-06-18 11:38:43.956] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'protocols.common' version '1' completed.
[2009-06-18 11:38:45.230] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'settings.common' version '1' completed.
[2009-06-18 11:38:46.603] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'status.common' version '1' completed.
[2009-06-18 11:38:48.028] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'user.common' version '1' completed.
[2009-06-18 11:39:15.001] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'core.client' version '1' completed.
[2009-06-18 11:39:17.269] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'event.client' version '1' completed.
[2009-06-18 11:39:19.170] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'extension.client' version '1' completed.
[2009-06-18 11:39:21.104] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'config.client' version '1' completed.
[2009-06-18 11:39:23.489] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'user.client' version '1' completed.
[2009-06-18 11:39:25.367] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'globalscript.client' version '1' completed.
[2009-06-18 11:39:28.805] onnection(4)-10.10.3.197 <SPDE0010I> Deployment of 'status.client' version '1' completed.
[2009-06-18 11:39:33.139] server-dm-2 <SPDE0020E> Application context creation failure for bundle 'channel.client'.

As you can see it took over a minute to get thus far before failing on the last bundle I have added. I still have a bunch more modules to deploy as well, so startup time could be somewhere near 3 minutes! Anyone know anything about this?

Thanks!

What kind of Java application did you start with? A WAR file or something else?

If you are using the Eclipse based tools to deploy each bundle, then this introduces some delays over and above the time that dm Server takes to deploy the bundle and any time the bundle takes to build its beans.

In general, you might consider putting the (non-web) bundles providing package dependencies in the repository/bundles/usr directory of dm Server and then deploying the rest of the application, which will cause dm Server to fault in the other bundles from the repository.

Also, I wonder how much code is in the application and whether it really is appropriate to split it into 20+ bundles. For example, would it perhaps make more sense to have just a common and a client bundle?

Thanks Glyn,

This is just a regular java application split into bundles. In this case, it is a swing application. We had to split them into this many bundles because we need our application more modular to be able to hot swap out specific pieces.

We used to have just a client and a common "bundle" in our distros, but that's what made us decide to go more modular ;) So it looks like it's normal for full deploys to take this long to DM server from eclipse?

Certainly the time to deploy a collection of bundles one at a time using the Eclipse tooling has an overhead proportional to the size of the collection.

To speed this up, you'd need either to put some of the bundles in the repo and deploy the others or batch up the deploys. Perhaps doing the deployment with the server down and then starting the server would show the benefit of batching.

If you would like to dig into the Eclipse tooling behaviour further, please say so and I'll move this thread to the tooling forum.