September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1841) Subsystem parsers should be created lazily when needed

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1841?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-1841: ------------------------------------------ Something we did not mention when we talked about this but will also be benefit, there are scenarios where the version of the parser for the first load is different for all subsequent loads. > Subsystem parsers should be created lazily when needed > ------------------------------------------------------ > > Key: WFCORE-1841 > URL: https://issues.jboss.org/browse/WFCORE-1841 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > Currently when we register parsers for different versions of subsystem schema we always pass over instance of whole parser which is usually statically initialized. > In practice legacy (non current) parsers are only used rarely and there is no point in having them loaded in memory when not needed. > Impl should be based on provider pattern and as such also allow us to on demand create new instance of parser when needed, as well as enable us for parsers to be GCed, when they are not in use. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1841) Subsystem parsers should be created lazily when needed

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1841?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFCORE-1841: ----------------------------------- Summary: Subsystem parsers should be created lazily when needed (was: Subsystem parsers should be created lazly when need) > Subsystem parsers should be created lazily when needed > ------------------------------------------------------ > > Key: WFCORE-1841 > URL: https://issues.jboss.org/browse/WFCORE-1841 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > Currently when we register parsers for different versions of subsystem schema we always pass over instance of whole parser which is usually statically initialized. > In practice legacy (non current) parsers are only used rarely and there is no point in having them loaded in memory when not needed. > Impl should be based on provider pattern and as such also allow us to on demand create new instance of parser when needed, as well as enable us for parsers to be GCed, when they are not in use. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7209) Operation to list installed Resource Adapters

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-7209?page=com.atlassian.jira.plugin.... ] Stefano Maestri commented on WFLY-7209: --------------------------------------- You are confusing rar deployed (through deployment or modules) w/ activation (through subsystem or ironjacamar.xml) You could have more than one activation for each rar, and from a runtime POV activations are the only ones important. Frankly, I don't see an operation mixing both concepts as useful. > Operation to list installed Resource Adapters > --------------------------------------------- > > Key: WFLY-7209 > URL: https://issues.jboss.org/browse/WFLY-7209 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Guillermo González de Agüero > Assignee: Stefano Maestri > Fix For: 10.1.0.Final > > > Currently there's no way to list all the installed Resource Adapters. Only configured resource adapters can be queried. However, they are automatically enabled at deployment time. > I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers. This would allow HAL to provide a wizard of available options when configuring them. > The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1841) Subsystem parsers should be created lazly when need

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-1841: ----------------------------------- Summary: Subsystem parsers should be created lazly when need Key: WFCORE-1841 URL: https://issues.jboss.org/browse/WFCORE-1841 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Tomaz Cerar Assignee: Tomaz Cerar Currently when we register parsers for different versions of subsystem schema we always pass over instance of whole parser which is usually statically initialized. In practice legacy (non current) parsers are only used rarely and there is no point in having them loaded in memory when not needed. Impl should be based on provider pattern and as such also allow us to on demand create new instance of parser when needed, as well as enable us for parsers to be GCed, when they are not in use. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7244) Web sockets are always enabled

by Kabir Khan (JIRA)

Kabir Khan created WFLY-7244: -------------------------------- Summary: Web sockets are always enabled Key: WFLY-7244 URL: https://issues.jboss.org/browse/WFLY-7244 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Kabir Khan Assignee: Stuart Douglas Fix For: 11.0.0.Alpha1 TCK testing for WFLY-6784 unearthed that websockets were always turned on in the undertow subsystem, while they should be explicitly turned on with the websocket element. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7243) Web sockets are always enabled

by Kabir Khan (JIRA)

