March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1488) Fix JSONMarshaller.writeMap() check for double-wrapping for map values

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-1488?page=com.atlassian.jira.plugi... ] Edson Tirelli closed DROOLS-1488. --------------------------------- Resolution: Won't Do > Fix JSONMarshaller.writeMap() check for double-wrapping for map values > ---------------------------------------------------------------------- > > Key: DROOLS-1488 > URL: https://issues.jboss.org/browse/DROOLS-1488 > Project: Drools > Issue Type: Bug > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > The fix is the same as highlighted in the [closed PR #856|https://github.com/kiegroup/droolsjbpm-integration/pull/856]. > While the originally proposed fix is working on serialization, it posed some issues during de-serialization side, suggesting the correction cannot be a blind-fix as per original [closed PR #856|https://github.com/kiegroup/droolsjbpm-integration/pull/856]. > It is suggested to investigate further with a comprehensive test, including serialization and deserialization. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4364) Allow management audit logging to write JSON log messages to stdout

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4364?page=com.atlassian.jira.plugi... ] James Perkins moved EAP7-1225 to WFCORE-4364: --------------------------------------------- Project: WildFly Core (was: EAP 7 Planning Pilot) Key: WFCORE-4364 (was: EAP7-1225) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Logging Management (was: Logging) (was: Management) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.3.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Allow management audit logging to write JSON log messages to stdout > ------------------------------------------------------------------- > > Key: WFCORE-4364 > URL: https://issues.jboss.org/browse/WFCORE-4364 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging, Management > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Management audit logging can already log messages in JSON format. However these can only be written to a file or a syslog server. We need the ability for these messages to be written to {{stdout}}. This is useful for containers like OpenShift which consume the {{stdout}} data to feed to log aggregators. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2316) DNS_PING is not using correct ports with SRV based service discovery

by Eric Thompson (Jira)

