March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11818) wildfly-16.0.0.Final: "From address" is no more used as default from in email

by Wolfgang Mayer (Jira)

[ https://issues.jboss.org/browse/WFLY-11818?page=com.atlassian.jira.plugin... ] Wolfgang Mayer commented on WFLY-11818: --------------------------------------- I've made some more tests. The only option which seems to work is now: *message.setFrom(new InternetAddress(mySession.getProperty("mail.from")));* I still think this is not correct. But at least this can be used as workaround. > wildfly-16.0.0.Final: "From address" is no more used as default from in email > ----------------------------------------------------------------------------- > > Key: WFLY-11818 > URL: https://issues.jboss.org/browse/WFLY-11818 > Project: WildFly > Issue Type: Bug > Components: Mail > Affects Versions: 16.0.0.Final > Environment: mvn -v > Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00) > Maven home: /apps/apache-maven-3.6.0 > Java version: 11.0.2, vendor: Oracle Corporation, runtime: /usr/java/jdk-11.0.2 > Default locale: de_DE, platform encoding: UTF-8 > OS name: "linux", version: "4.12.14-lp150.12.48-default", arch: "amd64", family: "unix" > Reporter: Wolfgang Mayer > Assignee: Tomaz Cerar > Priority: Major > > As mentioned in the Help (description) of 'Mail Session' configuration: > From: *From address that is used as default from, if not set when sending* > Apparently this is not the case anymore in wildfly-16.0.0.Final. > For example I made a test with quickstart-16.0/mail/. > When omitting the line > *message.setFrom(new InternetAddress(from));* > Sending mail fails with: > com.sun.mail.smtp.SMTPSendFailedException: 554-Transaction failed > 554 Unauthorized sender address. > I have the same issue when replacing the line above with > message.setFrom(new InternetAddress()); > I am pretty sure that this is working in wildfly-15 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1716) Develop an alternative to 'wildfly-elytron-credential-source-deprecated'

by Justin Cook (Jira)

[ https://issues.jboss.org/browse/ELY-1716?page=com.atlassian.jira.plugin.s... ] Justin Cook updated ELY-1716: ----------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1249 (was: https://github.com/wildfly-security-incubator/wildfly-elytron/pull/71) > Develop an alternative to 'wildfly-elytron-credential-source-deprecated' > ------------------------------------------------------------------------ > > Key: ELY-1716 > URL: https://issues.jboss.org/browse/ELY-1716 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Justin Cook > Priority: Critical > Fix For: 1.9.0.CR1, 2.0.0.Alpha2 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1724) Develop an alternative to 'org.wildfly.security.credential.source.OAuth2CredentialSource'

by Justin Cook (Jira)

[ https://issues.jboss.org/browse/ELY-1724?page=com.atlassian.jira.plugin.s... ] Justin Cook updated ELY-1724: ----------------------------- Git Pull Request: (was: https://github.com/wildfly-security-incubator/wildfly-elytron/pull/71) > Develop an alternative to 'org.wildfly.security.credential.source.OAuth2CredentialSource' > ----------------------------------------------------------------------------------------- > > Key: ELY-1724 > URL: https://issues.jboss.org/browse/ELY-1724 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Justin Cook > Priority: Critical > Fix For: 1.9.0.CR1, 2.0.0.Alpha2 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1723) Separate auth client parsing from the API.

by Justin Cook (Jira)

[ https://issues.jboss.org/browse/ELY-1723?page=com.atlassian.jira.plugin.s... ] Justin Cook reassigned ELY-1723: -------------------------------- Assignee: Justin Cook > Separate auth client parsing from the API. > ------------------------------------------ > > Key: ELY-1723 > URL: https://issues.jboss.org/browse/ELY-1723 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Justin Cook > Priority: Blocker > Fix For: 1.9.0.CR1, 2.0.0.Alpha2 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4355) Add utility for event logging such as audit and access logging

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4355?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4355: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3700 > Add utility for event logging such as audit and access logging > -------------------------------------------------------------- > > Key: WFCORE-4355 > URL: https://issues.jboss.org/browse/WFCORE-4355 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > There are open feature requests to write audit and access logging to {{stdout}} in JSON format to be consumed by log aggregators. It would be useful to have a minimal API to handle this so that output can be standard. This should go through standard logging. -- 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 reassigned WFLY-11233: ----------------------------------- Assignee: (was: Scott Marlow) > 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] (WFLY-11818) wildfly-16.0.0.Final: "From address" is no more used as default from in email

by Wolfgang Mayer (Jira)

[ https://issues.jboss.org/browse/WFLY-11818?page=com.atlassian.jira.plugin... ] Wolfgang Mayer commented on WFLY-11818: --------------------------------------- I've now tested this with java version "1.8.0_181" and got the same error. So I guess the problem was there already before and did nor come up before any change in my environment. But the question still is why is the from user not taken from the configuration as default? Is this working in your environment? > wildfly-16.0.0.Final: "From address" is no more used as default from in email > ----------------------------------------------------------------------------- > > Key: WFLY-11818 > URL: https://issues.jboss.org/browse/WFLY-11818 > Project: WildFly > Issue Type: Bug > Components: Mail > Affects Versions: 16.0.0.Final > Environment: mvn -v > Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00) > Maven home: /apps/apache-maven-3.6.0 > Java version: 11.0.2, vendor: Oracle Corporation, runtime: /usr/java/jdk-11.0.2 > Default locale: de_DE, platform encoding: UTF-8 > OS name: "linux", version: "4.12.14-lp150.12.48-default", arch: "amd64", family: "unix" > Reporter: Wolfgang Mayer > Assignee: Tomaz Cerar > Priority: Major > > As mentioned in the Help (description) of 'Mail Session' configuration: > From: *From address that is used as default from, if not set when sending* > Apparently this is not the case anymore in wildfly-16.0.0.Final. > For example I made a test with quickstart-16.0/mail/. > When omitting the line > *message.setFrom(new InternetAddress(from));* > Sending mail fails with: > com.sun.mail.smtp.SMTPSendFailedException: 554-Transaction failed > 554 Unauthorized sender address. > I have the same issue when replacing the line above with > message.setFrom(new InternetAddress()); > I am pretty sure that this is working in wildfly-15 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3742) Implement Test scenario coverage report for DMN

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3742?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3742: ---------------------------------------- Hi [~danielezonca] I've linked a couple of JIRA that relate to this requirement. I agree with you and think that it'd be more consistent to open the DMN file and show the applicable element rather than use a popup. It is possible to pass parameters to a screen (by setting parameters on a {{PathPlaceRequest}}). This could include the {{DRGElement}} UUID that we'd then use to highlight the applicable element within the editor. > Implement Test scenario coverage report for DMN > ----------------------------------------------- > > Key: DROOLS-3742 > URL: https://issues.jboss.org/browse/DROOLS-3742 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > Use this ticket as specs > https://issues.jboss.org/browse/DROOLS-3516 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3742) Implement Test scenario coverage report for DMN

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3742?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3742: --------------------------------------- [~manstis] For DMN Scenario we should implement a mechanism to open automatically a decision in the DMN Editor and highlight the reason why a decision has been taked (for instance the row of the decision table). UX proposed to open it in a popup ( https://redhat.invisionapp.com/share/MHQTRRJYATR#/screens/349225348 ) but I don't think it is really possible. I think it could be enough to have a way to call the DMN Editor and automatically open a specific decision. Maybe it could be related to this ticket too https://issues.jboss.org/browse/DROOLS-3731 Wdyt? > Implement Test scenario coverage report for DMN > ----------------------------------------------- > > Key: DROOLS-3742 > URL: https://issues.jboss.org/browse/DROOLS-3742 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > Use this ticket as specs > https://issues.jboss.org/browse/DROOLS-3516 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3743) Implement Test scenario coverage report for RULE

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3743?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3743: ---------------------------------- Description: Use this ticket as specs https://issues.jboss.org/browse/DROOLS-3516 > Implement Test scenario coverage report for RULE > ------------------------------------------------ > > Key: DROOLS-3743 > URL: https://issues.jboss.org/browse/DROOLS-3743 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > Use this ticket as specs > https://issues.jboss.org/browse/DROOLS-3516 -- 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