Details
-
Bug
-
Resolution: Outdated
-
Neutral
-
None
-
5.4.7, 5.5
-
None
-
None
Description
500 error happens the first time this URL is reached, and then works fine. That makes the build fail on OS X, though.
[ERROR] Failed to execute goal org.codehaus.gmaven:gmaven-plugin:1.5:execute (web-crawler) on project magnolia-integration-tests: java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8399/magnoliaTest/.magnolia/jcrprop/?path=/modules/site/config/site/extends&value=/modules/travel-demo/config/travel -> [Help 1]
After some investigation, Robert, Espen and I arrived to the following conclusions:
- with OS X, the "-XX:-MaxFDLimit" flag is needed, both in cargo.jvmargs (magnolia-integration-tests/tests/pom.xml), as well as in the user's setup.
- a QA commit should do that on CE (EE?)
- it would be nice that the crawler would check if the necessary flags are set, and tell it to the user if that's not the case, as we can't directly add those flags in gmaven-plugin.
The way to add it to one's setup is to:
- pass -Darguments=-XX:-MaxFDLimit to mvn (the -D flag allows it to be forwarded to subprocesses)
- add -XX:-MaxFDLimit as a Java flag. (Don't add it to $JAVA_OPTS, unless you do alias java='java $JAVA_OPTS', because that one is only read by Tomcat by default.)
Checklists
Acceptance criteria