iPhone App Timeout

Deadline
1

Hello Ryan,

It seems that the iphone app is returning an error message that it wasn’t able to connect to the server and that I should check my settings before pulse got the chance to send the joblist.

The webserver is running correctly, I’ve tested it with a browser to the addresses http://ip_address:8080/getJobs and http://ip_address:8080/Mobile_GetJobList and got results with both and on the pulse window I can see the log “Web Service: Executing Mobile_GetJobList script…” when sending request from the desktop’s browser and from the iphone app (by clicking refresh button) but the error message from the iphone appears before the log message “Web Service: Done executing Mobile_GetJobList script…”

I’ve even tested to go to the website address http://ip_address:8080/Mobile_GetJobList through the iphone browser and got results so I guess the only thing I can think of would be a timeout happening on the app.

The iphone is connected through a wifi connection in the same subnet of the server.

The last test i did was to delete some of the completed jobs in the list and I got the list on the iphone but we can’t decrease the number of days in the autodelete completed job repository option.

So, is there any requirements for the iphone to run the app? in the doc I can only find that it was tested on iOS 3.0. and if you think it’s a timeout problem is there anything I can do about it? and if not what could it be?

Thanks

2

There must be a timeout in the iPhone app code, so we’ll have to either disable it, or make the timeout configurable in the app settings. Out of curiosity, do you recall how many jobs you had in the queue when the app connected properly, versus the number of jobs that caused the app to timeout?

Cheers,

  • Ryan
3

Sorry, I didn’t check the exact numbers but I can tell you that now we have 1800 jobs and it’s causing the timeout and as a guess I would say we had around 1300 when it worked…

Thanks

4

I checked the app code, and it is using a timeout of 60 seconds. I am surprised that the timeout occurs, since I tested 10,500 jobs here and it didn’t timeout, bug regardless I think we should expose the timeout setting to the app settings so that users can adjust it as necessary.

Cheers,

  • Ryan
5

Hmm, I think that timeout is used after the connection has already been established. So that would imply that there is a period of 1 minute where Pulse isn’t sending any data to the iPhone application. Unfortunately, I have no idea what would cause this…