December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3884) Integrate mod_cluster subsystem with security subsystem for SSL configuration

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3884?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-3884: -------------------------------------- Targeted for Elytron, thus WF 11. > Integrate mod_cluster subsystem with security subsystem for SSL configuration > ----------------------------------------------------------------------------- > > Key: WFLY-3884 > URL: https://issues.jboss.org/browse/WFLY-3884 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > > Currently, the SSL certificate configuration is embedded within the mod_cluster subsystem configuration. Ideally, mod_cluster would reference this configuration from the security subsystem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1951) Flexible buffers for scatter/gather

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1951?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1951: -------------------------------- - {{WriteBuffers}} was merged into {{Buffers}} - Reading into a variable number of buffers is possible by adding (e.g.) 3 buffers, doing a scattering read and reading the individual buffers, see {{BuffersTest.testRead3Buffers()}} for an example > Flexible buffers for scatter/gather > ----------------------------------- > > Key: JGRP-1951 > URL: https://issues.jboss.org/browse/JGRP-1951 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.7 > > > Currently, {{Buffers}} and {{WriteBuffers}} are inflexible in that they always expect a length buffer followed by data ({{Buffers}}), or a sequence of len/data pairs ({{WriteBuffers}}). > This is bad if we for example want to read a sequence like the one below (for connection establishment in TCP): > {noformat} > | cookie | version | len | peer-address | > (4) (2) (2) (variable) > {noformat} > Goals: > * Have only 1 buffer, for reading *and* writing > * Allow to define the sequence by adding buffers dynamically, e.g. in the above case, we'd add a 4 and a 2-length buffer and read data into them. If the cookie and version don't match, throw an exception, else *dynamically* add a length buffer (possibly doing a clear() which removes the first 2 buffers), read data into it, then add a new buffer sized to the read length and finally read data into it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5801) The capability 'org.wildfly.extension.undertow.handler.file' should not contain '.file' as it is also used for reverse proxy.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-5801: -------------------------------------- Summary: The capability 'org.wildfly.extension.undertow.handler.file' should not contain '.file' as it is also used for reverse proxy. Key: WFLY-5801 URL: https://issues.jboss.org/browse/WFLY-5801 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 10.0.0.CR5 A very minor issue but raising as blocker as once capability names reach releases they are a part of the API and inherit all other backwards compatibility requirements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5800) The capability 'org.wildfly.extension.undertow.handler.file' should not contain '.file' as it is also used for reverse proxy.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-5800: -------------------------------------- Summary: The capability 'org.wildfly.extension.undertow.handler.file' should not contain '.file' as it is also used for reverse proxy. Key: WFLY-5800 URL: https://issues.jboss.org/browse/WFLY-5800 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 10.0.0.CR5 A very minor issue but raising as blocker as once capability names reach releases they are a part of the API and inherit all other backwards compatibility requirements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-255) Primitive array return values cause invalid cast to Object

by Shigeru Chiba (JIRA)

[ https://issues.jboss.org/browse/JASSIST-255?page=com.atlassian.jira.plugi... ] Shigeru Chiba resolved JASSIST-255. ----------------------------------- Resolution: Done > Primitive array return values cause invalid cast to Object > ---------------------------------------------------------- > > Key: JASSIST-255 > URL: https://issues.jboss.org/browse/JASSIST-255 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.20.0-GA > Reporter: Shigeru Chiba > Assignee: Shigeru Chiba > Fix For: 3.21.0-GA > > > "(Object) $_" causes "invalid cast" when the return value is a byte array. > (This was originally reported at https://github.com/jboss-javassist/javassist/issues/63#issuecomment-16157... ) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-255) Primitive array return values cause invalid cast to Object

by Shigeru Chiba (JIRA)

[ https://issues.jboss.org/browse/JASSIST-255?page=com.atlassian.jira.plugi... ] Shigeru Chiba closed JASSIST-255. --------------------------------- > Primitive array return values cause invalid cast to Object > ---------------------------------------------------------- > > Key: JASSIST-255 > URL: https://issues.jboss.org/browse/JASSIST-255 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.20.0-GA > Reporter: Shigeru Chiba > Assignee: Shigeru Chiba > Fix For: 3.21.0-GA > > > "(Object) $_" causes "invalid cast" when the return value is a byte array. > (This was originally reported at https://github.com/jboss-javassist/javassist/issues/63#issuecomment-16157... ) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-255) Primitive array return values cause invalid cast to Object

by Shigeru Chiba (JIRA)

Shigeru Chiba created JASSIST-255: ------------------------------------- Summary: Primitive array return values cause invalid cast to Object Key: JASSIST-255 URL: https://issues.jboss.org/browse/JASSIST-255 Project: Javassist Issue Type: Bug Affects Versions: 3.20.0-GA Reporter: Shigeru Chiba Assignee: Shigeru Chiba Fix For: 3.21.0-GA "(Object) $_" causes "invalid cast" when the return value is a byte array. (This was originally reported at https://github.com/jboss-javassist/javassist/issues/63#issuecomment-16157... ) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1019) History browsing in CLI (using the up arrow) works strangely

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1019?page=com.atlassian.jira.plugi... ] Alexey Loubyansky closed WFCORE-1019. ------------------------------------- Fix Version/s: 1.0.2.Final Resolution: Done The issue was fixed by upgrading Aesh to version 0.66.1 (which was done for WFCORE-877) > History browsing in CLI (using the up arrow) works strangely > ------------------------------------------------------------ > > Key: WFCORE-1019 > URL: https://issues.jboss.org/browse/WFCORE-1019 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 2.0.0.CR1, 2.0.0.CR5 > Reporter: Ladislav Thon > Assignee: Alexey Loubyansky > Fix For: 1.0.2.Final > > > I tend to rely on history browsing in the CLI a lot, but it got broken in WildFly 10.0.0.CR1 / WildFly Core 2.0.0.CR1 (I'd guess that the cause is the AESH upgrade). Let's see: > {code} > rm ~/.jboss-cli-history # let's start with clean slate > ./wildfly-10.0.0.Beta2/bin/standalone.sh > # the following is in second console > ./wildfly-10.0.0.Beta2/bin/jboss-cli.sh -c > :read-resource > :whoami > [up arrow shows :whoami, so press Enter to run it] > [and repeat, up arrow shows :whoami] > {code} > OK, that's expected. Repeat the process with WildFly 10.0.0.CR1 or CR2 and you'll find out that the second \[up arrow\] shows {{:read-resource}}. This is IMHO highly wrong and it confused me _a lot_ when I first encoutered this bad behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5799) Handle correctly auto-created Infinispan resources with child redirection

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-5799: ------------------------------------ Summary: Handle correctly auto-created Infinispan resources with child redirection Key: WFLY-5799 URL: https://issues.jboss.org/browse/WFLY-5799 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR4 Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5794) Handle correctly auto-created Infinispan resources with child redirection

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5794?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-5794. -------------------------------- Resolution: Done > Handle correctly auto-created Infinispan resources with child redirection > -------------------------------------------------------------------------- > > Key: WFLY-5794 > URL: https://issues.jboss.org/browse/WFLY-5794 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2015