[JBoss JIRA] (JBIDE-22005) Unexpected EOF in pod log
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22005:
----------------------------------
Labels: openshift_v3 (was: )
> Unexpected EOF in pod log
> -------------------------
>
> Key: JBIDE-22005
> URL: https://issues.jboss.org/browse/JBIDE-22005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
>
> I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.
> Last lines from console (output of application pod log)
> {code}
> ...
> [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe...
> error: unexpected EOF
> {code}
> I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22005) Unexpected EOF in pod log
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22005:
-------------------------------------
Summary: Unexpected EOF in pod log
Key: JBIDE-22005
URL: https://issues.jboss.org/browse/JBIDE-22005
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Priority: Critical
I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.
Last lines from console (output of application pod log)
{code}
...
[0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe...
error: unexpected EOF
{code}
I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3738:
-----------------------------
Fix Version/s: 9.1.0.CR1
> Getting Started / Readme for new users after Dev Platform install is complete
> -----------------------------------------------------------------------------
>
> Key: JBDS-3738
> URL: https://issues.jboss.org/browse/JBDS-3738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 9.1.0.CR1
>
>
> Per discussion today, we need some sort of README / Getting Started Guide for new CDK users.
> This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline.
> Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3738:
-----------------------------
> Getting Started / Readme for new users after Dev Platform install is complete
> -----------------------------------------------------------------------------
>
> Key: JBDS-3738
> URL: https://issues.jboss.org/browse/JBDS-3738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 9.1.0.CR1
>
>
> Per discussion today, we need some sort of README / Getting Started Guide for new CDK users.
> This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline.
> Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3738:
-----------------------------
> Getting Started / Readme for new users after Dev Platform install is complete
> -----------------------------------------------------------------------------
>
> Key: JBDS-3738
> URL: https://issues.jboss.org/browse/JBDS-3738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 9.1.0.CR1
>
>
> Per discussion today, we need some sort of README / Getting Started Guide for new CDK users.
> This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline.
> Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3738:
-----------------------------
> Getting Started / Readme for new users after Dev Platform install is complete
> -----------------------------------------------------------------------------
>
> Key: JBDS-3738
> URL: https://issues.jboss.org/browse/JBDS-3738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
>
> Per discussion today, we need some sort of README / Getting Started Guide for new CDK users.
> This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline.
> Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years