[JBoss JIRA] (WFLY-6184) "java.lang.RuntimePermission" "createClassLoader" by some tests running with security manager
by Hynek Švábek (JIRA)
Hynek Švábek created WFLY-6184:
----------------------------------
Summary: "java.lang.RuntimePermission" "createClassLoader" by some tests running with security manager
Key: WFLY-6184
URL: https://issues.jboss.org/browse/WFLY-6184
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Hynek Švábek
Some tests fail with java.security.AccessControlException: WFSM000001: Permission check failed "java.lang.RuntimePermission" "createClassLoader" when security manager is enabled.
{code}
Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "createClassLoader")" in code source "(vfs:/content/hibernate4native_transactiontest.ear/beans.jar <no signer certificates>)" of "null")
at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273)
at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:611)
at org.wildfly.security.manager.WildFlySecurityManager.checkCreateClassLoader(WildFlySecurityManager.java:335)
at java.lang.ClassLoader.checkCreateClassLoader(ClassLoader.java:274)
at java.lang.ClassLoader.<init>(ClassLoader.java:316)
at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.<init>(ClassLoaderServiceImpl.java:164)
at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.<init>(ClassLoaderServiceImpl.java:160)
at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.<init>(ClassLoaderServiceImpl.java:94)
at org.hibernate.boot.registry.BootstrapServiceRegistryBuilder.build(BootstrapServiceRegistryBuilder.java:207)
at org.hibernate.cfg.Configuration.<init>(Configuration.java:119)
at org.jboss.as.test.integration.hibernate.SFSBHibernateTransaction.setupConfig(SFSBHibernateTransaction.java:63)
... 200 more
{code}
Falling tests
* ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.Hibernate2LCacheStatsTestCase#testHibernateStatistics
org.jboss.as.test.integration.hibernate.Hibernate2LCacheStatsTestCase#testHibernateStatistics
* ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.Hibernate4NativeAPIProviderTestCase#testSimpleOperation
org.jboss.as.test.integration.hibernate.Hibernate4NativeAPIProviderTestCase#testSimpleOperation
* ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.HibernateNativeAPITransactionTestCase
org.jboss.as.test.integration.hibernate.HibernateNativeAPITransactionTestCase#testRollBackOperation
org.jboss.as.test.integration.hibernate.HibernateNativeAPITransactionTestCase#testSimpleOperation
* ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.envers.Hibernate4NativeAPIEnversTestCase#testEnversonHibernateNativeAPI
org.jboss.as.test.integration.hibernate.envers.Hibernate4NativeAPIEnversTestCase#testEnversonHibernateNativeAPI
* ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.search.HibernateSearchJPATestCase#testFullTextQuery
org.jboss.as.test.integration.hibernate.search.HibernateSearchJPATestCase#testFullTextQuery
* ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.secondlevelcache.HibernateSecondLevelCacheTestCase#testSecondLevelCache
org.jboss.as.test.integration.hibernate.secondlevelcache.HibernateSecondLevelCacheTestCase#testSecondLevelCache
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6184) "java.lang.RuntimePermission" "createClassLoader" by some tests running with security manager
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFLY-6184?page=com.atlassian.jira.plugin.... ]
Hynek Švábek reassigned WFLY-6184:
----------------------------------
Assignee: Hynek Švábek
> "java.lang.RuntimePermission" "createClassLoader" by some tests running with security manager
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-6184
> URL: https://issues.jboss.org/browse/WFLY-6184
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Hynek Švábek
> Assignee: Hynek Švábek
>
> Some tests fail with java.security.AccessControlException: WFSM000001: Permission check failed "java.lang.RuntimePermission" "createClassLoader" when security manager is enabled.
> {code}
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "createClassLoader")" in code source "(vfs:/content/hibernate4native_transactiontest.ear/beans.jar <no signer certificates>)" of "null")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
> at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:611)
> at org.wildfly.security.manager.WildFlySecurityManager.checkCreateClassLoader(WildFlySecurityManager.java:335)
> at java.lang.ClassLoader.checkCreateClassLoader(ClassLoader.java:274)
> at java.lang.ClassLoader.<init>(ClassLoader.java:316)
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.<init>(ClassLoaderServiceImpl.java:164)
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.<init>(ClassLoaderServiceImpl.java:160)
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.<init>(ClassLoaderServiceImpl.java:94)
> at org.hibernate.boot.registry.BootstrapServiceRegistryBuilder.build(BootstrapServiceRegistryBuilder.java:207)
> at org.hibernate.cfg.Configuration.<init>(Configuration.java:119)
> at org.jboss.as.test.integration.hibernate.SFSBHibernateTransaction.setupConfig(SFSBHibernateTransaction.java:63)
> ... 200 more
> {code}
> Falling tests
> * ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.Hibernate2LCacheStatsTestCase#testHibernateStatistics
> org.jboss.as.test.integration.hibernate.Hibernate2LCacheStatsTestCase#testHibernateStatistics
> * ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.Hibernate4NativeAPIProviderTestCase#testSimpleOperation
> org.jboss.as.test.integration.hibernate.Hibernate4NativeAPIProviderTestCase#testSimpleOperation
> * ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.HibernateNativeAPITransactionTestCase
> org.jboss.as.test.integration.hibernate.HibernateNativeAPITransactionTestCase#testRollBackOperation
> org.jboss.as.test.integration.hibernate.HibernateNativeAPITransactionTestCase#testSimpleOperation
> * ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.envers.Hibernate4NativeAPIEnversTestCase#testEnversonHibernateNativeAPI
> org.jboss.as.test.integration.hibernate.envers.Hibernate4NativeAPIEnversTestCase#testEnversonHibernateNativeAPI
> * ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.search.HibernateSearchJPATestCase#testFullTextQuery
> org.jboss.as.test.integration.hibernate.search.HibernateSearchJPATestCase#testFullTextQuery
> * ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.hibernate.secondlevelcache.HibernateSecondLevelCacheTestCase#testSecondLevelCache
> org.jboss.as.test.integration.hibernate.secondlevelcache.HibernateSecondLevelCacheTestCase#testSecondLevelCache
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6183) wildfly-9.0.0.CR1
by Krishna Ramaiah (JIRA)
Krishna Ramaiah created WFLY-6183:
-------------------------------------
Summary: wildfly-9.0.0.CR1
Key: WFLY-6183
URL: https://issues.jboss.org/browse/WFLY-6183
Project: WildFly
Issue Type: Bug
Components: Server
Environment: Windows server 2008 R2
Reporter: Krishna Ramaiah
Assignee: Jason Greene
Priority: Critical
1. OS is shutdown without closing the Wildfy services.
2. OS is started and Wildfly is started
3. Wildfy server starts without any error but http/https listener does not start. There is no error in the log
4. Wildlfy is re-installed and then it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6161) Error when using websocket with wildfly 9.0.2.Final
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-6161?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-6161.
----------------------------------
Resolution: Rejected
Whatever you are connecting to is sending a transfer-encoding header in the response, which is not allowed
> Error when using websocket with wildfly 9.0.2.Final
> ---------------------------------------------------
>
> Key: WFLY-6161
> URL: https://issues.jboss.org/browse/WFLY-6161
> Project: WildFly
> Issue Type: Bug
> Components: IO
> Affects Versions: 9.0.2.Final
> Reporter: taha eddahabi
> Assignee: Jason Greene
> Priority: Blocker
>
> When my web application deployed in wildfly 9.0.2.final try to send a websocket (using the method RemoteEndPoint .sendObject of javax.websocket-api-1.1 ). I get this error :
> {code:java}
> [org.xnio.http.HttpUpgrade$HttpUpgradeState.handleUpgrade(HttpUpgrade.java:490),
> org.xnio.http.HttpUpgrade$HttpUpgradeState.access$1200(HttpUpgrade.java:165),
> org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:461),
> org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:400),
> org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92),
> org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66),
> org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88),
> org.xnio.nio.WorkerThread.run(WorkerThread.java:539)] Line Number : 490"}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6173) Classes not unloaded after undeployment
by Joey Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-6173?page=com.atlassian.jira.plugin.... ]
Joey Wang commented on WFLY-6173:
---------------------------------
[~jaikiran], the issue can be reproduced in WildFly 10.0.0.Final as well.
> Classes not unloaded after undeployment
> ---------------------------------------
>
> Key: WFLY-6173
> URL: https://issues.jboss.org/browse/WFLY-6173
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.2.0.Final, 10.0.0.Final
> Reporter: Joey Wang
> Assignee: Jason Greene
> Priority: Minor
> Attachments: memory-leak.zip
>
>
> I deployed a small web application with one single JSF and one managed bean, accessed the page and then undeployed the application. I found the classes of this application had never been unloaded via monitoring with Java VistualVM, also using '-XX:+TraceClassUnloading' JVM option proved the classes not unloaded.
> Then checking the heap dump of it, I found there were instance for each enum item (the managed bean has one enum type field, which is always initialized when the managed bean constructed) and one array instance including these enum instances.
> Please refer to the attachment for the same application. I started to verify the classloader memory leak issue because we found hot redeployment of our real application swallow some memory each time, then after lots of redeployment the server was short of memories.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6173) Classes not unloaded after undeployment
by Joey Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-6173?page=com.atlassian.jira.plugin.... ]
Joey Wang updated WFLY-6173:
----------------------------
Affects Version/s: 10.0.0.Final
> Classes not unloaded after undeployment
> ---------------------------------------
>
> Key: WFLY-6173
> URL: https://issues.jboss.org/browse/WFLY-6173
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.2.0.Final, 10.0.0.Final
> Reporter: Joey Wang
> Assignee: Jason Greene
> Priority: Minor
> Attachments: memory-leak.zip
>
>
> I deployed a small web application with one single JSF and one managed bean, accessed the page and then undeployed the application. I found the classes of this application had never been unloaded via monitoring with Java VistualVM, also using '-XX:+TraceClassUnloading' JVM option proved the classes not unloaded.
> Then checking the heap dump of it, I found there were instance for each enum item (the managed bean has one enum type field, which is always initialized when the managed bean constructed) and one array instance including these enum instances.
> Please refer to the attachment for the same application. I started to verify the classloader memory leak issue because we found hot redeployment of our real application swallow some memory each time, then after lots of redeployment the server was short of memories.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5511) DomainDeploymentOverlayTestCase fails on pure IPv6 if proxy is used
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5511?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-5511:
-----------------------------------
[~mkopecky] is there any change the proxy itself can be upgrade to newer version, as one that is currently there has quite lots of known issues around ipv6
> DomainDeploymentOverlayTestCase fails on pure IPv6 if proxy is used
> -------------------------------------------------------------------
>
> Key: WFLY-5511
> URL: https://issues.jboss.org/browse/WFLY-5511
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.CR2
> Reporter: Marek Kopecký
> Assignee: ehsavoie Hugonnet
>
> *Description of problem:*
> DomainDeploymentOverlayTestCase fails on pure IPv6 machine with {{Unable to determine IP address from host name "2620:52:0:105f::ffff:8%eth0"}}
> *How reproducible:*
> Always on pure IPv6 machine if proxy is used
> *Steps to Reproduce:*
> # export PROXY_PARAMS="-DproxySet=true -DproxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -DproxyPort=3128 -Dhttp.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttp.proxyPort=3128 -Dhttps.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttps.proxyPort=3128"
> # ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dmcast=$MCAST_ADDRV6 -Dipv6 -Djboss.dist=$JBOSS_DIST -Dtest=DomainDeploymentOverlayTestCase -Dts.domain -DfailIfNoTests=false $PROXY_PARAMS
> *Actual results:*
> MYTESTIPV6_1=2620:52:0:105f::ffff:8
> {noformat}
> The following error was encountered while trying to retrieve the URL: http://2620:52:0:105f::ffff:8%eth0:8080/deployment0/SimpleServlet?
> Unable to determine IP address from host name "2620:52:0:105f::ffff:8%eth0"
> The DNS server returned:
> Name Error: The domain name does not exist.
> This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.
> Your cache administrator is sysadmin-engops-jbossqe(a)redhat.com.
> {noformat}
> *Expected results:*
> No error
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5511) DomainDeploymentOverlayTestCase fails on pure IPv6 if proxy is used
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-5511?page=com.atlassian.jira.plugin.... ]
ehsavoie Hugonnet reassigned WFLY-5511:
---------------------------------------
Assignee: ehsavoie Hugonnet (was: Alexey Loubyansky)
> DomainDeploymentOverlayTestCase fails on pure IPv6 if proxy is used
> -------------------------------------------------------------------
>
> Key: WFLY-5511
> URL: https://issues.jboss.org/browse/WFLY-5511
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.CR2
> Reporter: Marek Kopecký
> Assignee: ehsavoie Hugonnet
>
> *Description of problem:*
> DomainDeploymentOverlayTestCase fails on pure IPv6 machine with {{Unable to determine IP address from host name "2620:52:0:105f::ffff:8%eth0"}}
> *How reproducible:*
> Always on pure IPv6 machine if proxy is used
> *Steps to Reproduce:*
> # export PROXY_PARAMS="-DproxySet=true -DproxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -DproxyPort=3128 -Dhttp.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttp.proxyPort=3128 -Dhttps.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttps.proxyPort=3128"
> # ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dmcast=$MCAST_ADDRV6 -Dipv6 -Djboss.dist=$JBOSS_DIST -Dtest=DomainDeploymentOverlayTestCase -Dts.domain -DfailIfNoTests=false $PROXY_PARAMS
> *Actual results:*
> MYTESTIPV6_1=2620:52:0:105f::ffff:8
> {noformat}
> The following error was encountered while trying to retrieve the URL: http://2620:52:0:105f::ffff:8%eth0:8080/deployment0/SimpleServlet?
> Unable to determine IP address from host name "2620:52:0:105f::ffff:8%eth0"
> The DNS server returned:
> Name Error: The domain name does not exist.
> This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.
> Your cache administrator is sysadmin-engops-jbossqe(a)redhat.com.
> {noformat}
> *Expected results:*
> No error
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JASSIST-260) Stack frame corruption after writing to attribute on injected after method
by Shigeru Chiba (JIRA)
[ https://issues.jboss.org/browse/JASSIST-260?page=com.atlassian.jira.plugi... ]
Shigeru Chiba resolved JASSIST-260.
-----------------------------------
Fix Version/s: 3.20.0-GA
Resolution: Rejected
This is not a bug. The result is correct because insertAfter() inserts code "after" a return statement. The return value is captured before executing the inserted code.
> Stack frame corruption after writing to attribute on injected after method
> --------------------------------------------------------------------------
>
> Key: JASSIST-260
> URL: https://issues.jboss.org/browse/JASSIST-260
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.20.0-GA
> Environment: Using java 1.8, also tested with java 1.7 same behavior on eclipse Version: Mars.1 Release (4.5.1) on windows 7 x64 bits.
> Reporter: Rafael Campos
> Assignee: Shigeru Chiba
> Priority: Minor
> Fix For: 3.20.0-GA
>
> Attachments: Image1.png
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months