Problem starting dm Server out of the box

[Janx]

Thanks again for all your help.

You are correct - attempting to start with -clean produces the same output as the first attempt. I'll open a ticket on that issue.

I could run under the host OS (Windows), but I'm doing some investigation for solutions for work, and we're on all Linux there. I'm going to look into improving the performance of VirtualBox and see if anything can be gained there.

Thanks again -
Gregg

[jcperron]

I have the same problem 'Kernel failed to start within 30 seconds.' and for now I can't get any better computer to improve the performance. Does someone found a workaround for this ?

The source of dmserver is now public maybe I can change the code to hardcode another value ? As I see no other solution I will check if it's possible.

[Glyn Normington]

We are seeing a similar timeout on some of our continuous integration servers and we have a theory that it is associated with the repository scanning logic (one of the dumps produces showed the repository scan still in progress and other bundles waiting for the repository to be available), which fits in with the strange repository message mentioned above. 30 seconds is a long time even on a slowish box, so we are going to profile the startup and focus in on the repository scanning.

[candy.chiu.ad]

I encountered the same problem. The server seems to take longer time on consecutive starts. Eventually, it fails to start within 30 seconds.

https://issuetracker.springsource.com/browse/DMS-2396

[pdurcek]

I'm having the same issue on one of my machines. Is there currently any workaround for this?

[Glyn Normington]

We are currently testing 2.0.2 which fixes the problem and should ship later this week.

[cadee]

I have tried setting the timeout in the kernel.properties file to 0 so that there is no timeout, but it behaves the same.

[Glyn Normington]

The deployer.timeout in the kernel properties file controls the timeout applied when applications are deployed. The timeout referred to earlier in this thread is not configurable and controls the startup of the dm Server kernel, but has been increased as of 2.0.2, to 30 minutes IIRC.