[JBoss JIRA] (WFLY-11891) Add tests that enable JPA entity class bytecode enhancement
by Gail Badner (Jira)
[ https://issues.jboss.org/browse/WFLY-11891?page=com.atlassian.jira.plugin... ]
Gail Badner commented on WFLY-11891:
------------------------------------
Test failures will be fixed by https://hibernate.atlassian.net/browse/HHH-13343.
> Add tests that enable JPA entity class bytecode enhancement
> -----------------------------------------------------------
>
> Key: WFLY-11891
> URL: https://issues.jboss.org/browse/WFLY-11891
> Project: WildFly
> Issue Type: Enhancement
> Components: JPA / Hibernate
> Affects Versions: 16.0.0.Final
> Reporter: Scott Marlow
> Assignee: Gail Badner
> Priority: Minor
> Attachments: bytebuddy.log, javassist.log
>
>
> Pick a few unit tests and add the following settings to enable [entity bytecode enhancement|http://docs.jboss.org/hibernate/orm/5.3/userguide/html_single...]:
> {code}
> <property name="hibernate.enhancer.enableDirtyTracking" value="true"/>
> <property name="hibernate.enhancer.enableLazyInitialization" value="true"/>
> <property name="hibernate.enhancer.enableAssociationManagement" value="true"/>
> {code}
> Steps to reproduce:
> * Build WildFly
> * cd testsuite/integration/basic
> * mvn clean install -Dtest=org.jboss.as.test.integration.jpa.transaction.TransactionTestCase
> * mvn clean install -Dtest=org.jboss.as.test.integration.jpa.hibernate.management.ManagementTestCase
> * mvn clean install -Dtest=org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase
> * mvn clean install -Dtest=org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase
> Note that the org.jboss.as.test.integration.jpa.transaction.TransactionTestCase test should pass since javassist is specified in the persistence.xml but that seems to be ignored (we still get the ByteBuddy failure).
> To workaround failures, prestart wildfly via: ./standalone.sh -Dhibernate.bytecode.provider=javassist and then run tests.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-11919) [WFLY-11846] Deployment classloader leak on EE Concurrency managed threads
by Teresa Miyar Gil (Jira)
Teresa Miyar Gil created WFLY-11919:
---------------------------------------
Summary: [WFLY-11846] Deployment classloader leak on EE Concurrency managed threads
Key: WFLY-11919
URL: https://issues.jboss.org/browse/WFLY-11919
Project: WildFly
Issue Type: Bug
Components: Concurrency Utilities
Affects Versions: 16.0.0.Final
Reporter: Teresa Miyar Gil
Assignee: Eduardo Martins
Fix For: 17.0.0.Beta1
A followup to WFLY-11678, managed threads have another deployment CL leak, which happens due to parent thread having a reference to it in its AccessControlContext. When a thread is created it inherits parent's AccessControlContext.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[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:
---------------------------------------
This works indeed.
Thanks for your help.
Wolfgang
> 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: Yeray Borges
> 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)
6 years, 7 months
[JBoss JIRA] (SWSQE-655) Kiali tableue reports-Test execution report does not show all the sprints
by Sunil Kondkar (Jira)
[ https://issues.jboss.org/browse/SWSQE-655?page=com.atlassian.jira.plugin.... ]
Sunil Kondkar commented on SWSQE-655:
-------------------------------------
Added sprint iterations to polarion- added sprint 19 and sprint 20 iterations
Linked test runs in each sprint to related iterations
To do: Check if Kiali Test execution report shows all sprints in Tableue.
> Kiali tableue reports-Test execution report does not show all the sprints
> -------------------------------------------------------------------------
>
> Key: SWSQE-655
> URL: https://issues.jboss.org/browse/SWSQE-655
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Sunil Kondkar
> Assignee: Prachi Yadav
> Priority: Major
> Labels: pqi
>
> Kiali tableue reports-Test execution report does not show all the sprints
> To-do:
> -Search if the sprint milestones exist, if not then create
> -Link existing test plans of each sprint to related milestone sprint
> -Verify if reports show all test cases and sprints
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months