Jabberwrex Network Timeout

[basudebAcharjee231]

We have an  observation (irrespective of Finesse version) on CISCO Jabberwrex library(version:'2.1.1.19913'version:'2.1.1.19913').

Our SoftPhone is using Jabberwrex library to communicate Cisco notification service. The   console log(attached document) we captured for Jabberwrex library and we would like to know why Jabberwrex library is returning same “network timeout retry 1”   several times. But is not disconnected. It works perfectly.  Please see the below the console Log.  Please concentrate on the log marked with red bold color where we receive  “network timeout retry 1”  four(4) times  and then “network timeout retry 2”  and then again “network timeout retry 1” so on.

As per my understanding, If there is any network issue, Jabberwrex should report as follows:

network timeout retry 1

network timeout retry 2

network timeout retry 3

….

….

And not what we observed in real scenario(marked with red bold color in the attached document).

Regards,

Basudeb

Message was edited by: Basudeb Acharyya

[npetrele]

Hi Basudeb,

I'm taking a look at it.  Is it possible this is a Finesse issue?  It looks like a lot of the timeouts may be due to a finesseNotReady. 

[sschibon]

Below is some clarification on what is being asked.  There are actually 4 questions.

1. The application is working and appears to be connected so why are error messages being generated?
2. Is there a way to determine what is happening when a log of the following nature is seen?
   1. LOG: network timeout retry 1
   2. LOG: network timeout retry 2
   3. LOG: network timeout retry 1
   4. LOG: network timeout retry 2
   5. LOG: network timeout retry 1
   6. LOG: network timeout retry 2
   7. LOG: network timeout retry 1
   8. LOG: network timeout retry 2
   9. LOG: network timeout retry 1
3. If the application is disconnecting why would you not see
   1. network timeout retry 1
   2. network timeout retry 2
   3. network timeout retry 3
4. Is there a way to determine if the application is dropping/reconnecting/dropping/reconnecting when the following is being seen
   1. LOG: network timeout retry 1
   2. LOG: network timeout retry 1
   3. LOG: network timeout retry 1
   4. LOG: network timeout retry 1

[dzmilos]

Hi all,

“network timeout retry x” means that some kind of network level error occurred after request has been sent from the client. If after 3 retries request could not be sent, the server is considered unavailable and connection is closed.

I'll try to answer above questions:

1. As noted above, connection is closed after 3 retries. If after 1 or 2 retries request is sent successfully, communication is continued without interruption.
2. This is the most probably some micro network interruptions. Network level trace in situations when this is happening would be very helpful.

   3,4. Application is not disconnecting/dropping, it just cannot send some request successfully from the first attempt, but after first attempt, requests are sent successfully.

As a conclusion, these issues are most probably related to some network level problems and network tracing would show what is actually happening, I guess.

Regards, Milos.