[JBoss JIRA] (SWSQE-594) Jenkins Jobs Hung
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-594?page=com.atlassian.jira.plugin.... ]
Filip Brychta commented on SWSQE-594:
-------------------------------------
Exception from previous comment is probably not relevant, it was visible even before the upgrade:
Feb 10, 2019 1:41:20 AM hudson.TcpSlaveAgentListener$ConnectionHandler run
WARNING: Connection #7511 failed
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:197)
at java.io.DataInputStream.readFully(DataInputStream.java:169)
at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242)
> Jenkins Jobs Hung
> -----------------
>
> Key: SWSQE-594
> URL: https://issues.jboss.org/browse/SWSQE-594
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Matt Mahoney
> Assignee: Filip Brychta
> Priority: Major
> Attachments: image-2019-02-11-16-35-41-783.png
>
>
> Jenkins jobs hung in the following state:
> !image-2019-02-11-16-35-41-783.png|thumbnail!
> After nearly 30 min, restarting the Jenkins service cleared the issue and the jobs ran fine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (SWSQE-594) Jenkins Jobs Hung
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-594?page=com.atlassian.jira.plugin.... ]
Filip Brychta commented on SWSQE-594:
-------------------------------------
There is also following error where the # of connections is increasing, maybe some pool gets full with incorrectly closed connections?
Feb 11, 2019 1:33:52 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (1/100): jenkins-slave-kiali-ui-tests-vxltp
Feb 11, 2019 1:33:53 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
WARNING: Connection #181 failed
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:197)
at java.io.DataInputStream.readFully(DataInputStream.java:169)
at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:244)
Feb 11, 2019 1:33:53 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
INFO: Accepted JNLP4-connect connection #182 from /10.16.23.44:41946
> Jenkins Jobs Hung
> -----------------
>
> Key: SWSQE-594
> URL: https://issues.jboss.org/browse/SWSQE-594
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Matt Mahoney
> Assignee: Filip Brychta
> Priority: Major
> Attachments: image-2019-02-11-16-35-41-783.png
>
>
> Jenkins jobs hung in the following state:
> !image-2019-02-11-16-35-41-783.png|thumbnail!
> After nearly 30 min, restarting the Jenkins service cleared the issue and the jobs ran fine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (SWSQE-594) Jenkins Jobs Hung
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-594?page=com.atlassian.jira.plugin.... ]
Filip Brychta commented on SWSQE-594:
-------------------------------------
Working scenario looks like this:
Feb 11, 2019 4:26:41 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
INFO: Excess workload after pending Kubernetes agents: 1
Feb 11, 2019 4:26:41 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
INFO: Template for label python3&&kiali-rest-tests: Kubernetes Pod Template
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: --> GET https://b22.jonqe.lab.eng.bos.redhat.com:8443/api/v1/namespaces/jenkins-s... http/1.1
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: Authorization: Bearer dCQTu4OLfQougsTTTAlLDaYErPShtStPgdg8AiPKH7g
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: Host: b22.jonqe.lab.eng.bos.redhat.com:8443
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: Connection: Keep-Alive
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: Accept-Encoding: gzip
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: User-Agent: okhttp/3.9.1
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: --> END GET
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: <-- 200 OK https://b22.jonqe.lab.eng.bos.redhat.com:8443/api/v1/namespaces/jenkins-s... (10ms)
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: Cache-Control: no-store
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: Content-Type: application/json
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: Date: Mon, 11 Feb 2019 21:26:41 GMT
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: Content-Length: 142
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO:
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: {"kind":"PodList","apiVersion":"v1","metadata":{"selfLink":"/api/v1/namespaces/jenkins-slaves/pods","resourceVersion":"54607963"},"items":[]}
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: <-- END HTTP (142-byte body)
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: --> GET https://b22.jonqe.lab.eng.bos.redhat.com:8443/api/v1/namespaces/jenkins-s... http/1.1
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: Authorization: Bearer dCQTu4OLfQougsTTTAlLDaYErPShtStPgdg8AiPKH7g
Feb 11, 2019 4:26:41 PM okhttp3.internal.platform.Platform log
INFO: Host: b22.jonqe.lab.eng.bos.redhat.com:8443
> Jenkins Jobs Hung
> -----------------
>
> Key: SWSQE-594
> URL: https://issues.jboss.org/browse/SWSQE-594
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Matt Mahoney
> Assignee: Filip Brychta
> Priority: Major
> Attachments: image-2019-02-11-16-35-41-783.png
>
>
> Jenkins jobs hung in the following state:
> !image-2019-02-11-16-35-41-783.png|thumbnail!
> After nearly 30 min, restarting the Jenkins service cleared the issue and the jobs ran fine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (SWSQE-594) Jenkins Jobs Hung
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-594?page=com.atlassian.jira.plugin.... ]
Filip Brychta commented on SWSQE-594:
-------------------------------------
Problem started with this exception:
Feb 11, 2019 3:53:01 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
INFO: Excess workload after pending Kubernetes agents: 1
Feb 11, 2019 3:53:01 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
INFO: Template for label python3&&kiali-rest-tests: Kubernetes Pod Template
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: --> GET https://b22.jonqe.lab.eng.bos.redhat.com:8443/api/v1/namespaces/jenkins-s... http/1.1
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: Authorization: Bearer MFljxQA42Qvm2IZtUkWryYR4s1-bQJP9j4N5ibtWkU4
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: Host: b22.jonqe.lab.eng.bos.redhat.com:8443
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: Connection: Keep-Alive
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: Accept-Encoding: gzip
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: User-Agent: okhttp/3.9.1
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: --> END GET
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: <-- 401 Unauthorized https://b22.jonqe.lab.eng.bos.redhat.com:8443/api/v1/namespaces/jenkins-s... (4ms)
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: Cache-Control: no-store
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: Content-Type: application/json
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: Date: Mon, 11 Feb 2019 20:53:01 GMT
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: Content-Length: 129
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO:
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}
Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log
INFO: <-- END HTTP (129-byte body)
Feb 11, 2019 3:53:01 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
WARNING: Failed to count the # of live instances on Kubernetes
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://b22.jonqe.lab.eng.bos.redhat.com:8443/api/v1/namespaces/jenkins-s.... Message: Unauthorized. Received status: Status(apiVersion=v1, code=401, details=null, kind=Status, message=Unauthorized, metadata=ListMeta(_continue=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Unauthorized, status=Failure, additionalProperties={}).
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:478)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:417)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:381)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:344)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:328)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.listRequestHelper(BaseOperation.java:193)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:618)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:68)
at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:505)
at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:458)
at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715)
at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320)
at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61)
at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72)
at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
> Jenkins Jobs Hung
> -----------------
>
> Key: SWSQE-594
> URL: https://issues.jboss.org/browse/SWSQE-594
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Matt Mahoney
> Assignee: Filip Brychta
> Priority: Major
> Attachments: image-2019-02-11-16-35-41-783.png
>
>
> Jenkins jobs hung in the following state:
> !image-2019-02-11-16-35-41-783.png|thumbnail!
> After nearly 30 min, restarting the Jenkins service cleared the issue and the jobs ran fine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-10319) NameBinding annotations on resources are ignored in subresources
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-10319?page=com.atlassian.jira.plugin... ]
Marek Kopecký commented on WFLY-10319:
--------------------------------------
[~jestevezsanchez], [~ron_sigal] Have you repored this to the jaxrs-spec group? Clear explanation in jax-rs next spec would be useful.
[~ron_sigal]: No objections for closing (based on dev decision) this jira.
> NameBinding annotations on resources are ignored in subresources
> ----------------------------------------------------------------
>
> Key: WFLY-10319
> URL: https://issues.jboss.org/browse/WFLY-10319
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 12.0.0.Final
> Reporter: Javier Estevez Sanchez
> Assignee: Alessio Soldano
> Priority: Major
>
> The following JAX-RS resource exposes two resources via a GET operation: /demo and /demo/subresource. The first one via a sub-resource method, the latter via a sub-resource locator. Additionally, a response filter is binded to the JAX-RS resource class to modify the response. From the JAX-RS 2.0 spec, §6.5.2 Name Binding:
> {quote}
> Binding annotations that decorate resource classes apply to all resource methods defined in them.
> {quote}
> However, the binding annotation is not applying to the sub-resource locator method. This happens when the name binding annotation is on the resource class or on the sub-resource locator method. Annotating the sub-resource class or the method within works as expected, though.
> Below is the code needed to reproduce this issue:
> {code:java|title=The resource and subresource}
> @DemoNameBinding
> @Produces(MediaType.APPLICATION_JSON)
> @Path("/demo")
> public class DemoResource {
> @GET
> public String getDemoValue() {
> return "A value";
> }
> @Path("/subresource")
> public DemoSubResource getSubResource() {
> return new DemoSubResource();
> }
> public class DemoSubResource {
> @GET
> public String getDemoValue() {
> return "A value";
> }
> }
> }
> {code}
> {code:java|title=The filter}
> @Provider
> @DemoNameBinding
> public class SomeFilter implements ContainerResponseFilter {
> @Override
> public void filter(ContainerRequestContext requestContext, ContainerResponseContext responseContext) {
> responseContext.setEntity("A filtered value");
> }
> }
> {code}
> {code:java|title=The binding}
> @NameBinding
> @Target({ElementType.TYPE, ElementType.METHOD})
> @Retention(RetentionPolicy.RUNTIME)
> public @interface DemoNameBinding {
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11696) Remove ParameterCorrector added for WFLY-11617
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11696:
---------------------------------------
Summary: Remove ParameterCorrector added for WFLY-11617
Key: WFLY-11696
URL: https://issues.jboss.org/browse/WFLY-11696
Project: WildFly
Issue Type: Task
Components: JMS
Reporter: Brian Stansberry
Assignee: ehsavoie Hugonnet
See https://github.com/wildfly/wildfly/pull/12020 for discussion. For compatibility reasons we added a ParameterCorrector as part of the WFLY-11617 fix. But really that results in the server ignoring invalid input, which is a bug. That's the right thing to do for a while, as a form of "bug deprecation notice" but eventually we should cut the code size, get rid of the corrector, and require the user to provide a valid value.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11695) Remove ParameterCorrector added for WFLY-11617
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11695:
---------------------------------------
Summary: Remove ParameterCorrector added for WFLY-11617
Key: WFLY-11695
URL: https://issues.jboss.org/browse/WFLY-11695
Project: WildFly
Issue Type: Task
Components: JMS
Reporter: Brian Stansberry
Assignee: ehsavoie Hugonnet
See https://github.com/wildfly/wildfly/pull/12020 for discussion. For compatibility reasons we added a ParameterCorrector as part of the WFLY-11617 fix. But really that results in the server ignoring invalid input, which is a bug. That's the right thing to do for a while, as a form of "bug deprecation notice" but eventually we should cut the code size, get rid of the corrector, and require the user to provide a valid value.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (SWSQE-594) Jenkins Jobs Hung
by Matt Mahoney (Jira)
Matt Mahoney created SWSQE-594:
----------------------------------
Summary: Jenkins Jobs Hung
Key: SWSQE-594
URL: https://issues.jboss.org/browse/SWSQE-594
Project: Kiali QE
Issue Type: Bug
Reporter: Matt Mahoney
Assignee: Filip Brychta
Attachments: image-2019-02-11-16-35-41-783.png
Jenkins jobs hung in the following state:
!image-2019-02-11-16-35-41-783.png|thumbnail!
After nearly 30 min, restarting the Jenkins service cleared the issue and the jobs ran fine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11535) Cluster fails to merge if instances started simultaneously
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11535?page=com.atlassian.jira.plugin... ]
Radoslav Husar resolved WFLY-11535.
-----------------------------------
Fix Version/s: 16.0.0.Beta1
Assignee: Radoslav Husar (was: Paul Ferraro)
Resolution: Done
Resolving for 16.0.0.Beta1 since JGroups 4.0.16.Final which resolves the issue is already merged via WFLY-11449.
> Cluster fails to merge if instances started simultaneously
> ----------------------------------------------------------
>
> Key: WFLY-11535
> URL: https://issues.jboss.org/browse/WFLY-11535
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.0.Final
> Environment: Keycloak 4.6.0 official docker image, AWS ECS cluster
> Reporter: Ian Rodgers
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 16.0.0.Beta1
>
> Attachments: Dockerfile, docker-entrypoint.sh, entrypoint.sh, standalone-ha.xml, standalone-ha.xml
>
>
> Our Keycloak docker cluster has four instances, clustered using Jgroups/Infinispan as per the standalone-ha.xml. If you start them all simultaneously the "Receive new cluster" logs indicate four separate clusters, each with a single member. They never get merged into the proper single cluster of four members. It seems to be the merging that has changed. The application then fails (we are not using sticky sessions, and each member is ignorant of the sessions on the other members).
> We can only start the cluster by first starting one instance, then when it is running, starting the other three. The logs then indicate the creation of a single cluster which subsequent instances join.
> This is consistent behaviour, and when we revert back to v.4.5.0, the issue goes away, Unfortunately we need 4.6.0 for an important fix.
> On 4.5.0 we get the message "Received new, MERGED cluster view for channel ejb: MergeView::" when it detects a number of subgroups to merge. This never appears in 4.6.0.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months