it's up to you how many servers to have It should be 0+ On Wed, Oct 21, 2015 at 9:12 PM, Bhushan Patil <[email protected]> wrote:
> > > On Tuesday 20 October 2015 08:37 PM, Maxim Solodovnik wrote: > > The issue is here: > > <property name="serverId" value="10.1.2.2" /> > > according to the comments serverId is the DB ID of the server > So you need to > 1) install OM on single machine > 2) go to admin > 3) create 2 servers (ID will be 1 and 2 on clean machine) > 4) perform set up of cluster > > You mean, in this case, I will need 3 systems to perform clustering ? > So, I am going to try following. I will have 3 system, say A (10.1.2.1), B > (10.1.2.2), C (10.1.2.3). > > 1. Install database on machine A (whose IP is 10.1.2.1) > 2. Install OM on machine A. > 3. Will go to admin of A and create 2 servers(whose id will be 1 n 2 > respectively. and their IPs will 10.1.2.2, 10.1.2.3 respectively). > 4. Will extract OM on system B and C. > 5. Will modify the files persistence.xml and > openmeetings-applicationContext.xml of B and C as per the > documentation. > 1. On system B > > <property name="serverId" value="1" /> > > <property name="openjpa.RemoteCommitProvider" > value="tcp(Addresses=10.1.1.2;10.1.1.3)" /> > > 2. On system C > > <property name="serverId" value="2" /> > > <property name="openjpa.RemoteCommitProvider" > value="tcp(Addresses=10.1.1.2;10.1.1.3)" /> > > 6. Will ran ./red5.sh on system B n C and complete installation. > > Please tell me if this approach is correct or not and thanks for your > guidance. > > > On Mon, Oct 19, 2015 at 2:13 PM, Bhushan Patil <[email protected]> > wrote: > >> I want to do clustering on OpenMeeting-3.0.7. I have two >> machines(10.1.2.2 and 10.1.2.3). 10.1.2.2 have database Postgres installed >> on it. >> I did the following >> >> 1. Extracted apache-openmeetings-3.0.7.tar.gz on 10.1.2.2. >> 2. Changed following properties in persistence.xml and >> openmeetings-applicationContext.xml >> respectively. >> >> <property name="serverId" value="10.1.2.2" /> >> >> <property name="openjpa.RemoteCommitProvider" >> value="tcp(Addresses=10.1.1.2;10.1.1.3)" /> >> >> 3. >> >> Ran ./red5.sh and installed OpenMeetings successfully. >> >> 4. >> >> Extracted apache-openmeetings-3.0.7.tar.gz on 10.1.2.3. >> >> 5. >> >> Changed following properties in persistence.xml and >> openmeetings-applicationContext.xml respectively. >> <property name="serverId" value="10.1.2.3" /> >> <property name="openjpa.RemoteCommitProvider" >> value="tcp(Addresses=10.1.1.2;10.1.1.3)" /> >> >> 6. Now when I ran ./red5.sh, i got following error. >> >> Installation is failed >> >> org.springframework.dao.DataIntegrityViolationException: The >> transaction has been rolled back. See the nested exceptions for details >> on >> the errors that occurred.; nested exception is >> <openjpa-2.4.0-r422266:1674604 fatal store error> >> org.apache.openjpa.persistence.EntityExistsException: The transaction has >> been rolled back. See the nested exceptions for details on the errors >> that >> occurred. >> FailedObject: >> org.apache.openmeetings.db.entity.basic.Configuration@3d65f054 >> at >> >> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:407) >> at >> >> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:122) >> at >> >> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:521) >> at >> >> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:757) >> at >> >> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:726) >> at >> >> org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:521) >> at >> >> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:291) >> at >> >> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) >> at >> >> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) >> at >> >> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653) >> at >> >> org.apache.openmeetings.db.dao.basic.ConfigurationDao$$EnhancerBySpringCGLIB$$2b956ef0.add(<generated>) >> at >> >> org.apache.openmeetings.installation.ImportInitvalues.loadConfiguration(ImportInitvalues.java:283) >> at >> >> org.apache.openmeetings.installation.ImportInitvalues.loadSystem(ImportInitvalues.java:714) >> at >> >> org.apache.openmeetings.installation.ImportInitvalues.loadAll(ImportInitvalues.java:726) >> at >> >> org.apache.openmeetings.web.pages.install.InstallWizard$InstallProcess.run(InstallWizard.java:616) >> at java.lang.Thread.run(Thread.java:745) >> Caused by: <openjpa-2.4.0-r422266:1674604 fatal store error> >> org.apache.openjpa.persistence.EntityExistsException: The transaction has >> been rolled back. See the nested exceptions for details on the errors >> that >> occurred. >> FailedObject: >> org.apache.openmeetings.db.entity.basic.Configuration@3d65f054 >> at >> >> org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2368) >> at >> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2205) >> at >> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:2103) >> at >> >> org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:2021) >> at >> >> org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:81) >> at >> org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java:1526) >> at >> >> org.apache.openjpa.kernel.DelegatingBroker.commit(DelegatingBroker.java:932) >> at >> >> org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:569) >> at >> >> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:517) >> ... 13 more >> Caused by: <openjpa-2.4.0-r422266:1674604 fatal store error> >> org.apache.openjpa.persistence.EntityExistsException: ERROR: duplicate key >> value violates unique constraint "u_cnfgrtn_conf_key" >> Detail: Key (conf_key)=(crypt_ClassName) already exists. {prepstmnt >> 55686682 INSERT INTO configuration (comment_field, conf_key, conf_value, >> deleted, starttime, updatetime, user_id) VALUES (?, ?, ?, ?, ?, ?, ?)} >> [code=0, state=23505] >> FailedObject: >> org.apache.openmeetings.db.entity.basic.Configuration@3d65f054 >> at >> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4986) >> at >> >> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4961) >> at >> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:133) >> at >> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:75) >> at >> >> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:144) >> at >> >> org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:79) >> at >> >> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:100) >> at >> >> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:88) >> at >> >> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:550) >> at >> >> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:106) >> at >> >> org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59) >> at >> >> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:104) >> at >> >> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:77) >> at >> >> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:731) >> at >> >> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131) >> at >> >> org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:668) >> at >> >> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131) >> ... 21 more >> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: ERROR: >> duplicate key value violates unique constraint "u_cnfgrtn_conf_key" >> Detail: Key (conf_key)=(crypt_ClassName) already exists. {prepstmnt >> 55686682 INSERT INTO configuration (comment_field, conf_key, conf_value, >> deleted, starttime, updatetime, user_id) VALUES (?, ?, ?, ?, ?, ?, ?)} >> [code=0, state=23505] >> at >> >> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:218) >> at >> >> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:194) >> at >> >> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:58) >> at >> >> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1133) >> at >> >> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:275) >> at >> >> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:275) >> at >> >> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:275) >> at >> >> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:268) >> at >> >> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:119) >> ... 33 more >> >> >> >> > > > -- > WBR > Maxim aka solomax > > > -- WBR Maxim aka solomax
