[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22425#action_22425 ]
Egor Kolesnikov commented on MAGNOLIA-2716:
-------------------------------------------
By the way, it now seems to me like STK problem, because this exception does not happen if you either:
1) do not run jboss with derby config before changing repo to mysql;
2) do not install STK before changing repo to mysql;
in case (2), by the way, there are lot of "workspace invalid" exceptions, but everything looks like working:
1. unpack magnolia-4.0.1 to m.war (or whatever);
2. deploy m.war to JBOSS5_0_1_HOME/server/default/deploy;
3. start jboss;
4. run magnolia install/update routine (at localhost:8080/m), start up Magnolia;
5. stop jboss;
6. reconfigure magnolia to use mysql:
6.1. update config/default/magnolia.properties to use jackrabbit-bundle-mysql-search.xml;
6.2. update jackrabbit-bundle-mysql-search.xml to use local mysql 5 db;
6.3. delete repositories/magnolia;
6.4. add mysql-connector to jboss/server/default/lib);
7. create empty mysql database;
8. start jboss;
9. (A lot of exceptions here, but magnolia deploys successfully).
Additionally, it seems now that proposed workaround (replace JARs) does not work:
1. unpack magnolia-4.0.1 to m.war (or whatever);
2. deploy m.war to JBOSS5_0_1_HOME/server/default/deploy;
3. start jboss;
4. run magnolia install/update routine (at localhost:8080/m), start up Magnolia;
5. stop jboss;
6. reconfigure magnolia to use mysql:
6.1. update config/default/magnolia.properties to use jackrabbit-bundle-mysql-search.xml;
6.2. update jackrabbit-bundle-mysql-search.xml to use local mysql 5 db;
6.3. delete repositories/magnolia;
6.4. add mysql-connector to jboss/server/default/lib);
7. create empty mysql database;
8. replace WEB-INF/lib/jaxen-1.0-FCS.jar and WEB-INF/lib/jdom-1.0.jar with jdom.jar, jaxen-core.jar and jaxen-jdom.jar from JDOM1.0 distribution obtained from jdom.org
8. start jboss;
9. jboss hangs with 100% CPU load in process of deploying magnolia
> Invalid JDOM/JAXEN distribution included
> ----------------------------------------
>
> Key: MAGNOLIA-2716
> URL:
http://jira.magnolia-cms.com/browse/MAGNOLIA-2716> Project: Magnolia
> Issue Type: Bug
> Components: build
> Affects Versions: 4.0.1
> Environment: ubuntu 9.04, JBoss 5.0.1, MySQL 5.0
> Reporter: Egor Kolesnikov
> Assignee: Grégory Joseph
> Attachments: server.txt
>
>
> After changing DERBY repository to MYSQL one, the following error appears while deploying to JBoss 5.0.1:
> java.lang.NoSuchMethodError: org.jdom.Element.getParent()Lorg/jdom/Element;
> at org.jaxen.jdom.DocumentNavigator.getParentAxisIterator(DocumentNavigator.java:252)
> at org.jaxen.expr.iter.IterableParentAxis.iterator(IterableParentAxis.java:82)
> at org.jaxen.expr.DefaultStep.axisIterator(DefaultStep.java:139)
> at org.jaxen.expr.DefaultLocationPath.evaluate(DefaultLocationPath.java:188)
> However, after replacing WEB-INF/lib/jaxen-1.0-FCS.jar and WEB-INF/lib/jdom-1.0.jar with jdom.jar, jaxen-core.jar and jaxen-jdom.jar from JDOM1.0 distribution obtained from jdom.org, everything started working properly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.htmlTo unsubscribe, E-mail to: <
dev-list-unsubscribe@...>
----------------------------------------------------------------