XIG Hanging on successful HTTP GET

[GoogleCodeExporter]

What steps will reproduce the problem?

There are 4 Xbees transmitting to XIG on an X4.  Everything will be running 
fine, and the last statement on the terminal will be Successful HTTP GET, and 
then XIG stops responding.

What is the expected output? What do you see instead?

What version of the product are you using?

1.4.2   
I did notice this starting on the final beta of 1.4.1 b3 too.

Please provide any additional information below.

The Xbees do issue an XIG://abort  when they fail to get a response.  This 
hasn't made any difference.
I have started up another Xbee with X-CTU to see if I could get a response via 
the terminal, but XIG doesn't respond at all.  There are no further messages 
reported until I restart XIG, and then the Xbees immediately start transmitting 
again.

I have a few instances where there are single Xbee's with XIG 1.4.2 - they 
never run into this issue.  It seems to only happen when there are multiple 
devices transmitting.

Original issue reported on code.google.com by rhaist...@gmail.com on 13 Mar 2012 at 3:32

[GoogleCodeExporter]

Can you post the last 25 or 50 lines from the XIG trace buffer?

Also, can you telnet to your gateway and capture the complete output from 
"display techsupport"?

Original comment by Jordan.H...@gmail.com on 13 Mar 2012 at 3:45

[GoogleCodeExporter]

Sure, I will do that for you the next time that it happens.

We experienced another hang, just prior to me seeing your request, and I had 
already restarted services.  I did note that the hang coincided with a brief 
network outage on our end (server upgrades.)  The network is back, but XIG 
didn't come back.  I'm not sure if this is the culprit, but I thought I'd 
mention it as the timing was bang on.

Original comment by rhaist...@gmail.com on 13 Mar 2012 at 5:49

[GoogleCodeExporter]

Have you experienced this behavior again?

Original comment by Jordan.H...@gmail.com on 21 Mar 2012 at 10:35

[GoogleCodeExporter]

We did, but it didn't get captured unfortunately.  This was happening whilst 
our corporate network was being upgraded.  Since then, it hasn't happened.  It 
seems like frequent network disconnections caused it to hang, indefinitely.  
I'll keep you posted if it happens again.

Original comment by rhaist...@gmail.com on 22 Mar 2012 at 4:28

[GoogleCodeExporter]

This should be resolved on XIG v1.5; please let us know if it is encountered 
again.

Original comment by Jordan.H...@gmail.com on 19 Jul 2012 at 6:40

• Changed state: Fixed