[JBoss JIRA] (WFCORE-313) DefaultOperationDescriptionProvider uses incorrect call to create reply parameter description
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-313?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-2947 to WFCORE-313:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-313 (was: WFLY-2947)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> DefaultOperationDescriptionProvider uses incorrect call to create reply parameter description
> ---------------------------------------------------------------------------------------------
>
> Key: WFCORE-313
> URL: https://issues.jboss.org/browse/WFCORE-313
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> When creating reply descriptions, DefaultOperationDescriptionProvider calls attributeDescriptionResolver.getOperationParameterDescription instead of attributeDescriptionResolver.getOperationReplyValueTypeDescription.
> A fix needs to not break compatibility for existing users of the incorrect behavior; i.e. call the correct method in a try block, catch any MissingResourceException, and if caught call the incorrect method.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-311) Better error message if authentication is required to connect to the master but no realm is associated on the slave
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-311?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3035 to WFCORE-311:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-311 (was: WFLY-3035)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.CR1
(was: 9.0.0.Beta1)
> Better error message if authentication is required to connect to the master but no realm is associated on the slave
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-311
> URL: https://issues.jboss.org/browse/WFCORE-311
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Environment: RH EL 6.3 - JBoss EAP 6.2
> Reporter: Riccardo Benvenuti
> Priority: Minor
> Fix For: 1.0.0.CR1
>
>
> In JBoss 6.2 domain environment if in the host.xml file on the slave is missing the realm in the domain-controller tag as reported below
> <domain-controller>
> <remote host="10.123.137.200" port="9999"/>
> </domain-controller>
> we get the following error:
> JBoss Bootstrap Environment
> JBOSS_HOME: /opt/jboss7/jboss-eap-6.2
> JAVA: /usr/java/jdk1.7.0_51/bin/java
> JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:45:58,529 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
> 16:45:58,746 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 16:45:59,735 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
> [Host Controller] 16:45:59,913 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
> [Host Controller] 16:46:00,023 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting
> [Host Controller] 16:46:00,991 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1
> [Host Controller] 16:46:01,010 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
> [Host Controller] 16:46:01,033 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)
> [Host Controller] 16:46:01,045 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.18.GA-redhat-1
> [Host Controller] 16:46:01,173 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 10.123.137.201:9999
> [Host Controller] 16:46:01,857 ERROR [org.jboss.remoting.remote.connection] (Remoting "testjb7s1:MANAGEMENT" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> [Host Controller] 16:46:01,869 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS010942: Unable to connect due to authentication failure.
> [Host Controller] 16:46:01,891 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report
> [Host Controller] JBAS014775: New missing/unsatisfied dependencies:
> [Host Controller] service jboss.server.controller.management.security_realm.ApplicationRealm.properties_authentication (missing) dependents: [service jboss.server.controller.management.security_realm.ApplicationRealm]
> [Host Controller]
> [Host Controller] 16:46:01,897 INFO [org.jboss.as.controller] (MSC service thread 1-1) JBAS014774: Service status report
> [Host Controller] JBAS014775: New missing/unsatisfied dependencies:
> [Host Controller] service jboss.server.controller.management.security_realm.ManagementRealm (missing) dependents: [service jboss.remoting.authentication_provider.management]
> [Host Controller]
> [Host Controller] 16:46:01,922 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report
> [Host Controller] JBAS014776: Newly corrected services:
> [Host Controller] service jboss.server.controller.management.security_realm.ApplicationRealm.properties_authentication (no longer required)
> [Host Controller] service jboss.server.controller.management.security_realm.ManagementRealm (no longer required)
> [Host Controller]
> [Host Controller] 16:46:01,927 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) stopped in 28ms
> 16:46:02,245 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 99
> 16:46:02,247 INFO [org.jboss.as.process] (Thread-8) JBAS012016: Shutting down process controller
> 16:46:02,247 INFO [org.jboss.as.process] (Thread-8) JBAS012015: All processes finished; exiting
> Adding the realm everything works correctly
> <domain-controller>
> <remote host="10.123.137.200" port="9999" security-realm="ManagementRealm"/>
> </domain-controller>
> Maybe a warning message could be useful to find the problem.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-312) Taking thread dumps via HC
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-312?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3025 to WFCORE-312:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-312 (was: WFLY-3025)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
> Taking thread dumps via HC
> --------------------------
>
> Key: WFCORE-312
> URL: https://issues.jboss.org/browse/WFCORE-312
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: James Livingston
> Assignee: James Livingston
>
> It would be useful to be able to gather low-level per-server information such as Java thread dumps. This would best be gathered from the Host Controllers, and be available via the management model.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-310) Don't copy the contents to all hosts when assigning a deployment to a server-group
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-310?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-310:
-----------------------------------------
Emanuel, could you update the title and description of this to reflect the private comments in https://bugzilla.redhat.com/show_bug.cgi?id=1073585 ? Basically, we already have ignore-unused-configuration for this, but we need to tighten up the relationship of this to --backup, --cached-dc, etc and look into have the default behavior to be ignoring, at least in some cases. Let's use this JIRA for that work.
> Don't copy the contents to all hosts when assigning a deployment to a server-group
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-310
> URL: https://issues.jboss.org/browse/WFCORE-310
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Emanuel Muckenhuber
> Assignee: Emanuel Muckenhuber
> Fix For: 1.0.0.CR1
>
>
> When assigning a deployment to a server-group it also copies the actual deployment contents to all hosts regardless of the whether the deployment is used locally or not. This should be changed that the contents are only retrieved if they are actually needed on a local server.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-310) Don't copy the contents to all hosts when assigning a deployment to a server-group
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-310?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3110 to WFCORE-310:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-310 (was: WFLY-3110)
Issue Type: Enhancement (was: Bug)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.CR1
(was: 9.0.0.Beta1)
> Don't copy the contents to all hosts when assigning a deployment to a server-group
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-310
> URL: https://issues.jboss.org/browse/WFCORE-310
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Emanuel Muckenhuber
> Assignee: Emanuel Muckenhuber
> Fix For: 1.0.0.CR1
>
>
> When assigning a deployment to a server-group it also copies the actual deployment contents to all hosts regardless of the whether the deployment is used locally or not. This should be changed that the contents are only retrieved if they are actually needed on a local server.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-309) system properties are trim()'d and loose whitespace
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-309?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFCORE-309:
---------------------------------------
Assignee: Tom Fonteyne (was: Brian Stansberry)
Tom, you mentioned sending up a PR for this. Do you still intend to do that? If not, please reassign back to me.
We should do this soon if we want it in WF 9.
> system properties are trim()'d and loose whitespace
> ---------------------------------------------------
>
> Key: WFCORE-309
> URL: https://issues.jboss.org/browse/WFCORE-309
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Tom Fonteyne
> Assignee: Tom Fonteyne
> Fix For: 1.0.0.Beta1
>
>
> When a system property was defined as:
> /system-property=foo:add(value=" spaces ");
> it gets written with the correct spaces around it to the configuration file.
> When the configuration is read the value gets trimmed and the prefix/suffix of spaces is lost.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-309) system properties are trim()'d and loose whitespace
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-309?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3170 to WFCORE-309:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-309 (was: WFLY-3170)
Affects Version/s: (was: 8.1.0.CR1)
Component/s: Domain Management
(was: Domain Management)
> system properties are trim()'d and loose whitespace
> ---------------------------------------------------
>
> Key: WFCORE-309
> URL: https://issues.jboss.org/browse/WFCORE-309
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Tom Fonteyne
> Assignee: Brian Stansberry
>
> When a system property was defined as:
> /system-property=foo:add(value=" spaces ");
> it gets written with the correct spaces around it to the configuration file.
> When the configuration is read the value gets trimmed and the prefix/suffix of spaces is lost.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-308) Switch default of skip-group-loading to 'true' for local auth.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-308?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3216 to WFCORE-308:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-308 (was: WFLY-3216)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Switch default of skip-group-loading to 'true' for local auth.
> --------------------------------------------------------------
>
> Key: WFCORE-308
> URL: https://issues.jboss.org/browse/WFCORE-308
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Beta1
>
>
> The new attribute skip-group-loading was added to the local authentication definition by WFLY-3048 this needed to have a default of false for backwards compatibility purposes however in reality most would probably assume a default of true.
> For WildFly 9 switch the default to true. This change in default should probably only occur if the schema version is 3 or above.
> A transformer should not be required as this is not configuration that is propagated around a domain.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-307) When Wildfly fails with JBAS015810: failed to resolve interface management, it should terminate.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-307?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3264 to WFCORE-307:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-307 (was: WFLY-3264)
Affects Version/s: (was: 8.1.0.CR1)
Component/s: Domain Management
(was: Domain Management)
> When Wildfly fails with JBAS015810: failed to resolve interface management, it should terminate.
> ------------------------------------------------------------------------------------------------
>
> Key: WFCORE-307
> URL: https://issues.jboss.org/browse/WFCORE-307
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Jay Kumar SenSharma
>
> - When Wildfly fails with **JBAS015810: failed to resolve interface management**, it should terminate rather than dangling.
> - When starting the Wildfly with an IP address which is non-existent, you get the error 'JBAS015810: failed to resolve interface management'.
> -The server starts, but with the error message :
> {code}
> 10:41:15,390 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public
> at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:96) [wildfly-server-8.1.0.CR1.jar:8.1.0.CR1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> 10:41:15,390 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
> at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:96) [wildfly-server-8.1.0.CR1.jar:8.1.0.CR1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> {code}
> - Since the server could not bind to the given address and port, and neither the cli nor the admin console are enabled, the server is as good as dead. The server should exit instead of starting up with errors when this of error is seen .
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months