search

gbak / stoker-web

Automatically exported from code.google.com/p/stoker-web
2 stars 1 forks source link

Random disconnects with the Stoker #19

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Stokerweb was disconnecting every few minutes and then reconnecting, it looks 
to have been not receiving telnet data points from the stoker.  watching the 
log, it paused after a string of sending messages to clients messages.  Below 
is the TRACE messages from last temp point to the reconnect. 

Can't reproduce consistently
1.  Browser push may delay telnet processing?
2.  Network problems?

What is the expected output? What do you see instead?
No pauses and reconnects.

21:51:55,917 TRACE CometMessenger:82 - sending message to browser
21:51:55,920 TRACE CometMessenger:82 - sending message to browser
21:51:56,525 TRACE StokerTelnetController:426 - t
21:51:56,526 TRACE StokerPitMonitor:188 - StokerPitMonitor:addDataPoint( 
SDataPoint )
21:51:56,527 TRACE StokerPitMonitor:250 - Debug: DeviceID: 0E0000116F0B2130
collectedTime: Fri Sep 21 21:51:56 EDT 2012
Timed Event: false

21:52:00,519 TRACE CometMessenger:82 - sending message to browser
21:52:00,522 TRACE CometMessenger:82 - sending message to browser
21:52:00,525 TRACE CometMessenger:82 - sending message to browser
21:52:00,528 TRACE CometMessenger:82 - sending message to browser
21:52:00,533 TRACE CometMessenger:82 - sending message to browser
21:52:00,535 TRACE CometMessenger:82 - sending message to browser
21:52:00,540 TRACE CometMessenger:82 - sending message to browser
21:52:00,541 TRACE CometMessenger:82 - sending message to browser
21:52:00,544 TRACE CometMessenger:82 - sending message to browser
21:52:00,547 TRACE CometMessenger:82 - sending message to browser
21:52:00,548 TRACE CometMessenger:82 - sending message to browser
21:52:00,550 TRACE CometMessenger:82 - sending message to browser
21:52:00,553 TRACE CometMessenger:82 - sending message to browser
21:52:00,554 TRACE CometMessenger:82 - sending message to browser
21:52:00,557 TRACE CometMessenger:82 - sending message to browser
21:52:08,556 DEBUG StokerTelnetController:647 - StokerTelnetController:start() 
run()
21:52:23,471 DEBUG StokerTelnetController:647 - StokerTelnetController:start() 
run()
21:52:42,737 DEBUG StokerTelnetController:647 - StokerTelnetController:start() 
run()
21:53:00,520 TRACE CometMessenger:82 - sending message to browser
21:53:00,527 TRACE CometMessenger:82 - sending message to browser
21:53:00,530 TRACE CometMessenger:82 - sending message to browser
21:53:00,533 TRACE CometMessenger:82 - sending message to browser
21:53:00,534 TRACE CometMessenger:82 - sending message to browser
21:53:00,536 TRACE CometMessenger:82 - sending message to browser
21:53:00,539 TRACE CometMessenger:82 - sending message to browser
21:53:00,540 TRACE CometMessenger:82 - sending message to browser
21:53:00,543 TRACE CometMessenger:82 - sending message to browser
21:53:00,546 TRACE CometMessenger:82 - sending message to browser
21:53:00,547 TRACE CometMessenger:82 - sending message to browser
21:53:00,555 TRACE CometMessenger:82 - sending message to browser
21:53:00,558 TRACE CometMessenger:82 - sending message to browser
21:53:00,559 TRACE CometMessenger:82 - sending message to browser
21:53:00,562 TRACE CometMessenger:82 - sending message to browser
21:53:01,528  WARN StokerTelnetController:561 - No activity from stoker in the 
last minute, attempting reconnect
21:53:01,529 DEBUG StokerTelnetController:524 - stopInternal()
21:53:01,530 TRACE CometMessenger:82 - sending message to browser
21:53:01,531 TRACE CometMessenger:82 - sending message to browser
21:53:01,535 TRACE CometMessenger:82 - sending message to browser
21:53:01,550 ERROR StokerTelnetController:463 - Reader exiting
21:53:01,554 DEBUG StokerTelnetController:647 - StokerTelnetController:start() 
run()
21:53:01,555 DEBUG StokerTelnetController:650 - StokerTelnetController:start() 
run() - calling startHelper()
21:53:01,555 DEBUG StokerTelnetController:578 - StokerTelnet .start()
21:53:01,556  INFO StokerTelnetController:156 - Creating Telnet connection.
21:53:01,582  WARN StokerTelnetController:169 - Interrupting thread
21:53:07,690 TRACE StokerTelnetController:426 - t
21:53:07,691  WARN StokerTelnetController:436 - Invalid Data Point: [Welcome to 
slush.  (Version 1.16)
]
21:53:07,791  INFO StokerTelnetController:369 - found login string
21:53:07,794 DEBUG StokerTelnetController:223 - Sent: [root
]

Original issue reported on code.google.com by gary...@gmail.com on 22 Sep 2012 at 1:28

GoogleCodeExporter commented 9 years ago 
after physically moving the stoker outside, Stoker restart but no stoker-web 
restart, the problem went away.

Original comment by gary...@gmail.com on 22 Sep 2012 at 1:29

GoogleCodeExporter commented 9 years ago 
Checked the code and the comet library does not wait to push a message to the 
client, the messages are queued.

Original comment by gary...@gmail.com on 24 Sep 2012 at 2:50

GoogleCodeExporter commented 9 years ago 
Only see this issue when two instances of stoker-web are running at the same 
time.  Have not seen this otherwise.

Original comment by gary...@gmail.com on 5 Nov 2012 at 5:17