Re: idbroker generates existing ID's
Thanks Adam Alvaro, I use a normal size integer, so I should be save for a while. The case of the table name is a good issue. I have been struggling with MySQL and the id_table for a while. I have checked both databases, but alas, no double id tables. I think I'll fall back to Torque 3.2 for now and see if the problems reoccur. I might be 'blaming' Torque while the problems might be related to some other package:-) Thanks for your input, and I'll keep the list informed if I find anything relevant... Kind regards, -- Hidde Boonstra Us Media B.V. Stadhouderskade 115 1073 AX Amsterdam t: 020 428 68 68 f: 020 470 69 05 www.usmedia.nl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
idbroker generates existing ID's
Hi all, we're experiencing some weird trouble while using the IDBroker. Two of our sites (one running on MySQL 5.x + Torque 3.3-RC1 and one running on Postgres 8.x + Torque 3.3-RC2) start throwing duplicate key exceptions after running (without problems) for a while. The IDs generated are much lower than the next_id entry in the id_table. When I restart the application the problem is gone, but after a while (days/weeks) it returns. Does anybody know what is going on, or has experienced similar problems? Thanks in advanced, with kind regards, -- Hidde Boonstra Us Media B.V. Stadhouderskade 115 1073 AX Amsterdam t: 020 428 68 68 f: 020 470 69 05 www.usmedia.nl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: idbroker generates existing ID's
Sorry, nothing for here similar. 2007/11/15, Hidde Boonstra [Us Media] [EMAIL PROTECTED]: Hi all, we're experiencing some weird trouble while using the IDBroker. Two of our sites (one running on MySQL 5.x + Torque 3.3-RC1 and one running on Postgres 8.x + Torque 3.3-RC2) start throwing duplicate key exceptions after running (without problems) for a while. The IDs generated are much lower than the next_id entry in the id_table. When I restart the application the problem is gone, but after a while (days/weeks) it returns. Does anybody know what is going on, or has experienced similar problems? Thanks in advanced, with kind regards, -- Hidde Boonstra Us Media B.V. Stadhouderskade 115 1073 AX Amsterdam t: 020 428 68 68 f: 020 470 69 05 www.usmedia.nl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: idbroker generates existing ID's
Are you having multiple servers or multiple applications access the database? This can cause problems in the absence of transactions. WILL On Nov 15, 2007 5:40 AM, Hidde Boonstra [Us Media] [EMAIL PROTECTED] wrote: Hi all, we're experiencing some weird trouble while using the IDBroker. Two of our sites (one running on MySQL 5.x + Torque 3.3-RC1 and one running on Postgres 8.x + Torque 3.3-RC2) start throwing duplicate key exceptions after running (without problems) for a while. The IDs generated are much lower than the next_id entry in the id_table. When I restart the application the problem is gone, but after a while (days/weeks) it returns. Does anybody know what is going on, or has experienced similar problems? Thanks in advanced, with kind regards, -- Hidde Boonstra Us Media B.V. Stadhouderskade 115 1073 AX Amsterdam t: 020 428 68 68 f: 020 470 69 05 www.usmedia.nl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com
Re: idbroker generates existing ID's
What types are you using? are you sure you are not hitting a maximum somewhere? Short.MAXIMUM is only 32767 Hidde Boonstra [Us Media] [EMAIL PROTECTED] wrote: Hi will, thanks for your response. No, I don't. I have thought about the possibility of transactions (or the lack of transactions) causing the problem, but since it also occurs with Postgres I thought I could rule it out. The weird thing is that the id_table states (for example) a next id of 18 and a quantity of 1400, but the exception states it trying to insert an entry with id 24000. It does increment with each call (although I haven't tried 1400 calls). I have never had this problem with earlier version (i.e. pre 3.3 releases of Torque) and similar usage patterns. Will Glass-Husain wrote: Are you having multiple servers or multiple applications access the database? This can cause problems in the absence of transactions. WILL On Nov 15, 2007 5:40 AM, Hidde Boonstra [Us Media] [EMAIL PROTECTED] wrote: Hi all, we're experiencing some weird trouble while using the IDBroker. Two of our sites (one running on MySQL 5.x + Torque 3.3-RC1 and one running on Postgres 8.x + Torque 3.3-RC2) start throwing duplicate key exceptions after running (without problems) for a while. The IDs generated are much lower than the next_id entry in the id_table. When I restart the application the problem is gone, but after a while (days/weeks) it returns. Does anybody know what is going on, or has experienced similar problems? Thanks in advanced, with kind regards, -- Hidde Boonstra Us Media B.V. Stadhouderskade 115 1073 AX Amsterdam t: 020 428 68 68 f: 020 470 69 05 www.usmedia.nl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.
