February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11704) Support -Ddebug for clustering testsuite

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11704?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-11704: ---------------------------------- Priority: Minor (was: Major) > Support -Ddebug for clustering testsuite > ---------------------------------------- > > Key: WFLY-11704 > URL: https://issues.jboss.org/browse/WFLY-11704 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 15.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > This has been broken for a while now; there are still traces of properties such as {{as.debug.port.node3}} but never set. > * What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server with specific ports, i.e. ports. > * However, {{suspend=y}} need to be used reasonably, since this makes for an arduous debugging session. > * Probably one server could be picked up for debugging. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11704) Support -Ddebug for clustering testsuite

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11704?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-11704: ---------------------------------- Description: This has been broken for a while now; there are still traces of properties such as {{as.debug.port.node3}} but never set. * What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server with specific ports, i.e. ports. * However, {{suspend=y}} need to be used reasonably, since this makes for an arduous debugging session. * Probably one server could be picked up for debugging. * Moreover, timeouts should probably be heavily increased not to timeout very quickly. was: This has been broken for a while now; there are still traces of properties such as {{as.debug.port.node3}} but never set. * What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server with specific ports, i.e. ports. * However, {{suspend=y}} need to be used reasonably, since this makes for an arduous debugging session. * Probably one server could be picked up for debugging. > Support -Ddebug for clustering testsuite > ---------------------------------------- > > Key: WFLY-11704 > URL: https://issues.jboss.org/browse/WFLY-11704 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 15.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > This has been broken for a while now; there are still traces of properties such as {{as.debug.port.node3}} but never set. > * What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server with specific ports, i.e. ports. > * However, {{suspend=y}} need to be used reasonably, since this makes for an arduous debugging session. > * Probably one server could be picked up for debugging. > * Moreover, timeouts should probably be heavily increased not to timeout very quickly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11704) Support -Ddebug for clustering testsuite

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11704?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-11704: ---------------------------------- Description: This has been broken for a while now; there are still traces of properties like as.debug.port.node3 but never set. * What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server with specific ports, i.e. ports. * However, {{suspend=y}} need to be used reasonably, since this makes for an arduous debugging session. * Probably one server could be picked up for debugging. was: This has been broken for a while now; there are still traces of properties like as.debug.port.node3 but never set. What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server with specific ports. > Support -Ddebug for clustering testsuite > ---------------------------------------- > > Key: WFLY-11704 > URL: https://issues.jboss.org/browse/WFLY-11704 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 15.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > This has been broken for a while now; there are still traces of properties like as.debug.port.node3 but never set. > * What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server with specific ports, i.e. ports. > * However, {{suspend=y}} need to be used reasonably, since this makes for an arduous debugging session. > * Probably one server could be picked up for debugging. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11704) Support -Ddebug for clustering testsuite

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-11704: ------------------------------------- Summary: Support -Ddebug for clustering testsuite Key: WFLY-11704 URL: https://issues.jboss.org/browse/WFLY-11704 Project: WildFly Issue Type: Task Components: Clustering, Test Suite Affects Versions: 15.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar This has been broken for a while now; there are still traces of properties like as.debug.port.node3 but never set. What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server with specific ports. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11604) Non-anonymous principal is not propagated from EJB context to CDI bean

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11604?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFLY-11604: ----------------------------------------- [~manovotn] Are you Ok for me to take a look into this one? > Non-anonymous principal is not propagated from EJB context to CDI bean > ---------------------------------------------------------------------- > > Key: WFLY-11604 > URL: https://issues.jboss.org/browse/WFLY-11604 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Security > Affects Versions: 14.0.1.Final, 15.0.1.Final > Reporter: Nikoleta Žiaková > Assignee: Matej Novotny > Priority: Critical > > This is a follow-up on WFLY-11587 which only dealt with being able to inject the principal. > However, during testing I have tried a scenario when the caller principal was not anonymous (run-as-principal setting in jboss-ejb3.xml). See the test case in this [commit|https://github.com/nziakova/wildfly/commit/9ae586ad0159e6399f65103...]. > The principal is not propagated from the EJB context. The result is that injected principal in the CDI bean is always anonymous, although {{ctx.getCallerPrincipal()}} in the EJB returns correct principal. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3046) FileKeystore is hard to use with non-file-based keystores

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-3046?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-3046. -------------------------------------- Assignee: Darran Lofthouse Resolution: Rejected The WildFly Elytron subsystem allows key stores to be loaded and filtered without the same assumptions in the legacy security realms. > FileKeystore is hard to use with non-file-based keystores > --------------------------------------------------------- > > Key: WFCORE-3046 > URL: https://issues.jboss.org/browse/WFCORE-3046 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Jan Pazdziora > Assignee: Darran Lofthouse > Priority: Major > > We are implementing JCA KeyStore provider to get certificates and keys via external process over the network: > https://github.com/latchset/custodia-jca-provider > However, code in https://github.com/wildfly/wildfly-core/blob/master/domain-management/src... makes use of such code hard. > It seems that FileKeystore has two modes of operation -- either alias is specified and then the KeyStore is treated as file (isKeyStore = true) which has to exist and it has to be able to list aliases, or the file is not required to exist (isKeyStore = false) but then alias cannot be specified (and if it is specified as alias attribute to <keystore> element, it is ignored). > In case we'd like to be able to use our provider without additional configuration in java.security, we'd like to be able to specify alias to retrieve specified entry, especially since getting the list of aliases might be either slow (for large sets) or not possible. For that however, we need to go the isKeyStore = true route with path specified and file existing. Alas, when we try > <ssl> > <keystore provider="custodia-cli" path="/dev/null" alias="wildfly/server-ssl" keystore-password="thepassword" /> > </ssl> > then due to the extra check in WildFly's code, startup fails with > Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYDM0083: The KeyStore /dev/null does not contain any keys. > at org.jboss.as.domain.management.security.FileKeystore.assertContainsKey(FileKeystore.java:169) > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:120) > at org.jboss.as.domain.management.security.FileKeyManagerService.loadKeyStore(FileKeyManagerService.java:189) > Please consider removing the > if (isKeyStore) { > assertContainsKey(loadedKeystore); > } > code from https://github.com/wildfly/wildfly-core/blob/master/domain-management/src... since existence of the keystore file does not guarantee that the keys will be stored in it and that the provider will be able to loop through them. The file might be just /dev/null or some config file of the provider. > Ideally though, it should be possible to specify alias even for keystore which has no path specified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3680) WFLYJMX0037 occurs with RBAC enabled when disconnecting JConsole

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-3680?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-3680. -------------------------------------- Fix Version/s: 8.0.0.Beta4 Resolution: Done > WFLYJMX0037 occurs with RBAC enabled when disconnecting JConsole > ---------------------------------------------------------------- > > Key: WFCORE-3680 > URL: https://issues.jboss.org/browse/WFCORE-3680 > Project: WildFly Core > Issue Type: Bug > Components: JMX, Remoting, Security > Reporter: Bartosz Baranowski > Assignee: Richard Opalka > Priority: Major > Labels: downstream_dependency > Fix For: 8.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11703) remote-cache-container resource is missing transaction configuration

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-11703: ----------------------------------- Summary: remote-cache-container resource is missing transaction configuration Key: WFLY-11703 URL: https://issues.jboss.org/browse/WFLY-11703 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 15.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Users need to be able to specify whether the hotrod client should be transactional. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2327) UNICAST3: create receiver table when non-first message is received first

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/JGRP-2327?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on JGRP-2327: -------------------------------------- [~belaban] What's the affected version here please? Just master for now? > UNICAST3: create receiver table when non-first message is received first > ------------------------------------------------------------------------ > > Key: JGRP-2327 > URL: https://issues.jboss.org/browse/JGRP-2327 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.17 > > > * A and B > * B sends 2 messages to A: B1 and B2 > * A receives B2 _before_ B1 (both B1 and B2 are OOB) > * The current code has A drop B2 and send a SEND_FIRST_SEQNO message to B > * B resends B1, but _not_ B2 > * Retransmission needs to kick in before A receives B2. This might take up to {{xmit_interval * 2}} ms before B2 is retransmitted and delivered > h4. Scenario (JGRP-2293): > * A installs a new view > * B sends a LEAVE-REQ to A (B is leaving, too) on the view installation and a VIEW-ACK for the view. Both messages are unicasts to A and OOB > * The VIEW-ACK (B2) is received first and dropped, so it will have to be retransmitted > * This delays the view installation, as A waits for {{view_ack_collection_timeout}} ms until it has received all VIEW-ACKs > h4. Workaround > * Set GMS.leave_timeout to a higher value (say 8000ms) > h4. Solution > * When B2 is received, and it is not the first message and we don't have a receiver table for B yet, investigate whether we can create the receiver table anyway > * However, this requires the first seqno from B *to always be 0* > --> Investigate whether the first seqno in UNICAST3 is always 0, then this solution will work -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11622) Multiple delivery group support for MDBs

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11622?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-11622: ----------------------------------- [~mnovak] Yeah, we need the mentioned upgrade before they can pass > Multiple delivery group support for MDBs > ---------------------------------------- > > Key: WFLY-11622 > URL: https://issues.jboss.org/browse/WFLY-11622 > Project: WildFly > Issue Type: Feature Request > Components: EJB, JMS > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > > Add support for multiple delivery groups in the same MDB. > For info on delivery groups, see https://docs.jboss.org/author/display/WFLY10/Message+Driven+Beans+Control... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2019