June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10342) Unsecured EJB causes "Multiple security domains" exception

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10342?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-10342: ----------------------------------- Test added for 14 in https://github.com/wildfly/wildfly/pull/11261 > Unsecured EJB causes "Multiple security domains" exception > ---------------------------------------------------------- > > Key: WFLY-10342 > URL: https://issues.jboss.org/browse/WFLY-10342 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Affects Versions: 12.0.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > Fix For: 13.0.0.Beta1, 13.0.0.Final > > > When trying to deploy deployment containing following two EJBs, secured and unsecured, deploying fails with "Multiple security domains not supported" exception: > {code} > 21:16:30,089 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."ejb-deployment-1.0-SNAPSHOT.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ejb-deployment-1.0-SNAPSHOT.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "ejb-deployment-1.0-SNAPSHOT.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:150) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0490: Multiple security domains not supported > at org.jboss.as.ejb3.deployment.processors.EJBDefaultSecurityDomainProcessor.deploy(EJBDefaultSecurityDomainProcessor.java:99) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:143) > ... 8 more > {code} > This behavior was in JBEAP-9289 considered correct for situation when one EJB references one security domain and the second references second security domain. > It seems unsecured EJB is considered to be using default security domain. > *Workaround:* Need to set unsecured bean secured by adding: > {code} > @PermitAll > @SecurityDomain("other2") // the same as for secured ejb > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2641) Executable model doesn't support parsing of a constraint containing a ternary operator

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2641?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2641. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/c2fae73b7ffd0795a23494bb9260d06... > Executable model doesn't support parsing of a constraint containing a ternary operator > -------------------------------------------------------------------------------------- > > Key: DROOLS-2641 > URL: https://issues.jboss.org/browse/DROOLS-2641 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2642) Executable model doesn't support parsing of a constraint containing a ternary operator

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2642: ----------------------------------- Summary: Executable model doesn't support parsing of a constraint containing a ternary operator Key: DROOLS-2642 URL: https://issues.jboss.org/browse/DROOLS-2642 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2598) PMML - Test GuidedScoreCardIntegrationJavaClassesOnClassPathTest.testIncrementalCompilation fails on Windows or MacOS

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2598?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2598: ---------------------------------- Comment: was deleted (was: I have probably a fix for this. Will make a PR with it for review. ) > PMML - Test GuidedScoreCardIntegrationJavaClassesOnClassPathTest.testIncrementalCompilation fails on Windows or MacOS > --------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2598 > URL: https://issues.jboss.org/browse/DROOLS-2598 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Lance Leverich > > When I run the test GuidedScoreCardIntegrationJavaClassesOnClassPathTest.testIncrementalCompilation [1] on Windows or Mac, it fails. However the test passes on Linux. That implies that something is wrong with incremental compilation with PMML resources when run on case non-sensitive systems. > [1] https://github.com/kiegroup/drools/blob/36eccb8a33550eb2049255f058fe016c6... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2641) Executable model doesn't support parsing of a constraint containing a ternary operator

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2641: ----------------------------------- Summary: Executable model doesn't support parsing of a constraint containing a ternary operator Key: DROOLS-2641 URL: https://issues.jboss.org/browse/DROOLS-2641 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2598) PMML - Test GuidedScoreCardIntegrationJavaClassesOnClassPathTest.testIncrementalCompilation fails on Windows or MacOS

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2598?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-2598: --------------------------------------- I have probably a fix for this. Will make a PR with it for review. > PMML - Test GuidedScoreCardIntegrationJavaClassesOnClassPathTest.testIncrementalCompilation fails on Windows or MacOS > --------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2598 > URL: https://issues.jboss.org/browse/DROOLS-2598 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Lance Leverich > > When I run the test GuidedScoreCardIntegrationJavaClassesOnClassPathTest.testIncrementalCompilation [1] on Windows or Mac, it fails. However the test passes on Linux. That implies that something is wrong with incremental compilation with PMML resources when run on case non-sensitive systems. > [1] https://github.com/kiegroup/drools/blob/36eccb8a33550eb2049255f058fe016c6... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-194) PasswordValidationCallback.clearPassword() does not clear the password.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/JBEE-194?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on JBEE-194: --------------------------------------- https://github.com/jboss/jboss-jaspi-api_spec/pull/7 > PasswordValidationCallback.clearPassword() does not clear the password. > ----------------------------------------------------------------------- > > Key: JBEE-194 > URL: https://issues.jboss.org/browse/JBEE-194 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jaspi-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > > The purpose of clear() methods on classes like this is to zero out the array holding the password, the current implementation just sets the reference to null leaving it to the garbage collector to dispose of - this would happen anyway as soon as the PasswordValidationCallback is eligible for garbage collection, -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-194) PasswordValidationCallback.clearPassword() does not clear the password.

by Darran Lofthouse (JIRA)

Darran Lofthouse created JBEE-194: ------------------------------------- Summary: PasswordValidationCallback.clearPassword() does not clear the password. Key: JBEE-194 URL: https://issues.jboss.org/browse/JBEE-194 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-jaspi-api Reporter: Darran Lofthouse Assignee: Darran Lofthouse The purpose of clear() methods on classes like this is to zero out the array holding the password, the current implementation just sets the reference to null leaving it to the garbage collector to dispose of - this would happen anyway as soon as the PasswordValidationCallback is eligible for garbage collection, -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3937) Error when running configured wildfly

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFCORE-3937: ------------------------------------- Stacktrace is {code} 10:32:24,264 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-103224260: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:498) at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) at java.nio.file.Files.move(Files.java:1395) at org.jboss.as.controller.persistence.ConfigurationFile.forcedMove(ConfigurationFile.java:773) at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:655) at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:500) at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:95) at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:535) at org.jboss.as.server.ServerService.finishBoot(ServerService.java:418) at org.jboss.as.server.ServerService.boot(ServerService.java:388) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:372) at java.lang.Thread.run(Thread.java:748) {code} It's using the same UnixFileSystemProvider. This occurs only with Docker. Could it be related to having different layers? The standalone_xml_history/current/standalone.v1.xml is created by the testing image. However the error occurs when the layer below (from jboss/wildfly:13.0.0.Final) tries to unlink the directory. > Error when running configured wildfly > ------------------------------------- > > Key: WFCORE-3937 > URL: https://issues.jboss.org/browse/WFCORE-3937 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Final > Reporter: Stephen Buergler > Assignee: Jeff Mesnil > Priority: Minor > Attachments: Dockerfile > > > 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current > ... > 08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot. > To reproduce: > docker build -ttesting . > docker run --rm -it testing -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10607) Fix intermittent failures in RemoteEJBForwardingTestCases

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10607?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-10607: --------------------------------------- [~pkremens] Great, thanks. Re: "intermittently failing test" is a general topic not specific to this issue. > Fix intermittent failures in RemoteEJBForwardingTestCases > --------------------------------------------------------- > > Key: WFLY-10607 > URL: https://issues.jboss.org/browse/WFLY-10607 > Project: WildFly > Issue Type: Bug > Components: EJB, Test Suite > Reporter: Petr Kremensky > > The tests were ignored by https://github.com/wildfly/wildfly/pull/10563/files -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 June 2018