February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8007) Replace WorkManager elytron-enabled atttribute by elytron-security-domain

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-8007?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-8007: ------------------------------------- [~flavia.rainone] I'm not sure if I'll have the time. I'm trying to get Arquillian to work with Elytron and I've got some days of PTO coming up. If I get done with the Arquillian stuff quickly I'll let you know though. I'm just currently having issues with it. > Replace WorkManager elytron-enabled atttribute by elytron-security-domain > ------------------------------------------------------------------------- > > Key: WFLY-8007 > URL: https://issues.jboss.org/browse/WFLY-8007 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Reporter: Flavia Rainone > Assignee: James Perkins > > Right now the elytron-enabled attribute does not allow the dependency on the security domain capability. We need to replace it by elytron-security-domain and have the capability dependency sorted out. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1420) (int) ($p * 1_000.0) throws a misleading exception

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1420?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1420. --------------------------------- Fix Version/s: 7.0.0.CR1 Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/d70058bb6ea7516a0054ef5063d94... > (int) ($p * 1_000.0) throws a misleading exception > -------------------------------------------------- > > Key: DROOLS-1420 > URL: https://issues.jboss.org/browse/DROOLS-1420 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta5 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.CR1 > > > This fails with *$p cannot be resolved to a variable*: > {code} > rule R when > Cheese($p : price) > then > int b = (int) ($p * 1_000.0); // FAILS, because $p cannot be resolved ?! > end > {code} > That error message is nonsense. It should just work. If it doesn't due to ECJ, it should say something like "cannot be cast". > This works in java: > {code} > int a = 42; > int b = ((int) (a * 1_000.0)); > {code} > Removing the underscore fixes it: > {code} > rule R when > Cheese($p : price) > then > int b = (int) ($p * 1000.0); // SUCCESS > end > {code} > Regardless of an upstream ECJ problem (which should be reported if that's indeed the problem), the error message is wrong and send me on a wild goose hunt. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8014) Remote store cannot be added to a cache via CLI

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/WFLY-8014?page=com.atlassian.jira.plugin.... ] Michal Petrov commented on WFLY-8014: ------------------------------------- [~pferraro] okay, but why is the flag needed for store=remote but not for store=file? > Remote store cannot be added to a cache via CLI > ----------------------------------------------- > > Key: WFLY-8014 > URL: https://issues.jboss.org/browse/WFLY-8014 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Michal Petrov > Assignee: Paul Ferraro > > It is not possible to add remote store to a new cache: > {quote} > /subsystem=infinispan/cache-container=web/local-cache=myCache/store=remote:add(remote-servers=\[mail-smtp\]) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache-configuration.web.myCache.store is already registered", > "rolled-back" => true > } > {quote} > However it is possible to add a file store: > {{/subsystem=infinispan/cache-container=web/local-cache=myCache/store=file:add}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-662) Autopublish drools-website, optaplanner-website and jbpm-website through travis

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-662?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer commented on DROOLS-662: ----------------------------------------------- done: see https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Websites/ it was tested and it works. When a commit was pushed to one of the websites, it will automatically run one of these three jobs which creates a Docker images based on the Dockerfile in the respective web in _dockerPublisher, runs a Docker Container which does a rake setup, rake clean build and rake publish. > Autopublish drools-website, optaplanner-website and jbpm-website through travis > ------------------------------------------------------------------------------- > > Key: DROOLS-662 > URL: https://issues.jboss.org/browse/DROOLS-662 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > > The jboss-tools guys already auto publish their awestruct website. xcoulon on irc #awestruct told me how they do this at Devoxx. > Travis is like Jenkins, but works really well for ruby stuff (such as awestruct websites). It can publish our websites automatically if we push a commit. Here's how to set it up: > - Add a .travis.yml file, look at this one for inspiration: https://github.com/jbosstools/jbosstools-website/blob/master/.travis.yml > - Get a secret token to be able to publish a website on jboss.org filemanagement server. Then encrypt that secret token with Travis's public key (so only Travis can decrypt it). Write the encrypted secret token in the travis.yml file. Remove all knowledge of the actual secret token, so it can't leak. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-662) Autopublish drools-website, optaplanner-website and jbpm-website through travis

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-662?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer closed DROOLS-662. ----------------------------------------- Resolution: Done > Autopublish drools-website, optaplanner-website and jbpm-website through travis > ------------------------------------------------------------------------------- > > Key: DROOLS-662 > URL: https://issues.jboss.org/browse/DROOLS-662 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > > The jboss-tools guys already auto publish their awestruct website. xcoulon on irc #awestruct told me how they do this at Devoxx. > Travis is like Jenkins, but works really well for ruby stuff (such as awestruct websites). It can publish our websites automatically if we push a commit. Here's how to set it up: > - Add a .travis.yml file, look at this one for inspiration: https://github.com/jbosstools/jbosstools-website/blob/master/.travis.yml > - Get a secret token to be able to publish a website on jboss.org filemanagement server. Then encrypt that secret token with Travis's public key (so only Travis can decrypt it). Write the encrypted secret token in the travis.yml file. Remove all knowledge of the actual secret token, so it can't leak. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8014) Remote store cannot be added to a cache via CLI

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8014?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-8014. ------------------------------ Resolution: Rejected You must use the allow-resource-service-restart=true invocation flag, since the addition of the file cache-store implies the removal of the existing store=none resource. e.g. {noformat} /subsystem=infinispan/cache-container=web/local-cache=myCache/store=file:add(){allow-resource-service-restart=true} {noformat} Note that the above command automatically removes the existing default store=none resource. This one liner is equivalent to the following: {noformat} batch /subsystem=infinispan/cache-container=web/local-cache=myCache/store=none:remove(){allow-resource-service-restart=true} /subsystem=infinispan/cache-container=web/local-cache=myCache/store=file:add() run-batch {noformat} > Remote store cannot be added to a cache via CLI > ----------------------------------------------- > > Key: WFLY-8014 > URL: https://issues.jboss.org/browse/WFLY-8014 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Michal Petrov > Assignee: Paul Ferraro > > It is not possible to add remote store to a new cache: > {quote} > /subsystem=infinispan/cache-container=web/local-cache=myCache/store=remote:add(remote-servers=\[mail-smtp\]) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache-configuration.web.myCache.store is already registered", > "rolled-back" => true > } > {quote} > However it is possible to add a file store: > {{/subsystem=infinispan/cache-container=web/local-cache=myCache/store=file:add}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8014) Remote store cannot be added to a cache via CLI

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/WFLY-8014?page=com.atlassian.jira.plugin.... ] Michal Petrov commented on WFLY-8014: ------------------------------------- This might be two different issues. From what I'm able to tell the file store is not installed through {{ResourceServiceHandler.installServices()}} and somehow skips the check for an existing service. Even then the problem is that store=none is treated as an existing service when it's meant to be overwritten. > Remote store cannot be added to a cache via CLI > ----------------------------------------------- > > Key: WFLY-8014 > URL: https://issues.jboss.org/browse/WFLY-8014 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Michal Petrov > Assignee: Paul Ferraro > > It is not possible to add remote store to a new cache: > {quote} > /subsystem=infinispan/cache-container=web/local-cache=myCache/store=remote:add(remote-servers=\[mail-smtp\]) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache-configuration.web.myCache.store is already registered", > "rolled-back" => true > } > {quote} > However it is possible to add a file store: > {{/subsystem=infinispan/cache-container=web/local-cache=myCache/store=file:add}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8014) Remote store cannot be added to a cache via CLI

