[JBoss JIRA] (WFCORE-837) Running tearDown() method of custom server setup task throws AssertionError in ActiveOperationSupport
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-837?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet commented on WFCORE-837:
------------------------------------------
Ok i've a solution by changing some code in wildfly-arquillian so that @AfterClass (junit) is run after the server setup tasks teardown.
> Running tearDown() method of custom server setup task throws AssertionError in ActiveOperationSupport
> ------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-837
> URL: https://issues.jboss.org/browse/WFCORE-837
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Final, 1.0.1.Final, 2.0.0.Alpha10
> Environment: Arquillian, Wildfly-9.0.0.CR2
> Reporter: Vitalii Chepeliuk
> Assignee: ehsavoie Hugonnet
>
> Running tearDown() method of custom server setup tasks in AbstractNodeAuthentication abstract test:
> KerberosSystemPropertiesSetupTask.class,
> SecurityDomainsSetupTask.class,
> SecurityTraceLoggingServerSetupTask.class,
> KrbLdapServerSetupTask.class,
> Krb5ConfServerSetupTask.class
> throws AssertionError.
> Example of SecurityTraceLoggingServerSetupTask
> {code}
> @Override
> public void tearDown(ManagementClient managementClient, String containerId) throws Exception {
> if (categories == null || categories.isEmpty()) {
> return;
> }
> final List<ModelNode> updates = new ArrayList<ModelNode>();
> for (String category : categories) {
> if (category == null || category.length() == 0) {
> continue;
> }
> updates.add(Util.createRemoveOperation(PATH_LOGGING.append("logger", category)));
> }
> ModelNode op = Util.createEmptyOperation("write-attribute", PATH_LOGGING.append("console-handler", "CONSOLE"));
> op.get("name").set("level");
> op.get("value").set("INFO");
> CoreUtils.applyUpdates(updates, managementClient.getControllerClient()); // Applying changes fails here
> }
> {code}
> and in ActiveOperationSupport:151 shutdown property is already true but should be still false
> {code}
> protected <T, A> ActiveOperation<T, A> registerActiveOperation(final Integer id, A attachment, ActiveOperation.CompletedCallback<T> callback) {
> lock.lock(); try {
> // Check that we still allow registration
> assert ! shutdown; // Here it throws AssertionError
> final Integer operationId;
> if(id == null) {
> // If we did not get an operationId, create a new one
> operationId = operationIdManager.createBatchId();
> } else {
> // Check that the operationId is not already taken
> if(! operationIdManager.lockBatchId(id)) {
> throw ProtocolLogger.ROOT_LOGGER.operationIdAlreadyExists(id);
> }
> operationId = id;
> }
> final ActiveOperationImpl<T, A> request = new ActiveOperationImpl<T, A>(operationId, attachment, getCheckedCallback(callback));
> final ActiveOperation<?, ?> existing = activeRequests.putIfAbsent(operationId, request);
> if(existing != null) {
> throw ProtocolLogger.ROOT_LOGGER.operationIdAlreadyExists(operationId);
> }
> activeCount++; // condition.signalAll();
> return request;
> } finally {
> lock.unlock();
> }
> }
> {code}
> Stack trace is following
> java.lang.AssertionError: null
> at org.jboss.as.protocol.mgmt.ActiveOperationSupport.registerActiveOperation(ActiveOperationSupport.java:151)
> at org.jboss.as.protocol.mgmt.ActiveOperationSupport.registerActiveOperation(ActiveOperationSupport.java:121)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:121)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80)
> at org.jboss.as.test.integration.security.common.CoreUtils.applyUpdate(CoreUtils.java:177)
> at org.jboss.as.test.integration.security.common.CoreUtils.applyUpdates(CoreUtils.java:172)
> at org.infinispan.test.integration.security.tasks.AbstractTraceLoggingServer
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFCORE-933) Embedded server start commands are lacking argument validation
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-933?page=com.atlassian.jira.plugin... ]
Petr Kremensky moved JBEAP-932 to WFCORE-933:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-933 (was: JBEAP-932)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: CLI
Domain Management
(was: CLI)
(was: Domain Management)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.0.Beta4
(was: 7.0.0.DR9)
> Embedded server start commands are lacking argument validation
> --------------------------------------------------------------
>
> Key: WFCORE-933
> URL: https://issues.jboss.org/browse/WFCORE-933
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 2.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Ken Wills
> Priority: Minor
>
> Commands for starting embedded instances are lacking argument validation.
> {noformat}[disconnected /] embed-server foo
> [standalone@embedded /]
> [disconnected /] embed-server foo -foo
> [standalone@embedded /]
> [disconnected /] embed-server foo --foo
> [standalone@embedded /]
> [standalone@embedded /] stop-embedded-server foo
> The command accepts 0 unnamed argument(s) but received: [foo]
> [standalone@embedded /] stop-embedded-server -foo
> Unrecognized arguments: [-foo]
> [standalone@embedded /] stop-embedded-server --foo
> Unrecognized arguments: [--foo]{noformat}
> Same case for embedded host controller.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFCORE-932) stop-embedded-server stops the embedded host controller and vice versa
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-932?page=com.atlassian.jira.plugin... ]
Petr Kremensky moved JBEAP-930 to WFCORE-932:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-932 (was: JBEAP-930)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: CLI
Domain Management
(was: CLI)
(was: Domain Management)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.0.Beta4
(was: 7.0.0.DR9)
> stop-embedded-server stops the embedded host controller and vice versa
> ----------------------------------------------------------------------
>
> Key: WFCORE-932
> URL: https://issues.jboss.org/browse/WFCORE-932
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 2.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Ken Wills
> Priority: Minor
>
> We have four new commands for controlling the lifecycle of embedded instances:
> * *embed-server* - launch embedded standalone
> * *stop-embedded-server* - stop embedded standalone
> * *embed-host-controller* - launch embedded host
> * *stop-embedded-host-controller* - stop embedded host
> \\
> I am able stop embedded standalone by *stop-embedded-host-controller* and embedded host controller by *stop-embedded-server*.
> {noformat}
> [disconnected /] embed-server
> [standalone@embedded /] stop-embedded-host-controller
> [disconnected /] embed-host-controller
> 14:22:18,781 INFO [org.jboss.modules] (AeshProcess: 15) JBoss Modules version 1.4.3.Final
> [domain@embedded /] stop-embedded-server
> [disconnected /]
> {noformat}
> \\
> A question comes to my mind, do we need two commands for stopping the embedded instance?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFLY-5176) Some tests end with Security Exception after login with security manager
by Ondrej Kotek (JIRA)
[ https://issues.jboss.org/browse/WFLY-5176?page=com.atlassian.jira.plugin.... ]
Ondrej Kotek reassigned WFLY-5176:
----------------------------------
Assignee: Ondrej Kotek (was: Josef Cacek)
> Some tests end with Security Exception after login with security manager
> ------------------------------------------------------------------------
>
> Key: WFLY-5176
> URL: https://issues.jboss.org/browse/WFLY-5176
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Marek Kopecký
> Assignee: Ondrej Kotek
>
> *Description of problem:*
> Some tests end with Security Exception after login with security manager.
> *Affected tests found so far:*
> * org.jboss.as.test.integration.ejb.security.AnnotationAuthorizationTestCase
> * org.jboss.as.test.integration.ejb.security.AuthenticationTestCase
> * org.jboss.as.test.integration.ejb.security.EJBInWarDefaultSecurityDomainTestCase#testSecurityOnBeanInAbsenceOfExplicitSecurityDomain
> * org.jboss.as.test.integration.ejb.security.LifecycleTestCase
> * org.jboss.as.test.integration.ejb.security.SecurityDDOverrideTestCase#testDDOverride
> * org.jboss.as.test.integration.ejb.security.asynchronous.AsynchronousSecurityTestCase
> * org.jboss.as.test.integration.ejb.security.missingmethodpermission.MissingMethodPermissionsDefaultAllowedTestCase
> * org.jboss.as.test.integration.ejb.security.missingmethodpermission.MissingMethodPermissionsTestCase
> * org.jboss.as.test.integration.ejb.security.rolelink.SecurityRoleLinkTestCase#testIsCallerInRole
> * org.jboss.as.test.integration.ejb.security.runas.RunAsTestCase
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=AnnotationAuthorizationTestCase
> *Actual results:*
> {noformat}
> javax.security.auth.login.LoginException: Security Exception
> at javax.security.auth.login.LoginContext.invoke(LoginContext.java:841)
> at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
> at javax.security.auth.login.LoginContext.login(LoginContext.java:588)
> at org.jboss.as.test.integration.ejb.security.AnnotationAuthorizationTestCase.testRolesAllowedOverriden_User2(AnnotationAuthorizationTestCase.java:187)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFCORE-931) Embedded host-controller throws NPE on regular shutdown
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-931?page=com.atlassian.jira.plugin... ]
Petr Kremensky moved JBEAP-927 to WFCORE-931:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-931 (was: JBEAP-927)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: CLI
Domain Management
(was: CLI)
(was: Domain Management)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.0.Beta4
(was: 7.0.0.DR8)
> Embedded host-controller throws NPE on regular shutdown
> -------------------------------------------------------
>
> Key: WFCORE-931
> URL: https://issues.jboss.org/browse/WFCORE-931
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 2.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Ken Wills
>
> Invoking the /host=master:shutdown operation on embedded host-controller gives me NPE.
> *Standalone*
> {noformat}
> [standalone@embedded /] shutdown
> The command is not available in the current context (e.g. required subsystems or connection to the controller might be unavailable).
> [standalone@embedded /] :shutdown
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0031: No operation named 'shutdown' exists at address []",
> "rolled-back" => true
> }
> {noformat}
> \\
> *Domain*
> Using operation style :shutdown throws NPE. Tab completion for this operation works, which could be a little bit misleading in this case.
> {noformat}
> [domain@embedded /] shutdown --host=master
> The command is not available in the current context (e.g. required subsystems or connection to the controller might be unavailable).
> [domain@embedded /] /host=master:shutdown
> 13:34:57,512 ERROR [org.jboss.as.controller.management-operation] (AeshProcess: 3) WFLYCTL0013: Operation ("shutdown") failed - address: ([("host" => "master")]): java.lang.NullPointerException
> at org.jboss.as.host.controller.DomainModelControllerService.stopLocalHost(DomainModelControllerService.java:911)
> at org.jboss.as.host.controller.DomainModelControllerService.stopLocalHost(DomainModelControllerService.java:903)
> at org.jboss.as.host.controller.operations.HostShutdownHandler$1.execute(HostShutdownHandler.java:89)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:846)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:637)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:362)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1296)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:395)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:212)
> at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:661)
> at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:651)
> at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.execute(DelegatingModelControllerClient.java:63)
> at org.jboss.as.cli.embedded.ThreadContextsModelControllerClient.execute(ThreadContextsModelControllerClient.java:59)
> at org.jboss.as.cli.handlers.OperationRequestHandler.handle(OperationRequestHandler.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:728)
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:774)
> at org.jboss.as.cli.impl.CommandContextImpl$2.execute(CommandContextImpl.java:389)
> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:53)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException",
> "rolled-back" => true
> }
> [domain@embedded /] :read-resource
> Failed to execute operation.: WFLYEMB0023: The embedded server is stopping and invocations on the ModelControllerClient are not available
> [domain@embedded /] stop-embedded-host-controller
> 13:35:19,252 ERROR [org.jboss.as.protocol] (AeshProcess: 5) WFLYPRT0003: Failed to close resource org.jboss.as.cli.embedded.ThreadContextsModelControllerClient@626966ee: java.lang.IllegalStateException: WFLYEMB0023: The embedded server is stopping and invocations on the ModelControllerClient are not available
> at org.wildfly.core.embedded.EmbeddedHostControllerFactory$HostControllerImpl.getActiveModelControllerClient(EmbeddedHostControllerFactory.java:331)
> at org.wildfly.core.embedded.EmbeddedHostControllerFactory$HostControllerImpl.access$200(EmbeddedHostControllerFactory.java:225)
> at org.wildfly.core.embedded.EmbeddedHostControllerFactory$HostControllerImpl$3.getDelegate(EmbeddedHostControllerFactory.java:309)
> at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.close(DelegatingModelControllerClient.java:103)
> at org.jboss.as.cli.embedded.ThreadContextsModelControllerClient.close(ThreadContextsModelControllerClient.java:139)
> at org.jboss.as.protocol.StreamUtils.safeClose(StreamUtils.java:66)
> at org.jboss.as.cli.impl.CommandContextImpl.disconnectController(CommandContextImpl.java:1165)
> at org.jboss.as.cli.embedded.StopEmbeddedHostControllerHandler.doHandle(StopEmbeddedHostControllerHandler.java:56)
> at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:88)
> at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:751)
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:774)
> at org.jboss.as.cli.impl.CommandContextImpl$2.execute(CommandContextImpl.java:389)
> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:53)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFLY-4423) ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4423?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-4423:
-----------------------------------------------
Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1201358|https://bugzilla.redhat.com/show_bug.cgi?id=1201358] from POST to MODIFIED
> ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory
> ----------------------------------------------------------------------------
>
> Key: WFLY-4423
> URL: https://issues.jboss.org/browse/WFLY-4423
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 9.0.0.Alpha1
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 9.0.0.Beta1
>
>
> To reproduce this issue follow the steps:
> - setup JMS bridge between two WildFly instances
> - once JMS bridge is running, login into jboss-cli and stop the bridge
> - restart the bridge fro jboss-cli
> The following exception appears in the serve log file.
> 10:12:59,414 INFO [org.hornetq.jms.server] (pool-9-thread-1) HQ121000: Failed to set up JMS bridge connections. Most probably the source or target servers are unavailable. Will retry after a pause of 60,000 ms
> 10:13:59,416 WARN [org.hornetq.jms.server] (pool-9-thread-1) HQ122010: Failed to connect JMS Bridge: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory org.jboss.naming.remote.client.InitialContextFactory from classloader ModuleClassLoader for Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory from [Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base))]]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:126)
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:107)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153) [rt.jar:1.7.0_75]
> at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:98)
> at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44)
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.7.0_75]
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) [rt.jar:1.7.0_75]
> at javax.naming.InitialContext.init(InitialContext.java:242) [rt.jar:1.7.0_75]
> at javax.naming.InitialContext.<init>(InitialContext.java:216) [rt.jar:1.7.0_75]
> at org.hornetq.jms.bridge.impl.JNDIFactorySupport.createObject(JNDIFactorySupport.java:55)
> at org.hornetq.jms.bridge.impl.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:40)
> at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1236)
> at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1474)
> at org.hornetq.jms.bridge.impl.JMSBridgeImpl.access$2200(JMSBridgeImpl.java:79)
> at org.hornetq.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:2082)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
> Caused by: java.lang.ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory from [Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.5.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.5.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.5.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.5.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.5.Final-redhat-1]
> at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_75]
> at java.lang.Class.forName(Class.java:274) [rt.jar:1.7.0_75]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:121)
> ... 17 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFLY-5222) Unable to grant custom permission from a WildFly module
by Josef Cacek (JIRA)
[ https://issues.jboss.org/browse/WFLY-5222?page=com.atlassian.jira.plugin.... ]
Josef Cacek updated WFLY-5222:
------------------------------
Description:
When a custom permission (without 2 param constructor) is defined in a WildFly module then it's not possible to grant it to deployments.
Neither defining permissions in {{security-manager}} subsystem nor requesting them in {{META-INF/permissions.xml}} works.
was:
When a custom permission is defined in a WildFly module (e.g. {{org.jboss.remoting3.security.RemotingPermission}}) then it's not possible to grant it to deployments.
Neither defining permissions in {{security-manager}} subsystem nor requesting them in {{META-INF/permissions.xml}} works.
I've updated the JIRA description to emphasize the missing 2-parameter constructor in the custom permission.
> Unable to grant custom permission from a WildFly module
> -------------------------------------------------------
>
> Key: WFLY-5222
> URL: https://issues.jboss.org/browse/WFLY-5222
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager
> Affects Versions: 10.0.0.Beta2
> Reporter: Josef Cacek
> Assignee: Stefan Guilhen
> Priority: Blocker
>
> When a custom permission (without 2 param constructor) is defined in a WildFly module then it's not possible to grant it to deployments.
> Neither defining permissions in {{security-manager}} subsystem nor requesting them in {{META-INF/permissions.xml}} works.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFLY-5222) Unable to grant custom permission from a WildFly module
by Josef Cacek (JIRA)
[ https://issues.jboss.org/browse/WFLY-5222?page=com.atlassian.jira.plugin.... ]
Josef Cacek commented on WFLY-5222:
-----------------------------------
I've fixed the point 1 in the reproducer. Thanks for pointing it out.
The point 2 is not a valid requirement AFAIK.
You could even have a Permission with a constructor without parameters. Look at [getInstance() method of Java default Policy implementation|http://hg.openjdk.java.net/jdk7/jdk7/jdk/file/tip/src/shar...] - it works for 0-2 params in constructor.
The module dependency in point 3 is already part of the reproducer. I'll add one more war with {{permissions.xml}} included.
> Unable to grant custom permission from a WildFly module
> -------------------------------------------------------
>
> Key: WFLY-5222
> URL: https://issues.jboss.org/browse/WFLY-5222
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager
> Affects Versions: 10.0.0.Beta2
> Reporter: Josef Cacek
> Assignee: Stefan Guilhen
> Priority: Blocker
>
> When a custom permission is defined in a WildFly module (e.g. {{org.jboss.remoting3.security.RemotingPermission}}) then it's not possible to grant it to deployments.
> Neither defining permissions in {{security-manager}} subsystem nor requesting them in {{META-INF/permissions.xml}} works.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFCORE-930) Missing help texts for embedded host controller
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-930?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFCORE-930:
----------------------------------
Description:
Help files for embedded host controller are missing.
{noformat}
[disconnected /] embed-host-controller --help
Failed to locate command description help/embed-host-controller.txt
[domain@embedded /] stop-embedded-host-controller --help
Failed to locate command description help/stop-embedded-host-controller.txt
{noformat}
was:
Help files for embedded host controlled are missing.
{noformat}
[disconnected /] embed-host-controller --help
Failed to locate command description help/embed-host-controller.txt
[domain@embedded /] stop-embedded-host-controller --help
Failed to locate command description help/stop-embedded-host-controller.txt
{noformat}
> Missing help texts for embedded host controller
> -----------------------------------------------
>
> Key: WFCORE-930
> URL: https://issues.jboss.org/browse/WFCORE-930
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 2.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Ken Wills
>
> Help files for embedded host controller are missing.
> {noformat}
> [disconnected /] embed-host-controller --help
> Failed to locate command description help/embed-host-controller.txt
> [domain@embedded /] stop-embedded-host-controller --help
> Failed to locate command description help/stop-embedded-host-controller.txt
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months