Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development


Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.


Reply
New Developer
Posts: 5
Registered: ‎06-24-2009
My Device: Not Specified

[urgent question]TCP IO Timed Out for background application after lock screen

Hi, All,

 

Our application has one background service which will send GPS fixes to server every X minutes via TCP or BIS. I notice that if the device is not locked, the transaction can get through successfully most of times. However, after the lock screen shows, it begins to get TCP IO timed Out. Not sure whether it is just coincident with the lock screen.

 

I am using OS 4.6.x and 4.7.x, on Sprint, T-Mobile and Verizon. Any one can share any thought what the cause might be?

 

It is kind of urgent. Any input will be appreciated.

 

Thanks.

 

--J

Developer
Posts: 1,474
Registered: ‎04-14-2009
My Device: Not Specified

Re: [urgent question]TCP IO Timed Out for background application after lock screen

1. Do the timeouts occur on BIS-B or Direct TCP connections?

2. Are those read timeouts?

3. Are you establishing a new connection every time you need to send the data, or are you keeping the connection open?

4. Do you receive any applicaton-level data soon after sending a fix? (i.e., Is it request-response, or request only)

New Developer
Posts: 5
Registered: ‎06-24-2009
My Device: Not Specified

Re: [urgent question]TCP IO Timed Out for background application after lock screen

1. Do the timeouts occur on BIS-B or Direct TCP connections?

 tried on both. TCP is IO Timed out.   BIS is local connection time out.

 

2. Are those read timeouts?

 

those are write timeout

 

3. Are you establishing a new connection every time you need to send the data, or are you keeping the connection open?

no, I open and write, then close it

 

4. Do you receive any applicaton-level data soon after sending a fix? (i.e., Is it request-response, or request only)

 

No.

 

I tried more times, actually, it might be related to backlight too. So I add the permission for reset idel time.  However, so 4.7.x devices(tour) still the same, TCP timed out. T-mobile (curve 4.6) though seems working...

 

Any thought?

Developer
Posts: 1,474
Registered: ‎04-14-2009
My Device: Not Specified

Re: [urgent question]TCP IO Timed Out for background application after lock screen

Try kicking off a thread that reads from the connection too. See if that makes a difference. The BlackBerry tcp/stream network stack is a bit weird sometimes.

Highlighted
New Developer
Posts: 5
Registered: ‎06-24-2009
My Device: Not Specified

Re: [urgent question]TCP IO Timed Out for background application after lock screen

well, actually, we do read and write both. But just in different thread.