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

BlackBerry Web Services

Reply
New Contributor
Posts: 3
Registered: ‎07-18-2012
My Device: 9860

Delay using ConnectionFactory and MDS Connection Service Connection

We have a native BlackBerry Java Apllication for use with OS6 and higher. Our application is a thin Client and relies heavily on its Server connection.We are using the ConnectionFactory for communication on the BlackBerry. All Requests are http-get. On our old client we were using a TCP connection with deviceside=true, this usually worked in the timeframe of 1500 msecs, but the connection would often drop.We have tried different settings for use with the Connection Factory, but this always leads to an unstable connection or the connection not being available.

 

We have noticed that there is a delay in the communication with our server, when the Connection Factory is used over the MDS Connection service. Usually the Request/Response and rendering the data takes about 1.5 seconds. When the MDS Connection service is used there is a delay/lag of app. 2000 milliseconds. We have tracked this with Wireshark on the BES Server but cannot find a cause for this.What is also strange is, that after restarting the BES or MDS Connection service this delay is not there. Request are fast for about 5-30 minutes, then the delay is back.

 

The Application Server is configured in the Proxy Mappings with http://IPADDRESS: port and type DIRECT.

We are using BES 5.0.3 MR8

 

Does anyon have an idea what could be wrong?

 

Here is an example of the Request Headers from Wireshark from on Request:

