Sorry -- left out a detail:  The *first* time you run the demo server
you'll need to run it with provision, otherwise the services won't...
be provisioned.  But after that, it will be provisioned.

Best Regards,
Myrle

On Mon, Apr 16, 2018 at 9:33 PM, Myrle Krantz <my...@apache.org> wrote:
> Hey Det,
>
> This is possible.  You just need to set the property
> demoserver.persistent and *not* set the property
> "demoserver.provision".
>
> Best Regards,
> Myrle
>
> On Mon, Apr 16, 2018 at 6:36 PM, Det Prest <detp...@gmail.com> wrote:
>> Hi Yannick
>> Sorry for the Typo.
>>
>> Thanks for the assistance, will try again later in the week.
>>
>> Regarding making provisioner to reuse an existing
>> tenant and config DB on every rerun, I think this is a good idea especially
>> in development stage. Maybe a rudimentary Startup Shutdown script can be
>> written.
>> Thanks again for the assistance.
>>
>> Regard
>> David
>>
>>
>> On Fri, Apr 13, 2018 at 9:43 PM, Awasum Yannick <awa...@apache.org> wrote:
>>
>>> 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
>>> -Ddemoserver.provision=true.
>>>
>>> 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
>>> decision.
>>>
>>> Make sure host ActiveMQ is not running too.
>>>
>>>
>>> Thanks
>>> Awasum
>>>
>>> On Fri, Apr 13, 2018 at 2:48 PM, Det Prest <detp...@gmail.com> 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=127.0.0.1:9042 <http://127.0.0.1:9042>
>>> > -Dcassandra.cluster.user=cassandra
>>> > -Dcassandra.cluster.pwd=password -Dcustom.mariadb.host=localhost
>>> > -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.dev.ServiceRunner)
>>> > 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: java.net.ConnectException: 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*
>>> >
>>>

Reply via email to