Uploaded image for project: 'Runtime'
  1. Runtime
  2. RUNTIME-784

Enhance servercomm behavior on request failure

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • 4.3.0
    • None
    • None
    • None
    • 4.3 RC2
    • 1 - Middle term
    • 2 - Normal

      When is request failed this can be due to several problems :

      • network down
      • server down
      • network timeout
      • authentication timeout

      Instead of directly asking the user, we should display a waiting message to try to determine the reason.
      During this time, we should launch another request to a know pipeline that will allow to detect if server was restarted (reason 2) or if authentication is off (reason 4) or finally if this is a network issue (1 or 3) and we could associate different behavior

      we should think in preloading

          [RUNTIME-784] Enhance servercomm behavior on request failure

          Raphaël Franchet added a comment -

          Cedric a écrit

          j'en ai marre des "erreurs systèmes" juste parce que ma session a expiré et que le ping du back-office se prend le formulaire. Pourtant je suis censé avoir le cookie qui me relogue tout seul, mais ça doit pas bien marcher...

          On pourrait pas en deux secondes mettre un header de response dans le FormBasedCredentialsProvider et le tester en JS pour avertir que la session a expiré et que l'utilisateur pourra rien faire d'autre que de se reloguer ?
          Note bien que dans ce cas, on pourrait même afficher un formulaire en surimpression et ne pas quitter le BO...

          Raphaël Franchet added a comment - Cedric a écrit j'en ai marre des "erreurs systèmes" juste parce que ma session a expiré et que le ping du back-office se prend le formulaire. Pourtant je suis censé avoir le cookie qui me relogue tout seul, mais ça doit pas bien marcher... On pourrait pas en deux secondes mettre un header de response dans le FormBasedCredentialsProvider et le tester en JS pour avertir que la session a expiré et que l'utilisateur pourra rien faire d'autre que de se reloguer ? Note bien que dans ce cas, on pourrait même afficher un formulaire en surimpression et ne pas quitter le BO...

          Raphaël Franchet added a comment -

          They are 2 different cases : no response or non-xml response
          The dispatcher should be unauthentified, to allow it to answer a specific response
          We could try to re-authentify in another browser tab
          Depending on the workspace we could should a permanent message saying communication has problems and stop showing popups
          When clicking Ok on the popup we could stop the following handleBadResponse messages

          Raphaël Franchet added a comment - They are 2 different cases : no response or non-xml response The dispatcher should be unauthentified, to allow it to answer a specific response We could try to re-authentify in another browser tab Depending on the workspace we could should a permanent message saying communication has problems and stop showing popups When clicking Ok on the popup we could stop the following handleBadResponse messages

            Unassigned Unassigned
            raphael Raphaël Franchet
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: