Uploaded image for project: 'Geronimo'
  1. Geronimo
  2. GERONIMO-585

No indication when DefaultWorkManager pool is exhausted

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.0-M3
    • 1.2
    • connector
    • None

    Description

      I created a connector that executes 8 long-running Work objects at startup (DefaultWorkManager pool size = 10). If I deploy it twice, the second deploy operation hangs, causing the deploy tool to hang as well (and in fact the server hangs if you try to shut down and you have to kill -9 it). There's no evidence what the problem is. It would be nice if we at least printed a debug message or something when you submit work and there's no worker thread available. In truth, there are better ways to code the RA, but the hangs, and the fact that it hangs the deployer and server shutdown too...

      Attachments

        1. WorkExecutorPoolImpl.patch
          2 kB
          Krishnakumar B

        Activity

          People

            hogstrom Matt Richard Hogstrom
            ammulder Aaron Mulder
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: