search

sean-cc / jain-slee

Automatically exported from code.google.com/p/jain-slee
0 stars 0 forks source link

Ro Requests are sent before activities are created (clustered) #29

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Generate a high load on a diameter Ro client application in clustered 
configuration
2. Start a new Diameter Activity, send InitialRequest
3. If the load is high and the Diameter server responses fast it happens that 
on response we get:
java.lang.IllegalStateException: No activity for handle: Diameter Session 
ID[inscp-diameter;316;2038060368]
    at org.mobicents.slee.resource.diameter.ro.DiameterRoResourceAdaptor.fireEvent(DiameterRoResourceAdaptor.java:608)

Despite we used the activity for sending out request and not doing antyhing in 
meantime. It seems that under high load 
AbstractClusteredDiameterActivityManagement waits some time before putting 
activity into activities, thus if the answer comes to quick Ro RA cannot find 
activity 

What is the expected output? What do you see instead?
The requests should be sent after activity initiation is done

What version of the product are you using? On what operating system?
510a9a107f32b8b559d2ea60784a535c0ef3babd

Please provide any additional information below.
It may be somehow related with the way clustered activities are managed.

Original issue reported on code.google.com by Tomasz.D...@arevocom.com on 27 Jan 2013 at 11:55