August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4453) Test Scenario: empty values in collection should be always skipped

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4453: ------------------------------------- Summary: Test Scenario: empty values in collection should be always skipped Key: DROOLS-4453 URL: https://issues.jboss.org/browse/DROOLS-4453 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca See this project as reproducer https://github.com/juliaaano/temp -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12326) Move Messaging management model version to 8

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12326?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12326: ------------------------------------ Issue Type: Task (was: Feature Request) > Move Messaging management model version to 8 > -------------------------------------------- > > Key: WFLY-12326 > URL: https://issues.jboss.org/browse/WFLY-12326 > Project: WildFly > Issue Type: Task > Components: JMS > Affects Versions: 17.0.1.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 18.0.0.Beta1 > > > Update messaging subsystem model to 8 -- 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 Matt Drees (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] Matt Drees commented on WFLY-2859: ---------------------------------- [~jamezp] I think "Out of Date" isn't very accurate. The problem was fixed in resteasy, but only a few days ago. > 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] (REMJMX-167) IllegalStateException: No standard field found for reverse order comparator!

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/REMJMX-167?page=com.atlassian.jira.plugin... ] Brian Stansberry updated REMJMX-167: ------------------------------------ Description: https://github.com/jbossas/remoting-jmx/issues/41 You are also affected with: https://developer.jboss.org/thread/279791 https://issues.jboss.org/browse/WFLY-11720?focusedCommentId=13697026&page... jboss-marshalling should probably be updated. I got the same error as on those cases when I upgraded to java 11. java.lang.ExceptionInInitializerError at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335) at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54) ... Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator! at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287) ... 9 more But because I got it a few months ago (I posted it to your github, but got no responce from there) I can't provide any details on how to reproduce it. After a few days of debugging I tracked the cause down to the pre-JDK11 jboss-marshalling version you are depending on. was: https://github.com/jbossas/remoting-jmx/issues/41 You are also affected with: https://developer.jboss.org/thread/279791 https://209.132.182.82/browse/WFLY-11720?focusedCommentId=13697026&page=c... jboss-marshalling should probably be updated. I got the same error as on those cases when I upgraded to java 11. java.lang.ExceptionInInitializerError at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335) at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54) ... Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator! at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287) ... 9 more But because I got it a few months ago (I posted it to your github, but got no responce from there) I can't provide any details on how to reproduce it. After a few days of debugging I tracked the cause down to the pre-JDK11 jboss-marshalling version you are depending on. > IllegalStateException: No standard field found for reverse order comparator! > ---------------------------------------------------------------------------- > > Key: REMJMX-167 > URL: https://issues.jboss.org/browse/REMJMX-167 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 3.0.3.Final > Reporter: Andres Luuk > Priority: Major > > https://github.com/jbossas/remoting-jmx/issues/41 > You are also affected with: > https://developer.jboss.org/thread/279791 > https://issues.jboss.org/browse/WFLY-11720?focusedCommentId=13697026&page... > jboss-marshalling should probably be updated. > I got the same error as on those cases when I upgraded to java 11. > java.lang.ExceptionInInitializerError > at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335) > at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54) > ... > Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator! > at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287) > ... 9 more > But because I got it a few months ago (I posted it to your github, but got no responce from there) I can't provide any details on how to reproduce it. > After a few days of debugging I tracked the cause down to the pre-JDK11 jboss-marshalling version you are depending on. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12405) Reduce distributed web session expiration scheduler payload

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12405: ----------------------------------- Summary: Reduce distributed web session expiration scheduler payload Key: WFLY-12405 URL: https://issues.jboss.org/browse/WFLY-12405 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 17.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro If a web request is handled by a member other than the primary owner of the session, we schedule the expiration of that session on the primary owner. The command responsible for this serialized both the session ID and the meta data of the session. However, given that the primary owner will already have this information cached locally, there is no reason to include it in the payload of the scheduler command. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2274) ASYM_ENCRYPT: deprecate sign_msgs

by Nick Sawadsky (Jira)

[ https://issues.jboss.org/browse/JGRP-2274?page=com.atlassian.jira.plugin.... ] Nick Sawadsky commented on JGRP-2274: ------------------------------------- [~belaban] I understand the reasoning about putting integrity-checking in a different protocol. That would probably be more work than I could take on. But if you're open to a pull request for adding GCM support in Encrypt, I think that's something I could tackle. The goal would be to allow the mode and padding to be configured, in addition to the basic encryption algorithm (e.g. AES). I'll create an enhancement request for that and start working on the change, if you're okay with the basic idea. > ASYM_ENCRYPT: deprecate sign_msgs > --------------------------------- > > Key: JGRP-2274 > URL: https://issues.jboss.org/browse/JGRP-2274 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.12 > > > In {{ASYM_ENCRYPT}}, signing messages means that the checksum of an encrypted message is computed and used together with the secret key of the sender to sign the message. On the receiver side, the public key of the sender is used to validate the signature. > However, this is redundant, as decryption of a message will fail if the contents have been changed. > If needed, signing of messages can be done in a separate protocol. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-939) b10 did not survive outage

by Filip Brychta (Jira)

Filip Brychta created SWSQE-939: ----------------------------------- Summary: b10 did not survive outage Key: SWSQE-939 URL: https://issues.jboss.org/browse/SWSQE-939 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-938) Start all services after outage

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-938?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-938. --------------------------------- Resolution: Done Comments in the doc. > Start all services after outage > ------------------------------- > > Key: SWSQE-938 > URL: https://issues.jboss.org/browse/SWSQE-938 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Critical > Labels: infrastructure > > When the work in bos lab is done we need to start everything. > https://docs.google.com/document/d/1QRABnGYjgG9J0_QImiMPA78uL8NXmjLJbV864... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-938) Start all services after outage

by Filip Brychta (Jira)

Filip Brychta created SWSQE-938: ----------------------------------- Summary: Start all services after outage Key: SWSQE-938 URL: https://issues.jboss.org/browse/SWSQE-938 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta When the work in bos lab is done we need to start everything. https://docs.google.com/document/d/1QRABnGYjgG9J0_QImiMPA78uL8NXmjLJbV864... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-214) Update Jaspi to use JBoss parent

by Ashley Abdel-Sayed (Jira)

Ashley Abdel-Sayed created JBEE-214: --------------------------------------- Summary: Update Jaspi to use JBoss parent Key: JBEE-214 URL: https://issues.jboss.org/browse/JBEE-214 Project: JBoss Enterprise Spec APIs Issue Type: Task Components: jboss-jaspi-api Reporter: Ashley Abdel-Sayed Assignee: Ashley Abdel-Sayed This is required to be able to publish artefacts to the JBoss repo. -- 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