April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1509) Add a way to have the management services for Core Model Testing

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1509?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-1509: ----------------------------------------- Assignee: ehsavoie Hugonnet (was: Tomaz Cerar) > Add a way to have the management services for Core Model Testing > ---------------------------------------------------------------- > > Key: WFCORE-1509 > URL: https://issues.jboss.org/browse/WFCORE-1509 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 2.1.0.Final > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Fix the Gigantic HACK to disable the runtime part of this for the core model testing. > The core model testing currently uses RunningMode.ADMIN_ONLY, but in the real world > the http interface needs to be enabled even when that happens. > We don't want to wire up all the services unless wean avoid it, so for now the tests set this system property "jboss.as.test.disable.runtime" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1501) Failure to create timestamped config file history fails boot

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1501?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1501: ------------------------------------- Labels: 2.2 (was: ) > Failure to create timestamped config file history fails boot > ------------------------------------------------------------ > > Key: WFCORE-1501 > URL: https://issues.jboss.org/browse/WFCORE-1501 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Labels: 2.2 > Fix For: 2.2.0.Beta1, 3.0.0.Alpha1 > > > Something like the following shouldn't be allowed to fail a boot; if it happens an ERROR should be logged but no exception thrown: > {code} > 2016-04-22 22:10:21,247 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: java.lang.IllegalStateException: WFLYCTL0056: Could not rename C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\current to C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\20160422-221021244 > at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:668) > at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:500) > at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94) > at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:452) > at org.jboss.as.server.ServerService.boot(ServerService.java:367) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) > at java.lang.Thread.run(Thread.java:745) > {code} > That stack trace indicates file standalone\configuration\standalone_xml_history\20160422-221021144 must already exist but the 2nd attempt renameTo standalone\configuration\standalone_xml_history\20160422-221021244 has failed. It would be good to sort out what happened, but regardless it should not fail boot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1139) Incomplete cloning of the EvalCondition evaluator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1139?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated DROOLS-1139: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1329735, https://bugzilla.redhat.com/show_bug.cgi?id=1330327 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1329735) > Incomplete cloning of the EvalCondition evaluator > ------------------------------------------------- > > Key: DROOLS-1139 > URL: https://issues.jboss.org/browse/DROOLS-1139 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > > An EvalCondition evaluator needs to be cloned when 2 eval nodes have the same condition, but not the same parent and then cannot be shared. This cloning process is currently incomplete because the eval invoker (generated via ASM) remains the same (same instance) for the 2 evaluators thus resulting in an evaluation with wrong params. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6554) Cache configuration are not eagerly defined in Cache Container

by Mathieu Lachance (JIRA)

