dm Server
  1. dm Server
  2. DMS-2396

As a user I would like to be able to configure the startup timeout which is currently hardcoded at 30 seconds

    Details

    • Type: Story Story
    • Status: To Do To Do
    • Priority: Blocker Blocker
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Issue Links

        Activity

        Hide
        Glyn Normington (c) added a comment - - edited

        This should have been raised as a defect, but a task is closer than a user story. (JIRA does not permit us to convert a user story or a task into a defect.)

        Show
        Glyn Normington (c) added a comment - - edited This should have been raised as a defect, but a task is closer than a user story. (JIRA does not permit us to convert a user story or a task into a defect.)
        Hide
        Glyn Normington (c) added a comment -

        Please could you provide some details so that we can consider why you are seeing this.

        What hardware are you using, particularly what is the processor speed and how much RAM do you have?

        What operating system are you using?

        What is the JVM version (displayed via java -version)?

        What are the precise steps to recreate the problem? In particular, what applications do you deploy and how many times do you restart before you notice the slow down?

        If you could attach serviceability/log/log.log for the failing run to this issue, that may help.

        Finally, if you restart dm Server with the -clean option, is it still slow?

        Thanks!

        Show
        Glyn Normington (c) added a comment - Please could you provide some details so that we can consider why you are seeing this. What hardware are you using, particularly what is the processor speed and how much RAM do you have? What operating system are you using? What is the JVM version (displayed via java -version)? What are the precise steps to recreate the problem? In particular, what applications do you deploy and how many times do you restart before you notice the slow down? If you could attach serviceability/log/log.log for the failing run to this issue, that may help. Finally, if you restart dm Server with the -clean option, is it still slow? Thanks!
        Hide
        Candy Chiu added a comment - - edited

        What hardware are you using, particularly what is the processor speed and how much RAM do you have?
        I am running Windows 7 as a VM inside Ubuntu. I have an Intel Core 2 Duo T7700 @ 2.4GHZ. The VM is allotted 2.5GB of RAM.

        What operating system are you using?
        Windows 7

        What is the JVM version (displayed via java -version)?
        1.6.0_17

        What are the precise steps to recreate the problem? In particular, what applications do you deploy and how many times do you restart before you notice the slow down?
        Usually this happens when I have a few other applications running simultaneously- STS, one or two DB servers, chrome and/or IE, windows explorer, 1-3 other tools.
        I found a way around the problem by shutting down all the application before I started the dm Sever. It worked. However, I had to edit my files via nodepad (or equivalent) and build with maven in a command prompt.

        If you could attach serviceability/log/log.log for the failing run to this issue, that may help.
        After I started using the workaround, the logs that showed the error were gone. Essentially, the log showed that dm server tried to start, then a few lines of "Reference .. is waiting for Service". After 30 seconds, it showed "Kernel failed to start within 30 seconds". You may refer to the forum post for the complete message. Mine's the same as what Janx posted at Jan 25th, 2010, 12:42 AM.

        Finally, if you restart dm Server with the -clean option, is it still slow
        -clean didn't seem to help.

        You mentioned in your reply to Janx that "The 30 second timeout is unfortunately hard coded at 30 seconds. We should make that configurable to allow for slow systems like yours. Please raise a user story JIRA issue if you would like to." That's the reason this was raised as a user story instead of a defect or a task. This is not a blocker anymore as I found a workaround, however, it still hurts convenience and efficiency.

        Show
        Candy Chiu added a comment - - edited What hardware are you using, particularly what is the processor speed and how much RAM do you have? I am running Windows 7 as a VM inside Ubuntu. I have an Intel Core 2 Duo T7700 @ 2.4GHZ. The VM is allotted 2.5GB of RAM. What operating system are you using? Windows 7 What is the JVM version (displayed via java -version)? 1.6.0_17 What are the precise steps to recreate the problem? In particular, what applications do you deploy and how many times do you restart before you notice the slow down? Usually this happens when I have a few other applications running simultaneously- STS, one or two DB servers, chrome and/or IE, windows explorer, 1-3 other tools. I found a way around the problem by shutting down all the application before I started the dm Sever. It worked. However, I had to edit my files via nodepad (or equivalent) and build with maven in a command prompt. If you could attach serviceability/log/log.log for the failing run to this issue, that may help. After I started using the workaround, the logs that showed the error were gone. Essentially, the log showed that dm server tried to start, then a few lines of "Reference .. is waiting for Service". After 30 seconds, it showed "Kernel failed to start within 30 seconds". You may refer to the forum post for the complete message. Mine's the same as what Janx posted at Jan 25th, 2010, 12:42 AM. Finally, if you restart dm Server with the -clean option, is it still slow -clean didn't seem to help. You mentioned in your reply to Janx that "The 30 second timeout is unfortunately hard coded at 30 seconds. We should make that configurable to allow for slow systems like yours. Please raise a user story JIRA issue if you would like to." That's the reason this was raised as a user story instead of a defect or a task. This is not a blocker anymore as I found a workaround, however, it still hurts convenience and efficiency.
        Hide
        Glyn Normington (c) added a comment -

        Converting back to story now we understand the purpose of the JIRA.

        Show
        Glyn Normington (c) added a comment - Converting back to story now we understand the purpose of the JIRA.
        Hide
        Glyn Normington (c) added a comment -

        Tagging for Virgo.

        Show
        Glyn Normington (c) added a comment - Tagging for Virgo.
        Hide
        Glyn Normington (c) added a comment -

        DMS-2424 is providing a work-around for this issue in the dm Server service stream.

        When this issue is addressed properly in Virgo, we should decide whether it is better to make the timeout configurable or infinite. A configuration parameter increases the surface area of the kernel that the user has to deal with and does not necessarily provide much useful function.

        Show
        Glyn Normington (c) added a comment - DMS-2424 is providing a work-around for this issue in the dm Server service stream. When this issue is addressed properly in Virgo, we should decide whether it is better to make the timeout configurable or infinite. A configuration parameter increases the surface area of the kernel that the user has to deal with and does not necessarily provide much useful function.

          People

          • Assignee:
            Unassigned
            Reporter:
            Candy Chiu
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              First Response Date: