Skip to main content

Use 64 bit data model JVM on Sun X Solaris

Goal: Either to determine the bit width in a Java program or use a 64 bit data model JVM.
OS: SunX Solaris 64 bit OS.
  1. First of all install 32 bit JDK/JRE (steps 1 and 2 are valid for JDK 1.6)
  2. Then add 64 bit packages over it. This will convert the JDK to work in both 32 bit and 64 bit modes (but 32 bit is still default).
  3. To test it for 32 bit, run $ java -version
  4. To test it for 64 bit, run $ java -d64 -version
  5. In ant binary file (in bin folder of apache-ant) add line ANT_OPTS="$ANT_OPTS -d64"
  6. If you do not want to change ant binary file, then you can set the environment variable every time you run the ant command. For e.g. setenv ANT_OPTS -d64
  7. Next you add instructions in build.xml file used by ant. In Java/JUnit tags, add property clonevm="true" if you have fork="true" property. This will clone the same VM environment for all forked processes, as for ant process itself. clonevm will not have any effect if fork is false.
  8. Run you ant target.
Following is the code example:
JVMBitSize.java
class JVMBitSize
{
  private static int jvmBit = 32;
  public static void main(String args[])
  {
    String sysProp = System.getProperty("sun.arch.data.model");
    System.out.println(sysProp);
    if(sysProp != null) {
      try {
        jvmBit = Integer.parseInt(sysProp.trim());
        System.out.println("JVMBit = " + jvmBit);
      } catch(NumberFormatException e) {
        System.out.println(e.getMessage());
      }
    }
  }
}

build.xml
<project name=" JVMBitSize " default="run" basedir=".">
  <path id="JVMBitSize.classpath">
    <path location="${basedir}"/>
  </path>
  <target name="compile">
    <javac srcdir="."/>
  </target>
  <target name="run" depends="compile">
    <echo level="info" message="JVM bit size in ant, before java task: ${sun.arch.data.model}"/>
    <java classname=" JVMBitSize" fork="true" clonevm="true">
      <classpath refid="JVMBitSize.classpath"/>
    </java>
  </target>
</project>

ant
#So that 64 bit data model of JVM is used and no java.lang.OutOfMemoryError exceptions are thrown
ANT_OPTS="$ANT_OPTS -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m -d64"

To run program:
$ant run

Comments

Connor Harley said…
I was pretty clueless at first but I asked my brother and boom! Thanks for this.
Anonymous said…
This comment has been removed by a blog administrator.

Popular posts from this blog

MPlayer subtitle font problem in Windows

While playing a video with subtitles in mplayer, I was getting the following problem: New_Face failed. Maybe the font path is wrong. Please supply the text font file (~/.mplayer/subfont.ttf). Solution is as follows: Right click on "My Computer". Select "Properties". Go to "Advanced" tab. Click on "Environment Variables". Delete "HOME" variable from User / System variables.

wget and curl behind corporate proxy throws certificate is not trusted or certificate doesn't have a known issuer

If you try to run wget or curl in Ununtu/Debian behind corporate proxy, you might receive errors like: ERROR: The certificate of 'apertium.projectjj.com' is not trusted. ERROR: The certificate of 'apertium.projectjj.com' doesn't have a known issuer. wget https://apertium.projectjj.com/apt/apertium-packaging.public.gpg ERROR: cannot verify apertium.projectjj.com's certificate, issued by 'emailAddress=proxyteam@corporate.proxy.com,CN=diassl.corporate.proxy.com,OU=Division UK,O=Group name,L=Company,ST=GB,C=UK': Unable to locally verify the issuer's authority. To connect to apertium.projectjj.com insecurely, use `--no-check-certificate'. To solution is to install your company's CA certificate in Ubuntu. In Windows, open the first part of URL in your web browser. e.g. open https://apertium.projectjj.com in web browser. If you inspect the certifcate, you will see the same CN (diassl.corporate.proxy.com), as reported by the error above ...

Kafka performance tuning

Performance Tuning of Kafka is critical when your cluster grow in size. Below are few points to consider to improve Kafka performance: Consumer group ID : Never use same exact consumer group ID for dozens of machines consuming from different topics. All of those commits will end up on the same exact partition of __consumer_offsets , hence the same broker, and this might in turn cause performance problems. Choose the consumer group ID to group_id+topic_name . Skewed : A broker is skewed if its number of partitions is greater that the average of partitions per broker on the given topic. Example: 2 brokers share 4 partitions, if one of them has 3 partitions, it is skewed (3 > 2). Try to make sure that none of the brokers is skewed. Spread : Brokers spread is the percentage of brokers in the cluster that has partitions for the given topic. Example: 3 brokers share a topic that has 2 partitions, so 66% of the brokers have partitions for this topic. Try to achieve 100% broker spread...