Mathieu Lachance created WFLY-6554: -------------------------------------- Summary: Cache configuration are not eagerly defined in Cache Container Key: WFLY-6554 URL: https://issues.jboss.org/browse/WFLY-6554 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.Final, 10.1.0.Final Reporter: Mathieu Lachance Assignee: Paul Ferraro In WF8 we used the cache configuration start="EAGER" to force the initialization of the cache configuration. In my scenario, we especially used that trick to define all cache configuration (i.e. entity / timestamps / local-query) in the hibernate cache container before any of our war was deployed. Doing so, when wiring the EntityManager programatically (in our application), we were able to depend on the JNDIRegionFactory without getting any NullPointerException/etc. This trick has only one bad side effect, which was the creation of unecessary caches. Now in WF10, the eager feature is gone and it seems that even if the cache container is available at startup (as discussed in: https://developer.jboss.org/thread/259151) the defined caches are not. I do not know if this is a bug or this is by design but this seems wrong to me. If we define caches within standalone.xml, I would definitly like to have them defined at the container level. I think it's fair to assume that when pulling the CacheManager all defined caches should have been there. I would suggest that when reading all the infinispan subsystem, each cache contained in each cache container be eagerly defined to avoid any issue (and I really meant "defined" and not "started"). Doing so this would resolve our EntityManager second level cache bootstraping without relying on our application to define the missing cache configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1508) CLI prompt is not displayed after the first command line executed

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-1508: ----------------------------------------- Summary: CLI prompt is not displayed after the first command line executed Key: WFCORE-1508 URL: https://issues.jboss.org/browse/WFCORE-1508 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 3.0.0.Alpha1 This issue appeared after the fix for WFCORE-1315 In interactive mode the prompt is not displayed after the first command line execution. It is correctly displayed afterwards. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1506) Add a HostControllerEnvironmentService

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1506?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1506: ------------------------------------- Labels: 2.2 (was: ) > Add a HostControllerEnvironmentService > -------------------------------------- > > Key: WFCORE-1506 > URL: https://issues.jboss.org/browse/WFCORE-1506 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Labels: 2.2 > Fix For: 3.0.0.Alpha1 > > > On servers we add a ServerEnvironmentService giving subsystems access to the ServerEnvironment. > For the host controller subsystems it would be useful to have something similar to allow access to the HostControllerEnvironment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1507) Expose the ModelController via a capability

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1507: ---------------------------------------- Summary: Expose the ModelController via a capability Key: WFCORE-1507 URL: https://issues.jboss.org/browse/WFCORE-1507 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry A server installs ServerService while an HC installs DomainModelControllerService, under different service names but both of which implement Service<ModelController>. To make it easier for subsystems that want ModelController access to work on both a server and an HC, we should create a capability with service type ModelController and have both processes use it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1506) Add a HostControllerEnvironmentService

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1506?page=com.atlassian.jira.plugi... ] Kabir Khan reassigned WFCORE-1506: ---------------------------------- Assignee: Kabir Khan (was: Brian Stansberry) > Add a HostControllerEnvironmentService > -------------------------------------- > > Key: WFCORE-1506 > URL: https://issues.jboss.org/browse/WFCORE-1506 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha1 > > > On servers we add a ServerEnvironmentService giving subsystems access to the ServerEnvironment. > For the host controller subsystems it would be useful to have something similar to allow access to the HostControllerEnvironment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1501) Failure to create timestamped config file history fails boot

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1501?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1501: ------------------------------------------ I believe the WFCORE-1078 fix is responsible for making this more apparent in CI, since it resulted in the problematic code path being called as part of every reload. > Failure to create timestamped config file history fails boot > ------------------------------------------------------------ > > Key: WFCORE-1501 > URL: https://issues.jboss.org/browse/WFCORE-1501 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.2.0.Beta1, 3.0.0.Alpha1 > > > Something like the following shouldn't be allowed to fail a boot; if it happens an ERROR should be logged but no exception thrown: > {code} > 2016-04-22 22:10:21,247 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: java.lang.IllegalStateException: WFLYCTL0056: Could not rename C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\current to C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\20160422-221021244 > at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:668) > at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:500) > at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94) > at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:452) > at org.jboss.as.server.ServerService.boot(ServerService.java:367) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) > at java.lang.Thread.run(Thread.java:745) > {code} > That stack trace indicates file standalone\configuration\standalone_xml_history\20160422-221021144 must already exist but the 2nd attempt renameTo standalone\configuration\standalone_xml_history\20160422-221021244 has failed. It would be good to sort out what happened, but regardless it should not fail boot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1504) Add /core-service=service-container resource to host model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1504?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1504: ------------------------------------------ I put a "2.2" label on this to track it for consideration for cherry-picking into any 2.2.0 release we do for WF 10.1. But this one is ineligible; it's a management API change and I don't want a new API version out there. We can reconsider this if we end up with a new version anyway. > Add /core-service=service-container resource to host model > ---------------------------------------------------------- > > Key: WFCORE-1504 > URL: https://issues.jboss.org/browse/WFCORE-1504 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha1 > > > {quote} > Kabir Khan·17:30 > @BrianStansberry I'm replying to mazz > Just trying to dump services though, is there any reason why we have /core-service=service-container on a server, but no /host=master/core-service=service-container on a HC? > Brian Stansberry·17:37 > @KabirKhan I don't think so > for some reason I was poking at that a few days ago and I couldn't find any reason why not > Kabir Khan·17:37 > I'll add a Jira > Brian Stansberry·17:37 > I think it's something historical that no longer applies > Kabir Khan·17:37 > Probably just an oversight > we had jconsole all the time > and probably enhanced this for servers at some stage > Brian Stansberry·17:38 > I'm quite certain I put that TODO in there and there was a real reason at the time > Kabir Khan·17:38 > where is the TODO? > Brian Stansberry·17:40 > @KabirKhan https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m... > {quote} > So we should > a) investigate if this is possible or not > b) Make it happen if it is -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016