October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2138) Cannot add security realm child resources in a domain

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2138?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2138: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Cannot add security realm child resources in a domain > ----------------------------------------------------- > > Key: WFLY-2138 > URL: https://issues.jboss.org/browse/WFLY-2138 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Critical > Fix For: 8.0.0.CR1 > > > /] /host=master/core-service=management/security-realm=JBossTest:add > { > "outcome" => "success", > "result" => undefined, > "server-groups" => undefined > } > [domain@localhost:9990 /] /host=master/core-service=management/security-realm=JBossTest/authentication=properties:add(path=application-users.properties, relative-to=jboss.server.config.dir) > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.", > "rolled-back" => true, > "server-groups" => {"main-server-group" => {"host" => {"master" => { > "server-one" => {"response" => { > "outcome" => "failed", > "failure-description" => "JBAS014883: No resource definition is registered for address [ > (\"host\" => \"master\"), > (\"core-service\" => \"management\"), > (\"security-realm\" => \"JBossTest\"), > (\"authentication\" => \"properties\") > ]", > "rolled-back" => true > }}, > "server-two" => {"response" => { > "outcome" => "failed", > "failure-description" => "JBAS014883: No resource definition is registered for address [ > (\"host\" => \"master\"), > (\"core-service\" => \"management\"), > (\"security-realm\" => \"JBossTest\"), > (\"authentication\" => \"properties\") > ]", > "rolled-back" => true > }} > }}}} > } > Note the addresses in the server level failure messages. It appears the /host=master level is not being stripped from the request to the server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2128) Support one-port connection for JMS

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2128?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2128: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Support one-port connection for JMS > ----------------------------------- > > Key: WFLY-2128 > URL: https://issues.jboss.org/browse/WFLY-2128 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 8.0.0.Alpha4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > Fix For: 8.0.0.CR1 > > > WildFly 8 needs to support one-port where all the remote connections goes through HTTP with Upgrade header. > A JMS client will be able to connect to WildFly's HTTP port to access its JMS resources instead of connecting to the TCP socket on HornetQ remote port (5445). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2119) RBAC-based tab completion for the CLI commands

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2119?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2119: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > RBAC-based tab completion for the CLI commands > ---------------------------------------------- > > Key: WFLY-2119 > URL: https://issues.jboss.org/browse/WFLY-2119 > Project: WildFly > Issue Type: Sub-task > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Labels: RBAC-WF-only > Fix For: 8.0.0.CR1 > > > With the RBAC in place, the CLI tab-completion should take the advantage (where possible and reasonable) and suggest only the commands, arguments and argument values that are available and allowed to be executed by the current user. > Since performing access control checks may be time consuming (especially in the domain mode) this feature should be optional and exposed through CLI configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2207) CLI Unable to connect using https-remoting address.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2207?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2207: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > CLI Unable to connect using https-remoting address. > --------------------------------------------------- > > Key: WFLY-2207 > URL: https://issues.jboss.org/browse/WFLY-2207 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.CR1 > > > The CLI is failing to connect over https with the following: - > {code} > [disconnected /] connect https-remoting://localhost:9993 > The controller is not available at localhost:9993: java.net.ConnectException: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2202) Update to HAL 2.0.2.Final

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2202?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2202: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Update to HAL 2.0.2.Final > ------------------------- > > Key: WFLY-2202 > URL: https://issues.jboss.org/browse/WFLY-2202 > Project: WildFly > Issue Type: Task > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2201) Server-side XTS handlers not added if @WebService#portName is missing

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2201?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2201: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: WFLY-2201 > URL: https://issues.jboss.org/browse/WFLY-2201 > Project: WildFly > Issue Type: Bug > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 8.0.0.CR1 > > > To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails with: > {code} > "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" > {code} > The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2194) Difficulty Enabling SSL for Management Interfaces Using CLI

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2194?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2194: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Difficulty Enabling SSL for Management Interfaces Using CLI > ----------------------------------------------------------- > > Key: WFLY-2194 > URL: https://issues.jboss.org/browse/WFLY-2194 > Project: WildFly > Issue Type: Task > Components: CLI, Domain Management, Security > Affects Versions: 8.0.0.Alpha4 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Trying to enable the HTTPS port for the HTTP management interface using the CLI results in the following: - > {code} > [standalone@localhost:9990 /] ./core-service=management/management-interface=http-interface:write-attribute(name=secure-socket-binding, value=management-https) > Communication error: java.util.concurrent.ExecutionException: Operation failed: Operation failed: Channel closed > {code} > Server side the following is logged: - > {code} > 17:59:54,193 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015890: Creating http management service using socket-binding (management-http) and secure-socket-binding (management-https) > 17:59:54,212 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015888: Creating http management service using socket-binding (management-http) > 17:59:54,236 WARN [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014626: Operation was interrupted before stability could be reached > {code} > i.e. What appears to be happening is that as communication is lost with the client the update is being detected as a failure. > As interface updates do result in restarting the services used to make the updates it may be better to switch these to reload required updates instead of being immediate - also the chances are that security realm updates would be made simultaneously and those also require a reload. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2192) MessageEndpointFactory should use unique RA id

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2192?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2192: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > MessageEndpointFactory should use unique RA id > ---------------------------------------------- > > Key: WFLY-2192 > URL: https://issues.jboss.org/browse/WFLY-2192 > Project: WildFly > Issue Type: Bug > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 8.0.0.CR1 > > > This is causing a regression in TCK -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2171) Use deployment unit processors to register mod_cluster metrics

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2171?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2171: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Use deployment unit processors to register mod_cluster metrics > -------------------------------------------------------------- > > Key: WFLY-2171 > URL: https://issues.jboss.org/browse/WFLY-2171 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 8.0.0.CR1 > > > Remove static dependency and make it runtime using DUPs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2170) Intermittent failure in ReloadWSDLPublisherTestCase

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2170?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2170: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Intermittent failure in ReloadWSDLPublisherTestCase > --------------------------------------------------- > > Key: WFLY-2170 > URL: https://issues.jboss.org/browse/WFLY-2170 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.0.0.Alpha4 > Reporter: Joe Wertz > Assignee: Joe Wertz > Priority: Minor > Fix For: 8.0.0.CR1 > > > Intermittent failure reconnecting to the server after it is restarted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013