Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EJB3_1 1.0.4
    • Fix Version/s: EJB3_1 1.0.5
    • Component/s: core
    • Labels:
      None

      Description

      Recent hanging jobs on Mike have shown that the remoting client socket timeout (default = 30 mins) doesn't work because of JBREM-1188. The workaround to the issue is to explicitly set a timeout value. Even if it wasn't a bug, the default timeout of 30 minutes is a bit too high. Maybe a timeout of 10 minutes (or lesser) would be sufficient. I'll open a forum thread just in case someone has any inputs for a sensible timeout value.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jaikiran Jaikiran Pai
                Reporter:
                jaikiran Jaikiran Pai
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: