0 Replies Latest reply on Jan 18, 2011 8:28 PM by Tim S.

    Error: relation "jbm_dual" already exists

    Tim S. Newbie

      I've set up jboss messaging in a 2 node Jboss 4.2.3 cluster with a postgresql database for shared jboss messaging datastore.  When the second node is started, I see errors in the log like the second node is trying to recreate the messaging database tables.

       

      2011-01-18 18:04:55,891 DEBUG [org.jboss.messaging.core.impl.JDBCSupport] Failed to execute: CREATE TABLE JBM

      _DUAL (DUMMY INTEGER, PRIMARY KEY (DUMMY))

      org.postgresql.util.PSQLException: ERROR: relation "jbm_dual" already exists

              at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)

              at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795)

              at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)

              at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)

              at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:353)

              at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:299)

              at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:249)

              at org.jboss.messaging.core.impl.JDBCSupport.createSchema(JDBCSupport.java:301)

              at org.jboss.messaging.core.impl.JDBCSupport.start(JDBCSupport.java:167)

              at org.jboss.messaging.core.impl.JDBCPersistenceManager.start(JDBCPersistenceManager.java:149)

              at org.jboss.messaging.core.jmx.JDBCPersistenceManagerService.startService(JDBCPersistenceManagerServ

      ice.java:100)

              at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)

              at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)

              at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)

              at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)

              at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

              at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java

      :142)

      ....

       

      Similar errors are repeated for all the tables and user inserts.

       

       

      This seems to me like a problem, but as near as I can tell things seem to be working dispite the errors.  Is this error something to worry about?  Is there a configuration which will prevent the second node from trying to recreate the tables which already exist?