Monthly Archives: November 2013

Mele Kalikimaka!

Ok, I totally stole that post title from Amy’s Facebook page. She’ll figure it out one of these days. I stole the picture below too.


Jamie, Ailsa, and their cousin Kayla were all in the Farmville Arts Council’s production of “White Christmas”. The play runs from Thursday Nov. 21st – Sunday Nov. 24th. Amy and I, as well as Amy’s mom Eve, sister Melanie and her husband Rob all had tickets to see the kids perform last night. THEY WERE AWESOME!

The central characters of the play are two American GI’s who were together in WWII. The play begins on the battlefield in 1944, but quickly fast forwards to their post-army lives ten years later, in 1954. By this time these characters have hit it big in music. They have it all, except that is, love. Naturally they meet up with two girls (also musicians but not big time yet). They also meet up with their former General, who just happens to own an inn in Vermont. So that’s where much of the story is set — at the inn, which is in danger of being foreclosed. In the end the inn is not foreclosed, the general figures out that he can’t run his inn like a battalion, and the main characters are all in love. 🙂

The kids had a small part at the beginning of act II. It’s a scene set in the barn at this inn, where they are practicing to put on a show. They had to sing and dance, and they were all great!

My favorite part might just have been the end of the show — the curtain call. I loved seeing all the kids come out, take each other by the hand, and bow to an applauding audience. That was something I won’t soon forget.

Great job kids!

JBoss + HornetMQ + Encrypted FS + AIO

I wrestled with an …. interesting issue today that sunk most of my morning. I was working on an EJB3 application with a local installation of JBoss 6.1. In fact, I worked on the same application last Friday. Today, however, when I started the server I was greeted with this:

16:23:28,800 ERROR [org.hornetq.ra.inflow.HornetQActivation] Unable to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@4076fc9 destination= destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): HornetQException[errorCode=2 message=Cannot connect to server(s). Tried with all available servers.]
at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory( [:6.1.0.Final]
at org.hornetq.ra.inflow.HornetQActivation.setupSession( [:6.1.0.Final]
at org.hornetq.ra.inflow.HornetQActivation.setup( [:6.1.0.Final]

So, I did what any software developer would and ran to Google. Google, unfortunately, didn’t give me much. I wrestled with it for longer than I should have, feeling stumped, when finally I found towards the top of the log :

10:12:20,837 INFO [AIOFileLockNodeManager] Waiting to obtain live lock
10:12:20,837 INFO [AIOFileLockNodeManager] Live Server Obtained live lock
10:12:21,159 SEVERE [HornetQServerImpl] Failure in initialisation: HornetQException[errorCode=205 message=Can’t open file]
at org.hornetq.core.asyncio.impl.AsynchronousFileImpl.init(Native Method) [:6.1.0.Final]

This was me: “Uhm, what? Is this a permissions issue? But I haven’t touched this configuration and it was just working!!! #$)**!@!”

With that additional information I turned back to Google, and this time found the issue. On Linux systems (I am running Linux Mint) with libaio installed, JBoss will attempt to use AIO for direct and asynchronous file operations. Basically, it’s a performance optimization that bypasses the file system cache in favor of very low level file operations. HOWEVER, if you are on an ENCRYPTED file system (which I am), then this breaks.

That was great, but if it worked Friday, and I haven’t updated the config, then what gives? Well, I did install MySQL over the weekend – and it turns out that MySQL on Ubuntu based systems does install libaio. So, in short, though the configuration hasn’t changed, the environment did.

Finally, I discovered a solution – just configure JBoss to not use AIO. I haven’t used it up until now anyway, but now I had to explictly tell it not to. This can be done in /deploy/hornetq/hornetq-configuration.xml with one line:

< journal-type > NIO < /journal-type >

Hopefully that saves someone out there a little trouble. Probably me in 6 or 12 months from now. 🙂