Hello. I have another question.
I’m trying to track down a delay problem with our platform in the authorization request. I’m not sure what could be causing this but I want to be sure that the problem is not the Radiator. I have a Radiator version 4.9 for authorization, connected to an Oracle DB as a backend. I’m using simpleClient.pl to check the service and to monitor the response time from the Radiator. From time to time I see high delay time between the send of a Request and the Received answer, near 2000ms or 3000ms. This is reported by simpleClient, but when I see the debug from the Radiator and the “statistics” i don’t see this delay. For a particular handler this is the output : 1353438260:Handler:Request-Type = Access-Request, NAS-IP-Address=10.0.0.112:58223:0:11:58234:0:0:0:0:0.0350093824817378 1353438260:Handler:Request-Type = Access-Request, NAS-IP-Address=10.0.0.149:66961:0:0:66961:0:0:0:0:0.0308877178051726 1353438260:Handler:Request-Type = Access-Request, NAS-IP-Address=10.0.0.130:27024:0:0:27024:0:0:0:0:0.0463723194159608 But for the same Handler I see delay time reported by the simpleClient.pl near 2000 msecs. This make me think, is there any queque in Radiator for the Authorization packets? Can I see this queque?, can I take measures? For example, if 10 or 20 Access-Request packet arrives to Radiator, how are processed? Hope someone can give some hints here. Thanks in advance, *Ricardo Martínez*
_______________________________________________ radiator mailing list [email protected] http://www.open.com.au/mailman/listinfo/radiator