by Michal Petrov (JIRA)

Michal Petrov created WFLY-8014: ----------------------------------- Summary: Remote store cannot be added to a cache via CLI Key: WFLY-8014 URL: https://issues.jboss.org/browse/WFLY-8014 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 11.0.0.Alpha1 Reporter: Michal Petrov Assignee: Paul Ferraro It is not possible to add remote store to a new cache: {quote} /subsystem=infinispan/cache-container=web/local-cache=myCache/store=remote:add(remote-servers=\[mail-smtp\]) { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache-configuration.web.myCache.store is already registered", "rolled-back" => true } {quote} However it is possible to add a file store: {{/subsystem=infinispan/cache-container=web/local-cache=myCache/store=file:add}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7912) It's not possible to change election-policy of singleton-policy

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-7912?page=com.atlassian.jira.plugin.... ] Tomas Hofman commented on WFLY-7912: ------------------------------------ Right, that works, thanks for explanation. > It's not possible to change election-policy of singleton-policy > --------------------------------------------------------------- > > Key: WFLY-7912 > URL: https://issues.jboss.org/browse/WFLY-7912 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Tomas Hofman > Assignee: Paul Ferraro > > Attempt to change election policy: > {code} > [standalone@localhost:9990 /] batch > [standalone@localhost:9990 / #] /subsystem=singleton/singleton-policy=default/election-policy=simple:remove > [standalone@localhost:9990 / #] /subsystem=singleton/singleton-policy=default/election-policy=random:add > [standalone@localhost:9990 / #] run-batch > {code} > results in > {code} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): > WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: > Step: step-2 > Operation: /subsystem=singleton/singleton-policy=default/election-policy=random:add > Failure: WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.singleton.policy.default.election-policy is already registered > {code} > The bug seems to be introduced by https://github.com/wildfly/wildfly/commit/605b22c30ae122492e7c019e330fea2... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8013) Out of memory exception after a number of remote deploys

