September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8595) Wildfly fails if wrapper class calls MemoryMXBean due to "logging manager" conflict (IBM JDK and YAJSW)

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-8595?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski commented on WFLY-8595: ------------------------------------------ [~milspec] ^^ > Wildfly fails if wrapper class calls MemoryMXBean due to "logging manager" conflict (IBM JDK and YAJSW) > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-8595 > URL: https://issues.jboss.org/browse/WFLY-8595 > Project: WildFly > Issue Type: Feature Request > Components: Logging > Affects Versions: 10.1.0.Final > Environment: * Wildfly 10.1 > * IBM JDK 8 > * YAJSW 11 > Reporter: will milspec > Assignee: James Perkins > > *Upshot* > Wildfly 10.1 fails to run when called from YAJSW (Yet Another Service Wrapper) on the IBM JDK. > It fails because YAJSW instantiates/calls MemoryMXBean prior to running the wildfly classes. > IBM's implementation of MemoryMXBean instantiates the Logging manager, i.e. class identified by -Djava.util.logging.manager. > A "class/classloader" conflict exists for the logging manager. Because IBM JDK's MemoryMXBean "got to the log manager" first, wildfly presuppositions are undermined, i.e. the "system classloader" loaded the log manager, not the "jboss module classloader". A 'class identify check' (see below) fails. > *More Details* > This test returns false for Oracle JDK, true for IBM when run under yajsw. i.e. Under OracleJDK, LogManager.getLogManager() has a different classloader (the jboss module classoader ) than does the LogManager.class (system classloader) > jboss-modules.git/src/main/java/org/jboss/modules/Main.java > {{ final String logManagerName = getServiceName(bootClassLoader, "java.util.logging.LogMa > nager"); > if (logManagerName != null) { > System.setProperty("java.util.logging.manager", logManagerName); > * if (LogManager.getLogManager().getClass() == LogManager.class) { > * System.err.println("WARNING: Failed to load the specified log manager class " + logManagerName); > } else { > Module.setModuleLogger(new JDKModuleLogger()); > } > } > }} > *Workaround Gets Farther but Undermines Presuppositions of App Server* > If I add this jar to the Xbootclasspath/p, the "ibm system classes" loads org.jboss.logmanager.LogManager, but a downstream check in the jboss code throws an exception because the wrong classloader loaded org.jboss.logmanager.LogManager. > *Steps to Reproduce* > -Download IBM JDK > -Download yajsw. Run its "genconfig" tool to generate a configration file > -Start wildfly > *Resource Xref* > When I first came across this issue, I had trouble discerning "where the problem lay", i.e. in what source code. I posted on the ibm developer works, yajsw and wildfly forums. > https://sourceforge.net/p/yajsw/discussion/810311/thread/e730451b/ > ibm developer works forum: > https://www.ibm.com/developerworks/community/forums/html/topic?id=8e9e4ae... > jboss developer forum: > https://developer.jboss.org/thread/272840 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9310) Class loading hierarchie

by stefano canu (JIRA)

