Re: Exceptions on MySQL 4.1
May be true, I did my tests with the 4.0 schema and it worked just fine. No idea what the original problem is. Anyway, use the 4.0 schema even for 4.1 and it should work. Oliver On Mon, 06 Dec 2004 14:44:48 -0800, Mirko Froehlich <[EMAIL PROTECTED]> wrote: > I have upgraded my database to MySQL 4.1 and changed the adapter to > "MySql41RDBMSAdapter" in Domain.xml. I also dropped my old Slide > database and created a fresh database using the MySQL 4.1 Slide db > script. The first startup worked fine, and I was able to access the > repository through the WebDAV client API (note that I ran into the same > deadlock issues...). Now, every time I start Tomcat, I get the following > exceptions in the log. If I try to hit Slide using the browser, it > complains about the actions cache not being loaded and also spits out an > exception in the logs (at the bottom, below). Any ideas? > > -Mirko > > At startup: > > > 06 Dec 2004 14:36:38 - org.apache.slide.common.XMLUnmarshaller - INFO - > Loading object / > 06 Dec 2004 14:36:38 - org.apache.slide.common.XMLUnmarshaller - INFO - > Object already exists at / > 06 Dec 2004 14:36:38 - > org.apache.slide.store.impl.rdbms.MySqlRDBMSAdapter - ERROR - SQL error > 1267 on /: General error message from server: "Illegal mix of collations > (utf8_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for > operation 'substr_index'" > org.apache.slide.common.ServiceAccessException: Service > [EMAIL PROTECTED] access error : > General error message from server: "Illegal mix of collations > (utf8_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for > operation 'substr_index'" > at > org.apache.slide.store.impl.rdbms.MySqlRDBMSAdapter.createException(MySqlRDBMSAdapter.java:66) > at > org.apache.slide.store.impl.rdbms.StandardRDBMSAdapter.retrieveRevisionDescriptors(StandardRDBMSAdapter.java:942) > at > org.apache.slide.store.impl.rdbms.AbstractRDBMSStore.retrieveRevisionDescriptors(AbstractRDBMSStore.java:652) > at > org.apache.slide.store.AbstractStore.retrieveRevisionDescriptors(AbstractStore.java:996) > at > org.apache.slide.store.ExtendedStore.retrieveRevisionDescriptors(ExtendedStore.java:816) > at > org.apache.slide.content.ContentImpl.retrieve(ContentImpl.java:168) > at > org.apache.slide.common.XMLUnmarshaller.loadObjectRevision(XMLUnmarshaller.java:340) > at > org.apache.slide.common.XMLUnmarshaller.loadDefaultObjectRevision(XMLUnmarshaller.java:307) > at > org.apache.slide.common.XMLUnmarshaller.loadObjectNode(XMLUnmarshaller.java:237) > at > org.apache.slide.common.XMLUnmarshaller.unmarshal(XMLUnmarshaller.java:90) > at > org.apache.slide.common.NamespaceAccessTokenImpl.importData(NamespaceAccessTokenImpl.java:272) > at > org.apache.slide.common.Namespace.loadBaseData(Namespace.java:808) > at org.apache.slide.common.Domain.initNamespace(Domain.java:845) > at org.apache.slide.common.Domain.init(Domain.java:432) > at org.apache.slide.common.Domain.init(Domain.java:366) > at org.apache.slide.common.Domain.init(Domain.java:329) > at > org.apache.slide.webdav.WebdavServlet.init(WebdavServlet.java:253) > at javax.servlet.GenericServlet.init(GenericServlet.java:211) > at > org.apache.slide.webdav.WebdavServlet.init(WebdavServlet.java:195) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1029) > at > org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:862) > at > org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4013) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4357) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823) > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595) > at > org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:277) > at > org.apache.catalina.core.StandardHost.install(StandardHost.java:832) > at > org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:617) > at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:431) > at > org.apache.catalina.startup.HostConfig.start(HostConfig.java:968) > at > org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349) > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091) > at > org.apache.catalina.core.StandardHost.start(StandardHost.java:789) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) > at > org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
Re: Exceptions on MySQL 4.1
In that case, should I continue to use the MySqlRDBMSAdapter, or should I use the MySql41RDBMSAdapter? -Mirko On Mon, 2004-12-06 at 16:25, Oliver Zeigermann wrote: > May be true, I did my tests with the 4.0 schema and it worked just > fine. No idea what the original problem is. Anyway, use the 4.0 schema > even for 4.1 and it should work. > > Oliver
Re: Exceptions on MySQL 4.1
Nono, use the MySql41RDBMSAdapter. That's what worked for me. Oliver On Mon, 06 Dec 2004 16:37:36 -0800, Mirko Froehlich <[EMAIL PROTECTED]> wrote: > In that case, should I continue to use the MySqlRDBMSAdapter, or should I > use the MySql41RDBMSAdapter? > > -Mirko > > > > > On Mon, 2004-12-06 at 16:25, Oliver Zeigermann wrote: > May be true, I did my tests with the 4.0 schema and it worked just fine. No > idea what the original problem is. Anyway, use the 4.0 schema even for 4.1 > and it should work. Oliver > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Exceptions on MySQL 4.1
In that case, I don't think this will solve my issue. Slide actually started up fine with MySQL 4.1 for the first time, using the MySql41RDBMSAdapter and the new schema. I ran my concurrency test, which again failed after less than a minute. Only subsequent startups failed due to the schema issues, for some reason. -Mirko On Mon, 2004-12-06 at 16:47, Oliver Zeigermann wrote: > Nono, use the MySql41RDBMSAdapter. That's what worked for me. > > Oliver > > > On Mon, 06 Dec 2004 16:37:36 -0800, Mirko Froehlich > <[EMAIL PROTECTED]> wrote: > > In that case, should I continue to use the MySqlRDBMSAdapter, or should I > > use the MySql41RDBMSAdapter? > > > > -Mirko > > > > > > > > > > On Mon, 2004-12-06 at 16:25, Oliver Zeigermann wrote: > > May be true, I did my tests with the 4.0 schema and it worked just fine. No > > idea what the original problem is. Anyway, use the 4.0 schema even for 4.1 > > and it should work. Oliver > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: Exceptions on MySQL 4.1
As a final hint: set isolation level to read committed! Oliver P.S.: Thanks for reporting all this; I am currently working on the deadlock retry thing... On Mon, 06 Dec 2004 17:02:56 -0800, Mirko Froehlich <[EMAIL PROTECTED]> wrote: > In that case, I don't think this will solve my issue. Slide actually > started up fine with MySQL 4.1 for the first time, using the > MySql41RDBMSAdapter and the new schema. I ran my concurrency test, which > again failed after less than a minute. Only subsequent startups failed > due to the schema issues, for some reason. > > > > -Mirko > > On Mon, 2004-12-06 at 16:47, Oliver Zeigermann wrote: > > > Nono, use the MySql41RDBMSAdapter. That's what worked for me. > > > > Oliver > > > > > > On Mon, 06 Dec 2004 16:37:36 -0800, Mirko Froehlich > > <[EMAIL PROTECTED]> wrote: > > > In that case, should I continue to use the MySqlRDBMSAdapter, or should I > > > use the MySql41RDBMSAdapter? > > > > > > -Mirko > > > > > > > > > > > > > > > On Mon, 2004-12-06 at 16:25, Oliver Zeigermann wrote: > > > May be true, I did my tests with the 4.0 schema and it worked just fine. > > > No > > > idea what the original problem is. Anyway, use the 4.0 schema even for 4.1 > > > and it should work. Oliver > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Exceptions on MySQL 4.1
OK, this should work for MySQL now. Mirko, do you still have enough patience to try it with the latest CVS head? Oliver On Tue, 7 Dec 2004 15:40:15 +0100, Oliver Zeigermann <[EMAIL PROTECTED]> wrote: > As a final hint: set isolation level to read committed! > > Oliver > > P.S.: Thanks for reporting all this; I am currently working on the > deadlock retry thing... > > On Mon, 06 Dec 2004 17:02:56 -0800, Mirko Froehlich > > > <[EMAIL PROTECTED]> wrote: > > In that case, I don't think this will solve my issue. Slide actually > > started up fine with MySQL 4.1 for the first time, using the > > MySql41RDBMSAdapter and the new schema. I ran my concurrency test, which > > again failed after less than a minute. Only subsequent startups failed > > due to the schema issues, for some reason. > > > > > > > > -Mirko > > > > On Mon, 2004-12-06 at 16:47, Oliver Zeigermann wrote: > > > > > Nono, use the MySql41RDBMSAdapter. That's what worked for me. > > > > > > Oliver > > > > > > > > > On Mon, 06 Dec 2004 16:37:36 -0800, Mirko Froehlich > > > <[EMAIL PROTECTED]> wrote: > > > > In that case, should I continue to use the MySqlRDBMSAdapter, or > > > > should I > > > > use the MySql41RDBMSAdapter? > > > > > > > > -Mirko > > > > > > > > > > > > > > > > > > > > On Mon, 2004-12-06 at 16:25, Oliver Zeigermann wrote: > > > > May be true, I did my tests with the 4.0 schema and it worked just > > > > fine. No > > > > idea what the original problem is. Anyway, use the 4.0 schema even for > > > > 4.1 > > > > and it should work. Oliver > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Exceptions on MySQL 4.1
Absolutely! I'll let you know how it goes. Again, thanks for implementing these fixes. -Mirko On Tue, 2004-12-07 at 09:18, Oliver Zeigermann wrote: > OK, this should work for MySQL now. > > Mirko, do you still have enough patience to try it with the latest CVS head? > > Oliver > > On Tue, 7 Dec 2004 15:40:15 +0100, Oliver Zeigermann > <[EMAIL PROTECTED]> wrote: > > As a final hint: set isolation level to read committed! > > > > Oliver > > > > P.S.: Thanks for reporting all this; I am currently working on the > > deadlock retry thing... > > > > On Mon, 06 Dec 2004 17:02:56 -0800, Mirko Froehlich > > > > > > <[EMAIL PROTECTED]> wrote: > > > In that case, I don't think this will solve my issue. Slide actually > > > started up fine with MySQL 4.1 for the first time, using the > > > MySql41RDBMSAdapter and the new schema. I ran my concurrency test, which > > > again failed after less than a minute. Only subsequent startups failed > > > due to the schema issues, for some reason. > > > > > > > > > > > > -Mirko > > > > > > On Mon, 2004-12-06 at 16:47, Oliver Zeigermann wrote: > > > > > > > Nono, use the MySql41RDBMSAdapter. That's what worked for me. > > > > > > > > Oliver > > > > > > > > > > > > On Mon, 06 Dec 2004 16:37:36 -0800, Mirko Froehlich > > > > <[EMAIL PROTECTED]> wrote: > > > > > In that case, should I continue to use the MySqlRDBMSAdapter, or > > > > > should I > > > > > use the MySql41RDBMSAdapter? > > > > > > > > > > -Mirko > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, 2004-12-06 at 16:25, Oliver Zeigermann wrote: > > > > > May be true, I did my tests with the 4.0 schema and it worked just > > > > > fine. No > > > > > idea what the original problem is. Anyway, use the 4.0 schema even > > > > > for 4.1 > > > > > and it should work. Oliver > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
