If you’re trying to bind a Hibernate SessionFactory to a WebLogic cluster and you’re getting the following error message:

“Conflict start: You tried to bind an object under the name [{factory.name}] in the JNDI tree. The object from [{factory.name}] is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server.”

You may want to add this to you hibernate.cfg.xml file:

<property name="hibernate.jndi.weblogic.jndi.replicateBindings">false</property>

This has worked for me with WebLogic 8.1, and it is probably applicable to other WebLogic versions as well. While I haven’t come across any solid documentation which states that the SessionFactory is not a clusterable object, it appears that this is the case. This isn’t a big deal however, especially if you’re not using a second-level cache. If you need to use a second-level cache, you’ll want to use a cluster-aware cache such as JBoss Cache or Tangosol Coherence.

This weekend I finally got around to upgrading this blog to WordPress 2.0.3, and my photo blog, to PixelPost 1.5. Recently, both blogs have been getting hammered with comment SPAM. This blog doesn’t get a large amount of traffic, but the number of comment SPAM, and referrer SPAM, has been difficult to manage. Thankfully, the folks at Automattic (the makers of WordPress) offer the ever-so-helpful Akismet service, which is integrated into WordPress 2.0 in the form of a plugin. To use it, you’ll need WordPress.com API which is pretty easy to come by. One the plugin is activated, the SPAM comments pretty much go away. PixelPost 1.5 also boasts some great new anti-spam tools as well, plus and optional hack to work with Akismet. Even without the Akisment hack, I haven’t had a single obscene comment visible on the site. With both of these upgrades, I haven’t had to spend time deleting some 100+ comments a day from Zyban & Zoloft. I couldn’t be happier