* This is the VOP Radius mailing list * It's an OS-level problem..not Vircom's. MS is informing Vircom that the ODBC queue is full. You can tune the ODBC connection yourself.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of it > Sent: Thursday, February 05, 2004 10:43 AM > To: [EMAIL PROTECTED] > Subject: [VOPRadius] ODBC Queue FULL > > > * This is the VOP Radius mailing list * > Eric, > > I'm doing only accounting in this connection. > > I increase the performance of the triggers and with index but > still I believe Vircom should hold a bigger queue or have a > different solution to assist us. > > > Daniel > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Eric Dean > Sent: Thursday, February 05, 2004 1:11 PM > To: [EMAIL PROTECTED] > Subject: [VOPRadius] ODBC Queue FULL > > * This is the VOP Radius mailing list * > It is due to Rodopi. VOP merely tries to insert into SQL Server. > > A queue filling up is typically the result of too many > requests trying to get inserted. If Rodopi is firing triggers > upon an accounting insert, then it's very important that the > triggers have indexed fields so that SQL can provide quickly > deal with the trigger prior to the next accounting packet arriving. > > The problem is one of performance...specifically, database > performance. I wouldn't be surprised if Vop blames Rodopi and > Rodopi blames the hardware. Assuming the hardware is > adequate, take a look at triggers and indexing. > > Also, ALWAYS create a separate ODBC for authentication and > accounting...you don't want the accounting to starve our > authentication > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of operations > > Sent: Thursday, February 05, 2004 9:56 AM > > To: [EMAIL PROTECTED] > > Subject: [VOPRadius] ODBC Queue FULL > > > > > > * This is the VOP Radius mailing list * > > Hi, > > > > I don't have a solution for you, but we had the same problem > > with VOP Radius and Rodopi Billing System and Vircom said its > > due to Rodopi and they can fix it. > > > > We worked with Rodopi and STILL the same problem is there !! > > > > I'm not sure if Vircom has any suggestions on this CRITICAL > > issue. Regards.. > > > > Kais > > > > > > > > > > > > > > > > > Guys, > > > > > > > > > > > > I'm using the Vrcom radius for voip. After it publish the > > data in a MS > > > SQL Accouting table, it fires some triggers for billing issue. > > > > > > > > > Due to the high volume of data been published, I start to > get "DBC > > > Queue FULL message" in the Vircom Error log and loose important > > > data. > > > > > > > > > Is there a way to increase the size of this Queue? Any other > > > suggestion? > > > > > > > > > I'm using version 3.3 Build 225. > > > > > > > > > > > > Thanks in advance for any assistance, > > > > > > > > > > > > Daniel > > > > > > > > > > > > > > > > ** > > To leave this list, send an email to > > [EMAIL PROTECTED] and put the word "LEAVE" in the > > BODY of the email. > > > > > > > ** > To leave this list, send an email to > [EMAIL PROTECTED] and put the word "LEAVE" in the > BODY of the email. > > > > > ** > To leave this list, send an email to > [EMAIL PROTECTED] and put the word "LEAVE" in the > BODY of the email. > > ** To leave this list, send an email to [EMAIL PROTECTED] and put the word "LEAVE" in the BODY of the email.
