Hi Bernat We had a problem with visitId, which I suspect is related to your problem. While our problem is different, and our solution possibly won't work for you, I thought I'd share the information in case it helps you.
We use MySQL and saw a lot of errors in the logs about duplicate keys for visitId. We switched to Postgresql to try to eliminate the errors. It didn't work: we still got the errors, just a lot less of them. So we switched back to MySQL. We've only ever seen the errors during development, never production (even though production servers get a lot more hits per second). We stop and start OFBiz all the time during development, often not cleanly. So we eventually decided the errors were being triggered by something we did during the development process, and could be ignored as they didn't affect production. After all, we wouldn't see the errors for days, then suddenly they would start flooding the logs. Dropping the database and reinitialising it would stop the errors. So we eventually decided to disable hit logging. Haven't seen one error message since. We don't use the search you are having problems with. I don't know if disabling hit logging would affect it. But I suspect reloading the database might make the problem go away temporarily. Cheers, Anne. On 14 March 2012 06:08, Jacques Le Roux <[email protected]>wrote: > > From: "Bernat Arlandis" <[email protected]> > > On 13/03/12 06:09, Jacques Le Roux wrote: >> >>> This might be due to your version of MySQL, check >>> https://cwiki.apache.org/**confluence/display/OFBIZ/Sub+** >>> Second+TimeStamp+Not+**Supported+for+Storage<https://cwiki.apache.org/confluence/display/OFBIZ/Sub+Second+TimeStamp+Not+Supported+for+Storage> >>> >>> >> It worked well, it just started failing after creating some digital >> products and catalogs. I also rebuilt ofbiz without changing the database >> but that shouldn't be a problem, should it? >> > > No, that's not the reason > > > That page also states this: "Generally, this shouldn't be an issue with >> the way the community's applications work but could have repercussions in >> custom applications.". We aren't using any custom app. >> > > My suggestion was to test the same with either Derby, Postgres or to > update your MySql version to release 5.6.4 > > I can't help more > > Jacques > > > Thanks! >> >> -- >> Bernat Arlandis<[email protected]> >> JPL TSolució S.L. >> >> -- Coherent Software Australia Pty Ltd PO Box 2773 Cheltenham Vic 3192 Phone: (03) 9585 6788 Fax: (03) 9585 1086 Web: http://www.cohsoft.com.au/ Email: [email protected] Bonsai ERP, the all-inclusive ERP system http://www.bonsaierp.com.au/
