April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-43) Clarify the meaning of the 'server-state' and 'host-state' attributes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-43?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFCORE-43: ---------------------------------------- If this slips to 2.0.0.Beta1 that's fine. Please reschedule it if you think that's likely. > Clarify the meaning of the 'server-state' and 'host-state' attributes > --------------------------------------------------------------------- > > Key: WFCORE-43 > URL: https://issues.jboss.org/browse/WFCORE-43 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: luck3y > Fix For: 1.0.0.CR1 > > > This JIRA is to implement what I described in the dev list discussion around the various states a server can be in for graceful shutdown (http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002360.html) > "I do think these are orthogonal and should not be combined. > The existing attribute is fundamentally about how the state of the > runtime services relates to the persistent configuration. > STARTING == out of sync due to still getting in sync during start > RUNNING == in sync > RELOAD_REQURIRED = out of sync, needs a reload to get in sync > RESTART_REQUIRED = out of sync, needs a full process restart to get in sync > There are two problems though with the existing attribute that exposes this: > 1) It's named "server-state" on a server and "host-state" on a Host > Controller. Really crappy name; way too broad. > That's fixable by creating a new attribute and making the old one an > alias for compatibility purposes. > 2) The RUNNING state is really poorly named. > The could perhaps be fixed by coming up with a new name and translating > it back to "RUNNING" in the handlers for the legacy "server-state" and > "host-state" attributes." -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-379) Give option to make the content repository browsable

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-379?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-379: --------------------------------------- Fix Version/s: (was: 1.0.0.CR1) Assignee: luck3y Ken, I'm assigning this to you as it's in the area of content repository management where you have a couple other tasks. > Give option to make the content repository browsable > ---------------------------------------------------- > > Key: WFCORE-379 > URL: https://issues.jboss.org/browse/WFCORE-379 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Ben Schofield > Assignee: luck3y > > JBoss admins regularly need to view the application content that is deployed to a server. On previous versions of JBoss this was easy to do with the deploy directory. When using the new API to install applications the contents of applications are not easily browsable or searchable. > Would like to have a setting that enables all content to be stored in exploded format in the content repository. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-626) Global list-get operation can inadvertently create list elements

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-626?page=com.atlassian.jira.plugin... ] Tomaz Cerar commented on WFCORE-626: ------------------------------------ tests for global collection operations are in org.jboss.as.controller.operation.global.CollectionOperationsTestCase. I agree that fix is correct, i just want to also add tests for this, for future proofing it. > Global list-get operation can inadvertently create list elements > ---------------------------------------------------------------- > > Key: WFCORE-626 > URL: https://issues.jboss.org/browse/WFCORE-626 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Beta2 > Reporter: Paul Ferraro > Assignee: Tomaz Cerar > Fix For: 1.0.0.CR1 > > > Consider the following sequence of operations: > # :list-clear(name=attribute) > # :list-get(name=attribute, index=0) > # :list-add(name=attribute, value=test) > # :list-get(name=attribute, index=0) > #2 will return <undefined> as expected. The expected result of #4 is "test". However, it returns <undefined>. This is because #2 will create the missing element at index 0 causing #3 to operate on index 1. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-626) Global list-get operation can inadvertently create list elements

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFCORE-626?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFCORE-626: ------------------------------------- Thanks. I didn't find any tests for these global operations - though I validated this particular fix against my tests for WFLY-4488. > Global list-get operation can inadvertently create list elements > ---------------------------------------------------------------- > > Key: WFCORE-626 > URL: https://issues.jboss.org/browse/WFCORE-626 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Beta2 > Reporter: Paul Ferraro > Assignee: Tomaz Cerar > Fix For: 1.0.0.CR1 > > > Consider the following sequence of operations: > # :list-clear(name=attribute) > # :list-get(name=attribute, index=0) > # :list-add(name=attribute, value=test) > # :list-get(name=attribute, index=0) > #2 will return <undefined> as expected. The expected result of #4 is "test". However, it returns <undefined>. This is because #2 will create the missing element at index 0 causing #3 to operate on index 1. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4488) Replace Infinispan cache-container add-alias/remove-alias operations with global list operations

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-4488: ---------------------------------- Summary: Replace Infinispan cache-container add-alias/remove-alias operations with global list operations Key: WFLY-4488 URL: https://issues.jboss.org/browse/WFLY-4488 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 9.0.0.Beta2 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 9.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-387) Describe inheritance relationships in the resource description metadata

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-387?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-387: ------------------------------------ Fix Version/s: (was: 1.0.0.CR1) > Describe inheritance relationships in the resource description metadata > ----------------------------------------------------------------------- > > Key: WFCORE-387 > URL: https://issues.jboss.org/browse/WFCORE-387 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > > Some elements in the management model have an inheritance relationship with other elements located elsewhere. For example, system properties can be defined as a child of the root domain resource, as a child of a server-group resource, as a child of the root host resource, and as a child of the server-config resource. > The resource description metadata for a resource needs to describe these relationships. It needs to cover the inheritance hierarchy, as well as how any conflicts are resolved (i.e. does the child win, as is the case with system properties and interfaces, or is some sort of merging strategy employed, as is the case with profiles and socket-binding-groups, where the sets of child resources (subsystems and socket-bindings) are merged, provided that the two sets are disjoint. > A factor to include in this metadata is whether the relationship is fixed (i.e. host system-property inherits from server-group) or whether there is some attribute that defines the inheritance (e.g. a profile's that "includes" another profile has an attribute that defines the name of the included profile.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-622) DomainOperationContext transformation assumes slave host and slave host's servers receive the same ops

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-622?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-622: --------------------------------------- Fix Version/s: 2.0.0.CR1 (was: 1.0.0.CR1) Assignee: (was: Brian Stansberry) https://github.com/wildfly/wildfly-core/pull/597 (for WFCORE-282) has a partial workaround for this issue. > DomainOperationContext transformation assumes slave host and slave host's servers receive the same ops > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-622 > URL: https://issues.jboss.org/browse/WFCORE-622 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 2.0.0.CR1 > > > https://github.com/wildfly/wildfly-core/commit/f5c516f2#diff-dc2038399fc7... assumes that the result transformer for the host request is appropriate for use with the subsequent requests to that host's servers during domain rollout. > That's a shaky supposition, as the server ops generated from a host request have no fixed relationship to the host request itself. Alignment is the norm but not a rule. In particular it can faill apart with composite ops where some steps in the composite are not relevant to all hosts. > Without this extra transformation, test at [1] fails. This indicates the server op is not getting the transformation registered at [2] applied. But if it's not getting the result transformation applied, wouldn't that mean relevant operation transformation isn't being applied as well? > [1] https://github.com/wildfly/wildfly-core/blob/master/testsuite/domain/src/... > [2] https://github.com/wildfly/wildfly-core/blob/master/testsuite/domain/src/... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3290) Cannot use a cluster name other than "ejb"

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-3290?page=com.atlassian.jira.plugin.... ] Paul Ferraro resolved WFLY-3290. -------------------------------- Fix Version/s: 9.0.0.CR1 Resolution: Out of Date This is no longer an issue as of WF9. Infinispan transports are configured with a specific channel - so the cluster name can be manipulated via using different channels. > Cannot use a cluster name other than "ejb" > ------------------------------------------ > > Key: WFLY-3290 > URL: https://issues.jboss.org/browse/WFLY-3290 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Chris Stillwell > Assignee: Panagiotis Sotiropoulos > Priority: Critical > Fix For: 9.0.0.CR1 > > Attachments: helloworld-test.zip > > > When deploying a clustered session bean the cluster will form only if the cluster name is "ejb". If the standalone-ha.xml is modified to use a different cluster name then the cluster will not form. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-757) Upgrade maven from 3.2.2 to latest 3.2.x release

