2

To keep Azure SQL alive MS have provided this workaround , After following this workaround the keep alive messages are sent I traced over wireshark .

But still my application is facing Connection Reset after 30 minutes ..

I have made a normal connection to azure using jdbc libs provided by microsoft. my connection uri is : 

jdbc:sqlserver://server.database.windows.net:1433;database=dbsample;user=username;password=abcd;encrypt=true;hostNameInCertificate=*.database.windows.net;socketKeepAlive=true

Can someone throw some spark over this ?

Arun Kumar G R
  • 178
  • 2
  • 13
  • Long lived tcp connections over the internet never last long, Microsoft are clear in their advice that you need to build in resiliency and expect connection failures - build retries into your application :) – Ed Elliott Mar 15 '18 at 20:03
  • Well Thanks for your reply . Building retries in the application is the last trump card move as it requires application testing flow again . I am expecting a workaround without any change in application , Since Microsoft provided the workaround I beleived in it . But still my issue persists . – Arun Kumar G R Mar 16 '18 at 05:58
  • I thought you might say that which is why just a comment and not an answer :), I honestly wish you the best of luck with it but from experience, adding a cloud service to an application requires some re-writing otherwise you end up with things like this. Maybe someone else knows of a 30 min sql db timeout. – Ed Elliott Mar 16 '18 at 12:49
  • Thanks @EdElliott . will try my best to sort it out . – Arun Kumar G R Mar 16 '18 at 12:57

0 Answers0