Tomcat 7.0.19 (Windows 2008 R2 x86, JDK 7 x86) - like issue 3579

Note, this is caused by http://jira.codehaus.org/browse/XSTR-651

If you replace the bundled xstream:

nexus-oss-webapp-1.9.2/runtime/apps/nexus/lib/xstream-1.3.1.jar

with the latest 1.4-SNAPSHOT from:

https://nexus.codehaus.org/content/groups/public/com/thoughtworks/xstream/xstream/1.4-SNAPSHOT/

and add the XmlPull API (or any jar which has XmlPullParserFactory)

http://search.maven.org/#artifactdetails%7Cxmlpull%7Cxmlpull%7C1.1.3.4a%7Cjar

Then you should be able to start it with Java7

I wouldn't recommend running with Java 7 yet. Nexus makes heavy use of Lucene indexes, and there are known incompatibilities. See here for details:

http://lucene.apache.org/java/docs/index.html#28+July+2011+-+WARNING%3A+Index+corruption+and+crashes+in+Apache+Lucene+Core+%2F+Apache+Solr+with+Java+7

If you do decide to run with Java 7 anyhow be sure to set the flags as suggested in the above link.

Stuart, Rich,
Ok (will keep nexus running on Java 6). Thanks for the pointers and your time, really appreciated.

Great, thanks for these hints!

This also happens with the current version 1.9.2.3 using the bundle jetty, so I think this is a major issue: running nexus using 1.7.0 results in the error mentioned, running it under 1.6.0_27 works without problems.

Easiest remedy: add full path to property "wrapper.java.command" in nexus-oss-webapp-19.2.3/bin/jsw/conf/wrapper.conf

Karsten, right, the problem is not related to tomcat, I'll update the issue subject. The problem is due to bugs in the 1.7 JVM, so we are going to hold off testing on 1.7 until they are fixed (see link above)

FYI JDK 7u1, which fixes the Lucene bug, has been released.

Thanks for the update. I've moved this up in ranking, should be supported in next release.

Thanks for the feedback. FWIW, you might also want to check out running with JDK 8 for which weekly snapshot releases are available. It seems stable and fast. I'm using it in production in a few places. Best, David.

Please update the xstream in Nexus so it's compatible with JDK 7, and state minimum requirement of JDK 7 to JDK 7u1 so Lucene is working properly

imho this is a must feature for the 2.0 release. More and more companies are moving to JDK 7. Also OpenJDK 7 will be the default JDK/JRE on the upcoming Ubuntu, debian and RedHat releases. In addition Oracle will EOL Java 6 in 2012...

@all this is already done in master branch (XStream updated to 1.4.1), and naturally Nexus 2.0 will support Java 7

Is that an official position I can put into the training material?

Yes, running Nexus 2.0 under Java 7 will be officially supported.

Training material updated. You might want to create an issue to update the book as well.

Run the IT's with 1.7u1 and note any issues in the release notes

Running with java 1.7
https://builds.sonatype.org/view/nexus/job/nexus-oss-its/156/

After verifying this, set the to use java 1.6 again.

build failed with enunciate error

Same problem here: Kubuntu 11.04

Running only the ITs (not the build itself b/c of the enunciate problem):

https://builds.sonatype.org/view/nexus/job/nexus-oss-its-jdk7

There are three IT failures, all dealing with the error reporting failing to validate ZIP contents.

Hi. Its not clear from the comment history which version of jdk7 you're currently validating, but 7u2 (http://www.oracle.com/technetwork/java/javase/downloads/index.html) was released. In addition, 7u4 is in final pre-release stage so you might consider testing for issues with it: http://jdk7.java.net/download.html.

David

ITs succeeded for OSS and PRO with 1.7.0_02.

Hi Brian. Is the fix to use 1.7.0_02 with latest 1.9.2.x?

David, you might be able to fudge it by using 1.7.0_02 along with Stuart's suggestion above, but officially we will not support 1.7 until the 2.0 release.

Version 1.9.2.4 also will not start under Windows Server 2008 64-bit unless you use the 32-bit wrapper and 32-bit JDK. The community version of Tanuki Wrapper doesn't support 64-bit. It gives the 503 service unavailable error.

Not related to this issue:
Chris, did you try the 64 bit launcher located in <nexus-home>bin/jsw/windows-x86-64/ along with a 64 bit JVM?