You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2011/04/04 17:41:05 UTC
[jira] [Created] (STANBOL-142) Error 404 on / in
enhancer/launchers/full
Error 404 on / in enhancer/launchers/full
-----------------------------------------
Key: STANBOL-142
URL: https://issues.apache.org/jira/browse/STANBOL-142
Project: Stanbol
Issue Type: Bug
Components: Enhancer
Reporter: Bertrand Delacretaz
Since the STANBOL-120 changes I have problems with startup of the enhancers/launchers/full launcher.
Looks like a startup timing/problem with org.apache.stanbol.commons.web.base, steps to reproduce:
cd enhancer/launchers/full
rm -rf sling
java -Xmx1024M -jar target/org.apache.stanbol.enhancer.launchers.full-0.9-SNAPSHOT.jar
http://localhost:8080/engines -> 404
Stop and restart the org.apache.stanbol.commons.web.base
Console says "INFO: Initiating Jersey application, version 'Jersey: 1.2 05/07/2010 02:04 PM'
http://localhost:8080/engines -> 200OK
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (STANBOL-142) Error 404 on / in
enhancer/launchers/full
Posted by "Olivier Grisel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015766#comment-13015766 ]
Olivier Grisel commented on STANBOL-142:
----------------------------------------
I have updated all the pom.xml to use static version numbers, cleaned up all stanbol artifacts from my local maven repo and rebuild everything from sources and I cannot reproduce this.
> Error 404 on / in enhancer/launchers/full
> -----------------------------------------
>
> Key: STANBOL-142
> URL: https://issues.apache.org/jira/browse/STANBOL-142
> Project: Stanbol
> Issue Type: Bug
> Components: Enhancer
> Reporter: Bertrand Delacretaz
> Assignee: Olivier Grisel
>
> Since the STANBOL-120 changes I have problems with startup of the enhancers/launchers/full launcher.
> Looks like a startup timing/problem with org.apache.stanbol.commons.web.base, steps to reproduce:
> cd enhancer/launchers/full
> rm -rf sling
> java -Xmx1024M -jar target/org.apache.stanbol.enhancer.launchers.full-0.9-SNAPSHOT.jar
> http://localhost:8080/engines -> 404
> Stop and restart the org.apache.stanbol.commons.web.base
> Console says "INFO: Initiating Jersey application, version 'Jersey: 1.2 05/07/2010 02:04 PM'
> http://localhost:8080/engines -> 200OK
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (STANBOL-142) Error 404 on / in
enhancer/launchers/full
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved STANBOL-142.
-----------------------------------------
Resolution: Fixed
Works for me and Jenkins build passes, looks good.
> Error 404 on / in enhancer/launchers/full
> -----------------------------------------
>
> Key: STANBOL-142
> URL: https://issues.apache.org/jira/browse/STANBOL-142
> Project: Stanbol
> Issue Type: Bug
> Components: Enhancer
> Reporter: Bertrand Delacretaz
> Assignee: Olivier Grisel
>
> Since the STANBOL-120 changes I have problems with startup of the enhancers/launchers/full launcher.
> Looks like a startup timing/problem with org.apache.stanbol.commons.web.base, steps to reproduce:
> cd enhancer/launchers/full
> rm -rf sling
> java -Xmx1024M -jar target/org.apache.stanbol.enhancer.launchers.full-0.9-SNAPSHOT.jar
> http://localhost:8080/engines -> 404
> Stop and restart the org.apache.stanbol.commons.web.base
> Console says "INFO: Initiating Jersey application, version 'Jersey: 1.2 05/07/2010 02:04 PM'
> http://localhost:8080/engines -> 200OK
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (STANBOL-142) Error 404 on / in
enhancer/launchers/full
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015466#comment-13015466 ]
Bertrand Delacretaz commented on STANBOL-142:
---------------------------------------------
Environment: macosx 10.6.6, Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-10M3326)
> Error 404 on / in enhancer/launchers/full
> -----------------------------------------
>
> Key: STANBOL-142
> URL: https://issues.apache.org/jira/browse/STANBOL-142
> Project: Stanbol
> Issue Type: Bug
> Components: Enhancer
> Reporter: Bertrand Delacretaz
>
> Since the STANBOL-120 changes I have problems with startup of the enhancers/launchers/full launcher.
> Looks like a startup timing/problem with org.apache.stanbol.commons.web.base, steps to reproduce:
> cd enhancer/launchers/full
> rm -rf sling
> java -Xmx1024M -jar target/org.apache.stanbol.enhancer.launchers.full-0.9-SNAPSHOT.jar
> http://localhost:8080/engines -> 404
> Stop and restart the org.apache.stanbol.commons.web.base
> Console says "INFO: Initiating Jersey application, version 'Jersey: 1.2 05/07/2010 02:04 PM'
> http://localhost:8080/engines -> 200OK
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (STANBOL-142) Error 404 on / in
enhancer/launchers/full
Posted by "Olivier Grisel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Grisel reassigned STANBOL-142:
--------------------------------------
Assignee: Olivier Grisel
> Error 404 on / in enhancer/launchers/full
> -----------------------------------------
>
> Key: STANBOL-142
> URL: https://issues.apache.org/jira/browse/STANBOL-142
> Project: Stanbol
> Issue Type: Bug
> Components: Enhancer
> Reporter: Bertrand Delacretaz
> Assignee: Olivier Grisel
>
> Since the STANBOL-120 changes I have problems with startup of the enhancers/launchers/full launcher.
> Looks like a startup timing/problem with org.apache.stanbol.commons.web.base, steps to reproduce:
> cd enhancer/launchers/full
> rm -rf sling
> java -Xmx1024M -jar target/org.apache.stanbol.enhancer.launchers.full-0.9-SNAPSHOT.jar
> http://localhost:8080/engines -> 404
> Stop and restart the org.apache.stanbol.commons.web.base
> Console says "INFO: Initiating Jersey application, version 'Jersey: 1.2 05/07/2010 02:04 PM'
> http://localhost:8080/engines -> 200OK
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (STANBOL-142) Error 404 on / in
enhancer/launchers/full
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015778#comment-13015778 ]
Bertrand Delacretaz commented on STANBOL-142:
---------------------------------------------
Reproduced the problem with revision 1088907, I'll have a closer look.
BTW, that's certainly not related but there are still some stanbol-version variables left in poms:
$ find . -name pom.xml | xargs grep -l '${stanbol-version}'
./entityhub/indexing/genericrdf/pom.xml
./kres/jersey/pom.xml
./ontologymanager/ontonet/pom.xml
./ontologymanager/store/launchers/fise/pom.xml
./ontologymanager/store/launchers/lite/pom.xml
./ontologymanager/store/parent/pom.xml
./ontologymanager/web/pom.xml
./owl/pom.xml
./parent/pom.xml
./reasoners/base/pom.xml
./reasoners/web/pom.xml
./reengineer/base/pom.xml
./reengineer/db/pom.xml
./reengineer/web/pom.xml
./reengineer/xml/pom.xml
./rules/base/pom.xml
./rules/manager/pom.xml
./rules/refactor/pom.xml
./rules/web/pom.xml
> Error 404 on / in enhancer/launchers/full
> -----------------------------------------
>
> Key: STANBOL-142
> URL: https://issues.apache.org/jira/browse/STANBOL-142
> Project: Stanbol
> Issue Type: Bug
> Components: Enhancer
> Reporter: Bertrand Delacretaz
> Assignee: Olivier Grisel
>
> Since the STANBOL-120 changes I have problems with startup of the enhancers/launchers/full launcher.
> Looks like a startup timing/problem with org.apache.stanbol.commons.web.base, steps to reproduce:
> cd enhancer/launchers/full
> rm -rf sling
> java -Xmx1024M -jar target/org.apache.stanbol.enhancer.launchers.full-0.9-SNAPSHOT.jar
> http://localhost:8080/engines -> 404
> Stop and restart the org.apache.stanbol.commons.web.base
> Console says "INFO: Initiating Jersey application, version 'Jersey: 1.2 05/07/2010 02:04 PM'
> http://localhost:8080/engines -> 200OK
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (STANBOL-142) Error 404 on / in
enhancer/launchers/full
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015798#comment-13015798 ]
Bertrand Delacretaz commented on STANBOL-142:
---------------------------------------------
Improved commons/web/base initialization in revision 1088915, enhancer integration tests pass on my box now.
> Error 404 on / in enhancer/launchers/full
> -----------------------------------------
>
> Key: STANBOL-142
> URL: https://issues.apache.org/jira/browse/STANBOL-142
> Project: Stanbol
> Issue Type: Bug
> Components: Enhancer
> Reporter: Bertrand Delacretaz
> Assignee: Olivier Grisel
>
> Since the STANBOL-120 changes I have problems with startup of the enhancers/launchers/full launcher.
> Looks like a startup timing/problem with org.apache.stanbol.commons.web.base, steps to reproduce:
> cd enhancer/launchers/full
> rm -rf sling
> java -Xmx1024M -jar target/org.apache.stanbol.enhancer.launchers.full-0.9-SNAPSHOT.jar
> http://localhost:8080/engines -> 404
> Stop and restart the org.apache.stanbol.commons.web.base
> Console says "INFO: Initiating Jersey application, version 'Jersey: 1.2 05/07/2010 02:04 PM'
> http://localhost:8080/engines -> 200OK
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira