You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by aledsage <gi...@git.apache.org> on 2016/08/31 21:26:15 UTC
[GitHub] brooklyn-docs pull request #103: Adds troubleshooting for chrome “waiting ...
GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-docs/pull/103
Adds troubleshooting for chrome \u201cwaiting for available socket\u201d
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-docs troubleshooting-for-chrome-waiting-for-socket
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-docs/pull/103.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #103
----
commit 89bf56d5a4119d6451b272c70142ab83c2c8080e
Author: Aled Sage <al...@gmail.com>
Date: 2016-08-31T21:25:05Z
Adds troubleshooting for chrome \u201cwaiting for available socket\u201d
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-docs pull request #103: Adds troubleshooting for chrome “waiting ...
Posted by aledsage <gi...@git.apache.org>.
Github user aledsage commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/103#discussion_r77082151
--- Diff: 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..."
--- End diff --
I'm not sure if Karaf has anything to do with it, except that maybe folk have additional WARs running in Karaf that use web-sockets so will consume a socket.
I think the main issue (for me at least) is the login dialog being open in a different tab.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-docs pull request #103: Adds troubleshooting for chrome “waiting ...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/brooklyn-docs/pull/103
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-docs issue #103: Adds troubleshooting for chrome “waiting for ava...
Posted by aledsage <gi...@git.apache.org>.
Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-docs/pull/103
Merging now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-docs issue #103: Adds troubleshooting for chrome “waiting for ava...
Posted by bostko <gi...@git.apache.org>.
Github user bostko commented on the issue:
https://github.com/apache/brooklyn-docs/pull/103
LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-docs pull request #103: Adds troubleshooting for chrome “waiting ...
Posted by bostko <gi...@git.apache.org>.
Github user bostko commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/103#discussion_r77079761
--- Diff: 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..."
--- End diff --
Worth's adding, it is reproduceable when running under karaf.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---