Time               Source Destination Protocol Length Info
10:50:05.993573000 BB     BES         TCP      476    50128 > brlp-0 [PSH, ACK] Seq=1 Ack=1 Win=32768 Len=422
10:50:05.998062000 BES    APPSVR      TCP      66     50900 > 57285 [SYN] Seq=0 Win=8192 Len=0 MSS=1440 WS=256 SACK_PERM=1
10:50:05.999352000 APPSVR BES         TCP      66     57285 > 50900 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 MSS=1460 WS=1 SACK_PERM=1
10:50:05.999376000 BES    APPSVR      TCP      54     50900 > 57285 [ACK] Seq=1 Ack=1 Win=66048 Len=0
10:50:06.000612000 BES    APPSVR      TCP      266    50900 > 57285 [PSH, ACK] Seq=1 Ack=1 Win=66048 Len=212
10:50:06.149113000 APPSVR BES         TCP      60     57285 > 50900 [ACK] Seq=1 Ack=213 Win=64028 Len=0
10:50:06.149138000 BES    APPSVR      TCP      310    50900 > 57285 [PSH, ACK] Seq=213 Ack=1 Win=66048 Len=256
10:50:06.349109000 APPSVR BES         TCP      60     57285 > 50900 [ACK] Seq=1 Ack=469 Win=63772 Len=0
10:50:06.550067000 BB     BES         TCP      476    [TCP Retransmission] 50128 > brlp-0 [PSH, ACK] Seq=1 Ack=1 Win=32768 Len=422
10:50:06.871962000 BES    BB          TCP      70     brlp-0 > 50128 [PSH, ACK] Seq=1 Ack=423 Win=258 Len=16
10:50:06.935628000 APPSVR BES         TCP      160    57285 > 50900 [PSH, ACK] Seq=1 Ack=469 Win=63772 Len=106
10:50:06.937863000 APPSVR BES         TCP      1494   57285 > 50900 [ACK] Seq=107 Ack=469 Win=63772 Len=1440
10:50:06.937885000 BES    APPSVR      TCP      54     50900 > 57285 [ACK] Seq=469 Ack=1547 Win=66048 Len=0
10:50:06.938882000 APPSVR BES         TCP      1494   57285 > 50900 [ACK] Seq=1547 Ack=469 Win=63772 Len=1440
10:50:06.939112000 APPSVR BES         TCP      1494   57285 > 50900 [ACK] Seq=2987 Ack=469 Win=63772 Len=1440
10:50:06.939130000 BES    APPSVR      TCP      54     50900 > 57285 [ACK] Seq=469 Ack=4427 Win=66048 Len=0
10:50:06.939232000 APPSVR BES         TCP      1494   57285 > 50900 [ACK] Seq=4427 Ack=469 Win=63772 Len=1440
10:50:06.940334000 APPSVR BES         TCP      1494   57285 > 50900 [ACK] Seq=5867 Ack=469 Win=63772 Len=1440
10:50:06.940348000 BES    APPSVR      TCP      54     50900 > 57285 [ACK] Seq=469 Ack=7307 Win=66048 Len=0
10:50:06.940458000 APPSVR BES         TCP      1494   57285 > 50900 [ACK] Seq=7307 Ack=469 Win=63772 Len=1440
10:50:06.940585000 APPSVR BES         TCP      1494   57285 > 50900 [ACK] Seq=8747 Ack=469 Win=63772 Len=1440
10:50:06.940599000 BES    APPSVR      TCP      54     50900 > 57285 [ACK] Seq=469 Ack=10187 Win=66048 Len=0
10:50:06.941856000 APPSVR BES         TCP      1494   57285 > 50900 [ACK] Seq=10187 Ack=469 Win=63772 Len=1440
10:50:06.941917000 APPSVR BES         TCP      1083   57285 > 50900 [FIN, PSH, ACK] Seq=11627 Ack=469 Win=63772 Len=1029
10:50:06.941936000 BES    APPSVR      TCP      54     50900 > 57285 [ACK] Seq=469 Ack=12657 Win=66048 Len=0
10:50:06.942599000 BES    APPSVR      TCP      54     50900 > 57285 [FIN, ACK] Seq=469 Ack=12657 Win=66048 Len=0
10:50:06.943615000 APPSVR BES         TCP      60     57285 > 50900 [ACK] Seq=12657 Ack=470 Win=63772 Len=0
10:50:07.276173000 BB     BES         TCP      60     50128 > brlp-0 [ACK] Seq=423 Ack=17 Win=32766 Len=0
10:50:07.276208000 BES    BB          TCP      1414   brlp-0 > 50128 [ACK] Seq=17 Ack=423 Win=258 Len=1360
10:50:07.315791000 BB     BES         TCP      60     [TCP Window Update] 50128 > brlp-0 [ACK] Seq=423 Ack=17 Win=32768 Len=0
10:50:07.429103000 BB     BES         TCP      60     50128 > brlp-0 [ACK] Seq=423 Ack=1377 Win=32768 Len=0
10:50:07.429131000 BES    BB          TCP      1768   brlp-0 > 50128 [PSH, ACK] Seq=1377 Ack=423 Win=258 Len=1714
10:50:07.489179000 BB     BES         TCP      60     50128 > brlp-0 [ACK] Seq=423 Ack=3091 Win=32553 Len=0
10:50:07.557259000 BB     BES         TCP      60     [TCP Window Update] 50128 > brlp-0 [ACK] Seq=423 Ack=3091 Win=32768 Len=0
10:50:08.796116000 BB     BES         TCP      70     50128 > brlp-0 [PSH, ACK] Seq=423 Ack=3091 Win=32768 Len=16
10:50:08.994837000 BES    BB          TCP      54     brlp-0 > 50128 [ACK] Seq=3091 Ack=439 Win=258 Len=0
10:50:09.331159000 BB     BES         TCP      70     50128 > brlp-0 [PSH, ACK] Seq=439 Ack=3091 Win=32768 Len=16
10:50:09.524844000 BES    BB          TCP      54     brlp-0 > 50128 [ACK] Seq=3091 Ack=455 Win=258 Len=0

 

Retired
Posts: 2,559
Registered: ‎10-16-2009
My Device: BlackBerry Z10

Re: Delay using ConnectionFactory and MDS Connection Service Connection

If the delay has been found to occur in the BES MDS then you will likely find better support for this issue over in the BES forums:

http://supportforums.blackberry.com/t5/BlackBerry-Enterprise-Solution/bd-p/BlackBerryEnterpriseSolut...

Garett
@garettBeuk
--
Goodbye everybody!
New Contributor
Posts: 3
Registered: ‎07-18-2012
My Device: 9860

Re: Delay using ConnectionFactory and MDS Connection Service Connection

Thanks for your reply. I thought to post it here, because the delay seems to happen in the communication between the BES and the BB, so maybe someone has experienced this and has a helpful idea. That the cause could be the MDS is an idea, but I could be wrong.

 

I have followed your advice and also posted it the Enterprise Solutions forum.

 

Thanks,

Christoph