[ https://issues.jboss.org/browse/JGRP-2316?page=com.atlassian.jira.plugin.... ] Eric Thompson commented on JGRP-2316: ------------------------------------- [~belaban] I tested this and now the logs show the correct port, but the clustering is still not working on AWS ECS. > DNS_PING is not using correct ports with SRV based service discovery > -------------------------------------------------------------------- > > Key: JGRP-2316 > URL: https://issues.jboss.org/browse/JGRP-2316 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.15 > Reporter: dmcnair > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.16 > > > This is a follow-up to JGRP-2296 - which changed `DefaultDNSResolver.java` to preserve the port for SRV records. While that change is working as desired, `DNS_PING.java` is not using the port when doing member discovery. > Here are the log entries using *4.0.15* > {noformat} > 2018-11-29 21:37:41,561 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) Entries collected from DNS (in 5 ms): [172.29.11.50:27106, 172.29.11.50:27105] > 2018-11-29 21:37:41,562 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) 982d38761cba: sending discovery requests to hosts [172.29.11.50:27106, 172.29.11.50:27105] on ports [7600 .. 7600] > {noformat} > Since the port was found via the SRV record, it should be used instead of the *transportPort* port. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11826) Upgrade Apache CXF from 3.2.7 to 3.2.9

by Ilia Vassilev (Jira)

Ilia Vassilev created WFLY-11826: ------------------------------------ Summary: Upgrade Apache CXF from 3.2.7 to 3.2.9 Key: WFLY-11826 URL: https://issues.jboss.org/browse/WFLY-11826 Project: WildFly Issue Type: Component Upgrade Components: Web Services Reporter: Ilia Vassilev Assignee: Bartosz Spyrko-Śmietanko Fix For: 16.0.0.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11826) Upgrade Apache CXF from 3.2.7 to 3.2.9

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-11826?page=com.atlassian.jira.plugin... ] Ilia Vassilev reassigned WFLY-11826: ------------------------------------ Assignee: Ilia Vassilev (was: Bartosz Spyrko-Śmietanko) > Upgrade Apache CXF from 3.2.7 to 3.2.9 > -------------------------------------- > > Key: WFLY-11826 > URL: https://issues.jboss.org/browse/WFLY-11826 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11826) Upgrade Apache CXF from 3.2.7 to 3.2.9

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-11826?page=com.atlassian.jira.plugin... ] Ilia Vassilev updated WFLY-11826: --------------------------------- Fix Version/s: (was: 16.0.0.Final) > Upgrade Apache CXF from 3.2.7 to 3.2.9 > -------------------------------------- > > Key: WFLY-11826 > URL: https://issues.jboss.org/browse/WFLY-11826 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11826) Upgrade Apache CXF from 3.2.7 to 3.2.9

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-11826?page=com.atlassian.jira.plugin... ] Ilia Vassilev updated WFLY-11826: --------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12051) > Upgrade Apache CXF from 3.2.7 to 3.2.9 > -------------------------------------- > > Key: WFLY-11826 > URL: https://issues.jboss.org/browse/WFLY-11826 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11825) CXF-7984 - UsernameTokenInterceptor doesn't respect contextual property "allowNamespaceQualifiedPasswordTypes"

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-11825?page=com.atlassian.jira.plugin... ] Ilia Vassilev moved JBEAP-16521 to WFLY-11825: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11825 (was: JBEAP-16521) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web Services (was: Web Services) Affects Version/s: 16.0.0.Final (was: 7.2.0.GA) Fix Version/s: (was: 7.2.2.GA) > CXF-7984 - UsernameTokenInterceptor doesn't respect contextual property "allowNamespaceQualifiedPasswordTypes" > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11825 > URL: https://issues.jboss.org/browse/WFLY-11825 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 16.0.0.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > allowNamespaceQualifiedPasswordTypes is not read from contextual properties before create wss4j UsernameToken. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11233) allow EntityManager caching in the JPA container

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11233?page=com.atlassian.jira.plugin... ] Scott Marlow closed WFLY-11233. ------------------------------- Resolution: Rejected Rejecting for now, reopen if this becomes important in the future. :) > allow EntityManager caching in the JPA container > ------------------------------------------------ > > Key: WFLY-11233 > URL: https://issues.jboss.org/browse/WFLY-11233 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Priority: Major > > It could be interesting to see if caching EntityManager instances (per EntityManagerFactory) could improve performance for applications, that could benefit from that. > The JPA 2.2 specification mentions the below, pay particular attention to the text "whether entity manager instances are sometimes reused" in section 7.8.2, also look at mention of [88]: > {quote} > 7.8 Requirements on the Container > 7.8.1 Application-managed Persistence Contexts > When application-managed persistence contexts are used, the container must instantiate the entity manager factory and expose it to the application via JNDI. The container might use internal APIs to create the entity manager factory, or it might use the PersistenceProvider.createContainerEntityManagerFactory method. However, the container is required to support third-party persistence providers, and in this case the container must use the PersistenceProvider.createContainerEntityManagerFactory method to create the entity manager factory and the EntityManagerFactory.close method to destroy the entity manager factory prior to shutdown (if it has not been previously closed by the application). > 7.8.2 Container Managed Persistence Contexts > The container is responsible for managing the lifecycle of container-managed persistence contexts, for injecting EntityManager references into web components and session bean and message-driven bean components, and for making EntityManager references available to direct lookups in JNDI. When operating with a third-party persistence provider, the container uses the contracts defined in section 7.9 to create and destroy container-managed persistence contexts. It is undefined whether a new entity manager instance is created for every persistence context, or whether entity manager instances are sometimes reused. Exactly how the container maintains the association between persistence context and JTA transaction is not defined. If a persistence context is already associated with a JTA transaction, the container uses that persistence context for subsequent invocations within the scope of that transaction, according to the semantics for persistence context propagation defined in section 7.6.4. > 7.9 Runtime Contracts between the Container and Persistence Provider > This section describes contracts between the container and the persistence provider for the pluggability of third-party persistence providers. Containers are required to support these pluggability contracts. [87] > 7.9.1 Container Responsibilities > For the management of a transaction-scoped persistence context, if there is no EntityManager already associated with the JTA transaction: > * The container creates a new entity manager by calling EntityManagerFactory.createEntityManager when the first invocation of an entity manager with PersistenceContextType.TRANSACTION occurs within the scope of a business method executing in the JTA transaction. > * After the JTA transaction has completed (either by transaction commit or rollback), the container closes the entity manager by calling EntityManager.close. [88] Note that the JTA transaction may rollback in a background thread (e.g., as a result of transaction timeout), in which case the container should arrange for the entity manager to be closed but the EntityManager.close method should not be concurrently invoked while the application is in an EntityManager invocation. > The container must throw the TransactionRequiredException if a transaction-scoped persistence context is used and the EntityManager persist, remove, merge, or refresh method is invoked when no transaction is active. > For stateful session beans with extended persistence contexts: > * The container creates an entity manager by calling EntityManagerFactory.createEntityManager when a stateful session bean is created that declares a dependency on an entity manager with PersistenceContextType.EXTENDED. (See section 7.6.3). > * The container closes the entity manager by calling EntityManager.close after the stateful session bean and all other stateful session beans that have inherited the same persistence context as the entity manager have been removed. > * When a business method of the stateful session bean is invoked, if the stateful session bean uses container managed transaction demarcation, and the entity manager is not already associated with the current JTA transaction, the container associates the entity manager with the current JTA transaction and, if the persistence context is of type SynchronizationType.SYNCHRONIZED, the container calls EntityManager.joinTransaction. If there is a different persistence context already associated with the JTA transaction, the container throws the EJBException. > * When a business method of the stateful session bean is invoked, if the stateful session bean uses bean managed transaction demarcation and a UserTransaction is begun within the method, the container associates the persistence context with the JTA transaction and, if the persistence context is of type SynchronizationType.SYNCHRONIZED, the container calls EntityManager.joinTransaction. > The container must throw the IllegalStateException if the application calls EntityManager.close on a container-managed entity manager. > [87] It is not required that these contracts be used when a third-party persistence provider is not used: the container might use these same APIs or its might use its own internal APIs. > [88] The container may choose to pool EntityManagers: it instead of creating and closing in each case, it may acquire one from its pool and call clear() on it. > {quote} > One challenge with introducing an entity manager (per EntityManagerFactory) cache, is knowing when to close EntityManagers after certain errors have occurred on the EntityManager. To deal with this robustness issue, we will discard entity managers that are marked close when retrieving them from the cache. To ensure that we always put the cached EM back in cache, EntityManagerCache use is only done within JTA transactions, since we have control of the release (closing) of the EntityManager and only with SynchronizationType.SYNCHRONIZED (never with SynchronizationType.UNSYNCHRONIZED) persistence contexts. > For this jira, the EntityManagerCache keeps strong references to the (cleared) EntityManager's from the cache. If this causes users OOM errors, we could consider using SOFT references so that the EntityManager's could be GCd in low memory conditions. We also offer users a choice between an unbounded cache (size=0) and a bounded cache. Users that have problems with OOM errors, should switch to a bounded cache. > Persistence unit hint "wildfly.jpa.emcache", may be: > * true, per EntityManagerFactory/persistence unit) cache that is shared between multiple threads. > * false (default), no caching is performed. > Persistence unit hint "wildfly.jpa.emcache.size", may be: > * 0 (default), the cache (if enabled) is unbounded. > * N, where N is the max number of EntityManager instances that can be placed in the EntityManagerCache, in between application use. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1761) Unicode normalization in SASL client breaks some non-ASCII passwords

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1761?page=com.atlassian.jira.plugin.s... ] Farah Juma commented on ELY-1761: --------------------------------- Checked the Plain SASL mechanism [RFC|https://tools.ietf.org/html/rfc4616#section-2], normalization is recommended but not required: {quote} The SASLPrep profile of the StringPrep algorithm is the RECOMMENDED preparation algorithm. The SASLprep preparation algorithm is not mandatory so as to allow the server to employ other preparation algorithms (including none) when appropriate. For instance, use of a different preparation algorithm may be necessary for the server to interoperate with an external system. {quote} Adding a new profile in {{StringPrep}} that skips over {{NORMALIZE_KC}} seems reasonable. A new SASL property could then be used to indicate that this new profile should be used. In particular, this would involve the following steps: # Add a new profile to {{StringPrep}} that is similar to {{PROFILE_SASL_STORED}} but does not include {{NORMALIZE_KC}}. # Add a new property to [WildFlySasl|https://github.com/wildfly-security/wildfly-elytron/blob/mast...] (e.g., something like {{SKIP_NORMALIZATION = "org.wildfly.sasl.skip-normalization"}}) that defaults to {{false}}. # Update [PlainSaslClientFactory#createSaslClient|https://github.com/wildfly-securi...] to check if {{props}} contains the new property and what its value is. Pass this to the [PlainSaslClient|https://github.com/wildfly-security/wildfly-elytron/blob/...] constructor. # Make use of this value in {{PlainSaslClient#evaluateChallenge}} to determine which {{StringPrep}} profile to use. > Unicode normalization in SASL client breaks some non-ASCII passwords > -------------------------------------------------------------------- > > Key: ELY-1761 > URL: https://issues.jboss.org/browse/ELY-1761 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Affects Versions: 1.7.0.Final > Reporter: Philippe Marschall > Priority: Major > > We have users that use U+00A8 ([diaeresis|https://en.wikipedia.org/wiki/Diaeresis_(diacritic)]) as an Active Directory password. They can not log in using the Elytron LDAP realm. Here's the sequence of events: > * PlainSaslClient.evaluateChallenge calls StringPrep.encode with the profile StringPrep.PROFILE_SASL_STORED https://github.com/wildfly-security/wildfly-elytron/blob/fd74e43caf3e7019... > * StringPrep.PROFILE_SASL_STORED ors PROFILE_SASL_QUERY which ors NORMALIZE_KC https://github.com/wildfly-security/wildfly-elytron/blob/fd74e43caf3e7019... > * StringPrep.encode then normalises using NFKC which replaces U+00A8 with U+0020 U+0308 https://github.com/wildfly-security/wildfly-elytron/blob/fd74e43caf3e7019... > * Active Directory rejects the login > We would be wiling to work on a patch but we need some guidance on the desired solution. A simple solution would be a new profile in StringPrep that doesn't normalize and is used for passwords. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019