August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-221) Port previous changes from jboss-jsf-api_spec pom.xml to the jboss-jakarta-faces-api pom.xml file

by Farah Juma (Jira)

Farah Juma created JBEE-221: ------------------------------- Summary: Port previous changes from jboss-jsf-api_spec pom.xml to the jboss-jakarta-faces-api pom.xml file Key: JBEE-221 URL: https://issues.jboss.org/browse/JBEE-221 Project: JBoss Enterprise Spec APIs Issue Type: Task Components: jboss-jsf-api Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.5#713005)

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: ----------------------------------- Good news! I was able to build JGroups myself with Ant. Both issues are resolved - my application properly shuts down, and, the intermittent NullPointerExceptions no longer occur with the succession of lock, unlock, and lock. Thanks. > 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.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-220) Annotations api repo includes a root pom.xml and spec/pom.xml

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/JBEE-220?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on JBEE-220: --------------------------------------- Here's the trick Alessio mentioned: https://github.com/resteasy/Resteasy/blob/master/testsuite/pom.xml#L54 > Annotations api repo includes a root pom.xml and spec/pom.xml > ------------------------------------------------------------- > > Key: JBEE-220 > URL: https://issues.jboss.org/browse/JBEE-220 > Project: JBoss Enterprise Spec APIs > Issue Type: Bug > Components: jboss-annotations-api > Affects Versions: jboss-jakarta-jacc-api_spec-2.0.0.CR1 > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > Get rid of https://github.com/bstansberry/jboss-jakarta-annotations-api_spec/blob/2.... and https://github.com/bstansberry/jboss-jakarta-annotations-api_spec/blob/2.... > We don't want to risk that anything other than the 'api' with the JBoss maven GA gets released. > [~asoldano] in chat mentioned a possibility of leaving the pom but somehow disabling releases, which is also a possible solution. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-218) Jakarta Concurrency Javadocs should have original Eclipse Foundation footer

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/JBEE-218?page=com.atlassian.jira.plugin.s... ] Eduardo Martins resolved JBEE-218. ---------------------------------- Fix Version/s: jboss-jakarta-concurrency-api-2.0.0.CR1 Resolution: Done > Jakarta Concurrency Javadocs should have original Eclipse Foundation footer > --------------------------------------------------------------------------- > > Key: JBEE-218 > URL: https://issues.jboss.org/browse/JBEE-218 > Project: JBoss Enterprise Spec APIs > Issue Type: Bug > Components: jboss-javaee-concurrency-api > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: jboss-jakarta-concurrency-api-2.0.0.CR1 > > > The original javadoc plugin config should be restored, so the proper Eclipse Foundation footer is kept in the fork's javadoc -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-217) Add LICENSE to Jakarta API artifact

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/JBEE-217?page=com.atlassian.jira.plugin.s... ] Eduardo Martins resolved JBEE-217. ---------------------------------- Fix Version/s: jboss-jakarta-concurrency-api-2.0.0.CR1 Resolution: Done > Add LICENSE to Jakarta API artifact > ----------------------------------- > > Key: JBEE-217 > URL: https://issues.jboss.org/browse/JBEE-217 > Project: JBoss Enterprise Spec APIs > Issue Type: Enhancement > Components: jboss-javaee-concurrency-api > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: jboss-jakarta-concurrency-api-2.0.0.CR1 > > > The root LICENSE.md file should be included in the built artifact. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-215) Jakarta Concurrency API Manifest Setup

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/JBEE-215?page=com.atlassian.jira.plugin.s... ] Eduardo Martins resolved JBEE-215. ---------------------------------- Fix Version/s: jboss-jakarta-concurrency-api-2.0.0.CR1 Resolution: Done > Jakarta Concurrency API Manifest Setup > -------------------------------------- > > Key: JBEE-215 > URL: https://issues.jboss.org/browse/JBEE-215 > Project: JBoss Enterprise Spec APIs > Issue Type: Enhancement > Components: jboss-javaee-concurrency-api > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: jboss-jakarta-concurrency-api-2.0.0.CR1 > > > The MANIFEST file for the Jakarta Concurrency API fork should be configured similar to what was done to Java EE Concurrency API fork, see https://github.com/jboss/jboss-javaee-concurrency-api_spec/blob/master/po... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-216) Cleanup Jakarta Concurrency API maven plugin management and executions

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/JBEE-216?page=com.atlassian.jira.plugin.s... ] Eduardo Martins resolved JBEE-216. ---------------------------------- Fix Version/s: jboss-jakarta-concurrency-api-2.0.0.CR1 Resolution: Done > Cleanup Jakarta Concurrency API maven plugin management and executions > ---------------------------------------------------------------------- > > Key: JBEE-216 > URL: https://issues.jboss.org/browse/JBEE-216 > Project: JBoss Enterprise Spec APIs > Issue Type: Enhancement > Components: jboss-javaee-concurrency-api > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: jboss-jakarta-concurrency-api-2.0.0.CR1 > > > There are several maven plugins not needed to be managed and/or executed when building Jakarta Concurrency, which adds unnecessary dependencies and/or conflicts with JBoss Parent definitions. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-220) Annotations api repo includes a root pom.xml and spec/pom.xml

by Brian Stansberry (Jira)

Brian Stansberry created JBEE-220: ------------------------------------- Summary: Annotations api repo includes a root pom.xml and spec/pom.xml Key: JBEE-220 URL: https://issues.jboss.org/browse/JBEE-220 Project: JBoss Enterprise Spec APIs Issue Type: Bug Components: jboss-annotations-api Affects Versions: jboss-jakarta-jacc-api_spec-2.0.0.CR1 Reporter: Brian Stansberry Assignee: Yeray Borges Get rid of https://github.com/bstansberry/jboss-jakarta-annotations-api_spec/blob/2.... and https://github.com/bstansberry/jboss-jakarta-annotations-api_spec/blob/2.... We don't want to risk that anything other than the 'api' with the JBoss maven GA gets released. [~asoldano] in chat mentioned a possibility of leaving the pom but somehow disabling releases, which is also a possible solution. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4631) Create tests for Elytron syslog reconnect attempts

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4631?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4631: ---------------------------------- Summary: Create tests for Elytron syslog reconnect attempts (was: Create tests for Elytron syslog reconnectsh) > Create tests for Elytron syslog reconnect attempts > -------------------------------------------------- > > Key: WFCORE-4631 > URL: https://issues.jboss.org/browse/WFCORE-4631 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: James Perkins > Priority: Major > > WFCORE-4394 currently has some tests which will be disabled for this. It's likely some integration tests will need to be done instead of unit tests. ELY-1864 is going to change the way the reconnect attempts are done resulting in the current unit tests failing. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4631) Create tests for Elytron syslog reconnectsh

by James Perkins (Jira)

James Perkins created WFCORE-4631: ------------------------------------- Summary: Create tests for Elytron syslog reconnectsh Key: WFCORE-4631 URL: https://issues.jboss.org/browse/WFCORE-4631 Project: WildFly Core Issue Type: Task Components: Security Reporter: James Perkins WFCORE-4394 currently has some tests which will be disabled for this. It's likely some integration tests will need to be done instead of unit tests. ELY-1864 is going to change the way the reconnect attempts are done resulting in the current unit tests failing. -- This message was sent by Atlassian Jira (v7.13.5#713005)

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