kodo.util.FatalUserException

Attempt to set column "my_table.version_number" to two different values: (java.lang.Integer)"27", (java.lang.Integer)"29" This can occur when you fail to set both sides of a two-sided relation between objects, or when you map different fields to the same column, but you do not keep the values of these fields in synch.)

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • via Unknown by 3004,
  • Stack trace

    • kodo.util.FatalUserException: Attempt to set column "my_table.version_number" to two different values: (java.lang.Integer)"27", (java.lang.Integer)"29" This can occur when you fail to set both sides of a two-sided relation between objects, or when you map different fields to the same column, but you do not keep the values of these fields in synch.) at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:415) at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:458) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:326) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:150) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:111) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:331) at org.jboss.ejb.Container.invoke(Container.java:709) at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:360) at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) Caused by: kodo.util.FatalUserException: Attempt to set column "my_table.version_number" to two different values: (java.lang.Integer)"27", (java.lang.Integer)"29" This can occur when you fail to set both sides of a two-sided relation between objects, or when you map different fields to the same column, but you do not keep the values of these fields in synch. at kodo.jdbc.runtime.VRow.setObjectInternal(VRow.java:95) at kodo.jdbc.sql.AbstractRow.setObject(AbstractRow.java:562) at kodo.jdbc.meta.ColumnVersionIndicator.change(ColumnVersionIndicator.java:512) at kodo.jdbc.meta.ColumnVersionIndicator.update(ColumnVersionIndicator.java:435) at kodo.jdbc.runtime.UpdateManagerImpl.update(UpdateManagerImpl.java:315) at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:128) at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:73) at kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:588) at kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:152) at kodo.runtime.PersistenceManagerImpl.flushInternal(PersistenceManagerImpl.java:969) at kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:814) at org.jboss.tm.TransactionImpl.doBeforeCompletion(TransactionImpl.java:1362) at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:347) ... 28 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.