October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-214) Consider logging "Number of cluster members" on view change like is done at server startup

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-214?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-214: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Consider logging "Number of cluster members" on view change like is done at server startup > ------------------------------------------------------------------------------------------ > > Key: WFLY-214 > URL: https://issues.jboss.org/browse/WFLY-214 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > Fix For: 8.0.0.CR1 > > > See https://community.jboss.org/message/754829#754829 > Could we just do the same as for the startup? -- 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-217) Strict location check of persistence.xml deployments

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-217?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-217: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Strict location check of persistence.xml deployments > ---------------------------------------------------- > > Key: WFLY-217 > URL: https://issues.jboss.org/browse/WFLY-217 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Bartosz Baranowski > Assignee: Scott Marlow > Priority: Minor > Fix For: 8.0.0.CR1 > > > As of: https://github.com/jbossas/jboss-as/commit/38815193011fba624170a7d938118e... it is possible to deploy persistence.xml from invalid location: > As per JPA spec(https://docs.jboss.org/author/display/AS71/JPA+Reference+Guide), valid locations are: > - an EJB-JAR file > - the WEB-INF/classes directory of a WAR file > - a jar file in the WEB-INF/lib directory of a WAR file > - a jar file in the EAR library directory > - an application client jar file -- 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-207) Add start/stop operations to hornetq-server resource

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-207?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-207: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add start/stop operations to hornetq-server resource > ---------------------------------------------------- > > Key: WFLY-207 > URL: https://issues.jboss.org/browse/WFLY-207 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > > Currently it is not possible to start/stop a hornetq-server resource without removing or adding it. > For HornetQ replicated nodes, it'd be useful to be able to start/stop the node (runtime operations) without changing its configuration. That'd be necessary to restart replicated backup servers that have fallen back -- 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-228) TS: Migrate from Surefire to Failsafe maven plugin.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-228?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-228: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > TS: Migrate from Surefire to Failsafe maven plugin. > --------------------------------------------------- > > Key: WFLY-228 > URL: https://issues.jboss.org/browse/WFLY-228 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Jakub Senko > Fix For: 8.0.0.CR1 > > Attachments: AS7-failsafe-surefire.html.zip > > > Surefire aims at unit testing. > Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify. > That not only moves test execution to the correct phase, but also brings possibility to test several issues present in the testsuite - like skipping successive Surefire executions in a single module if former fails (not affected by -fae). > -- 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-209) Move ClientConfigurationImpl factory methods into ModelControllerClientConfiguration

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-209?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-209: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Move ClientConfigurationImpl factory methods into ModelControllerClientConfiguration > ------------------------------------------------------------------------------------ > > Key: WFLY-209 > URL: https://issues.jboss.org/browse/WFLY-209 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Priority: Minor > Fix For: 8.0.0.CR1 > > > ClientConfigurationImpl includes a bunch of static factory methods that would fit better in a Factory class in the ModelControllerClientConfiguration interface. -- 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-205) AttributeDefinition validateOperation should convert all expression strings to ModelType.EXPRESSION

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-205?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-205: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > AttributeDefinition validateOperation should convert all expression strings to ModelType.EXPRESSION > --------------------------------------------------------------------------------------------------- > > Key: WFLY-205 > URL: https://issues.jboss.org/browse/WFLY-205 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.CR1 > > > AttributeDefinition.validateOperation currently only converts a string to an expression if the attribute supports expressions. It should convert any time it sees the syntax. This way if a STRING attribute that doesn't support expressions finds one, it will reject it instead of accepting it as a raw string. > Scheduling for 7.3 out of concern this may break things in 7.2 without time to notice/adapt. -- 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-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

12 years, 9 months

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

12 years, 9 months

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

12 years, 9 months

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

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