October 2013 - jboss-jira - Jboss List Archives

[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

12 years, 9 months

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

12 years, 9 months

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

12 years, 9 months

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

12 years, 9 months

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

12 years, 9 months

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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2159) Consolidate REPL and DIST cache configurations

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2159?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2159: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Consolidate REPL and DIST cache configurations > ---------------------------------------------- > > Key: WFLY-2159 > URL: https://issues.jboss.org/browse/WFLY-2159 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 8.0.0.Alpha4 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > Since Infinispan now implements REPL as a special case of DIST (i.e. where owners == cache view size), we can use DIST as default cache mode for our clustered caches, with owners="4" (or similar). -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2214) LDAP security realm needs to have configurable timeouts

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2214: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > LDAP security realm needs to have configurable timeouts > ------------------------------------------------------- > > Key: WFLY-2214 > URL: https://issues.jboss.org/browse/WFLY-2214 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.0.0.Alpha4 > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > LDAP security realm needs to have configurable timeouts. > The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy. > The following hack appears to work: > +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java > @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag > result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory); > String url = config.require(URL).asString(); > result.put(Context.PROVIDER_URL,url); > + result.put("com.sun.jndi.ldap.connect.timeout", "500"); > return result; > } -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2212) Update JPA subsystem to use default EE datasource binding

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2212?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2212: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Update JPA subsystem to use default EE datasource binding > --------------------------------------------------------- > > Key: WFLY-2212 > URL: https://issues.jboss.org/browse/WFLY-2212 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.CR1 > > > JPA subsystem should check if a default EE datasource binding is available to use and default to that if a persistence unit doesn't specify a datasource. > Also add a persistence unit hint to not use a default datasource (might be helpful for OGM which fails the deployment if a datasource is specified). -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2211) NullPointerException in RemotingHttpUpgradeService if no http port.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2211?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2211: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > NullPointerException in RemotingHttpUpgradeService if no http port. > ------------------------------------------------------------------- > > Key: WFLY-2211 > URL: https://issues.jboss.org/browse/WFLY-2211 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.CR1 > > > Starting with a HTTP port is not mandatory. > {code} > Caused by: java.lang.NullPointerException > at org.jboss.as.remoting.RemotingHttpUpgradeService.start(RemotingHttpUpgradeService.java:107) [wildfly-remoting-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > {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

12 years, 9 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 October 2013