October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-229) Expose mgmt client socket binding config through ModelControllerClient Factory

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-229?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-229: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Expose mgmt client socket binding config through ModelControllerClient Factory > ------------------------------------------------------------------------------ > > Key: WFLY-229 > URL: https://issues.jboss.org/browse/WFLY-229 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.CR1 > > > Parent task used a secret system property to configure this to support Open Shift's immediate need, but proper configuration is needed. -- 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-249) Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-249?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-249: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users > --------------------------------------------------------------------------------------------- > > Key: WFLY-249 > URL: https://issues.jboss.org/browse/WFLY-249 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.CR1 > > > Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users (e.g. in read-operation-names results etc) in order to not delude users into thinking they can do something like :write-attribute directly on a server (instead of modifying host or domain config elements.) > But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config should be valid. -- 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-231) HostControllerConnectionService connection timeout is not configurable

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-231?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-231: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > HostControllerConnectionService connection timeout is not configurable > ---------------------------------------------------------------------- > > Key: WFLY-231 > URL: https://issues.jboss.org/browse/WFLY-231 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: Dominik Pospisil > Assignee: Bartosz Baranowski > Fix For: 8.0.0.CR1 > > > I am seeing intermittent failures when starting AS7 in domain mode. It seems that this is due to HostControllerConnectionService has hardcoded 15s timeout when trying to connect to DC. I think that this value should be configurable. > HostControllerConnectionService.java: > ... > ProtocolChannelClient.Configuration configuration = new ProtocolChannelClient.Configuration(); > configuration.setEndpoint(endpointInjector.getValue()); > configuration.setConnectionTimeout(15000); > configuration.setUri(new URI("remote://" + hcAddressInjector.getValue().getHostName() + ":" + hcAddressInjector.getValue().getPort())); > client = ProtocolChannelClient.create(configuration); > ... > Exception I am getting: > [Server:server-two] 13:52:54,766 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.host.controller.channel: org.jboss.msc.service.StartException in service jboss.host.controller.channel: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out > [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:103) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] > [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] > [Server:server-two] Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out > [Server:server-two] at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:166) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] -- 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-230) Add @ValidIdRange annotation to message loggers and message bundles

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-230?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-230: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add @ValidIdRange annotation to message loggers and message bundles > ------------------------------------------------------------------- > > Key: WFLY-230 > URL: https://issues.jboss.org/browse/WFLY-230 > Project: WildFly > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.CR1 > > > A new release of the logging tooling will include a {{@ValidIdRange}} annotation. This will help document which id ranges allowed as well as provide compile time validation. -- 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-270) Use logger instead of [stdout] for JGroups GMS logger

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-270?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-270: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Use logger instead of [stdout] for JGroups GMS logger > ----------------------------------------------------- > > Key: WFLY-270 > URL: https://issues.jboss.org/browse/WFLY-270 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Trivial > Fix For: 8.0.0.CR1 > > > ...and possibly remove the unnecessary dash lines on the way. > {noformat} > [JBossINF] 12:11:12,677 INFO [org.jboss.as.osgi] (MSC service thread 1-15) JBAS011907: Register module: Module "deployment.clusterbench-ee6.ear.clusterbench-ee6-ejb.jar:main" from Service Module Loader > [JBossINF] 12:11:13,142 INFO [stdout] (ChannelService lifecycle - 1) > [JBossINF] 12:11:13,142 INFO [stdout] (ChannelService lifecycle - 1) ------------------------------------------------------------------- > [JBossINF] 12:11:13,142 INFO [stdout] (ChannelService lifecycle - 1) GMS: address=perf18/web, cluster=web, physical address=10.16.90.54:55200 > [JBossINF] 12:11:13,143 INFO [stdout] (ChannelService lifecycle - 1) ------------------------------------------------------------------- > [JBossINF] 12:11:13,209 INFO [stdout] (ChannelService lifecycle - 1) > [JBossINF] 12:11:13,209 INFO [stdout] (ChannelService lifecycle - 1) ------------------------------------------------------------------- > [JBossINF] 12:11:13,209 INFO [stdout] (ChannelService lifecycle - 1) GMS: address=perf18/ejb, cluster=ejb, physical address=10.16.90.54:55200 > [JBossINF] 12:11:13,210 INFO [stdout] (ChannelService lifecycle - 1) ------------------------------------------------------------------- > [JBossINF] 12:11:13,441 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated. > {noformat} -- 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-269) Updated infinispan management API

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-269?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-269: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Updated infinispan management API > --------------------------------- > > Key: WFLY-269 > URL: https://issues.jboss.org/browse/WFLY-269 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Richard Achmatowicz > Fix For: 8.0.0.CR1 > > > Expose updated management operations -- 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-264) Add support for use1PcForAutoCommitTransactions

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-264?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-264: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add support for use1PcForAutoCommitTransactions > ----------------------------------------------- > > Key: WFLY-264 > URL: https://issues.jboss.org/browse/WFLY-264 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Minor > Fix For: 8.0.0.CR1 > > > Since clustered web sessions/SFSBs won't ever incur inter-node concurrent access, we can tolerate a 1PC commit optimization - which will reduce the number of RPCs involved in replication/distribution. This should result it a significant performance gains for REPL_SYNC and DIST_SYNC caches. -- 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-261) Add way to properly parse JNDI urls in AS codebase

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-261?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-261: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add way to properly parse JNDI urls in AS codebase > -------------------------------------------------- > > Key: WFLY-261 > URL: https://issues.jboss.org/browse/WFLY-261 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 8.0.0.CR1 > > > This is a followup of AS7-2138. Original code, in case no URL context threw NamingException. The AS7-2138 introduced a fallback to NamingContext in case AS7 does not provide custom hack for url( like EJB ). However the fallback did not fail with NamingException in case it did not locate Context. This essentially made it go knee deep into AS7 service lookups, which hides real cause of failure. -- 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-262) Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources>

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-262?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-262: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources> > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-262 > URL: https://issues.jboss.org/browse/WFLY-262 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > 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-259) Auto ignore domain resources on a slave HC which do not affect its servers

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-259?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-259: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Auto ignore domain resources on a slave HC which do not affect its servers > -------------------------------------------------------------------------- > > Key: WFLY-259 > URL: https://issues.jboss.org/browse/WFLY-259 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.CR1 > > > Currently to avoid receiving resources and ops for parts of the domain model which do not work on an older slave we use <ignored-resources> in the slave host.xml to ignore them. > Instead we should only pull in parts of the domain model that is actually required on the slave for its servers to start. Once started we need to be able to update the slave with domain information as the config changes > The main things which can change affecting the data required are: > 1) A domain's server-group, where the profile (and thus extensions) and the socket-binding group can be changed. > 2) A host's server-config, where the server-group and the socket-binding-group override might be changed. > For 1) we can piggy-back missing data to the slave. > For 2) the slave needs to connect back to the DC, attempt to get the DC lock and pull down the required data. If the lock cannot be obtained, the operation should fail fast. -- 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