On 15/03/12 00:22, Anne wrote:
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.
Thank you Anne for sharing. I rebuilt the database (it was a test
installation anyway) and the error disappeared but I wouldn't be
surprised to see it again any time. I'll keep this as a reference.
Best regards.
--
Bernat Arlandis<[email protected]>
JPL TSolució S.L.
