zhoujian2030 / jdiameter

Automatically exported from code.google.com/p/jdiameter
0 stars 0 forks source link

Diameter s6a ActivityIsEndingException for answers #61

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run two mobicents instances in two servers. (say A, B)

2. A SBB in A will send an AuthenticationInformationRequest and B will receive 
it, and reply with an AuthenticationInformationAnswer with the appropriate AVPs 
filled in.

3. Listen to the AuthenticationInformationAnswer event in the SBB in A. (Print 
the reply)

What is the expected output? What do you see instead?
Expected output will be the reply with the filled in AVPs. The actual output is 
an ActivityIsEndingException.

What version of the product are you using? On what operating system?
S6a RA versions 1.0.0 and 2.7.1 had the issue. Tested on both Windows and 
CentOS. Used both jDiameter mux versions 1.4.0 and 1.5.0

Please provide any additional information below.
I tried a workaround and swapped the event fire and the state change in the 
jDiameter mux with successful results.
The following cloned source has what was done.
https://code.google.com/r/tdevinda-tyrion/source/detail?r=a965ee789203c984473d56
3a461838553d086085

Please refer to the following thread for more info.
https://groups.google.com/forum/?hl=en#!topic/mobicents-public/90bb6V614_8

Original issue reported on code.google.com by tdevi...@gmail.com on 11 Jun 2014 at 9:19