October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-216) Include Infinispan CDI as a JBoss module

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-216?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-216: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Include Infinispan CDI as a JBoss module > ---------------------------------------- > > Key: WFLY-216 > URL: https://issues.jboss.org/browse/WFLY-216 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Reporter: Avelino Martins > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > CDI has become an invaluable technology on any JavaEE project. I find hard to justify having to include infinispan-cdi as a compile dependency on every project that uses ISPN. -- 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-255) Improve reporting during deployment hang

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-255?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-255: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Improve reporting during deployment hang > ---------------------------------------- > > Key: WFLY-255 > URL: https://issues.jboss.org/browse/WFLY-255 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Environment: http://java.net/jira/browse/EJB_SPEC-60 > java version "1.7.0_09" > OpenJDK Runtime Environment (IcedTea7 2.3.3) (7u9-2.3.3-0ubuntu1~12.10.1) > OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode) > Ubuntu 12.10 > Reporter: Carlo de Wolf > Fix For: 8.0.0.CR1 > > Attachments: deployment-hang-20130205.txt, server.log > > > Management Thread waits indefinitely for, what seems to be, a finished operation. > {noformat} > "management-handler-thread - 2" prio=10 tid=0x00007fa1380d0000 nid=0x7683 in Object.wait() [0x00007fa136deb000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor) > at java.lang.Object.wait(Object.java:503) > at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158) > - locked <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor) > at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:464) > at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:148) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:299) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-244) Undertow Integration Tracker

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-244?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-244: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Undertow Integration Tracker > ---------------------------- > > Key: WFLY-244 > URL: https://issues.jboss.org/browse/WFLY-244 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Critical > Fix For: 8.0.0.CR1 > > > Tracking issue for all issues related to undertow integration. > as part of https://github.com/wildfly/wildfly/pull/4810 there tests removed that need to be re-added as part of this tracking issue -- 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-241) Specify and expose mod_cluster runtime information the should be shown within the console

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-241?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-241: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Specify and expose mod_cluster runtime information the should be shown within the console > ----------------------------------------------------------------------------------------- > > Key: WFLY-241 > URL: https://issues.jboss.org/browse/WFLY-241 > Project: WildFly > Issue Type: Clarification > Components: Clustering > Reporter: Heiko Braun > Assignee: Paul Ferraro > 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-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

11 years, 1 month

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

11 years, 1 month

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

11 years, 1 month

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

11 years, 1 month

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

11 years, 1 month

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

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