August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-171) Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME

by Ken Wills (Jira)

[ https://issues.jboss.org/browse/WFWIP-171?page=com.atlassian.jira.plugin.... ] Ken Wills resolved WFWIP-171. ----------------------------- Resolution: Done > Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME > ------------------------------------------------------------ > > Key: WFWIP-171 > URL: https://issues.jboss.org/browse/WFWIP-171 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > Is it expected? Is this work tracked somewhere? > [1] https://github.com/jboss-container-images/jboss-eap-7-openshift-image/blo... > [2] https://github.com/luck3y/jboss-eap-7-openshift-image/blob/CLOUD-3331/tem... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-171) Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME

by Ken Wills (Jira)

[ https://issues.jboss.org/browse/WFWIP-171?page=com.atlassian.jira.plugin.... ] Ken Wills commented on WFWIP-171: --------------------------------- @mchoma Fixed in the dev branches, so moving this to resolved as well > Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME > ------------------------------------------------------------ > > Key: WFWIP-171 > URL: https://issues.jboss.org/browse/WFWIP-171 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > Is it expected? Is this work tracked somewhere? > [1] https://github.com/jboss-container-images/jboss-eap-7-openshift-image/blo... > [2] https://github.com/luck3y/jboss-eap-7-openshift-image/blob/CLOUD-3331/tem... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2299) LockService does not work correctly if unlock/lock is called in immediate succession

by David White (Jira)

[ https://issues.jboss.org/browse/JGRP-2299?page=com.atlassian.jira.plugin.... ] David White commented on JGRP-2299: ----------------------------------- Bela - I have never built the JGroups project before. I just pulled the project from Git and I see your committed fix for the stop method. Is there a particular branch that I use for a test build or just "master"? > LockService does not work correctly if unlock/lock is called in immediate succession > ------------------------------------------------------------------------------------ > > Key: JGRP-2299 > URL: https://issues.jboss.org/browse/JGRP-2299 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.15 > Environment: Windows 10 Oracle JDK 1.8 131 > AIX IBM Java 8 > Reporter: Mirko Streckenbach > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.2 > > Attachments: JGroupsExample.java, image.png, udp+lock.xml > > > In our application we have encountered occasional cases of LockService allowing 2 processes to hold the same lock at the same time. I could reproduce this with a simple program (see atttachment) and it happens if for a lock "unlock" is called and immediately afterwards "lock". If there is a small delay (e.g. 1 second) between the two operations everything works as expected. > This can be produced with the attached program. The program does lock/unlock/lock on a lock and then tries to lock the same lock from a different JChannel and is awarded the lock. If you place a small sleep() after the unlock, everything works as expected and the parallel lock is not awarded. > If you turn on debugging you'll see no output between unlock and lock, so it looks to me like the lock is awarded without passing GRANT_LOCK messages to the stack. Using a conditional break point you can see that ClientLock.acquired is still true even after the unlock(). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] James Perkins resolved WFLY-2859. --------------------------------- Resolution: Out of Date > Treating all JAX-RS components as CDI Beans has some negative consequences > -------------------------------------------------------------------------- > > Key: WFLY-2859 > URL: https://issues.jboss.org/browse/WFLY-2859 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 8.0.0.CR1, 16.0.0.Beta1 > Reporter: Matt Drees > Assignee: Stuart Douglas > Priority: Major > > It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class. > See the forum link for a specific instance of this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-171) Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME

by Ken Wills (Jira)

[ https://issues.jboss.org/browse/WFWIP-171?page=com.atlassian.jira.plugin.... ] Ken Wills commented on WFWIP-171: --------------------------------- @mchoma I've cloned this to CLOUD-3359 and opened PRs. > Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME > ------------------------------------------------------------ > > Key: WFWIP-171 > URL: https://issues.jboss.org/browse/WFWIP-171 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > Is it expected? Is this work tracked somewhere? > [1] https://github.com/jboss-container-images/jboss-eap-7-openshift-image/blo... > [2] https://github.com/luck3y/jboss-eap-7-openshift-image/blob/CLOUD-3331/tem... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-176) Pod restarted because of failing liveness/rediness Probe

by Ken Wills (Jira)

[ https://issues.jboss.org/browse/WFWIP-176?page=com.atlassian.jira.plugin.... ] Ken Wills commented on WFWIP-176: --------------------------------- [~mchoma] 7.3 more closely resembles EAP CD 17 than it does EAP 7.2, so it uses the same approach for the probes. +1 to release notes though, yes. > Pod restarted because of failing liveness/rediness Probe > -------------------------------------------------------- > > Key: WFWIP-176 > URL: https://issues.jboss.org/browse/WFWIP-176 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > During testing 73 image I came to case where really corner case is tested [0]. > Test is not using templates for deployment. > In tested scenario liveness/readiness probe fails. In CD 17 and eap 73 pod is restarted. In CD 16 however, there was no liveness/rediness failures in events. Pod was not restarted. > I dont see differences in pod yaml for CD16 case > {code} > livenessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/livenessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > name: weirdusername > readinessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/readinessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > {code} > and CD 17 case > {code} > livenessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/livenessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > name: weirdusername > readinessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/readinessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > {code} > What could cause this behaviour change? > [0] https://issues.jboss.org/browse/CLOUD-1988 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-179) Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME

by Ken Wills (Jira)

Ken Wills created WFWIP-179: ------------------------------- Summary: Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME Key: WFWIP-179 URL: https://issues.jboss.org/browse/WFWIP-179 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Ken Wills Assignee: Ken Wills Is it expected? Is this work tracked somewhere? [1] https://github.com/jboss-container-images/jboss-eap-7-openshift-image/blo... [2] https://github.com/luck3y/jboss-eap-7-openshift-image/blob/CLOUD-3331/tem... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-171) Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME

by Ken Wills (Jira)

[ https://issues.jboss.org/browse/WFWIP-171?page=com.atlassian.jira.plugin.... ] Ken Wills commented on WFWIP-171: --------------------------------- [~mchoma] This doesn't need an image update, just a PR for the templates, which I'll do right now. > Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME > ------------------------------------------------------------ > > Key: WFWIP-171 > URL: https://issues.jboss.org/browse/WFWIP-171 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > Is it expected? Is this work tracked somewhere? > [1] https://github.com/jboss-container-images/jboss-eap-7-openshift-image/blo... > [2] https://github.com/luck3y/jboss-eap-7-openshift-image/blob/CLOUD-3331/tem... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4562) Update the pre-recorded messages in CertificateAuthoritiesTestCase and KeyStoresTestCase using the latest Boulder instance

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4562?page=com.atlassian.jira.plugi... ] Farah Juma commented on WFCORE-4562: ------------------------------------ [~mkopecky] It's ready to be merged. > Update the pre-recorded messages in CertificateAuthoritiesTestCase and KeyStoresTestCase using the latest Boulder instance > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4562 > URL: https://issues.jboss.org/browse/WFCORE-4562 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Farah Juma > Assignee: Ashley Abdel-Sayed > Priority: Major > > The tests in {{CertificateAuthoritiesTestCase}} and {{KeyStoresTestCase}} simulate a mock Let's Encrypt server by using messages that were actually sent from Boulder (Let's Encrypt's testing server) to our ACME client. Wireshark was used to record the messages. The use of these recorded messages prevents us from having to integrate the complex Boulder setup into the Core testsuite. > Since these messages were pre-recorded just before the ACME protocol became an RFC, it would be good to update the pre-recorded messages used in these tests using the latest Boulder instance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4615) Eliminated deprecated WorkerService constructors

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4615: -------------------------------------- Summary: Eliminated deprecated WorkerService constructors Key: WFCORE-4615 URL: https://issues.jboss.org/browse/WFCORE-4615 Project: WildFly Core Issue Type: Enhancement Components: IO Reporter: Richard Opalka Assignee: Flavia Rainone Fix For: 10.0.0.Beta4 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2019