[firebird-support] RE: Why is this setup not working?
Hey Mark. Thanks for your reply. The firebird DB is running SuperClassic. The config kan be found on pastebin http://pastebin.com/ZzxL4xVc http://pastebin.com/ZzxL4xVc
Re: [firebird-support] RE: Why is this setup not working?
Hi, There are some things in the config which could be tuned, but not many - I would increase size of lock table to 10Mb and number of page buffers to 512 pages. But in general it looks like typical problems are not in place here, i.e. your problem is not obvious and it requires professional support, with database statistics investigation, ongoing transaction's markers monitoring, queries audit, locks analysis, etc. Regards, Alexey Kovyazin Hey Mark. Thanks for your reply. The firebird DB is running SuperClassic. The config kan be found on pastebin http://pastebin.com/ZzxL4xVc
[firebird-support] RE: Why is this setup not working?
Hi Alexey. Thanks for your respons. I acknowledge your thoughts. I would like to address the issue of scale-ability. What are our options of scaling the environments. For now we have sharded the database into two separate servers(on psychical hardware). That helped for a while but bow the connections is killing us. We haven't been able to find any connection pool software that supports firebird(Anyone know of any?). /Ronnie
[firebird-support] CASCADE option in FK declaration doesn#39;t work - after some time
Hi, I'm using - ON UPDATE CASCADE, or ON DELETE CASCADE options in FK declarations - when I create the FK it works - but sometimes - after backup/restore or some undefined time - I don't know - it doesn't work. I'm using FB 2.5.2 64b on windows server 2008 R2 Example - today I wanted to change the key in primary table, but It raises an error org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544466. violation of FOREIGN KEY constraint quot;FK_DEF_LOK_TEMA_LOKACEquot; on table quot;DEF_LOK_TEMAquot;|Foreign key references are present for the record so I have to Ctrl+C from DDL - ALTER TABLE DEF_LOK_TEMA ADD CONSTRAINT FK_DEF_LOK_TEMA_LOKACE FOREIGN KEY (FK_LOKACE) REFERENCES DEF_LOKACE (ID_LOKACE) ON DELETE CASCADE ON UPDATE CASCADE; drop that FK and recreate it using the same definition as there was. And now I can change the recod - but I don't know how long it will work It is not the first time I met this problem. Do you anybody know how make it work properly for all times?
[firebird-support] Firebird and JBoss/Hibernate: LockAcquisitionException: could not update error raised
All, I realize that this is more of an JBoss/Hibernate issue, but web details on the error are sketchy so I thought I would reach out to see if anyone in the FB community had run into this error/exception. The exact message/error stack is: 15:25:02.349 [ActiveMQ Session Task-2276] ERROR c.b.brms.ruleserver.RuleServer - processTaskCommand() error: java.lang.RuntimeException: org.hibernate.exception.LockAcquisitionException: could not update: [com.broadview.model.amd.Advertisermaster#294399499] at com.broadview.brms.persistence.RuleServerTransaction.commit(RuleServerTransaction.java:126) ~[RuleServer.jar:na] at com.broadview.brms.persistence.BaseRuleServerPersistenceManager.commitTransaction(BaseRuleServerPersistenceManager.java:116) ~[RuleServer.jar:na] Restarting the application resolved the problem, we are trying to understand what the error really means. Any suggestions would be appreciated Sean
