Ah ok, now is a bit clearer, thanks :)
If application starts is good, I suggested better hardware because 2GB
are, maybe, the lower bound for memory.
Abou t the exceptions, they are too generic, I cannot give you a precise
answer on what could be the reason of your problem.
Please check also
Hi ,
Thanks for your reply
Sorry for the confusion.
We are using debian release of Syncope and for database, we have connected
syncope to AWS' RDS postgreSQL DB.
>From the exception, it doesn't looks issue is because of shortage memory (
not getting exception when do alloc). Do you still
Hi Mohit,
Il 10/03/2017 08:48, Mohit Agrawal ha scritto:
Hi Andrea ,
Yes i have deployed it on single machine (just for testing our
application), i am using the standalone version on tomcat 9 . Yes ,
after restart it works.
How is it possible that you're using tomcat 9? The newest
Hi Andrea ,
Yes i have deployed it on single machine (just for testing our
application), i am using the standalone version on tomcat 9 . Yes , after
restart it works.
Do you think , this issue is related to memory (no space) ?
our machine configuration is t2.medium in AWS (2 core, 2 GB RAM)
Hi ,
We are seeing frequent syncope stuck (say after 2 days) in our testing.
When we try to use authenticate API ( /users/self ) , we are seeing
exception in the syncope logs. Could you please help us to identify what
could be issue ? I have attached syncope log with this email. I have
attached
