Thanks Michael. On Thu, Oct 6, 2016 at 10:44 AM, Michael Russo <michaelaru...@gmail.com> wrote:
> Had a deeper look ( thanks for the log snippet, it helped). I think we > have a small bug in org/apache/usergrid/persistence/collection/exception/ > CollectionRuntimeException.java:60. Basically in the latest Master > branch, we've started to move some of the database code over to the > Datastax CQL driver from Astyanax. Because of this, the error messages > thrown from each of those is different and this is getting missed. I'll be > able to have a look further tomorrow 10/6 and fix in Master. I'll reply > back after I've verified the problem, and subsequently fixed it. > > Thanks. > -Michael > > On Wed, Oct 5, 2016 at 7:24 AM, Jaskaran Singh <jaskaran.singh@ > comprotechnologies.com> wrote: > >> Hi Michael, >> >> Thank you for your response. With the latest Usergrid 2.2.0 (Master >> branch from 1 October, SHA:77d2026907b03625ad7e1ef742c8656712497c8d), >> the ROOT war does not get loaded / deployed properly in Tomcat, due to >> startup errors (see below). Due to this we’re unable to call the “setup” >> and “bootstrap” curl calls, as mentioned in your mail. >> >> ------------------------------------------------------------ >> -------------------------------------- >> INFO ShutdownListener:59 - ShutdownListener invoked >> >> SEVERE: Error listenerStart >> >> Caused by: org.springframework.beans.BeanInstantiationException: Could >> not instantiate bean class [org.apache.usergrid.corepersi >> stence.CpEntityManagerFactory]: Constructor threw exception; nested >> exception is java.lang.RuntimeException: Unable to get management app after >> 101 retries >> >> ERROR ContextLoader:331 - Context initialization failed >> >> INFO DefaultListableBeanFactory:444 - Destroying singletons in >> org.springframework.beans.factory.support.DefaultListableBea >> nFactory@58548b9f: defining beans [queueJob,org.springframework. >> context.annotation.internalConfigurationAnnotationProcessor,..... >> >> InvalidRequestException(why:unconfigured table Data_Migration_Info) >> ERROR CpEntityManagerFactory:302 - 1: Error (BadRequestException) Unable >> to connect to cassandra to retrieve status >> >> InvalidRequestException(why:unconfigured table Data_Migration_Info) >> ERROR CpEntityManagerFactory:360 - Error getting entity manager >> com.google.common.util.concurrent.UncheckedExecutionException: >> java.lang.RuntimeException: Error getting application >> b6768a08-b5d5-11e3-a495-11ddb1de66c8 >> ------------------------------------------------------------ >> -------------------------------------- >> >> Please suggest if we are missing something. >> >> Thanks >> Jaskaran >> >> >> On Wed, Oct 5, 2016 at 8:51 AM, Michael Russo <michaelaru...@gmail.com> >> wrote: >> >>> In fresh, first-time deployments of Usergrid to a new database and >>> Elasticsearch cluster, you need to invoke the database setup and bootstrap >>> APIs: >>> >>> curl -i -X PUT -u <sysadmin user>:<sysadmin pass> " >>> http://localhost:8080/system/database/setup"; >>> curl -i -X PUT -u <sysadmin user>:<sysadmin pass> " >>> http://localhost:8080/system/database/bootstrap"; >>> >>> After starting tomcat and running the above curl commands, it should set >>> up the schema and bootstrap the system. >>> >>> Thanks. >>> -Michael R. >>> >>> >>> On Tue, Oct 4, 2016 at 3:22 AM, Jaskaran Singh < >>> jaskaran.si...@comprotechnologies.com> wrote: >>> >>>> Hello Usergrid Team, >>>> >>>> Our application works with Usergrid 1.0.2, 2.1.0 and 2.2.0 (Master >>>> branch from 2nd September commit SHA: 9fae8037a4b881e9c13a5a1f23f71d >>>> c34e950c40). >>>> >>>> Now, we tried testing our application with the latest 2.2.0 (Master >>>> branch from 1 October SHA: 77d2026907b03625ad7e1ef742c8656712497c8d). >>>> But during deployment/startup of Tomcat, we are getting the following >>>> error (with fresh Cassandra + ES environments). >>>> >>>> BadRequestException: InvalidRequestException(why:unconfigured table >>>> Data_Migration_Info) >>>> Caused by: java.lang.RuntimeException: Unable to connect to cassandra >>>> to retrieve status >>>> >>>> We checked and found that the connection to cassandra is fine. This >>>> error does 'not' come in previous versions of Usergrid (1.0.2, 2.1.0 and >>>> 2.2.0 - Master branch from 2nd September) >>>> I wanted to check if i am missing something? Please advise. >>>> >>>> Thanks >>>> Jaskaran >>>> >>> >>> >> >
