[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: F.CN installation

Hello Det,

I have never ran demo server with option ` -Ddemoserver.provision=false` as
it might be telling the service not to provision any tenant. Try using

For the `io.mifos.provisioner.api.v1.client.DuplicateIdentifierException`,
you might want to delete the seshat and playground databases after each
run. Whenever you forget to clean the DB, this error occurs.

I think we need to do better with making provisioner to reuse an existing
tenant and config DB on every rerun. Maybe this was an architectural

Make sure host ActiveMQ is not running too.


On Fri, Apr 13, 2018 at 2:48 PM, Det Prest <detp007@xxxxxxxxx> wrote:

> Hi
> Really hoping someone can help.
> I have followed the instructions in the wiki and hit a wall due to a
> maven/javamoney problem fortunately Awusum Kannick was nice enough to
> provide a link to an older 0.9 javamoney lib repo which enabled me to build
> each repo successfully with artifacts showing up in .m2.
> I ran *`java -Ddemoserver.provision=false -Ddemoserver.persistent=true
> -Dcustom.cassandra.contactPoints= <>
> -Dcassandra.cluster.user=cassandra
> -Dcassandra.cluster.pwd=password
> -Dcustom.mariadb.user=root -Dcustom.mariadb.password=mysql -jar
> demo-server-0.1.0-BUILD-SNAPSHOT.jar *
> and all microservices started without errors!! When i tried to run the web
> app with npm i and npm run dev I received a Node-Sass error at which point
> I decided to go to bed (4:30am) (Switched of PC) Woke up installed
> node-sass, built web app without errors and tried to login
>    1.  Incorrect password. I assumed I needed run the demoserver again
>    2. Ran the demoserver like above:
> There was 1 failure:
> 1) startDevServer(
> io.mifos.provisioner.api.v1.client.DuplicateIdentifierException
> Prior I am also getting on all services.
> [DefaultMessageListenerContainer-1] ERROR
> o.s.j.l.DefaultMessageListenerContainer - Could not refresh JMS Connection
> for destination 'accounting-v1' - retrying using
> FixedBackOff{interval=5000, currentAttempts=0, maxAttempts=unlimited}.
> Cause: Error while attempting to add new Connection to the pool; nested
> exception is javax.jms.JMSException: Could not connect to broker URL:
> tcp://localhost:61616. Reason: Connection
> refused (Connection refused)
> *This leads me to my questions. *
>    1. *How do I resolve this error?*
>    2. *Once installed what is the correct procedure for start up and shut
>    down?Power outages are regular occurrence*
> Thanks for the help!
> *Det*