Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.2.0
    • Fix Version/s: EAP_EWP 5.3.0.ER1
    • Component/s: IIOP
    • Labels:
      None
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      In previous versions of JBoss EAP 5, a problem with thread pool exhaustion was being encountered in some circumstances. This release has added a JacORB QoS to allow client connections to be completely closed if an error is detected rather than allowing them to be reused. This can avoid the thread pool exhaustion issues.
      Show
      In previous versions of JBoss EAP 5, a problem with thread pool exhaustion was being encountered in some circumstances. This release has added a JacORB QoS to allow client connections to be completely closed if an error is detected rather than allowing them to be reused. This can avoid the thread pool exhaustion issues.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW
    • Bugzilla Update:
      Perform

      Description

      closeAllowReopen causing thread pool exhaustion, since the threads are hanging around. Need to be able to have eager closing to free the threads.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ncross Nick Cross
                  Reporter:
                  bmaxwell Brad Maxwell
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: