[jbosstools-issues] [JBoss JIRA] (JBIDE-22005) Log console: Unexpected EOF in pod log

[Fred Bricon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon updated JBIDE-22005:
--------------------------------
    Story Points: 1
          Sprint: devex #113 April 2016


> Log console: 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
>            Assignee: Jeff Cantrill
>            Priority: Critical
>              Labels: openshift_v3
>             Fix For: 4.4.0.Alpha2
>
>
> 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}
> ...
> 09: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 at 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?labelSelector=application%3Deap-app]]
> 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 block user from checking pod log once it reach a specific length.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)