I discovered the following in the log files:

2011-08-15 18:06:24,605 [] INFO  o.a.catalina.core.StandardEngine - Starting Servlet Engine: Apache Tomcat/6.0.32
2011-08-15 18:06:24,606 [] INFO  o.a.catalina.ha.tcp.SimpleTcpCluster - Cluster is about to start
2011-08-15 18:06:24,650 [] INFO  o.a.c.tribes.transport.ReceiverBase - Receiver Server Socket bound to:/127.0.0.1:5000
2011-08-15 18:06:24,660 [] INFO  o.a.c.tribes.membership.McastService - Attempting to bind the multicast socket to /228.0.0.4:45564
2011-08-15 18:06:24,668 [] INFO  o.a.c.tribes.membership.McastService - Setting multihome multicast interface to:/127.0.0.1
2011-08-15 18:06:24,669 [] INFO  o.a.c.tribes.membership.McastService - Setting cluster mcast soTimeout to 500
2011-08-15 18:06:24,673 [] INFO  o.a.c.tribes.membership.McastService - Sleeping for 1000 milliseconds to establish cluster membership, start level:4
2011-08-15 18:06:25,675 [] INFO  o.a.c.tribes.membership.McastService - Done sleeping, membership established, start level:4
2011-08-15 18:06:25,681 [] ERROR o.a.catalina.ha.tcp.SimpleTcpCluster - Unable to start cluster.
org.apache.catalina.tribes.ChannelException: java.io.IOException: Can't assign requested address; No faulty members identified.

After some checking of my /etc/hosts file and a couple other things I found a very relevant Tomcat Cluster troubleshooting tip.

I added the following to my catalina.sh file for the JAVA_OPTS variable, and Tomcat started up as usual:

-Djava.net.preferIPv4Stack=true

Turns out it was trying to setup the Tomcat cluster on my IPv6 interface and then I assume trying to access it via the IPv4 interface. Obviously they couldn’t communicate.

I’ve never had to do this on any prior version of OS X, nor any of my Linux machines.

$Id: MySpecialClass.java 12234 2004-05-21 00:23:08Z derek $

I did some research into the problem and unfortunately there wasn’t anything on the server side I could do to force this setting on all files as they are added and checked in to the SVN repository. To automatically enable keyword substitution you must do two things.

First, uncomment the enable-auto-props = yes line in ~/.subversion/config in each users home directory.

### Set enable-auto-props to 'yes' to enable automatic properties
### for 'svn add' and 'svn import', it defaults to 'no'.
### Automatic properties are defined in the section 'auto-props'.
enable-auto-props = yes

Then you must configure the file types to which you will apply keyword substitution:

### Section for configuring automatic properties.
[auto-props]
### The format of the entries is:
###   file-name-pattern = propname[=value][;propname[=value]...]
### The file-name-pattern can contain wildcards (such as '*' and
### '?').  All entries which match will be applied to the file.
### Note that auto-props functionality must be enabled, which
### is typically done by setting the 'enable-auto-props' option.
*.c = svn:eol-style=native;svn:keywords=Date Author Id Revision HeadURL

I appended ;svn:keywords=Date Author Id Revision HeadURL to the entry for .c files in ~/.subversion/config. Uncomment other file types in the file and adjust them as needed. Feel free to add new lines to the file for other source files such as .php and .java. These settings will take effect for all new files that you add to the repository.

If you happen to have existing files in the repository that need to have the keyword property set you can set it by running the command:
svn propset svn:keywords 'Author Date Id Revision HeadURL'

svn:keyword documentation

Here’s a very useful set of instructions that every developer that deploys on unix/linux should know.

“If you want to be a serious server developer, you will need to have a certain facility with a number of UNIX tools; about 15. You will start to see similarities among them, particularly regular expressions, and soon you will feel very comfortable. Combining the simple commands, you can build very powerful tools very quickly–much faster than you could build the equivalent functionality in C or Java, for example.”

My favorite of all the commands mentioned is rsync. I use it daily to move things around between servers and even on the same machine. I’ll discuss rsync and how I use it later.