Visit my.sonatype.com for documentation on Nexus Repository version 2.
Nexus Repository 2 does not ship with solaris-x86-64 Java Service Wrapper binaries, only solaris-sparc-32, solaris-sparc-64, solaris-x86-32.
For those customers who need to run Nexus Repository 2 on Solaris x86 64bit, we provide these optional Java Service Wrapper binaries.
Until these binaries are officially added to a Sonatype Nexus distribution, these binaries are use at your own risk.
These have undergone limited testing with Solaris 11, Java 1.7.0_45 only.
Install the Binaries in Nexus Repository 2
Download the attached file to your Nexus Repository 2 application directory and extract.
Example:
cd nexus-professional-2.7.0-06 tar xzvf nexus-wrapper-3.2.3-solaris-x86-64.tar.gz
Force Nexus Control Script to Use the 64 bit Binaries
The existing Nexus control script does not properly detect the 64 bit environment on Solaris 11 using uname. Therefore we need to trick it to use the 64 bit binaries by default.
Edit bin/nexus control script, change:
DIST_BITS=32
to:
DIST_BITS=64
Force Nexus JVM to 64 bit
Edit bin/jsw/conf/wrapper.conf, adding
wrapper.java.additional.4=-d64
... changing the 4 to the next available unused index. This forces the JVM into 64 bit mode.
Explicitly set the java used to a 64 bit java installation. This is optional if java will always find the correct java 64bit install on the PATH. Example
wrapper.java.command=/home/nexus/java/jdk1.7.0_45/bin/java
Verification
You can rename the bin/jsw/solaris-x86-32 directory to solaris-x86-32-DISABLED to make sure the 32 bit JSW binaries are not used by accident.
If you set wrapper.debug=true in bin/jsw/conf/wrapper.conf temporarily, then on startup you will see the the wrapper print the following, proving Nexus is using the 64 bit binaries and 64bit mode of Java.
Running a 64-bit JVM Loaded native library: libwrapper-solaris-x86-64.so
As a final check, make sure Nexus Repository 2 responds to system signals. After starting with ./bin/nexus console, CTRL-C to stop Nexus Repository 2. Also test sending the process kill -QUIT <pid> and make sure thread dump is put in wrapper log.
0 Comments