July 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.Beta1 (was: 8.0.0.Alpha3) > 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.Beta1 > > > 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-215) Clustering tests leave a hanging instance if they are run in opposite order

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-215?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-215: ------------------------------ Fix Version/s: 8.0.0.Beta1 (was: 8.0.0.Alpha3) > Clustering tests leave a hanging instance if they are run in opposite order > --------------------------------------------------------------------------- > > Key: WFLY-215 > URL: https://issues.jboss.org/browse/WFLY-215 > Project: WildFly > Issue Type: Enhancement > Components: Clustering, Test Suite > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.Beta1 > > > Interestingly, if the tests are run in the opposite order i.e. alphabetically, one server instance remains running and doesn't shut down. > I have used a workaround for now > {code} > +  > + <runOrder>reversealphabetical</runOrder> > {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

13 years

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.Beta1 (was: 8.0.0.Alpha3) > 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.Beta1 > > > 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-211) Expose client socket binding config through CLI connect configs

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-211?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-211: ------------------------------ Fix Version/s: 8.0.0.Beta1 (was: 8.0.0.Alpha3) > Expose client socket binding config through CLI connect configs > --------------------------------------------------------------- > > Key: WFLY-211 > URL: https://issues.jboss.org/browse/WFLY-211 > Project: WildFly > Issue Type: Enhancement > Components: CLI > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > Fix For: 8.0.0.Beta1 > > > Once AS7-6277 is done, continue exposing the client bind socket config to CLI users. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-191) AS build fails in jboss-as-webservices-server-integration when working directory path contains special chars

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-191?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-191: ------------------------------ Fix Version/s: 8.0.0.Beta1 (was: 8.0.0.Alpha3) > AS build fails in jboss-as-webservices-server-integration when working directory path contains special chars > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-191 > URL: https://issues.jboss.org/browse/WFLY-191 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Ron Šmeral > Assignee: Paul Gier > Fix For: 8.0.0.Beta1 > > > When AS is built in a working directory like > {noformat} > /qa/services/hudson/hudson_workspace/workspace/Weld-2.x-release-repo/as_ref/7.2.0.Final-prerelease1/jdk/java17_default/label/RHEL5||RHEL6/jboss-as/ > {noformat} > the build fails in the {{jboss-as-webservices-server-integration}} module. > After changing the path to > {noformat}/qa/services/hudson/hudson_workspace/workspace/Weld-2.x-release-repo/c8bcde9a/jboss-as > {noformat} the build works OK again. > This can be seen here, builds 31 (broken) and 33 (works): [https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/Weld-2.x-release-rep...] > Tested only on 7.2.0.Final, not EAP 6.1.0. -- 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

13 years

1
0
0 / 0

[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.Beta1 (was: 8.0.0.Alpha3) > 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.Beta1 > > > 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-182) mod_proxy incompatible with logout mechanism

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-182?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-182: ------------------------------ Fix Version/s: 8.0.0.Beta1 (was: 8.0.0.Alpha3) > mod_proxy incompatible with logout mechanism > -------------------------------------------- > > Key: WFLY-182 > URL: https://issues.jboss.org/browse/WFLY-182 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Web Console > Reporter: Jason Greene > Assignee: Jason Greene > Fix For: 8.0.0.Beta1 > > Attachments: apache_mod_proxy_mgmt.conf, Screenshot_proxy_logs.png > > > We need to either outlaw proxies, or to make sure the console works with them. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-237) DUP for concurrency support

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-237?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-237: ------------------------------ Fix Version/s: 8.0.0.Beta1 (was: 8.0.0.Alpha3) > DUP for concurrency support > --------------------------- > > Key: WFLY-237 > URL: https://issues.jboss.org/browse/WFLY-237 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > Assignee: Eduardo Martins > Fix For: 8.0.0.Beta1 > > > Support the specification of thread pools within a deployment. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-236) JSR-236 Java EE 7 concurrency support parent issue

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-236?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-236: ------------------------------ Fix Version/s: 8.0.0.Beta1 (was: 8.0.0.Alpha3) > JSR-236 Java EE 7 concurrency support parent issue > -------------------------------------------------- > > Key: WFLY-236 > URL: https://issues.jboss.org/browse/WFLY-236 > Project: WildFly > Issue Type: Enhancement > Components: EE > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 8.0.0.Beta1 > > > Parent task for JSR-236 subtasks. Please resolve AS7-6430 only when this issue is resolved. -- 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

13 years

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.Beta1 (was: 8.0.0.Alpha3) > 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.Beta1 > > 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

13 years

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 July 2013