June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Ravi Soni (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Ravi Soni commented on WFLY-3805: --------------------------------- I am stuck on this issue in AWS deployment using S3_ping, is there workout alternative to this issue. until this get fix/PR get marge to master. > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 9.0.0.Final > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4806) Do not deploy artifacts until subsystem MBeans are registered

by Brian Riehman (JIRA)

[ https://issues.jboss.org/browse/WFLY-4806?page=com.atlassian.jira.plugin.... ] Brian Riehman closed WFLY-4806. ------------------------------- Resolution: Won't Fix Thank you for the very helpful comments, [~kabirkhan]. Closing since this seems to be working as intended. > Do not deploy artifacts until subsystem MBeans are registered > ------------------------------------------------------------- > > Key: WFLY-4806 > URL: https://issues.jboss.org/browse/WFLY-4806 > Project: WildFly > Issue Type: Feature Request > Components: JMX, Server > Reporter: Brian Riehman > Assignee: Kabir Khan > Priority: Minor > > When the server starts up and begins to deploy artifacts, the subsystem MBeans are not yet available. Our application has implemented a {{ServletContextListener}} and is attempting to lookup attributes from a DataSource MBean (e.g. {{jboss.as:subsystem=datasources,xa-data-source=DefaultDS}}). This MBean is not available at the time the listener is called when the server is first starting up. Some time after the deployment has run, the MBean is available and can be queried. > If the deployment is added after the server has already successfully started, the MBean can be queried successfully. I would imagine the deploy operation is done in parallel with the MBean registration, but I cannot find where the datasource subsystem MBean registration occurs. > It is odd that the datasource exists but the datasources subsystem MBean is not yet available for querying. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-220) Add a RegExSplittingNameRewriter

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-220?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-220: --------------------------------- The regex form was intended to allow this: {code} NameRewriter extractingRewriter = new RegexNameRewriter(Pattern.compile("([a-z0-9])(a)mycompany\\.com"), "$1", true); {code} If you want to put a literal $ in the target, you can escape it, or do this: {code} NameRewriter transformingRewriter = new RegexNameRewriter(Pattern.compile("@"), Matcher.quoteReplacement("$"), true); {code} > Add a RegExSplittingNameRewriter > --------------------------------- > > Key: ELY-220 > URL: https://issues.jboss.org/browse/ELY-220 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Utils > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha2 > > > The existing implementations allow for replacing a portion of a name based on a regular expression or validating a name based on a regular expression - however we do not have a form that allows you to easily extract a portion of a name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-220) Add a RegExSplittingNameRewriter

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-220: ------------------------------------ Summary: Add a RegExSplittingNameRewriter Key: ELY-220 URL: https://issues.jboss.org/browse/ELY-220 Project: WildFly Elytron Issue Type: Feature Request Components: Utils Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha2 The existing implementations allow for replacing a portion of a name based on a regular expression or validating a name based on a regular expression - however we do not have a form that allows you to easily extract a portion of a name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-809) Copyless stack

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-809?page=com.atlassian.jira.plugin.s... ] Bela Ban commented on JGRP-809: ------------------------------- Hi Sanne, yes, at first sight, I though I'd introduce ByteBuffer to the API. However, looking into NIO more closely, I realized there are many quirks that make it unfeasible to do that, e.g. not scattering reads and gathering writes for unconnected datagram sockets (UDP), lifecycle handling issues of direct buffers and so on. Please read [1] and then let's have a chat. I'm interested in your opinion on this. [1] https://github.com/belaban/JGroups/blob/master/doc/design/NIO2.txt > Copyless stack > -------------- > > Key: JGRP-809 > URL: https://issues.jboss.org/browse/JGRP-809 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0 > > > Currently (as of 2.7), the transport reads the contents of a received packet into a buffer, then passes a *copy* of the buffer to a thread from the OOB or incoming thread pools. To prevent this copy, we can > - have the receiver read only the version and OOB flag (to see which thread pool to dispatch the packet to) > - pass a ref to the socket to a thread from the incoming of OOB pool, have that thread read the packet and return > - each thread in the pool has its own buffer into which the buffer is read from the socket > Possibly use NIO: we can install a selector and get woken up whenever data to be read is present. At that point, we can pass the ref to the socket to the handler thread and return immediately. NIO with channels for multicast sockets is available only in JDK 7 (or 8?), so this is a bit off... However, we can already implement this with reading the version and flags bytes and then passing the socket to the handler -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-379) Fix & re-enable ignored security tests

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-379?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-379: ------------------------------ Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Fix & re-enable ignored security tests > -------------------------------------- > > Key: WFLY-379 > URL: https://issues.jboss.org/browse/WFLY-379 > Project: WildFly > Issue Type: Sub-task > Components: Security > Affects Versions: 8.0.0.Alpha1 > Environment: AS8 with undertow > Reporter: Tomaz Cerar > Assignee: Darran Lofthouse > Fix For: 10.0.0.Alpha5 > > > AS8 with undertow fails few security tests. > This issue is here just for tracking what they are so they can be fixed > Still disabled tests: > {noformat} > SPNEGOLoginModuleTestCase > AdvancedLdapLoginModuleTestCase > StackingJASPITestCase > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-319) OpenSSL SSL certificate support for domain management security realms (http and native interface)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-319?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-319: ------------------------------ Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > OpenSSL SSL certificate support for domain management security realms (http and native interface) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-319 > URL: https://issues.jboss.org/browse/WFLY-319 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security, Server > Reporter: Franck LEDAY > Assignee: Darran Lofthouse > Fix For: 10.0.0.Alpha5 > > > related to https://community.jboss.org/message/728665#728665 : > Request the feature to use SSL certificate issued from OpenSSL directly from SSL attribute of management interface instead of available use of JKS . -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-210) Point to explicit security doc in server.log

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-210?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-210: ------------------------------ Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Point to explicit security doc in server.log > -------------------------------------------- > > Key: WFLY-210 > URL: https://issues.jboss.org/browse/WFLY-210 > Project: WildFly > Issue Type: Enhancement > Components: Server > Environment: Thinkpad T510 w/ 4 cores, 8Gb, running CSB > Reporter: Chuck Mosher > Assignee: Darran Lofthouse > Priority: Minor > Labels: eap6-ux > Fix For: 10.0.0.Alpha5 > > > Nice to warn me (in the server.log) that I have a security issue due to the cluster admin/user pwd using the defaults. Warning tells me to look at the docs; would it be possible to put it the hyperlink to the specific doc? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-421) Domain Mode JMX access through the HostController

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-421?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-421: ------------------------------ Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Domain Mode JMX access through the HostController > ------------------------------------------------- > > Key: WFLY-421 > URL: https://issues.jboss.org/browse/WFLY-421 > Project: WildFly > Issue Type: Task > Components: JMX, Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: JMX, investigation_required > Fix For: 10.0.0.Alpha5 > > > This task is first to review if this should be considered. > At the moment access to JMX is provided through the remoting connector of each AS instance - this task is to consider if we should actually make it available through the host controller with the host controller acting as a proxy. > The main motivation being to separate management and app traffic. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-414) Add a non-caching authentication cache

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-414?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-414: ------------------------------ Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Add a non-caching authentication cache > -------------------------------------- > > Key: WFLY-414 > URL: https://issues.jboss.org/browse/WFLY-414 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Anil Saldhana > Fix For: 10.0.0.Alpha5 > > > Add an option to either disable the authentication cache or a cache implementation that does not cache. > This is for incoming requests where we do not have a username and password available to use to retrieve an verify items from a cache. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 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 June 2015