Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What issues should be specifically checked for when deploying a server application written in Java (without any specific platform dependencies) that was written and tested on Windows.

Two that I know of:

  1. Case sensitive file names
  2. Available fonts
share|improve this question
up vote 3 down vote accepted

Ensure that any third part JAR files you use (such as SWT) have the appropriate platform-dependent version. While you said "without any specific platform dependencies", platform-specific behavior can sometimes be hidden.


  1. File paths (do you have paths such as C:\Program Files?)
  2. File paths (do you use '/' or '\' or do you use the appropriate constant File.pathSeparator?)
  3. How do you locate important directories such as the user's home directory?
  4. If you're opening sockets below port 1024, will you be the root user in UNIX?
  5. Will you be using the Sun JVM, gcj, or some other JVM? Will differences in implementation or performance affect your application?
  6. Check the JVM release notes (e.g., for J2SE 5 or Java SE 6) for mention of bugs or other behavior differences on your platforms of choice.
share|improve this answer

You'll almost certainly want to set


in case any libraries try to do any font rendering, image manipulation, or anything else that touches Swing, AWT or ImageIO

share|improve this answer

1) Ensure your JVM's are identical on both platforms. 2) Some level of JVM tuning will likely be necessary. 3) Enable logging of your JVM for a short period of time to determine if you are having any problems.

share|improve this answer

Admittedly not particularly Windows-to-Unix specific, but worth noting based on our experiences:

  • Check the settings in $JAVA_HOME/jre/lib/security/ - particularly networkaddress.cache.ttl - the Sun JRE by default will cache DNS lookups forever, which has bitten us and our clients on several occasions. '' should override it from the command line.

  • Ensure you are running with an adequately sized heap: -Xmx2048m or similar (depending on your app requirements)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.