December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-263) JASPI Support for Web Services

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-263?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-263: ------------------------------ Fix Version/s: 8.0.0.Final > JASPI Support for Web Services > ------------------------------ > > Key: WFLY-263 > URL: https://issues.jboss.org/browse/WFLY-263 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security, Web Services > Reporter: Anil Saldhana > Assignee: Jim Ma > Fix For: 8.0.0.CR1, 8.0.0.Final > > > Take care of the JASPI requirements for SOAP layer. -- 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, 7 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.Final > 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 > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.CR1, 8.0.0.Final > > -- 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, 7 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.Final > 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 > Security Level: Public(Everyone can see) > Components: Naming > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 8.0.0.CR1, 8.0.0.Final > > > 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, 7 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.Final > Add support for use1PcForAutoCommitTransactions > ----------------------------------------------- > > Key: WFLY-264 > URL: https://issues.jboss.org/browse/WFLY-264 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Minor > Fix For: 8.0.0.CR1, 8.0.0.Final > > > 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, 7 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.Final > Updated infinispan management API > --------------------------------- > > Key: WFLY-269 > URL: https://issues.jboss.org/browse/WFLY-269 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Heiko Braun > Assignee: Richard Achmatowicz > Fix For: 8.0.0.CR1, 8.0.0.Final > > > 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, 7 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.Final > 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 > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Trivial > Fix For: 8.0.0.CR1, 8.0.0.Final > > > ...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, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-276) Clustering/multi-node tests cannot be run with -Djpda debugger

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.Final > Clustering/multi-node tests cannot be run with -Djpda debugger > -------------------------------------------------------------- > > Key: WFLY-276 > URL: https://issues.jboss.org/browse/WFLY-276 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering, Documentation, Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 8.0.0.CR1, 8.0.0.Final > > > 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

12 years, 7 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.Final > 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 > Security Level: Public(Everyone can see) > Components: Clustering, Documentation > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1, 8.0.0.Final > > > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-279) Add deployment-scanner for singleton deployments

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-279?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-279: ------------------------------ Fix Version/s: 8.0.0.Final > Add deployment-scanner for singleton deployments > ------------------------------------------------ > > Key: WFLY-279 > URL: https://issues.jboss.org/browse/WFLY-279 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1, 8.0.0.Final > > > To simplify the use of singleton deployments in standalone mode, it would be nice to have a mechanism analogous to the hasingleton-deploy directory in AS6 and earlier. To do this, we can enhance the existing deployment-scanner to accept an additional policy attribute. Something like: > <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> > <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" policy="standard"/> > <deployment-scanner path="singleton-deployments" relative-to="jboss.server.base.dir" scan-interval="5000" policy="singleton"/> > </subsystem> -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-277) TS: Integrate JUnitDiff

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-277?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-277: ------------------------------ Fix Version/s: 8.0.0.Final > TS: Integrate JUnitDiff > ----------------------- > > Key: WFLY-277 > URL: https://issues.jboss.org/browse/WFLY-277 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 8.0.0.CR1, 8.0.0.Final > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > Running with > {code} > -DjunitDiff='<path1>:<path2>:<path3>' > {code} > would create a comparison to given testsuite result sets (JUnit .xml and txt files). -- 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, 7 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 December 2013