app blocking after a period of inactivity

[laurent....@gmail.com]

Hi,

after doing some job and not refreshing or using kanbanik, when we come back using it, it stops working "failing to communicate with server" ?

Do you have an explanation/workaround ?

Many thanks for this great app !

[jel...@gmail.com]

This is interesting - I have never seen this issue and I always have it opened for the whole day (~8h).

So I need some more info:

- What version of kanbanik is doing this? 

- Where do you see this error? 

- Any error in the server's error log? 

- What web server are you using? The default from the runtime or some custom?

- What browser?

Thanx!

[laurent....@gmail.com]

Hi,

here a a few details :
- version of kanbanik = 0.2.8
- I see this error on the browser
- I have not yet investigated server's log, but I'll do so !

To complete the list :

• dockerized server (docker version 1.5.0, build a8a31ef)
• ubuntu:trusty
• tomcat7 (7.0.52-1ubuntu0.1) + mongodb (1:2.4.9-1ubuntu2) packages from ubuntu:trusty release
• java packages from ubuntu:trusty release
• version "1.7.0_79"
• OpenJDK Runtime Environment (IcedTea 2.5.5) (7u79-2.5.5-0ubuntu0.14.04.2)
• OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
  

I will now look for traces.

[jel...@gmail.com]

On Thursday, May 21, 2015 at 9:28:41 AM UTC+2, laurent....@gmail.com wrote:

Hi,

here a a few details :
- version of kanbanik = 0.2.8
- I see this error on the browser

- if you open the javascript console of your browser - anything suspicious? (in chrome in menu->more tools->javascript console)

- refresh of the page helps?

- any proxy in between which could kill the SSE connection?

- using normally the app works only the automatic updates break? (e.g. if someone moves some task you don't see it but you can move it freely)? Or also the normal usage breaks?

 

- I have not yet investigated server's log, but I'll do so !

To complete the list :

• dockerized server (docker version 1.5.0, build a8a31ef)

this sounds suspicious but maybe only because I have not too much experience with it 

[laurent....@gmail.com]

Found !

I've identified the pb.

Initially I've created only one docker container that did mongodb + tomcat + supervisor

The problem is now solved by creating one container for mongodb and another one for tomcat.

And no more supervisor that I suspect to be the root of my pb.

It now works like a champ !

No deconnection since yesterday.

[jel...@gmail.com]

On Friday, May 22, 2015 at 10:57:46 AM UTC+2, laurent....@gmail.com wrote:

Found !

I've identified the pb.

Initially I've created only one docker container that did mongodb + tomcat + supervisor

The problem is now solved by creating one container for mongodb and another one for tomcat.

And no more supervisor that I suspect to be the root of my pb.

It now works like a champ !

No deconnection since yesterday.

cool! btw keep in mind that the user sessions will expire in 8h - so don't expect to have the app opened forever...