[JBoss JIRA] (WFCORE-4229) Upgrade Byteman to 4.0.5 for better JDK12 support
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFCORE-4229?page=com.atlassian.jira.plugi... ]
Rostislav Svoboda commented on WFCORE-4229:
-------------------------------------------
[~adinn] any estimation when Byteman 4.0.5 would be released ? Asking because of JDK12 bytecode support - BYTEMAN-372. Thank you.
> Upgrade Byteman to 4.0.5 for better JDK12 support
> -------------------------------------------------
>
> Key: WFCORE-4229
> URL: https://issues.jboss.org/browse/WFCORE-4229
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Test Suite
> Affects Versions: 7.0.0.Beta1
> Reporter: Rostislav Svoboda
> Assignee: Rostislav Svoboda
> Priority: Major
>
> Byteman to 4.0.5 is not yet available, but running WildFly Core Testsuite with 4.0.5-SNAPSHOT fixes several failures on JDK 12 (12-ea+19 in my case). This is similar case like WFCORE-3990 for Java 10 and linked issues failures.
> BYTEMAN-372 brings support for Java 12 bytecode.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11357) Tests RemoteLocalCall*TestCase fail with security manager
by David Lloyd (Jira)
[ https://issues.jboss.org/browse/WFLY-11357?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-11357:
------------------------------------
I think the privileged block might need to be added in FileSystemXAResourceRegistry in the wildfly-transaction-client project.
> Tests RemoteLocalCall*TestCase fail with security manager
> ---------------------------------------------------------
>
> Key: WFLY-11357
> URL: https://issues.jboss.org/browse/WFLY-11357
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Test Suite, Transactions
> Affects Versions: 15.0.0.Beta1
> Reporter: Martin Choma
> Assignee: Amos Feng
> Priority: Major
> Labels: security-manager
>
> {noformat}
> org.jboss.as.test.multinode.remotecall (2)
> RemoteLocalCallProfileTestCase.testStatelessRemoteFromRemote
> RemoteLocalCallTestCase.testStatelessRemoteFromRemote
> {noformat}
> {noformat}
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/store/work/tc-work/8edf911abfd02209/testsuite/integration/multinode/target/jbossas-multinode-client/standalone/data/ejb-xa-recovery" "write")" in code source "(vfs:/content/remotelocalcall-test-client.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.remotelocalcall-test-client.jar" from Service Module Loader")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:294)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:191)
> at java.lang.SecurityManager.checkWrite(SecurityManager.java:979)
> at org.wildfly.security.manager.WildFlySecurityManager.checkWrite(WildFlySecurityManager.java:377)
> at java.io.File.mkdir(File.java:1311)
> at org.wildfly.transaction.client.provider.jboss.FileSystemXAResourceRegistry$XAResourceRegistryFile.<init>(FileSystemXAResourceRegistry.java:207)
> at org.wildfly.transaction.client.provider.jboss.FileSystemXAResourceRegistry.getXAResourceRegistryFile(FileSystemXAResourceRegistry.java:121)
> at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.getXAResourceRegistry(JBossLocalTransactionProvider.java:160)
> at org.wildfly.transaction.client.XAOutflowedResources.getOrEnlist(XAOutflowedResources.java:57)
> at org.wildfly.transaction.client.RemoteTransactionContext.outflowTransaction(RemoteTransactionContext.java:222)
> at org.jboss.ejb.protocol.remote.EJBClientChannel.writeTransaction(EJBClientChannel.java:567)
> at org.jboss.ejb.protocol.remote.EJBClientChannel.openSession(EJBClientChannel.java:623)
> at org.jboss.ejb.protocol.remote.RemoteEJBReceiver.createSession(RemoteEJBReceiver.java:149)
> at org.jboss.ejb.client.EJBSessionCreationInvocationContext.proceed(EJBSessionCreationInvocationContext.java:63)
> at org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleSessionCreation(RemotingEJBClientInterceptor.java:66)
> at org.jboss.ejb.client.EJBSessionCreationInvocationContext.proceed(EJBSessionCreationInvocationContext.java:70)
> at org.jboss.ejb.client.TransactionPostDiscoveryInterceptor.handleSessionCreation(TransactionPostDiscoveryInterceptor.java:89)
> at org.jboss.ejb.client.EJBSessionCreationInvocationContext.proceed(EJBSessionCreationInvocationContext.java:70)
> at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.handleSessionCreation(DiscoveryEJBClientInterceptor.java:150)
> at org.jboss.ejb.client.EJBSessionCreationInvocationContext.proceed(EJBSessionCreationInvocationContext.java:70)
> at org.jboss.ejb.client.NamingEJBClientInterceptor.handleSessionCreation(NamingEJBClientInterceptor.java:93)
> at org.jboss.ejb.client.EJBSessionCreationInvocationContext.proceed(EJBSessionCreationInvocationContext.java:70)
> at org.jboss.ejb.client.TransactionInterceptor.handleSessionCreation(TransactionInterceptor.java:100)
> at org.jboss.ejb.client.EJBSessionCreationInvocationContext.proceed(EJBSessionCreationInvocationContext.java:70)
> at org.jboss.ejb.client.EJBClientContext.createSession(EJBClientContext.java:834)
> at org.jboss.ejb.client.EJBClient.createSessionProxy(EJBClient.java:198)
> at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:157)
> ... 221 more
> {noformat}
> [1] https://ci.wildfly.org/viewLog.html?buildId=128138&buildTypeId=WF_MasterS...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11337) Hibernate tests failures with security manager
by David Lloyd (Jira)
[ https://issues.jboss.org/browse/WFLY-11337?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-11337:
------------------------------------
Yes it is very likely. In fact this looks familiar - I would not be surprised if this is an existent issue in the Hibernate JIRA instance.
> Hibernate tests failures with security manager
> ----------------------------------------------
>
> Key: WFLY-11337
> URL: https://issues.jboss.org/browse/WFLY-11337
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Test Suite
> Affects Versions: 14.0.0.Final
> Reporter: Martin Choma
> Priority: Major
> Labels: security-manager
>
> As a limitation documented by JBEAP-15368 there is lot of tests (approximately 75) using hibernate that are failing with security manager. E.g in package
> * org.jboss.as.test.compat.jpa.hibernate.transformer
> * org.jboss.as.test.integration.hibernate
> * org.jboss.as.test.integration.hibernate.envers
> This failure contains exception like this
> {noformat}
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/store/repository/org/hibernate/hibernate-envers/5.3.7.Final/hibernate-envers-5.3.7.Final.jar" "read")" in code source "(vfs:/content/org.jboss.as.test.compat.jpa.hibernate.transformer.VerifyHibernate51CompatibilityJDSEnabledTransformerTestCase.ear/main.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.org.jboss.as.test.compat.jpa.hibernate.transformer.VerifyHibernate51CompatibilityJDSEnabledTransformerTestCase.ear.main.war" from Service Module Loader")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:294)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:191)
> at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
> at org.wildfly.security.manager.WildFlySecurityManager.checkRead(WildFlySecurityManager.java:359)
> at sun.net.www.protocol.jar.JarFileFactory.getCachedJarFile(JarFileFactory.java:137)
> at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:81)
> at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:122)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:152)
> at java.net.URL.openStream(URL.java:1045)
> at java.util.ServiceLoader.parse(ServiceLoader.java:304)
> at java.util.ServiceLoader.access$200(ServiceLoader.java:185)
> at java.util.ServiceLoader$LazyIterator.hasNextService(ServiceLoader.java:357)
> at java.util.ServiceLoader$LazyIterator.access$600(ServiceLoader.java:323)
> at java.util.ServiceLoader$LazyIterator$1.run(ServiceLoader.java:396)
> at java.util.ServiceLoader$LazyIterator$1.run(ServiceLoader.java:395)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.ServiceLoader$LazyIterator.hasNext(ServiceLoader.java:398)
> at java.util.ServiceLoader$1.hasNext(ServiceLoader.java:474)
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.loadJavaServices(ClassLoaderServiceImpl.java:465)
> at org.hibernate.integrator.internal.IntegratorServiceImpl.<init>(IntegratorServiceImpl.java:40)
> at org.hibernate.boot.registry.BootstrapServiceRegistryBuilder.build(BootstrapServiceRegistryBuilder.java:224)
> at org.hibernate.cfg.Configuration.<init>(Configuration.java:118)
> at org.jboss.as.test.compat.jpa.hibernate.transformer.SFSBHibernateSessionFactory.setupConfig(SFSBHibernateSessionFactory.java:66)
> {noformat}
> Is there way to workaround this limitation in testsuite?
> [1] https://ci.wildfly.org/viewLog.html?buildId=128138&buildTypeId=WF_MasterS...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4229) Upgrade Byteman to 4.0.5 for better JDK12 support
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFCORE-4229?page=com.atlassian.jira.plugi... ]
Rostislav Svoboda updated WFCORE-4229:
--------------------------------------
Description:
Byteman to 4.0.5 is not yet available, but running WildFly Core Testsuite with 4.0.5-SNAPSHOT fixes several failures on JDK 12 (12-ea+19 in my case). This is similar case like WFCORE-3990 for Java 10 and linked issues failures.
BYTEMAN-372 brings support for Java 12 bytecode.
was:Byteman to 4.0.5 is not yet available, but running WildFly Core Testsuite with 4.0.5-SNAPSHOT fixes several failures on JDK 12 (12-ea+19 in my case). This is similar case like WFCORE-3990 for Java 10 and linked issues failures.
> Upgrade Byteman to 4.0.5 for better JDK12 support
> -------------------------------------------------
>
> Key: WFCORE-4229
> URL: https://issues.jboss.org/browse/WFCORE-4229
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Test Suite
> Affects Versions: 7.0.0.Beta1
> Reporter: Rostislav Svoboda
> Assignee: Rostislav Svoboda
> Priority: Major
>
> Byteman to 4.0.5 is not yet available, but running WildFly Core Testsuite with 4.0.5-SNAPSHOT fixes several failures on JDK 12 (12-ea+19 in my case). This is similar case like WFCORE-3990 for Java 10 and linked issues failures.
> BYTEMAN-372 brings support for Java 12 bytecode.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4230) [jdk12] DeletionCollisionTest#testFileLockByRemoveContent fails on Java 12, Byteman related issue
by Rostislav Svoboda (Jira)
Rostislav Svoboda created WFCORE-4230:
-----------------------------------------
Summary: [jdk12] DeletionCollisionTest#testFileLockByRemoveContent fails on Java 12, Byteman related issue
Key: WFCORE-4230
URL: https://issues.jboss.org/browse/WFCORE-4230
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Beta1
Reporter: Rostislav Svoboda
Assignee: Rostislav Svoboda
DeletionCollisionTest#testFileLockByRemoveContent fails on Java 12, Byteman related issue
Similar situation like in WFCORE-3869 case. Byteman needs update.
Running WildFly Core Testsuite with Byteman 4.0.5-SNAPSHOT fixes the failure on JDK 12 (12-ea+19 in my case).
BYTEMAN-372 brings support for Java 12 bytecode.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4229) Upgrade Byteman to 4.0.5 for better JDK12 support
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFCORE-4229?page=com.atlassian.jira.plugi... ]
Rostislav Svoboda updated WFCORE-4229:
--------------------------------------
Description: Byteman to 4.0.5 is not yet available, but running WildFly Core Testsuite with 4.0.5-SNAPSHOT fixes several failures on JDK 12 (12-ea+19 in my case). This is similar case like WFCORE-3990 for Java 10 and linked issues failures.
> Upgrade Byteman to 4.0.5 for better JDK12 support
> -------------------------------------------------
>
> Key: WFCORE-4229
> URL: https://issues.jboss.org/browse/WFCORE-4229
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Test Suite
> Affects Versions: 7.0.0.Beta1
> Reporter: Rostislav Svoboda
> Assignee: Rostislav Svoboda
> Priority: Major
>
> Byteman to 4.0.5 is not yet available, but running WildFly Core Testsuite with 4.0.5-SNAPSHOT fixes several failures on JDK 12 (12-ea+19 in my case). This is similar case like WFCORE-3990 for Java 10 and linked issues failures.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (LOGMGR-213) Add a System.LoggerFinder for Java 9+
by James Perkins (Jira)
James Perkins created LOGMGR-213:
------------------------------------
Summary: Add a System.LoggerFinder for Java 9+
Key: LOGMGR-213
URL: https://issues.jboss.org/browse/LOGMGR-213
Project: JBoss Log Manager
Issue Type: Enhancement
Reporter: James Perkins
Assignee: James Perkins
In Java 9 a {{java.lang.System.Logger}} and {{java.lang.System.LoggerFinder}} were added for system logging. By default this uses JUL. However as this is designed for system level logging there is a chance that the LogManager could be activated before the {{java.util.logging.manager}} system property is set. Creating a {{java.lang.System.LoggerFinder}} which sets the property will allow the JBoss Log Manager to be used assuming it's on the class path.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months