• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Handling Timeout scenarios

 
Ranch Hand
Posts: 312
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

This is very generic question. Sorry if this is not the right forum.
Currently we have a scenario in our (3 tier) application where in during communication with backend services the communication just timeouts.
In these cases the error the user encounters is not consistent varying from proper backend error like Could not communicate to just no results to null pointer stack traces etc. This stems from the fact that we have not provided for handling such timeouts in our application.

My question here is from UI perspective. What is the generic approach to detecting and handling timeout scenarios in a consistent fashion. Say like showing the user a standard page.


-Manish
 
Bartender
Posts: 1638
IntelliJ IDE MySQL Database Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am not sure whether your question is about "generically handling timeouts in UI" or "generically finding out whether it is a timeout".
If it is the first one then i dont have the skills to answer that
For second, i dont think there is a "generic" way of doing that because timeouts may happen at different levels:
HTTP connection timeout.
Database query timeout
Transaction timeout
etc.
So, in order for the UI to handle it, the backend should either throw a typed exception or a proper error code(whichever model your application follows). Otherwise, UI will not be able to concretely assert whether it was a timeout or some other error.
Hope this helps
reply
    Bookmark Topic Watch Topic
  • New Topic