brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aleds...@apache.org
Subject [1/2] brooklyn-docs git commit: Adds troubleshooting for chrome “waiting for available socket”
Date Wed, 31 Aug 2016 22:03:47 GMT
Repository: brooklyn-docs
Updated Branches:
  refs/heads/master 8086ff155 -> 25a6f5945


Adds troubleshooting for chrome “waiting for available socket”

Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/89bf56d5
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/89bf56d5
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/89bf56d5

Branch: refs/heads/master
Commit: 89bf56d5a4119d6451b272c70142ab83c2c8080e
Parents: 8086ff1
Author: Aled Sage <aled.sage@gmail.com>
Authored: Wed Aug 31 22:25:05 2016 +0100
Committer: Aled Sage <aled.sage@gmail.com>
Committed: Wed Aug 31 22:25:05 2016 +0100

----------------------------------------------------------------------
 guide/ops/troubleshooting/index.md              |  1 +
 guide/ops/troubleshooting/web-console-issues.md | 23 ++++++++++++++++++++
 2 files changed, 24 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/89bf56d5/guide/ops/troubleshooting/index.md
----------------------------------------------------------------------
diff --git a/guide/ops/troubleshooting/index.md b/guide/ops/troubleshooting/index.md
index 436cd84..f373537 100644
--- a/guide/ops/troubleshooting/index.md
+++ b/guide/ops/troubleshooting/index.md
@@ -3,6 +3,7 @@ title: Troubleshooting
 layout: website-normal
 children:
 - { path: overview.md, title: Overview }
+- { path: web-console-issues.md, title: Web Console Issues }
 - { path: deployment.md, title: Deployment }
 - { path: connectivity.md, title: Server Connectivity }
 - { path: slow-unresponsive.md, title: Brooklyn Slow or Unresponsive }

http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/89bf56d5/guide/ops/troubleshooting/web-console-issues.md
----------------------------------------------------------------------
diff --git a/guide/ops/troubleshooting/web-console-issues.md b/guide/ops/troubleshooting/web-console-issues.md
new file mode 100644
index 0000000..56c0ddc
--- /dev/null
+++ b/guide/ops/troubleshooting/web-console-issues.md
@@ -0,0 +1,23 @@
+---
+layout: website-normal
+title: Web Console Issues
+toc: /guide/toc.json
+---
+
+## Page Does Not Load in Chrome, Saying ""Waiting for available socket..."
+
+If you find that the Web Console does not load in Chrome (giving a message "Waiting for available

+socket..."), there are two possible explanations.
+
+The first reason is that another tab for the same host:port has a login dialog that is prompting
 
+for a username and password. This will block other tabs that are also trying to connect.
The 
+solution is to login at the first tab, or to close that tab.
+
+A second possible reason is that there are too many open connections in Chrome to that domain.

+There is a limit in Chrome for the number of open socket connections to a given domain. If
this
+is exceeded, subsequent tabs that try to connect will wait for an available socket.
+
+For more information, see 
+[http://stackoverflow.com/questions/23679968/chrome-hangs-after-certain-amount-of-data-transfered-waiting-for-available-soc](http://stackoverflow.com/questions/23679968/chrome-hangs-after-certain-amount-of-data-transfered-waiting-for-available-soc).
+
+[chrome://net-internals/#sockets](chrome://net-internals/#sockets) is also a useful diagnostic
tool.


Mime
View raw message