Kabir Khan created WFLY-7243: -------------------------------- Summary: Web sockets are always enabled Key: WFLY-7243 URL: https://issues.jboss.org/browse/WFLY-7243 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Kabir Khan Assignee: Stuart Douglas Fix For: 11.0.0.Alpha1 TCK testing for WFLY-6784 unearthed that websockets were always turned on in the undertow subsystem, while they should be explicitly turned on with the websocket element. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1310) Expired fact with activationCount > 0 are not evicted from objectstore

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1310?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1310: ----------------------------------- Attachment: RuleTest.java Standalone JUnit reproducer for the case. > Expired fact with activationCount > 0 are not evicted from objectstore > ---------------------------------------------------------------------- > > Key: DROOLS-1310 > URL: https://issues.jboss.org/browse/DROOLS-1310 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.CR2 > Reporter: Matteo Mortari > Assignee: Mario Fusco > Priority: Minor > Attachments: RuleTest.java > > > Expired fact with activationCount > 0 are not evicted from objectstore: intended behavior for serialization purposes, but for instance side-effects when used in an activation-group scenario where the rules are not 100% dual. > Sized-down reproducer will be submitted at a later time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2217) Enable reload tests

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-2217?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-2217: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9234 (was: https://github.com/wildfly/wildfly/pull/8437) > Enable reload tests > ------------------- > > Key: WFLY-2217 > URL: https://issues.jboss.org/browse/WFLY-2217 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 8.0.0.Beta1 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Original Estimate: 3 days > Time Spent: 4 days > Remaining Estimate: 0 minutes > > Tests need not stay ignored any longer! > Some tests which :reload are still ignored, even though :reload has been fixed ( well, it seems there is more to it due to other code changes ) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7229) WFLYCLWEBUT0001 for server-side invalidated sessions

by Michał Nowakowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-7229?page=com.atlassian.jira.plugin.... ] Michał Nowakowski commented on WFLY-7229: ----------------------------------------- @Paul: I'll try. We can disable server-side invalidation without losing security or functionality, but we're concerned about resources. Our interval has to be closer to 20 minutes than 20 seconds, and our sessions are not minute. Plus, no appserver we used before was having any problem with this invalidation, nor with being given valid cookies to invalid sessions - these were Tomcat, JBossAS and older versions of WF. I guess people that wrote CAS client for Java were also unaware of any. Or... is handling a HttpSession in context of a _foreign_ HttpRequest (that is, a request of a different session or with no session at all) still faithful to the spec? > WFLYCLWEBUT0001 for server-side invalidated sessions > ---------------------------------------------------- > > Key: WFLY-7229 > URL: https://issues.jboss.org/browse/WFLY-7229 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Affects Versions: 10.1.0.Final > Environment: Happens whenever <distributable/> is used in web.xml, both in standalone and domain modes. > Reporter: Michał Nowakowski > Assignee: Paul Ferraro > Attachments: stacktrace_01.txt, stacktrace_02.txt, stacktrace_03.txt, testPortlet.tar.gz > > > Attached is a simple webapp (pardon the name) with a single servlet "/main", that does the following: > - a session is assigned (or created, if none existed before) > - its details are printed and the browser is told to refresh after 20 seconds > - before the browser refreshes, the session is invalidated server-side by separate thread. > Expected behaviour is, that WF should give the user a new session. That's indeed how it works in standalone mode and without <distributable/> in web.xml. But in domain mode, OR with <distributable/> added (and, possibly, full-ha profile chosen), I get errors: > - The first stacktrace happens when the thread invalidates the session. > - The second stacktrace happens, when the browser refreshes. The user sees "Error 500". > - Then, after a minute or so, I get the last one. It then repeats periodically. > We can't upgrade from 10.0 because of this - and we know we need an upgrade because of fixes in Infinispan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2104) NAMING: provide logical names when IpAddressUUID is used as addresses

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2104?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2104. ---------------------------- Resolution: Done > NAMING: provide logical names when IpAddressUUID is used as addresses > --------------------------------------------------------------------- > > Key: JGRP-2104 > URL: https://issues.jboss.org/browse/JGRP-2104 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0 > > > This is a new protocol, typically added somewhere above {{NAKACK2}}. When {{TP.use_ip_addr}} is true, {{IpAddressUUID}} addresses will be used. > If {{Discovery.max_rank_to_reply}} is less than the max rank of the cluster view, not all members will receive discovery responses. They therefore won't have a mapping between the address and the logical name for all members. > {{NAMING}} fixes this by having the joiner multicast the address:name mapping after joining, and by everyone sending their mapping to the newly joined member as well. > Note that this protocol is not strictly necessary; as {{IpAddressUUID}} addresses will also work without logical names mapped to them, but it improves legibility, e.g. of logs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

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 September 2016