September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1369) MuxRpcDispatcher may encapsulate infinitely RequestOption's filter with NoMuxHandlerRspFilter

by Benoit Leblanc (JIRA)

MuxRpcDispatcher may encapsulate infinitely RequestOption's filter with NoMuxHandlerRspFilter --------------------------------------------------------------------------------------------- Key: JGRP-1369 URL: https://issues.jboss.org/browse/JGRP-1369 Project: JGroups Issue Type: Bug Affects Versions: 2.12.1 Reporter: Benoit Leblanc Assignee: Bela Ban MuxRpcDispatcher alters RequestOption's filter by encapsulating it with a NoMuxHandlerRspFilter. Passing the same instance of RequestOptions to rpc calls leads to : java.lang.StackOverflowError at org.jgroups.blocks.mux.NoMuxHandlerRspFilter.isAcceptable(NoMuxHandlerRspFilter.java:24) at org.jgroups.blocks.mux.NoMuxHandlerRspFilter.isAcceptable(NoMuxHandlerRspFilter.java:24) ..... ..... Solutions : 1/ "Clone" RequestOption at each call like fix used in https://issues.jboss.org/browse/JGRP-1271. The drawback with this solution, is the performance concern : useless object creation if a RequestOption is reused. 2/ Don't encapsulate RequestOption is a NoMuxHandlerRspFilter is already setted. Modification concerns two classes : * NoMuxHandlerRspFilter private NoMuxHandlerRspFilter(RspFilter filter) { this.filter = filter; } public static RspFilter createInstance(RspFilter filter) { if (filter instanceof NoMuxHandlerRspFilter) { return filter; } return new NoMuxHandlerRspFilter(filter) ; } * MuxRpcDispatcher protected GroupRequest cast(Collection<Address> dests, Message msg, RequestOptions options, boolean blockForResults) { RspFilter filter = options.getRspFilter(); return super.cast(dests, msg, options.setRspFilter(NoMuxHandlerRspFilter.createInstance(filter)), blockForResults); } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
6
0 / 0

[JBoss JIRA] Created: (JGRP-1336) GMS: if a member leaving takes a long time, it can get merged back into the cluster

by Bela Ban (JIRA)

GMS: if a member leaving takes a long time, it can get merged back into the cluster ----------------------------------------------------------------------------------- Key: JGRP-1336 URL: https://issues.jboss.org/browse/JGRP-1336 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.1 When JChannel.disconnect() is called, and the leave processing takes a long time (e.g. due to excessive CPU use and GC), then it can happen that the leaving node is merged back into the cluster. This occurred in the Infinispan testsuite which is run in parallel (high CPU contention). SOLUTION: after sending the LEAVE request, disable discovery, so MERGE2 won't discover us. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1966) Add list-snapshots to operations available to GET requests on HTTP interface

by Darran Lofthouse (JIRA)

Add list-snapshots to operations available to GET requests on HTTP interface ---------------------------------------------------------------------------- Key: AS7-1966 URL: https://issues.jboss.org/browse/AS7-1966 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 The operations allowed using GET are the read operations, list-snapshots is a read only operation so should be allowed over GET. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1432) Adding director element to action-log in a virtual-host causes xml parse error

by dan ginsberg (JIRA)

Adding director element to action-log in a virtual-host causes xml parse error ------------------------------------------------------------------------------- Key: AS7-1432 URL: https://issues.jboss.org/browse/AS7-1432 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Environment: Linux x86_64 Reporter: dan ginsberg Assignee: David Lloyd In standalone.xml, in a virutal-server, 1) add an access-log element Find: server starts correctly and creates the access log 2) in the access-log element, add a directory element Find: server no longer starts correctly. you may see an xml parse error logged, or you may just find that subsequent xml is not correclty parsed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

[JBoss JIRA] Created: (LOGMGR-32) NPE in Formatters

by Stuart Douglas (JIRA)

NPE in Formatters ----------------- Key: LOGMGR-32 URL: https://issues.jboss.org/browse/LOGMGR-32 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.2.0.GA Reporter: Stuart Douglas Assignee: David Lloyd In Formatters on line 452 there is a line: exceptionClass.getProtectionDomain().getCodeSource().getLocation() which can cause a NPE. This NPE then gets swallowed by: catch (Throwable t) { // ignore } This makes is extremely difficult to set a NPE breakpoint when debugging, as it keeps getting tripped by there spurious exceptions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1961) BufferPool platform mbean resources are registered under the wrong parent resource

by Brian Stansberry (JIRA)

BufferPool platform mbean resources are registered under the wrong parent resource ---------------------------------------------------------------------------------- Key: AS7-1961 URL: https://issues.jboss.org/browse/AS7-1961 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Alpha1, 7.0.2.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 ManagementResourceRegistration bufPool = memPoolRoot.registerSubModel(PathElement.pathElement(NAME), new DescriptionProvider() { ... That "memPoolRoot" should be "bufPoolRoot". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3227) Drools is incorrectly expiring events in CLOUD mode

by Edson Tirelli (JIRA)

Drools is incorrectly expiring events in CLOUD mode --------------------------------------------------- Key: JBRULES-3227 URL: https://issues.jboss.org/browse/JBRULES-3227 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.3.0.CR1 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.2.1.Final, 5.3.0.Final Regression introduced in 5.3.0.CR1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-74) Policy Management Console using JBoss SEAM

by Anil Saldhana (JIRA)

Policy Management Console using JBoss SEAM ------------------------------------------ Key: SECURITY-74 URL: http://jira.jboss.com/jira/browse/SECURITY-74 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossXACML-Console Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Need for a progressive Policy Management console using JBoss SEAM. The JAXB2 object model provided with JBoss XACML can be used to construct the policies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1943) HTTP management interface ignores wrong operation in GET request

by Dominik Pospisil (JIRA)

HTTP management interface ignores wrong operation in GET request ---------------------------------------------------------------- Key: AS7-1943 URL: https://issues.jboss.org/browse/AS7-1943 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Alpha1 Reporter: Dominik Pospisil Assignee: Brian Stansberry HTTP management interface ignores wrong operation in GET request. I think that ignoring wrong input in public API is wrong idea and should be avoided. Error should be returned instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1914) Proper description providers for Vault

by Kabir Khan (JIRA)

Proper description providers for Vault -------------------------------------- Key: AS7-1914 URL: https://issues.jboss.org/browse/AS7-1914 Project: Application Server 7 Issue Type: Feature Request Components: Security Reporter: Kabir Khan Assignee: Anil Saldhana Fix For: 7.1.0.Beta1 See https://github.com/jbossas/jboss-as/pull/333 for details. But basically I see some instances where attributes have type=LIST and no value-type -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2011