by Petr Široký (JIRA)

Petr Široký created DROOLS-757: ---------------------------------- Summary: Upgrade maven from 3.2.2 to latest 3.2.x release Key: DROOLS-757 URL: https://issues.jboss.org/browse/DROOLS-757 Project: Drools Issue Type: Task Components: tools Affects Versions: 6.2.0.Final Reporter: Petr Široký Assignee: Petr Široký Currently used maven 3.2.2 has nasty bug related to resolving imported dependencies from additional repos, see https://jira.codehaus.org/browse/MNG-5663 . I believe we should upgrade to the latest 3.2.x release. It seems only {{kie-ci}} and {{kie-maven-plugin}} should directly depend on maven. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4198) NullPointerException in LogDiagnosticContextRecoveryInterceptor when calling an asynchronous EJB

by Sergiy Barlabanov (JIRA)

[ https://issues.jboss.org/browse/WFLY-4198?page=com.atlassian.jira.plugin.... ] Sergiy Barlabanov updated WFLY-4198: ------------------------------------ Attachment: patch.diff > NullPointerException in LogDiagnosticContextRecoveryInterceptor when calling an asynchronous EJB > ------------------------------------------------------------------------------------------------ > > Key: WFLY-4198 > URL: https://issues.jboss.org/browse/WFLY-4198 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.2.0.Final > Reporter: Sergiy Barlabanov > Assignee: Bartosz Baranowski > Attachments: patch.diff > > > When trying to call an asynchronous EJB in a Web application using slf4j (1.7.5+) & logback(1.0.13+) for logging the following NullPointerException occurs (see below). > The problem is in the line 67 of LogDiagnosticContextRecoveryInterceptor class, when it tries to access MDC map, which is null. According to SLF4J API the copy of MDC map may be null: see the javadoc of org.slf4j.MDC#getCopyOfContextMap. > So LogDiagnosticContextRecoveryInterceptor or org.jboss.logging.Slf4jLoggerProvider have to check the map for null. > Currently there is no workaround for that :(. > {noformat} > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.component.interceptors.LogDiagnosticContextRecoveryInterceptor.processInvocation(LogDiagnosticContextRecoveryInterceptor.java:67) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AsyncFutureInterceptorFactory$1$2.runInvocation(AsyncFutureInterceptorFactory.java:97) > at org.jboss.as.ejb3.component.interceptors.AsyncInvocationTask.run(AsyncInvocationTask.java:73) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 April 2015