The *official* training starts today. Keeping things really simple.

• No Skipped Workouts
• All Runs Outside if possible
• No Alcohol
• No Soft Drinks
• No Fast Food
• No Processed Crap
• Nothing to drink except water, Propel, coffee and unsweetened tea.
• If all is followed - 1 cheat meal a week. Probably at BW3.

Blogging on Sunday every week to talk about the past week and what's on tap next week.

Last Week: Sick from strep and recovering from Vegas.

Next Week: Runs on Tues, Thurs and Fri. Easy, Tempo and Easy. Flying to Jersey City next week so my runs will need to be earlier and the temptation of eating like crap and boozing is always prevalent when on the road. Not the ideal week to start my training, but this week my resolve is solid so no worries. It's usually about 4 or 5 weeks into training when I start trying to convince myself it's ok to eat that breakfast burrito and drink a beer.

Here's the run from today.

Playing 9 at Tour 18 this evening.

Good run today. Next Run: Thursday at 6:30a.

3 days turned into 7.

So what's the problem? Little excuses turn into big, run-canceling excuses. I have a 13.1 mile race in 12 weeks in San Antonio. San Antonio and Houston have many differences but only a single one will be on my mind that day - Hills. These little excuses have to go. This can't be about training anymore, but rather a lifestyle change. If there is something that is going to interfere with my running schedule, it stops today. I know what to look for. I know what I need to do. It's not a matter of whether or not I can physically do it. It's a matter of whether I can focus and sacrifice for the goal.

Today, I sacrificed. After a week off, I got up two hours later on a Sunday and went for a run at 8:30a. I was overheated and couldn't keep my heart rate down. Where I can normally maintain a 160 for at least 3 or 4 miles, I was at 170 before I knew it and it killed my run, both on pace and distance. My de facto running coach said that your HR is a tell-tale sign of how your body is sustaining itself during the run. A high rate rate is the first sign that your body is saying it's tired. When I got to the end my heart rate was 183 and I could barely walk. It's been 45 minutes since with a 20 minute freezing cold shower and I am still sweating. Granted, I did play golf during the heat of the day yesterday and sweated a few gallons of water but that shouldn't affect me this hard. Needless to say, I have a bit of work ahead of me.

Next Run: Tuesday at 6:30. Running Workout, 3 miles and 3 sets.

List<String> names = new ArrayList<String>();
names.add("Bob");
NamedCache cache = CacheFactory.getCache("test");
cache.put("B", names);

List<String> names2 = (List<String>)cache.get("B");
names2.add("Bill");
cache.put("B", names2);

But what this does actually requires a complete serialization of the payload both from the (possibly) remote location and back to the backup node when the put is executed. Network traffic and IO no bueno.

Instead, extend the AbstractProcessor and ship that work out to the node, cutting network IO in half.

public class AddNameProcessor extends AbstractProcessor {

	private String name;

	public AddNameProcessor(String name) {
		this.name = name;
	}

	@SuppressWarnings("unchecked")
	public Object process(Entry entry) {
		List<String> list = null;
		if (entry.getValue() == null){
			list = new ArrayList<String>();
			list.add(name);
			entry.setValue(list);
			return list;
		} else {
			list = (List<String>)entry.getValue();
			list.add(name);
			entry.setValue(list);
			return list;
		}
	}

}

And call it in a similar way.

NamedCache cache = CacheFactory.getCache("test");
List<String> names = (List<String>) cache.invoke("B", new AddNameProcessor ("Bill"));

3) sudo vim /etc/apache2/apache2.conf
and type/past in:
# Load mod_jk module
# Update this path to match your modules location
LoadModule jk_module /usr/lib/apache2/modules/mod_jk.so
# Declare the module for (remove this line on Apache 2.x)
#AddModule mod_jk.c
# Where to find workers.properties
# Update this path to match your conf directory location (put workers.properties next to httpd.conf)
JkWorkersFile /etc/apache2/workers.properties
# Where to put jk shared memory
# Update this path to match your local state directory or logs directory
JkShmFile /var/log/apache2/mod_jk.shm
# Where to put jk logs
# Update this path to match your logs directory location (put mod_jk.log next to access_log)
JkLogFile /var/log/apache2/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel info
# Select the timestamp log format
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "

6) sudo vim /etc/apache2/sites-enabled/000-default
Delete "DocumentRoot /var/www"
And type in
JkMount / worker1
JkMount /* worker1
note, you can use JkUnMount to define directories you want apache to serve

7) Enable port 8009 on tomcat
sudo vim /etc/tomcat6/server.xml
remove the "" that is a line below

restart tomcat
sudo /etc/init.d/tomcat6 restart

9) restart apache
sudo /etc/init.d/apache2 restart

10) wget localhost
You should see the default tomcat page

Courtesy of: http://rcpeters.blogspot.com/2009/05/installing-apache2-and-tomcat6-on.html

<beans xmlns="http://www.springframework.org/schema/beans"
	xmlns:amq="http://activemq.apache.org/schema/core"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
  		http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd
  		http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">

	<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" />

	<broker xmlns="http://activemq.apache.org/schema/core" brokerName="MyBroker" dataDirectory="${activemq.base}/data">

		<destinations>
			<queue physicalName="MyQueue" />
		</destinations>

		<transportConnectors>
			<transportConnector name="openwire" uri="tcp://localhost:0" discoveryUri="multicast://default"/>
		</transportConnectors>

		<networkConnectors>
      		<networkConnector uri="multicast://default"/>
    	</networkConnectors>

	    <persistenceAdapter>
	      	<memoryPersistenceAdapter/>
	    </persistenceAdapter>

	</broker>

	<jetty xmlns="http://mortbay.com/schemas/jetty/1.0">
        <connectors>
            <nioConnector port="8161"/>
        </connectors>

        <handlers>
            <webAppContext contextPath="/admin" resourceBase="${activemq.base}/webapps/admin" logUrlOnStart="true"/>
        </handlers>
    </jetty>

</beans>

And here is the Spring code for the client.

<bean id="jmsConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
 		<property name="brokerURL">
 			<value>discovery:(multicast://default)</value>
 		</property>
 	</bean>

 	<bean id="destination" class="org.apache.activemq.command.ActiveMQQueue">
 		<constructor-arg index="0">
 			<value>MyQueue</value>
 		</constructor-arg>
 	</bean>

 	<bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">
 		<property name="connectionFactory">
 			<bean class="org.springframework.jms.connection.SingleConnectionFactory">
 				<property name="targetConnectionFactory" ref="jmsConnectionFactory" />
 			</bean>
 		</property>
 	</bean>

If you will notice, the ActiveMQ client uses the discovery mechanisms for finding the queue, which allows it to connect to any piece of hardware without actually having to know physical locations. You can replace your multicast://default (which happens to be multicast://239.255.2.3:6155) with whatever multicast address you would like. You could even DNS-it-up and have a url look like multicast://MyBroker.mydomain.com:6166.

Enjoy.

http://activemq.apache.org/multicast-transport-reference.html

Here's a basic drawing describing a minimum development environment for any company. The "servers" can be consolidated to a certain point, especially if you are using virtualization software.

Also, the source control, continuous integration and maven repository manager can realistically all run on a single server. You MIGHT be able to get away with running the actual builds on the box but might run into some performance issues, particularly if you are running a big build and simultaneously checking in a bunch of source code.