by Tiago Matias (JIRA)

[ https://issues.jboss.org/browse/WFLY-8013?page=com.atlassian.jira.plugin.... ] Tiago Matias updated WFLY-8013: ------------------------------- Environment: Server: Ubuntu 16.04.1 LTS x64 bq. bq. Startup arguments: bq. bq. bq. java -D[Standalone] -server -Xms256m -Xmx8096m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties -jar /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -c standalone.xml -b 0.0.0.0 was: Server: Ubuntu 16.04.1 LTS x64 Startup arguments: java -D[Standalone] -server -Xms256m -Xmx8096m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties -jar /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -c standalone.xml -b 0.0.0.0 > Out of memory exception after a number of remote deploys > -------------------------------------------------------- > > Key: WFLY-8013 > URL: https://issues.jboss.org/browse/WFLY-8013 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 10.1.0.Final > Environment: Server: Ubuntu 16.04.1 LTS x64 > bq. > bq. Startup arguments: > bq. > bq. > bq. java -D[Standalone] -server -Xms256m -Xmx8096m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties -jar /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -c standalone.xml -b 0.0.0.0 > Reporter: Tiago Matias > Assignee: Jason Greene > Priority: Minor > > Using the wildfly-maven-plugin for remotely deploying a WAR file do Wildfly and, after a few deploys (between 5 and 10) An outofmemory error emerges, requiring a full server restart. > *Full error log of maven.* > {quote} > [INFO] Authenticating against security realm: ManagementRealm > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 47.630 s > [INFO] Finished at: 2017-02-02T15:38:04+00:00 > [INFO] Final Memory: 22M/290M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Final:deploy (default) on project MyProject: Failed to execute goal deploy: {"WFLYCTL0062: Composite operation failed and was rolled back > . Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"backoffice.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\" > backoffice.war\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"backoffice.war\" > [ERROR] Caused by: java.lang.OutOfMemoryError: Metaspace"},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"MyProject.war\".POST_MODULE"],"WFLYCTL0180: Services with missing/una > vailable dependencies" => undefined}}} > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

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 February 2017