Hi,
We have built an application that uses JDE 4.2.1 and connects to an HTTP based rest service to fetch data. Already thousands of users are active users of this application, however, some of our users are reporting that the application fails to connect to the web service.
We had already tried all the different network connectivity techniques discussed on this forum, to make sure that we try every transport mechanism available on any user's device (e.g. WiFi, BES, WAP2 and DirectTCP) except BIS because we are not ISV partners and WAP because we can not ask our users to give APN settings inside the application.
After all else failed, we integrated the network diagnostic tool in our code and asked the users having problems to send us their logs. Here comes the most frustrating part. The log shows failed connections for all transport modes but the user insists that all other applications for example gmail and opera are working on their device. I have attached such a log from a user who insists that our application only works on WiFi while his other applications (opera, gmail etc.) do work on his regular EDGE/GPRS connection. Looking at this log, we are at the end of our wits. Can anyone shed any light on what other possibility we can try? Please note that this log is from the first request sent by the application so any "tunnel failed" messages cannot be because of excessive http connections.
I will really appreciate a quick response from the RIM team if they are reading this. Please see the log below. BTW, we have masked the URL for privacy reasons. Please assume that the user who reported this issue is able to browse to http://www.oururl.com from his or her blackberry browser.
Thanks.
Perturbed BB developers.
-------------------------------------------------------------------------------------------------
Transport: Direct TCP (HTTP)
Result: fail
Response: -1
Length: -1
URL: http://www.oururl.com:80/helpdata/blackberry/OurApp.jad;deviceside=true
Log:
Coverage Status: Online
Connecting to http://www.oururl.com:80/helpdata/blackberry/OurApp.jad;deviceside=true
Openning connection
Tunnel failed
========END OF LOG========
Transport: Direct TCP (Socket)
Result: fail
Response: -1
Length: -1
URL: socket://www.oururl.com:80;deviceside=true
Log:
Connecting socket to socket://www.oururl.com:80;deviceside=true
Openning connection
Tunnel failed
========END OF LOG========
Transport: MDS (HTTP)
Result: fail
Response: -1
Length: -1
URL: No url available
Log:
Skipped test: No MDS service records found.
Skipped test: MDS coverage is not available
Transport: MDS (Socket)
Result: fail
Response: -1
Length: -1
URL: No url available
Log:
Skipped test: No MDS service records found.
Skipped test: MDS coverage is not available
Transport: Unite (HTTP)
Result: fail
Response: -1
Length: -1
URL: No url available
Log:
Skipped test: No Unite service records found.
Skipped test: Unite coverage is not available
Transport: Unite (Socket)
Result: fail
Response: -1
Length: -1
URL: No url available
Log:
Skipped test: No Unite service records found.
Skipped test: Unite coverage is not available
Transport: BIS-B (HTTP)
Result: fail
Response: -1
Length: -1
URL: www.oururl.com:80/helpdata/blackberry/OurApp.jad;***
Log:
Coverage Status: Online
Connecting to http://www.oururl.com:80/helpdata/blackberry/OurApp.jad;deviceside=false
Openning connection
Invalid url parameter.
========END OF LOG========
Transport: BIS-B (Socket)
Result: fail
Response: -1
Length: -1
URL: www.oururl.com:80/helpdata/blackberry/OurApp.jad;***
Log:
Connecting socket to socket://www.oururl.com:80;deviceside=false
Openning connection
Invalid url parameter.
========END OF LOG========
Transport: WAP (HTTP)
Result: fail
Response: -1
Length: -1
URL: No url available
Log:
Coverage Status: Online
Skipped test: No WAP service records found.
Skipped test: Please provide WAP parameters
Transport: WAP (Socket)
Result: fail
Response: -1
Length: -1
URL: No url available
Log:
Skipped test: No WAP service records found.
Skipped test: Please provide WAP parameters
Transport: WAP2 (HTTP)
Result: fail
Response: -1
Length: -1
URL: http://www.oururl.com:80/helpdata/blackberry/OurApp.jad;deviceside=true;ConnectionUID=WAP2 trans
Log:
Coverage Status: Online
Connecting to http://www.oururl.com:80/helpdata/blackberry/OurApp.jad;deviceside=true;ConnectionUID=WAP2 trans
Openning connection
Tunnel failed
========END OF LOG========
Transport: WAP2 (Socket)
Result: fail
Response: -1
Length: -1
URL: socket://www.oururl.com:80;deviceside=true;ConnectionUID=WAP2 trans
Log:
Connecting socket to socket://www.oururl.com:80;deviceside=true;ConnectionUID=WAP2 trans
Openning connection
Tunnel failed
========END OF LOG========
Transport: WiFi (HTTP)
Result: pass
Response: 200
Length: 1550
URL: http://www.oururl.com:80/helpdata/blackberry/OurApp.jad;interface=wifi
Log:
Coverage Status: Online
Connecting to http://www.oururl.com:80/helpdata/blackberry/OurApp.jad;interface=wifi
Openning connection
Connection opened
Getting response code
Got response: 200
Reading content
Received content. Length: 1550
Closing connection
Connection closed
========END OF LOG========
Transport: WiFi (Socket)
Result: pass
Response: 400
Length: 447
URL: socket://www.oururl.com:80;interface=wifi
Log:
Connecting socket to socket://www.oururl.com:80;interface=wifi
Openning connection
Connection opened
OutputStream opened
Sent:
GET /helpdata/blackberry/OurApp.jad HTTP/1.0
Received content. Length: 447
Closing connection
Connection closed
========END OF LOG========
Message Edited by arbiarbi on 09-09-2009 03:39 AM
