org.hibernate.AssertionFailure: collection [ class name here ] was not processed by flush()

I tried changing the owning side of the collection, made a join table, and nothing helped.  The error started when I added an @IndexEmbedded annotation to the collection, and I discovered I was missing the @ContainedIn annotation in the collection entity.  That didn’t fix it.  After weeks of doing little tweaks, breaking, fixing, breaking, fixing, I finally discovered the problem.  I was using an older manual for Hibernate Search (3.0 specifically) and I had the following configuration parameter pushed into my SessionFactory:

hibernate.search.worker.batch_size = 1

As of Hibernate Search 3.1, that parameter has been deprecated.  It has been replaced by a number of other settings allowing finer-grained control over your batch processing in Hibernate Search.  Eventually we’re upgrading to Hibernate Search 3.2 which handles batches altogether differently/better.  Thought I’d share, because this one had me stumped.

http://sourceforge.net/projects/eclipse-rbe

It installs in a snap and provides a simple, yet powerful, interface for a bundle.

1. Open a new Finder window.
2. Click “Go” and then “Go to Folder” (or hit Command-Shift-G).
3. Type in “/System/Library/CoreServices” and hit enter.
4. Find the “Screen Sharing” application, click once to highlight.
5. Click “File” and then “Get Info” (or hit Command-I).
6. Find the checkbox labeled “Open in 32-bit mode” and check it.
7. Close the Info window and Finder folder window.

That’s it!  Apparently there is a bug in the application only when running in 64-bit mode.  I don’t really care why it fixes it, I’m just glad its fixed and I thought I’d share.

Thanks to the anonymous user on Mac OS X Hints!

Hibernate 3.3.2 is configured inside of Spring using the Annotation-based session factory bean.  Because I’m using JTA to manage transactions and Hibernate’s current session, I need to make sure that the secondary cache, whatever I choose, is aware of the transaction manager.  I originally had EHCache 2.0.1 hooked into Hibernate via Hibernate configuration parameters passed into Spring’s bean.  I was not setting the cache factory parameter on this bean.  Everything works fine in this configuration and it recognizes the JTA transactions.

This application needs to be clustered horizontally – ensuring each component of the solution is failover-ready.  JBoss Cache 2 is baked into JBoss AS 5.1 and a logical choice to pick.  Hibernate has an extension JAR and it’s a simple interface, especially when you’re pulling out the cache from JNDI.

The problem?  The JTA transaction manager that Spring proxies isn’t available to JBoss Cache.  JBoss Cache (on JBoss AS) runs at the container-level inside of a different classloader.  Spring holds onto the reference to the transaction manager proxy inside of a ThreadLocal variable which is NOT accessible to the container.  To get around this, I tried using Hibernate’s implementation of the JBoss Transaction Manager lookup class, thinking since it’s JTA it’ll work.

It didn’t.

When I tried bringing up the application, I ran into errors surrounding the current transaction.  At one point, the transaction was timing out during a cache pre-load process the application has.  In another configuration, the application loaded but after a few minutes the app exceptioned out with a stale JDBC connection to the database.  It was obvious to me that the JTA transaction surrounding the cache didn’t sync with the Spring JTA transaction.

I eventually gave up on JBoss Cache and am going with EHCache 2.0 using JGroups to synchronize each node.  The “all” configuration of JBoss AS 5.1 has both JGroups and JBoss Cache preconfigured.  I hooked into the synchronous JGroups UDP configuration, using the same JVM parameters the JBoss XML files use so that my app doesn’t need a special deployment for each server.  Theoretically, the configuration will work in a cluster without having to change anything around.

We’ll see how the clustering works later on but for now, single node in cluster mode is working just fine.

Head on over to Net Workz LLC to find the app.

I still have a lot of work left to do before I’m really happy with it.  Help screens, more graphing, and encryption are two things I really need to get out there.  Until then, enjoy!

> defaults delete com.apple.Xcode

> rm -rf ~/Library/Application\ Support/Xcode

After doing this, I had to re-add my Subversion repository, move my build folder to the /tmp directory, and pick my text editor color scheme again.  However, I now have a functioning Xcode and things seems happier again.  Yippy skippy!

http://googlevoiceblog.blogspot.com/2009/10/google-voice-with-your-existing-number.html

What this means is you can now have all of your voicemails handled by one service provider.  This feature only works with cell phones (most US carriers supported) but not landlines, VoIP or SIP phones yet.

I switched my iPhone voicemail over to Google Voice today for a trial period.  I’ll see if I like it and report back.  My first attempt wasn’t perfect – it took nearly four additional rings after I ignored a test call for Google Voice to pick up.  A total of eight rings is way too much for most callers to wait to leave a message.

One important thing to note – you will most likely have to pay airtime for the call while it is RINGING and inside of your Google Voice mailbox.  You’re not going to get something for free .

Xcode[669] -[XCBuildLogCommandInvocationSection setTestsPassedString:]: unrecognized selector sent to instance 0x2009b7620

Xcode[669] -runOperationInBackground raised an exception: -[XCBuildLogCommandInvocationSection setTestsPassedString:]: unrecognized selector sent to instance 0x2009b7620

Needless to say, I was losing my mind. Finally, a user in the Apple Developer forums, “cde”, posted the following gem:

We have recently discovered the root cause of this problem.

People who are affected can work around it by (I hope you’re ready for this)…

…changing the Time Zone on your Build machine away from Central Daylight Time.  (In six weeks you can change it back, and people in Mountain Standard TIme will be affected.)

No, seriously.  Give it a try.

The problem is a single-character typo in a regular expression that parses the date stamp of the unit test. It causes it to miss the beginning of unit tests that are executed at -0500 or +0500 relative to GMT, so the end of those unit tests is unexpected, and it causes the build log parsing logic to initially hang and eventually crash.

As has been said, “Then I decided to use regular expressions, and I had two problems…”

So until it’s fixed, change your timezone to Pacific time.

First task – find a template.  An SPMP is usually based off of IEEE’s standard 1058-1998, which costs more than a hundred dollars to get a copy of.  I’m not paying $100+ to get a 200KB document.  I’ve seen example around the Internet of a SPMP but nothing that was formatted well in Word or handled copying and pasting into Word.  I spent some time doing more digging and found this wonderful site -

Construx – Resources & Tools

The site/company was founded by Steve McConnell – a name I had not heard of until now.  He’s apparently well known for software design, etc.  Free registration gives you access to the tools and under Management there is a full and light template along with instructions.  Score!