[AC-1258] NODE.acs app starting twice when i deploy to cloud

GitHub Issue	n/a
Type	Bug
Priority	n/a
Status	Closed
Resolution	Cannot Reproduce
Resolution Date	2014-08-10T08:07:39.000+0000
Affected Version/s	n/a
Fix Version/s	n/a
Components	n/a
Labels	TCSupport
Reporter	Peter Ladis
Assignee	Mauro Parra-Miranda
Created	2014-07-26T13:48:29.000+0000
Updated	2016-03-08T07:37:39.000+0000

Description

07/26/2014 08:40:020.651 [INFO] [4136] ------------ Run MVC App ------------ You specified a Timezone but have not included the time module. Timezone functionality is disabled. Please install the time module to use Timezones in your application. info: socket.io started 07/26/2014 08:40:022.458 [INFO] [4136] Counter: 1 07/26/2014 08:40:022.554 [INFO] [4136] App started 07/26/2014 08:41:007.810 [INFO] [12055] ------------ Run MVC App ------------ You specified a Timezone but have not included the time module. Timezone functionality is disabled. Please install the time module to use Timezones in your application. info: socket.io started 07/26/2014 08:41:009.596 [INFO] [12055] Counter: 1 07/26/2014 08:41:009.695 [INFO] [12055] App started

Comments

Mauro Parra-Miranda 2014-07-30

Hello! I just tested with a simple testcase (printing the date of start every time) and looks good:

   07/30/2014 00:28:019.300 [INFO] [4702] ------------ Run MVC App ------------
   info: socket.io started
   07/30/2014 00:28:019.502 [INFO] [4702] Current Time: Wed Jul 30 2014 00:28:19 GMT-0400 (EDT)
   07/30/2014 00:28:019.517 [INFO] [4702] App started
   [PERF]  GET / 8 ms
   [PERF]  GET / 2 ms
   [PERF]  GET / 1 ms
   [PERF]  GET / - ms

Do you mind to rerun your testcase and report back? Thanks!

Mauro Parra-Miranda 2014-08-10

Tested with 3.3.0.GA, works fine.
Shin Suzuki 2014-09-24

I ran into the same problem. I guess this problem is due to some servers (AWS) and independent from codes on them. Thus, it shouldn't be closed just because one environment couldn't reproduce it. In my case, one-or-two-week running on cloud made this problem. I think frequent access to the server is also needed to reproduce this, as this problem might be related to AWS scaling or something... Replacing my code with the initial code produced by "acs new" also reproduced this problem.

JSON Source