<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ramblings &#187; jboss</title>
	<atom:link href="http://matthewkwilliams.com/index.php/category/jboss/feed/" rel="self" type="application/rss+xml" />
	<link>http://matthewkwilliams.com</link>
	<description>Musings of Matt Williams</description>
	<lastBuildDate>Wed, 09 Jun 2010 17:38:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Torquebox and Cygwin: Take I</title>
		<link>http://matthewkwilliams.com/index.php/2010/06/09/torquebox-and-cygwin-take-i/</link>
		<comments>http://matthewkwilliams.com/index.php/2010/06/09/torquebox-and-cygwin-take-i/#comments</comments>
		<pubDate>Wed, 09 Jun 2010 17:38:26 +0000</pubDate>
		<dc:creator>Matt Williams</dc:creator>
				<category><![CDATA[gotchas]]></category>
		<category><![CDATA[jboss]]></category>
		<category><![CDATA[jruby]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[torquebox]]></category>
		<category><![CDATA[cygwin]]></category>

		<guid isPermaLink="false">http://matthewkwilliams.com/?p=263</guid>
		<description><![CDATA[Torquebox and Cygwin don&#8217;t work as nicely together as one might hope. That said, here are a couple of findings: In order to deploy, you need to set the $JBOSS_HOME with the Windows path.  You can do this via export JBOSS_PATH=`cygpath -w PATH_TO_JBOSS`. Additionally, the JRUBY_HOME needs to be a windows path as well.   Otherwise [...]]]></description>
		<wfw:commentRss>http://matthewkwilliams.com/index.php/2010/06/09/torquebox-and-cygwin-take-i/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using jnp as a JBoss heartbeat</title>
		<link>http://matthewkwilliams.com/index.php/2009/08/25/using-jnp-as-a-jboss-heartbeat/</link>
		<comments>http://matthewkwilliams.com/index.php/2009/08/25/using-jnp-as-a-jboss-heartbeat/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 19:00:57 +0000</pubDate>
		<dc:creator>Matt Williams</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[jboss]]></category>
		<category><![CDATA[jruby]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Java Naming and Directory Interface]]></category>
		<category><![CDATA[JBoss application server]]></category>

		<guid isPermaLink="false">http://matthewkwilliams.com/?p=236</guid>
		<description><![CDATA[jnp is a JBoss protocol which exposes jndi.  It is, by default, bound to port 1099.  I&#8217;d been using that port as a heartbeat, but &#8220;cheating&#8221; &#8212; I would open a socket and then close it immediately.  However, this caused problems.  jnp is chatty.  And it got upset at my not letting it say &#8216;hi&#8217; [...]]]></description>
		<wfw:commentRss>http://matthewkwilliams.com/index.php/2009/08/25/using-jnp-as-a-jboss-heartbeat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JBoss port confusion</title>
		<link>http://matthewkwilliams.com/index.php/2009/07/29/jboss-port-confusion/</link>
		<comments>http://matthewkwilliams.com/index.php/2009/07/29/jboss-port-confusion/#comments</comments>
		<pubDate>Wed, 29 Jul 2009 14:16:30 +0000</pubDate>
		<dc:creator>Matt Williams</dc:creator>
				<category><![CDATA[gotchas]]></category>
		<category><![CDATA[jboss]]></category>
		<category><![CDATA[dns]]></category>
		<category><![CDATA[Java]]></category>

		<guid isPermaLink="false">http://matthewkwilliams.com/?p=233</guid>
		<description><![CDATA[Sometimes, JBoss reports that it is unable to bind to a port, saying it is already in use.  However, this is not always the case.]]></description>
		<wfw:commentRss>http://matthewkwilliams.com/index.php/2009/07/29/jboss-port-confusion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JBoss and Sesame Street&#8217;s Count</title>
		<link>http://matthewkwilliams.com/index.php/2008/12/17/jboss-and-sesame-streets-count/</link>
		<comments>http://matthewkwilliams.com/index.php/2008/12/17/jboss-and-sesame-streets-count/#comments</comments>
		<pubDate>Wed, 17 Dec 2008 20:05:24 +0000</pubDate>
		<dc:creator>Matt Williams</dc:creator>
				<category><![CDATA[jboss]]></category>
		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://matthewkwilliams.com/index.php/2008/12/17/jboss-and-sesame-streets-count/</guid>
		<description><![CDATA[One, One database record! Two, Two database record! Muahahaha! By default, when using datasources with JBoss, it does a count to validate a connection, both on creation and when it is requested from the connection pool.&#160; It looks something like: select count(*) from x Now, this can take take a while when working with tables [...]]]></description>
		<wfw:commentRss>http://matthewkwilliams.com/index.php/2008/12/17/jboss-and-sesame-streets-count/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JBoss run.sh may be harmful</title>
		<link>http://matthewkwilliams.com/index.php/2008/09/25/jboss-runsh-may-be-harmful/</link>
		<comments>http://matthewkwilliams.com/index.php/2008/09/25/jboss-runsh-may-be-harmful/#comments</comments>
		<pubDate>Thu, 25 Sep 2008 19:39:38 +0000</pubDate>
		<dc:creator>Matt Williams</dc:creator>
				<category><![CDATA[gotchas]]></category>
		<category><![CDATA[jboss]]></category>
		<category><![CDATA[shell]]></category>

		<guid isPermaLink="false">http://matthewkwilliams.com/?p=175</guid>
		<description><![CDATA[A coworker and I discovered an issue with jboss&#8217; run.sh (which starts the app server).  The problem lies in different flavours of unix (or unix-like) shells returning different values for wait. The relevant code is: # Wait until the background process exits WAIT_STATUS=0 while [ &#34;$WAIT_STATUS&#34; -ne 127 ]; do JBOSS_STATUS=$WAIT_STATUS wait $JBOSS_PID 2&#62;/dev/null WAIT_STATUS=$? [...]]]></description>
		<wfw:commentRss>http://matthewkwilliams.com/index.php/2008/09/25/jboss-runsh-may-be-harmful/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