[ https://issues.jboss.org/browse/WFLY-9310?page=com.atlassian.jira.plugin.... ] stefano canu commented on WFLY-9310: ------------------------------------ Please remove Attachments > Class loading hierarchie > ------------------------- > > Key: WFLY-9310 > URL: https://issues.jboss.org/browse/WFLY-9310 > Project: WildFly > Issue Type: Bug > Components: Class Loading, JPA / Hibernate > Affects Versions: 10.1.0.Final > Environment: windows 7 > oracle jdk hotspot 8 > wildfly 10 final > Reporter: stefano canu > Assignee: David Lloyd > Attachments: image-2017-09-07-12-57-48-779.png, image-2017-09-07-12-57-52-827.png, image-2017-09-07-12-57-59-849.png > > > Deployng an EAR application with hibernate 4.x jars in lib folders but is ignored and workning with AS module (hibernate 5.0.10) . i tried to do module exclusion by using jboss-deployment- structure but whitout any luck. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9310) Class loading hierarchie

by stefano canu (JIRA)

[ https://issues.jboss.org/browse/WFLY-9310?page=com.atlassian.jira.plugin.... ] stefano canu commented on WFLY-9310: ------------------------------------ Hi, the issue is not concerning hibernate/jpa but class loading policy, i tried to exclude dom4j for fixinf the error https://stackoverflow.com/questions/35533847/wildfly-10-java-lang-classca..., but the only way is to eliminate the jar from EAR lib > Class loading hierarchie > ------------------------- > > Key: WFLY-9310 > URL: https://issues.jboss.org/browse/WFLY-9310 > Project: WildFly > Issue Type: Bug > Components: Class Loading, JPA / Hibernate > Affects Versions: 10.1.0.Final > Environment: windows 7 > oracle jdk hotspot 8 > wildfly 10 final > Reporter: stefano canu > Assignee: David Lloyd > Attachments: image-2017-09-07-12-57-48-779.png, image-2017-09-07-12-57-52-827.png, image-2017-09-07-12-57-59-849.png > > > Deployng an EAR application with hibernate 4.x jars in lib folders but is ignored and workning with AS module (hibernate 5.0.10) . i tried to do module exclusion by using jboss-deployment- structure but whitout any luck. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3261) Unignore NotificationSupportImplTestCase.doManyNotificationOrderingWithExecutor

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3261?page=com.atlassian.jira.plugi... ] Jan Martiska moved JBEAP-13071 to WFCORE-3261: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3261 (was: JBEAP-13071) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.CR1) > Unignore NotificationSupportImplTestCase.doManyNotificationOrderingWithExecutor > ------------------------------------------------------------------------------- > > Key: WFCORE-3261 > URL: https://issues.jboss.org/browse/WFCORE-3261 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Jan Martiska > Assignee: Jan Martiska > Priority: Minor > > The test is currently ignored: https://github.com/wildfly/wildfly-core/blob/3.0.1.Final/controller/src/t... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9321) (Fix) and reenable PersistentCalendarTimerManagementTestCase

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-9321?page=com.atlassian.jira.plugin.... ] Jan Martiska reassigned WFLY-9321: ---------------------------------- Assignee: Jan Martiska > (Fix) and reenable PersistentCalendarTimerManagementTestCase > ------------------------------------------------------------ > > Key: WFLY-9321 > URL: https://issues.jboss.org/browse/WFLY-9321 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Jan Martiska > Assignee: Jan Martiska > Priority: Minor > > PersistentCalendarTimerManagementTestCase is currently ignored. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9321) (Fix) and reenable PersistentCalendarTimerManagementTestCase

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-9321?page=com.atlassian.jira.plugin.... ] Jan Martiska moved JBEAP-13069 to WFLY-9321: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9321 (was: JBEAP-13069) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.CR1) > (Fix) and reenable PersistentCalendarTimerManagementTestCase > ------------------------------------------------------------ > > Key: WFLY-9321 > URL: https://issues.jboss.org/browse/WFLY-9321 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Jan Martiska > Priority: Minor > > PersistentCalendarTimerManagementTestCase is currently ignored. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9320) Re-enable EJBClientAPIUsageTestCase.testSFSBAccessFailureWithoutSession in legacy ejb client test suite

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-9320?page=com.atlassian.jira.plugin.... ] Jan Martiska updated WFLY-9320: ------------------------------- Summary: Re-enable EJBClientAPIUsageTestCase.testSFSBAccessFailureWithoutSession in legacy ejb client test suite (was: Re-enable EJBClientAPIUsageTestCase in legacy ejb client test suite) > Re-enable EJBClientAPIUsageTestCase.testSFSBAccessFailureWithoutSession in legacy ejb client test suite > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-9320 > URL: https://issues.jboss.org/browse/WFLY-9320 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Jan Martiska > Assignee: Jan Martiska > Priority: Minor > > The same test in the "basic" test suite was fixed via JBEAP-11365. We can do the same for the test in legacy EJB client test suite. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9320) Re-enable EJBClientAPIUsageTestCase in legacy ejb client test suite

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-9320?page=com.atlassian.jira.plugin.... ] Jan Martiska moved JBEAP-13068 to WFLY-9320: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9320 (was: JBEAP-13068) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.CR1) > Re-enable EJBClientAPIUsageTestCase in legacy ejb client test suite > ------------------------------------------------------------------- > > Key: WFLY-9320 > URL: https://issues.jboss.org/browse/WFLY-9320 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Jan Martiska > Assignee: Jan Martiska > Priority: Minor > > The same test in the "basic" test suite was fixed via JBEAP-11365. We can do the same for the test in legacy EJB client test suite. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9319) Fix or remove MySqlDsDriverInEarReauthTestCase

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-9319?page=com.atlassian.jira.plugin.... ] Jan Martiska moved JBEAP-13067 to WFLY-9319: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9319 (was: JBEAP-13067) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.CR1) > Fix or remove MySqlDsDriverInEarReauthTestCase > ---------------------------------------------- > > Key: WFLY-9319 > URL: https://issues.jboss.org/browse/WFLY-9319 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Jan Martiska > Assignee: Jan Martiska > Priority: Minor > > This test is ignored: https://github.com/jbossas/jboss-eap7/blob/EAP_7.1.0.CR1-dev/testsuite/in... > It depends on the QA instance of MySQL database (via https://github.com/jbossas/jboss-eap7/blob/EAP_7.1.0.CR1-dev/testsuite/in...) which is direly unsuitable for the basic test suite and won't work without access to the VPN. > This testing scenario is covered in the QA tests so I think we can safely get rid of this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9318) Some EJB tests are ignored because they are incompatible with SLSB pooling

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-9318?page=com.atlassian.jira.plugin.... ] Jan Martiska moved JBEAP-13065 to WFLY-9318: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9318 (was: JBEAP-13065) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.CR1) > Some EJB tests are ignored because they are incompatible with SLSB pooling > -------------------------------------------------------------------------- > > Key: WFLY-9318 > URL: https://issues.jboss.org/browse/WFLY-9318 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Jan Martiska > Assignee: Jan Martiska > Priority: Minor > > This affects: > {{EjbRemoveUnitTestCase.testEjbRemoveCalledForEveryCall}}: https://github.com/jbossas/jboss-eap7/blob/EAP_7.1.0.CR1-dev/testsuite/in... > {{LifecycleTestCase.testStatelessBeanLifecyleCallback}}: https://github.com/jbossas/jboss-eap7/blob/EAP_7.1.0.CR1-dev/testsuite/in... > We should decide what to do with 'em. Options: > - fix them by applying the necessary config changes - explicitly disable SLSB pooling before the test > - remove them > My vote is for removing them, for two reasons: > - disabling SLSB pooling does not quite seem a real-world reasonable use case for me, so the benefit from having these tests is quite poor > - the needed config change requires server reload, which slows down the TS execution and has been known to cause instabilities -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 September 2017