ICEpush
  1. ICEpush
  2. PUSH-238

Server RuntimeException can create Push storm

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.3
    • Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
    • Component/s: Push Library
    • Labels:
      None
    • Environment:
      ICEpush
    • Assignee Priority:
      P2

      Description

      If a RuntimeException occurs in the BlockingConnectionServer$RunningServer.service() method, the response sent to the bridge results in a Push storm - a tight, never-ending loop of requests to re-establish the blocking connection which results another exeption, etc.

        Activity

        Repository Revision Date User Message
        ICEsoft Public SVN Repository #35206 Tue May 21 16:03:37 MDT 2013 mircea.toma PUSH-238 Remove stack trace and exception class name from the response since they can become a security breach in certain deployments.
        Files Changed
        Commit graph MODIFY /icepush/trunk/icepush/core/src/main/java/org/icepush/BlockingConnectionServer.java
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #35196 Tue May 21 11:32:22 MDT 2013 mircea.toma PUSH-238 Modified BlockingConnectionServer to respond with a custom server-error message in case an exception is captured during blocking request processing. The server error response sent to the bridge will trigger a re-try executed by the bridge (a number of times, depending on the configuration).
        Files Changed
        Commit graph MODIFY /icepush/trunk/icepush/core/src/main/java/org/icepush/BlockingConnectionServer.java

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Deryk Sinotte
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: