Worklight: Service connection failed Dialog Box - service

Question

I am facing an unexpected issue that is when I am running App
most of the times a dialog box open up and saying "Application failed
connection to the service " See snapshot:
Though after two or three times pressing "Reload" button on this dialog connects App with WL Server and then App works fine. But if I kill App and then re-run it , again same dialog appears.
It also appears when you first time run App after installing on a device.
My App was running perfectly fine from two months back.
The only new thing that I have done is Push Notification. This is the
only new feature that I have added in the App.
Any suggestion on this?
What could be the root cause of this issue? How can I trace it?
And if I want to disable this dialog and instead show a
custom message (alert) on screen. Because this dialog box reveals the
running service / WL server URL.
In the console it only shows "Application failed connection to the service "
And while clicking on the Details option on the dialog box. It shows correct address of WL Server. And after three/four times of reload it connects App with server and then works fine, and afterwards goes fine and doesn't show anything.
The Logs are given below:
Apr 15 14:24:51 iPhone myApp[2746] <Warning>: [LOG] ondeviceready event dispatched
Apr 15 14:24:51 iPhone myApp [2746] <Warning>: {
appVersionPref = "1.0";
freeSpace = 13572620288;
wlSkinLoaderChecksum = "(null)";
wlSkinName = default;
}
Apr 15 14:24:51 iPhone myApp [2746] <Warning>: [LOG] Application did not define an i18n messages object, skipping translation.
Apr 15 14:24:51 iPhone myApp [2746] <Warning>: [LOG] wlclient init started
Apr 15 14:24:51 iPhone myApp [2746] <Warning>: [LOG] Read cookies: null
Apr 15 14:24:51 iPhone myApp [2746] <Warning>: [LOG] CookieMgr read cookies: {}
Apr 15 14:24:57 iPhone myApp [2746] <Warning>: [LOG] Connection went Down: Mon Apr 15 2013 14:24:57 GMT+0300 (AST)
Apr 15 14:24:57 iPhone myApp [2746] <Warning>: [ERROR] Client init failed. Connection to the service is not available.
Apr 15 14:25:07 iPhone myApp [2746] <Warning>: [LOG] ondeviceready event dispatched
Apr 15 14:25:07 iPhone myApp [2746] <Warning>: {
appVersionPref = "1.0";
freeSpace = 13572620288;
wlSkinLoaderChecksum = "(null)";
wlSkinName = default;
}
by clicking Details:
Apr 15 2013 23:55:17 GMT+0300 (AST)
Apr 15 23:55:17 iPhone myApp[3116] <Warning>: [ERROR] Client init failed. Connection to the service is not available.
Apr 15 23:55:19 iPhone myApp[3116] <Warning>: WLReachability Flag Status: -R -----l- networkStatusForFlags
Apr 15 23:55:59 iPhone kernel[0] <Debug>: launchd[3120] Builtin profile: MobileSafari (sandbox)
Apr 15 23:56:02 iPhone kernel[0] <Debug>: launchd[3121] Builtin profile: syncdefaultsd (sandbox)
Apr 15 23:56:21 iPhone myApp[3116] <Warning>: Copied text: 'App Diagnostics
Time : Mon Apr 15 2013 23:55:19 GMT+0300 (AST)
Application Name : myApp
Application Version : 1.0
Service URL : https://www.mydomain.com.bh:443/AppProject/apps/services/api/myApp/iphone/
Device Platform : iPhone
Device Version : 6.1
Screen Resolution : 320x480
Airplane Mode : Not available
Using Network : WIFI
Wifi Name : Not available
Mobile Network Type : Not available
Carrier Name : Not available
IP Address : 192.168.109.101
Error Code : UNRESPONSIVE_HOST
Error Message : Connection to the service is not available.
HTTP Status :

Answer 1

It sounds like there's a network issue preventing you from connecting to your Worklight server.
This can be due to many different reasons, to list some:
Poor WiFi/3G
Faulty device
Firewall issues on the network where the webserver is hosted
Worklight server issue
To ensure that you are indeed reaching the server I would suggest using a network sniffer. One tool that runs on Windows is Fiddler.
Fiddler can be set up as a reverse proxy where your device will be making calls to the proxy. The proxy will then route your request to the web server but it will also log the information so you can view it.
If you are on Windows, I would suggest installing Fiddler and following Option #2 of this answer.
You should then be able to see if your requests are reaching the server and continue investigation from there.