October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-276) TS: How to use -Djpda with clustered tests

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-276?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-276: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > TS: How to use -Djpda with clustered tests > ------------------------------------------ > > Key: WFLY-276 > URL: https://issues.jboss.org/browse/WFLY-276 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Documentation, Test Suite > Reporter: Radoslav Husar > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 8.0.0.CR1 > > > The doc now says whats pasted below, but I am not sure if both servers are listening on 8787 because (that would fail the startup), if I have to connect to both or where do I configure that, etc. > {code} > Running JBoss AS instances with debugger > Adding -Djpda (May be changed to -Ddebug in the future) will make JBoss AS run with JPDA JVM arguments for debugging. > It will suspend and wait for the debugger to connect at port 8787. > JBoss AS is started by Arquillian, when the first test which requires given instance is run. There's (currently) no challenge text in the console, it will look like the first test is stuck. This is being solved in http://jira.codehaus.org/browse/SUREFIRE-781. > Depending on which test group(s) you run, multiple instances may be started. In that case, you need to attach the debugger multiple times. > {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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-273) Document how to configure firewall when using different JGroups stacks

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-273?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-273: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Document how to configure firewall when using different JGroups stacks > ---------------------------------------------------------------------- > > Key: WFLY-273 > URL: https://issues.jboss.org/browse/WFLY-273 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Documentation > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > Document how to configure firewall for using different clustering stacks > https://docs.jboss.org/author/display/AS71/High+Availability+Guide > Needed by OpenShift team (especially TCP stacks). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-307) Add ability to migrate timers between data stores

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-307?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-307: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add ability to migrate timers between data stores > ------------------------------------------------- > > Key: WFLY-307 > URL: https://issues.jboss.org/browse/WFLY-307 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > > It should be possible to move timers between data stores, so that timers can be migrated from the legacy file store. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-301) Undertow management API

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-301?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-301: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Undertow management API > ----------------------- > > Key: WFLY-301 > URL: https://issues.jboss.org/browse/WFLY-301 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Web (Undertow) > Reporter: Heiko Braun > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Expose undertow subsystem management opertions -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-288) SecurityDomainJndiInjectable should allow "java:/jaas" prefixed security domain on demand

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-288?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-288: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > SecurityDomainJndiInjectable should allow "java:/jaas" prefixed security domain on demand > ----------------------------------------------------------------------------------------- > > Key: WFLY-288 > URL: https://issues.jboss.org/browse/WFLY-288 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Anil Saldhana > Assignee: Stefan Guilhen > Fix For: 8.0.0.CR1 > > > Currently, security domain strings of the form "java:/jaas/sd" are not resolving properly. IMO we should allow users to deploy applications on AS4,5,6,7 if they need to. > So have a flag inside the SecurityDomainJndiInjectable class that is turned off by default. If you turn it on, then "java:/jaas" is unprefixed if present. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-308) Provide facility for running ejb3 ws endpoints authorization independently

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-308?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-308: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Provide facility for running ejb3 ws endpoints authorization independently > -------------------------------------------------------------------------- > > Key: WFLY-308 > URL: https://issues.jboss.org/browse/WFLY-308 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Affects Versions: 8.0.0.Alpha3 > Reporter: Alessio Soldano > Assignee: jaikiran pai > Fix For: 8.0.0.CR1 > > > We'd need a mean of checking auth for ejb3 ws endpoints before the actual invocation is performed. This is basically required to enforce security before running JAXWS handler. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-305) Implement mail inflow

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-305?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-305: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Implement mail inflow > --------------------- > > Key: WFLY-305 > URL: https://issues.jboss.org/browse/WFLY-305 > Project: WildFly > Issue Type: Feature Request > Components: EE > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > in previous versions of as we had mail-ra resource adapter that added functionality of handling inflow mails. > there is implementation of this ironjacamar so the code could be reused. > Resource addapter could/should be added the same way hornetq addapter is added in messaging subsystem. > code and documentation from ironjacamer > https://svn.jboss.org/repos/jbossas/projects/jboss-jca/trunk/adapters/src... > http://docs.jboss.org/ironjacamar/userguide/1.1/en-US/html/introduction.h... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-296) Batch integration API

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-296?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-296: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Batch integration API > --------------------- > > Key: WFLY-296 > URL: https://issues.jboss.org/browse/WFLY-296 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Cheng Fang > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-285) Add clustered database based timers

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-285?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-285: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add clustered database based timers > ----------------------------------- > > Key: WFLY-285 > URL: https://issues.jboss.org/browse/WFLY-285 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > > Clustering should be supported for database timers. > The general ideal will be that a single database is shared by all nodes in the cluster. When a timer is created it will be inserted into the database. Periodically at a configured interval nodes will refresh their list of active timers from the database. > When a timer expires a node will attempt to grab ownership of the timer in the database by updating the row. Due to the use of either optimisitic locking or traditional DB locks only 1 node will be successful, and that node will run the task. > We will also support write only nodes, nodes that can create timer tasks, but do not attempt to run them, to allow timer tasks to be run by a subset of the nodes. > So that you don't have hundreds of existing partition name feature will allow clustered timers to be grouped into smaller partitions, so you can limit the number of nodes that are contending for a timer. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-322) TS clustering: test with both repl and dist caches

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-322?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-322: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > TS clustering: test with both repl and dist caches > -------------------------------------------------- > > Key: WFLY-322 > URL: https://issues.jboss.org/browse/WFLY-322 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Test Suite > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > Just like we did in AS7-3954, but with different cache types. -- 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, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013