This looks similar to the optimistic locking algorythm of the EJB2 cmp persistence manager.
There all updates with OLock will have a version column and the update is e.g. 'UPDATE .... set ol_version=2 WHERE ol_version=1'
and if a concurrent process has updated before a message like yours occor.
So is the behaviour sporadicaly?
To get mor information you should active log level TRACE for 'org.jboss.mq.pm.jdbc2'.