[JBoss JIRA] (JBJCA-988) Core test suite
by Vladimir Rastseluev (JIRA)
Vladimir Rastseluev created JBJCA-988:
-----------------------------------------
Summary: Core test suite
Key: JBJCA-988
URL: https://issues.jboss.org/browse/JBJCA-988
Project: IronJacamar
Issue Type: Task
Components: Core
Affects Versions: 1.1.0.Beta3
Reporter: Vladimir Rastseluev
Assignee: Vladimir Rastseluev
Improve the subject
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6567) Hang in ProfileTransformersTestCase ModelTestModelControllerService.waitForSetup
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/AS7-6567?page=com.atlassian.jira.plugin.s... ]
Carlo de Wolf edited comment on AS7-6567 at 2/21/13 3:12 AM:
-------------------------------------------------------------
The {{ModelTestModelControllerService}} comes from {{/home/carlo/.m2/repository/org/jboss/as/jboss-as-core-model-test-framework/7.2.0.Alpha1-SNAPSHOT/jboss-as-core-model-test-framework-7.2.0.Alpha1-SNAPSHOT.jar}} which is an old bug in {{CoreModelTestDelegate}}. The more recent one uses {{/home/carlo/.m2/repository/org/jboss/as/jboss-as-core-model-test-framework/8.0.0.Alpha1-SNAPSHOT/jboss-as-core-model-test-framework-8.0.0.Alpha1-SNAPSHOT.jar}}.
The test should not be using any Maven repository artifact when running against master, it should be using the artifacts from the current build.
was (Author: wolfc):
The {{ModelTestModelControllerService}} comes from {{file:/home/carlo/.m2/repository/org/jboss/as/jboss-as-core-model-test-framework/7.2.0.Alpha1-SNAPSHOT/jboss-as-core-model-test-framework-7.2.0.Alpha1-SNAPSHOT.jar}} which is an old bug in {{CoreModelTestDelegate}}. The more recent one uses {{file:/home/carlo/.m2/repository/org/jboss/as/jboss-as-core-model-test-framework/8.0.0.Alpha1-SNAPSHOT/jboss-as-core-model-test-framework-8.0.0.Alpha1-SNAPSHOT.jar}}.
The test should not be using any Maven repository artifact when running against master, it should be using the artifacts from the current build.
> Hang in ProfileTransformersTestCase ModelTestModelControllerService.waitForSetup
> --------------------------------------------------------------------------------
>
> Key: AS7-6567
> URL: https://issues.jboss.org/browse/AS7-6567
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, Test Suite
> Reporter: Carlo de Wolf
> Assignee: Kabir Khan
> Attachments: AS7-6567-threaddump.txt
>
>
> {noformat}
> "main" prio=10 tid=0x00007fa1a8009000 nid=0x7f2 waiting on condition [0x00007fa1b1b13000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000007acdbe350> (a java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
> at org.jboss.as.model.test.ModelTestModelControllerService.waitForSetup(ModelTestModelControllerService.java:190)
> at org.jboss.as.core.model.test.AbstractKernelServicesImpl.create(AbstractKernelServicesImpl.java:108)
> at org.jboss.as.core.model.bridge.impl.ChildFirstClassLoaderKernelServicesFactory.create(ChildFirstClassLoaderKernelServicesFactory.java:63)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.as.core.model.bridge.local.ScopedKernelServicesBootstrap.createChildClassLoaderKernelServices(ScopedKernelServicesBootstrap.java:77)
> at org.jboss.as.core.model.bridge.local.ScopedKernelServicesBootstrap.createKernelServices(ScopedKernelServicesBootstrap.java:51)
> at org.jboss.as.core.model.test.CoreModelTestDelegate$LegacyKernelServicesInitializerImpl.install(CoreModelTestDelegate.java:565)
> at org.jboss.as.core.model.test.CoreModelTestDelegate$LegacyKernelServicesInitializerImpl.access$300(CoreModelTestDelegate.java:526)
> at org.jboss.as.core.model.test.CoreModelTestDelegate$KernelServicesBuilderImpl.build(CoreModelTestDelegate.java:493)
> at org.jboss.as.core.model.test.profile.ProfileTransformersTestCase.testProfilesTransformer(ProfileTransformersTestCase.java:66)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6567) Hang in ProfileTransformersTestCase ModelTestModelControllerService.waitForSetup
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/AS7-6567?page=com.atlassian.jira.plugin.s... ]
Carlo de Wolf commented on AS7-6567:
------------------------------------
The {{ModelTestModelControllerService}} comes from {{file:/home/carlo/.m2/repository/org/jboss/as/jboss-as-core-model-test-framework/7.2.0.Alpha1-SNAPSHOT/jboss-as-core-model-test-framework-7.2.0.Alpha1-SNAPSHOT.jar}} which is an old bug in {{CoreModelTestDelegate}}. The more recent one uses {{file:/home/carlo/.m2/repository/org/jboss/as/jboss-as-core-model-test-framework/8.0.0.Alpha1-SNAPSHOT/jboss-as-core-model-test-framework-8.0.0.Alpha1-SNAPSHOT.jar}}.
The test should not be using any Maven repository artifact when running against master, it should be using the artifacts from the current build.
> Hang in ProfileTransformersTestCase ModelTestModelControllerService.waitForSetup
> --------------------------------------------------------------------------------
>
> Key: AS7-6567
> URL: https://issues.jboss.org/browse/AS7-6567
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, Test Suite
> Reporter: Carlo de Wolf
> Assignee: Kabir Khan
> Attachments: AS7-6567-threaddump.txt
>
>
> {noformat}
> "main" prio=10 tid=0x00007fa1a8009000 nid=0x7f2 waiting on condition [0x00007fa1b1b13000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000007acdbe350> (a java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
> at org.jboss.as.model.test.ModelTestModelControllerService.waitForSetup(ModelTestModelControllerService.java:190)
> at org.jboss.as.core.model.test.AbstractKernelServicesImpl.create(AbstractKernelServicesImpl.java:108)
> at org.jboss.as.core.model.bridge.impl.ChildFirstClassLoaderKernelServicesFactory.create(ChildFirstClassLoaderKernelServicesFactory.java:63)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.as.core.model.bridge.local.ScopedKernelServicesBootstrap.createChildClassLoaderKernelServices(ScopedKernelServicesBootstrap.java:77)
> at org.jboss.as.core.model.bridge.local.ScopedKernelServicesBootstrap.createKernelServices(ScopedKernelServicesBootstrap.java:51)
> at org.jboss.as.core.model.test.CoreModelTestDelegate$LegacyKernelServicesInitializerImpl.install(CoreModelTestDelegate.java:565)
> at org.jboss.as.core.model.test.CoreModelTestDelegate$LegacyKernelServicesInitializerImpl.access$300(CoreModelTestDelegate.java:526)
> at org.jboss.as.core.model.test.CoreModelTestDelegate$KernelServicesBuilderImpl.build(CoreModelTestDelegate.java:493)
> at org.jboss.as.core.model.test.profile.ProfileTransformersTestCase.testProfilesTransformer(ProfileTransformersTestCase.java:66)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6557) Verify operation within a security manager
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-6557?page=com.atlassian.jira.plugin.s... ]
David Lloyd commented on AS7-6557:
----------------------------------
Just a few notes on that idea so when I wake up tomorrow it isn't all forgotten:
* We'll need to implement {{java.security.Policy}} with a simple policy that includes the jboss-modules.jar code source
* We have options:
** Just let all remaining permissions be installed via modules
** Or, use the policy mechanism to merge in some global config
* Notes:
** Look into keying off of something besides code source - maybe modules should maintain/cache protection domains in addition to/instead of permission sets?
> Verify operation within a security manager
> -------------------------------------------
>
> Key: AS7-6557
> URL: https://issues.jboss.org/browse/AS7-6557
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Security
> Reporter: David Lloyd
> Assignee: Anil Saldhana
> Fix For: 8.0.0.Alpha1
>
>
> As per the Java EE 7 spec, all Java EE products must be capable of running within a Java security manager. Test each Java EE configuration including application client for security manager operability.
> Discuss with [~dmlloyd] options around modules integration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6557) Verify operation within a security manager
by Anil Saldhana (JIRA)
[ https://issues.jboss.org/browse/AS7-6557?page=com.atlassian.jira.plugin.s... ]
Anil Saldhana commented on AS7-6557:
------------------------------------
David - I am planning to write a proposal tomorrow that highlights the plan. Apart from the jboss modules jar getting the trust entry somehow (probably via the security manager subsystem), I think we should be able to use the default security manager implementation (we will not use the global policy file like before but the security manager subsystem can define the global permission set). The proposal will revolve around the security manager subsystem.
> Verify operation within a security manager
> -------------------------------------------
>
> Key: AS7-6557
> URL: https://issues.jboss.org/browse/AS7-6557
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Security
> Reporter: David Lloyd
> Assignee: Anil Saldhana
> Fix For: 8.0.0.Alpha1
>
>
> As per the Java EE 7 spec, all Java EE products must be capable of running within a Java security manager. Test each Java EE configuration including application client for security manager operability.
> Discuss with [~dmlloyd] options around modules integration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6578) Domain Model global permission block
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-6578?page=com.atlassian.jira.plugin.s... ]
David Lloyd commented on AS7-6578:
----------------------------------
Some requirements:
# Allow permission specification for deployments...
## In deployment block?
## In a separate area?
# Allow permission specification for filesystem JAR files which are included via class-path
## By JAR file name
# Allow permission specification for extension JARs
## By extension name?
> Domain Model global permission block
> ------------------------------------
>
> Key: AS7-6578
> URL: https://issues.jboss.org/browse/AS7-6578
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Security
> Reporter: Anil Saldhana
> Assignee: Anil Saldhana
> Fix For: 8.0.0.Alpha1
>
>
> The domain model (domain.xml/standalone.xml) needs to have a block for assigning global permissions, that can be overridden by module level permissions as well as deployment permissions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6557) Verify operation within a security manager
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-6557?page=com.atlassian.jira.plugin.s... ]
David Lloyd commented on AS7-6557:
----------------------------------
Some experimentation reveals that the modules patch works great - *except* - there is the problem of getting jboss-modules.jar itself to be trusted. For my test, I pushed it on to the boot classpath in standalone.sh (an option which doesn't necessarily work for every JDK). This is a problem that will have to be solved somehow.
> Verify operation within a security manager
> -------------------------------------------
>
> Key: AS7-6557
> URL: https://issues.jboss.org/browse/AS7-6557
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Security
> Reporter: David Lloyd
> Assignee: Anil Saldhana
> Fix For: 8.0.0.Alpha1
>
>
> As per the Java EE 7 spec, all Java EE products must be capable of running within a Java security manager. Test each Java EE configuration including application client for security manager operability.
> Discuss with [~dmlloyd] options around modules integration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months