Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
is usergrid even being developed anymore? Looking at the check ins it seems like the support has fallen off. On Thu, Dec 7, 2017 at 7:24 AM, Jaskaran Singh wrote: > Usergrid (master branch) requires certain tables to be present in > Cassandra "before" starting tomcat. We solved this with the following > workaround for new installations: > Step 1: Setup a usergrid installation with a previous version of usergrid > (example v2.1.0) > Step 2: Run the database setup, database bootstrap and superuser setup > commands > Step 3: Stop tomcat > Step 4: In Tomcat, replace the ROOT.war (used in step 1) with the ROOT.war > compiled from the master branch of usergrid. > > Alternatively, for existing installations you just need to directly > perform step 4. > > On 4 April 2017 at 14:49, Jaskaran Singh comprotechnologies.com> wrote: > >> There is a JIRA for the issue as well: >> https://issues.apache.org/jira/browse/USERGRID-1321 >> >> >> On Tue, Apr 4, 2017 at 2:44 PM, Ganaraj Tejasvi >> wrote: >> >>> Yes. Same issue even now. >>> >>> On Tue, Apr 4, 2017 at 2:41 PM, Jaskaran Singh < >>> jaskaran.si...@comprotechnologies.com> wrote: >>> Hi Ganaraj, we were not able to get this to work. Have you tried with the latest master ? On Tue, Apr 4, 2017 at 1:25 PM, Ganaraj Tejasvi wrote: > Hi, > > Was this problem with usergrid resolved. If it was resolved could you > let me know what was the solution to the problem > > -- > Regards > Ganaraj Tejasvi > >>> >>> >>> -- >>> Regards >>> Ganaraj Tejasvi >>> >> >> >
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
Usergrid (master branch) requires certain tables to be present in Cassandra "before" starting tomcat. We solved this with the following workaround for new installations: Step 1: Setup a usergrid installation with a previous version of usergrid (example v2.1.0) Step 2: Run the database setup, database bootstrap and superuser setup commands Step 3: Stop tomcat Step 4: In Tomcat, replace the ROOT.war (used in step 1) with the ROOT.war compiled from the master branch of usergrid. Alternatively, for existing installations you just need to directly perform step 4. On 4 April 2017 at 14:49, Jaskaran Singh < jaskaran.si...@comprotechnologies.com> wrote: > There is a JIRA for the issue as well: > https://issues.apache.org/jira/browse/USERGRID-1321 > > > On Tue, Apr 4, 2017 at 2:44 PM, Ganaraj Tejasvi > wrote: > >> Yes. Same issue even now. >> >> On Tue, Apr 4, 2017 at 2:41 PM, Jaskaran Singh < >> jaskaran.si...@comprotechnologies.com> wrote: >> >>> Hi Ganaraj, we were not able to get this to work. Have you tried with >>> the latest master ? >>> >>> >>> On Tue, Apr 4, 2017 at 1:25 PM, Ganaraj Tejasvi >>> wrote: >>> Hi, Was this problem with usergrid resolved. If it was resolved could you let me know what was the solution to the problem -- Regards Ganaraj Tejasvi >>> >>> >> >> >> -- >> Regards >> Ganaraj Tejasvi >> > >
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
There is a JIRA for the issue as well: https://issues.apache.org/jira/browse/USERGRID-1321 On Tue, Apr 4, 2017 at 2:44 PM, Ganaraj Tejasvi wrote: > Yes. Same issue even now. > > On Tue, Apr 4, 2017 at 2:41 PM, Jaskaran Singh comprotechnologies.com> wrote: > >> Hi Ganaraj, we were not able to get this to work. Have you tried with the >> latest master ? >> >> >> On Tue, Apr 4, 2017 at 1:25 PM, Ganaraj Tejasvi >> wrote: >> >>> Hi, >>> >>> Was this problem with usergrid resolved. If it was resolved could you >>> let me know what was the solution to the problem >>> >>> -- >>> Regards >>> Ganaraj Tejasvi >>> >> >> > > > -- > Regards > Ganaraj Tejasvi >
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
Hi Ganaraj, we were not able to get this to work. Have you tried with the latest master ? On Tue, Apr 4, 2017 at 1:25 PM, Ganaraj Tejasvi wrote: > Hi, > > Was this problem with usergrid resolved. If it was resolved could you let > me know what was the solution to the problem > > -- > Regards > Ganaraj Tejasvi >
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
Hi Krzysztof, We are also facing the same issue. The Master branch from 2nd September commit SHA: 9fae8037a4b881e9c13a5a1f23f71dc34e950c40 does 'not' have this issue. This version of the master works well for us, and once the issue gets resolved we will pull the latest master. Regards Jaskaran On Wed, Nov 2, 2016 at 3:35 AM, Krzysztof Mesek wrote: > I've build usergrid using the master branch today and have the same > problem. Cassandra 2.2.8, the same error in log. Does this problem still > exist? > > -- > "nie skarby są przyjaciółmi, ale przyjaciele skarbami" >
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
Hi Michael, just checking if there was any update on this issue. thanks Jaskaran On Fri, Oct 7, 2016 at 1:37 PM, Jaskaran Singh < jaskaran.si...@comprotechnologies.com> wrote: > Hi Michael, > > I have attached our Usegrid configuration (usergrid-deployment.properties). > Please let me know if you need any other information. > > Thanks for the help. > Jaskaran > > On Thu, Oct 6, 2016 at 11:02 PM, Michael Russo > wrote: > >> I just tested fresh installation from Master branch and it worked fine >> actually. Can you provide your Usergrid configuration? Maybe there's a >> different configuration other than the default that triggers this. >> >> On Wed, Oct 5, 2016 at 10:29 PM, Jaskaran Singh < >> jaskaran.si...@comprotechnologies.com> wrote: >> >>> Thanks Michael. >>> >>> On Thu, Oct 6, 2016 at 10:44 AM, Michael Russo >>> wrote: >>> Had a deeper look ( thanks for the log snippet, it helped). I think we have a small bug in org/apache/usergrid/persistenc e/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.si...@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 > 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 : " >> http://localhost:8080/system/database/setup"; >> curl -i -X PUT -u : " >> 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: 77d2026907b03625ad7e1ef742c865 >>> 6712497c8d). >>> 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)
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
Hi Michael, I have attached our Usegrid configuration (usergrid-deployment.properties). Please let me know if you need any other information. Thanks for the help. Jaskaran On Thu, Oct 6, 2016 at 11:02 PM, Michael Russo wrote: > I just tested fresh installation from Master branch and it worked fine > actually. Can you provide your Usergrid configuration? Maybe there's a > different configuration other than the default that triggers this. > > On Wed, Oct 5, 2016 at 10:29 PM, Jaskaran Singh comprotechnologies.com> wrote: > >> Thanks Michael. >> >> On Thu, Oct 6, 2016 at 10:44 AM, Michael Russo >> wrote: >> >>> Had a deeper look ( thanks for the log snippet, it helped). I think we >>> have a small bug in org/apache/usergrid/persistenc >>> e/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.si...@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 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 : " > http://localhost:8080/system/database/setup"; > curl -i -X PUT -u : " > 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 miss
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
I just tested fresh installation from Master branch and it worked fine actually. Can you provide your Usergrid configuration? Maybe there's a different configuration other than the default that triggers this. On Wed, Oct 5, 2016 at 10:29 PM, Jaskaran Singh < jaskaran.si...@comprotechnologies.com> wrote: > Thanks Michael. > > On Thu, Oct 6, 2016 at 10:44 AM, Michael Russo > wrote: > >> Had a deeper look ( thanks for the log snippet, it helped). I think we >> have a small bug in org/apache/usergrid/persistenc >> e/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.si...@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 >>> 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 : " http://localhost:8080/system/database/setup"; curl -i -X PUT -u : " 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 > >>> >> >
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
Thanks Michael. On Thu, Oct 6, 2016 at 10:44 AM, Michael Russo 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 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 >> 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 : " >>> http://localhost:8080/system/database/setup"; >>> curl -i -X PUT -u : " >>> 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 >>> >>> >> >
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
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.si...@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.corepersistence.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.DefaultListableBeanFactory@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 > 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 : " >> http://localhost:8080/system/database/setup"; >> curl -i -X PUT -u : " >> 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 >>> >> >> >
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
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.corepersistence.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.DefaultListableBeanFactory@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 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 : " > http://localhost:8080/system/database/setup"; > curl -i -X PUT -u : "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 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: 9fae8037a4b881e9c13a5a1f23f71dc34e950c40). >> >> 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 >> > >
Re: Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
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 : " http://localhost:8080/system/database/setup"; curl -i -X PUT -u : " 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: 9fae8037a4b881e9c13a5a1f23f71dc34e950c40). > > 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 >
Usergrid 2.2 (Master Branch, 1 October) - Startup fails in Tomcat
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: 9fae8037a4b881e9c13a5a1f23f71dc34e950c40). 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
