Base code of Sessa web service.

[prasanthhs]

@Muzammil1234's Sessa code put into a new branch due to search being an older branch with code differences from master.

• Some timeout error and load balancing problem needs to be checked.

[RicardoUsbeck]

How can I start the SESSA app to test the that it runs and actually does what it is supposed to do?

[prasanthhs]

@RicardoUsbeck Sessa can be started by normal procedure(@Muzammil1234 checked in some code to Sessa WS under sessa_webservice branch). Other option is that sessa running in our vm as a docker,the same can be used to check.

[RicardoUsbeck]

After starting SESSA locally, I get the following error on command line after entering "Berlin" into the chat interface, see file. log_sessa_18.12.2017.txt

[prasanthhs]

@RicardoUsbeck Couple of things : First chatbot has to be started before web client can run(Because zuul internally gets the port of chatbot from eureka during run time). Hence the below error

Caused by: com.netflix.client.ClientException: Load balancer does not have available server for client: chatbot

Sometimes, we get either timeout error or load balance related error when using MacBook terminal, especially in re-runs on same terminal. Currently we have to check as to why it happens. The only workaround for this issue we have at the moment is to open a new terminal and restart web client after chatbot is running.

[guruprasads7]

Hi Ricardo,

We have setup a docker registry in our VM but with unsigned certificates.

Add the below snippet to /etc/docker/demon.json and restart the docker service

{ "insecure-registries" : ["project-group-search- extraction.cs.uni-paderborn.de:5000"] }

Then you can pull the sessa image using:

docker pull project-group-search-extraction.cs.uni-paderborn. de:5000/sessa:17122017 to check the image

And run the sessa docker using :

docker run -d --name sessa -p 7070:7070 project-group-search-extraction.cs.uni-paderborn.de:5000/sessa:17122017

Please let us know, if you have some issues while starting sessa,

Thanks, Guru

On Mon, Dec 18, 2017 at 4:36 PM, Ricardo Usbeck notifications@github.com wrote:

[image: image] https://user-images.githubusercontent.com/4354740/34113883-781a1fb0-e411-11e7-9995-9df025ab52bb.png How can I start the SESSA app to test the that it runs and actually does what it is supposed to do?

— You are receiving this because your review was requested. Reply to this email directly, view it on GitHub https://github.com/dice-group/sask/pull/17#issuecomment-352462585, or mute the thread https://github.com/notifications/unsubscribe-auth/AHcXu1I2aPfH_0ANJYq8GjJ2qgARhW3Cks5tBoZigaJpZM4RFjdH .

[prasanthhs]

For your reference!

[RicardoUsbeck]

Okay, so here are two potential issues: 1) A microservice is always independent of other microservices, so please get rid of the connection between the webclient and the chatbot before the pull request is merged. https://martinfowler.com/articles/microservices.html 2) SESSA can be successfully started from command line without docker. It is nice to know that there is a docker container and even a docker registry on the VM, however that was kind of not agreed upon. You start building your own shadow infrastructure which in the long term can lead to unrepeatable bugs and a very messy infrastructure. https://en.wikipedia.org/wiki/Shadow_IT

[prasanthhs]

@RicardoUsbeck I have added some change to the configuration file and the issue doesn't occur on my PC now atleast(tried a few combinations and also a few retries). Can you check if its the case at your end as well?