September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-47) Refactor the RemotingConnectorServer / JMXConnectorServer to pull initial comms earlier

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-47: -------------------------------------- Summary: Refactor the RemotingConnectorServer / JMXConnectorServer to pull initial comms earlier Key: REMJMX-47 URL: https://issues.jboss.org/browse/REMJMX-47 Project: Remoting JMX Issue Type: Task Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.4.CR1 The JMXConnectorServer implementation is supposed to associate incoming connections with a single MBean server - with the addition of an MBeanServerLocator in addition to the possibility of proxied requests to a remote MBeanServer there is also the possibility of multiple MBeanServers in the same process. Once a connection is established the connection is associated with the RemotingConnectorServer so the selection of MBeanServer / RemotingConnectorServer needs to happen before this. For version 2 of the protocol this association should happen after begin() is called i.e. the initial message exchange allows for the key/value pairs to be set to select the MBeanServer and then when begin is called the final association occurs. For version 1 we will be assuming only one MBeanServer or the MBeanServerLocator will need to select one with no properties, in this case will will assume begin has been called as soon as the connection is established. Although this change will move some of the initial negotiation of the connection out of the RemotingConnectorServer it is MANDATORY that for the initial version negotiation and for version 1 that there are no alterations to the protocol - version 2 however is a new protocol so AFTER it has been selected the protocol can diverge. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
3
0 / 0

[JBoss JIRA] (REMJMX-51) Add a test that tests all protocol versions currently run.

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-51: -------------------------------------- Summary: Add a test that tests all protocol versions currently run. Key: REMJMX-51 URL: https://issues.jboss.org/browse/REMJMX-51 Project: Remoting JMX Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.5.CR1 This is a fairly simple smoke test that will test each version, to achieve this all other versions will be excluded, the server will be started and then the client will make a series of calls. As new versions are added later this test will automatically run the same test for them all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
2
0 / 0

[JBoss JIRA] (JGRP-1513) windows and linux

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1513?page=com.atlassian.jira.plugin.... ] Bela Ban deleted JGRP-1513: --------------------------- > windows and linux > ----------------- > > Key: JGRP-1513 > URL: https://issues.jboss.org/browse/JGRP-1513 > Project: JGroups > Issue Type: Bug > Reporter: Balamurali L > Assignee: Bela Ban > -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1499) Configuration error message references "start_port" property that does not exist

by Dennis Reed (JIRA)

Dennis Reed created JGRP-1499: --------------------------------- Summary: Configuration error message references "start_port" property that does not exist Key: JGRP-1499 URL: https://issues.jboss.org/browse/JGRP-1499 Project: JGroups Issue Type: Bug Affects Versions: 3.0.11 Reporter: Dennis Reed Assignee: Dennis Reed Error message refers to the TCP "start_port" property which has been replaced with "bind_port". Error: java.lang.IllegalArgumentException: start_port cannot be set to 0, as no dynamic discovery protocol (e.g. MPING or TCPGOSSIP) has been detected. at org.jgroups.protocols.BasicTCP.init(BasicTCP.java:74) at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:847) at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:469) at org.jgroups.JChannel.init(JChannel.java:795) at org.jgroups.JChannel.<init>(JChannel.java:166) ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-5494) Add support for a modular AS7 build

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5494: ----------------------------------- Summary: Add support for a modular AS7 build Key: AS7-5494 URL: https://issues.jboss.org/browse/AS7-5494 Project: Application Server 7 Issue Type: Feature Request Components: Build System Reporter: Thomas Diesler Assignee: Thomas Diesler A modular build would allow to configure the set of subsystems that get included in the distribution. It must be guaranteed that the subset of system modules is the transitive set reachable from the configured subsystems. It could be the basis of a we-profile or simple osgi runtime. -- 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

11 years, 9 months

1
1
0 / 0

[JBoss JIRA] (JGRP-1513) windows and linux

by Balamurali L (JIRA)

Balamurali L created JGRP-1513: ---------------------------------- Summary: windows and linux Key: JGRP-1513 URL: https://issues.jboss.org/browse/JGRP-1513 Project: JGroups Issue Type: Bug Reporter: Balamurali L Assignee: Bela Ban -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3624) Memory leak in Planner benchmarker statistic: the Solver instance lives beyond SingleBenchmark.call()

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3624: ----------------------------------------- Summary: Memory leak in Planner benchmarker statistic: the Solver instance lives beyond SingleBenchmark.call() Key: JBRULES-3624 URL: https://issues.jboss.org/browse/JBRULES-3624 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Critical It's not noticeable for small or medium problems, because the number of Solvers is relatively low (1-100 per benchmark). But a Solver has a clone of the Solution, so for really big problems, for which the Solution takes a big chunk of the memory, this memory leak causes OOM after a few single benchmarks, usually near the end after running a long time. Big PITA in that case. -- 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

11 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7468) Memory leak in org.jboss.security.plugins.authorization.JBossAuthorizationContext

by Ganesh Ingle (JIRA)

Memory leak in org.jboss.security.plugins.authorization.JBossAuthorizationContext --------------------------------------------------------------------------------- Key: JBAS-7468 URL: https://jira.jboss.org/jira/browse/JBAS-7468 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.1.0.GA, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA Environment: JBoss Version: jboss-5.1.0.GA, OS: Linux (2.6.18-164.el5), Architecture: amd64 64bit, JVM: Java HotSpot(TM) 64-Bit Server VM (14.0-b16, mixed mode) Reporter: Ganesh Ingle Assignee: Anil Saldhana Our use case (only security related portion is mentioned here): Axis 1.4 webservice, standard J2EE declarative security through WEB-INF/web.xml, a http client sends soap request and BASIC auth information, the JBoss server performs authentication and authorization as per WEB-INF/web.xml configuration. We did a performance/stability test on above web service. After 8.5 million requests the server gone out of memory. We did heap dump analysis using VisualVM tool and found that the class org.jboss.security.plugins.authorization.JBossAuthorizationContext is consuming most of the memory. This class has a memer array named "controlFlags", this array was showing 25.7 million ControlFlag entries. When we investigated the code we found that there is one instance of JBossAuthorizationManager per security domain and this manager has one instance of JBossAuthorizationContext. For every authorization the JBossAuthorizationContext initializes authorization modules and pushes their control flags (instances of class ControlFlag) in member arrays. When the authorization is complete, a commit/abort is invoked on all modules and finally the "modules" array is cleared. However, the "controlFlags" array is not cleared. We checked the entire class, this array never gets cleared. We changed the code to clear both "modules" and "controlFlags" array in a finally block in method JBossAuthorizationContext.authorize(final Resource resource, final Subject subject, final RoleGroup callerRoles). We ran a 50million test after this fix, the test was successful which proves the fix worked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

7
13
0 / 0

[JBoss JIRA] (JGRP-1509) GMS: low leave_timeout may cause incorrect view installation

by Bela Ban (JIRA)

Bela Ban created JGRP-1509: ------------------------------ Summary: GMS: low leave_timeout may cause incorrect view installation Key: JGRP-1509 URL: https://issues.jboss.org/browse/JGRP-1509 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0.15, 3.2 - {A} - B joins, then C, the view is A2={A,B,C} - *No* messages are sent - GMS.leave_timeout=100 - NAKACK2.xmit_interval=1000 - A leaves gracefully (JChannel.disconnect()) - A multicasts B3={B,C}, the seqno is #3 - B discarded A#2 (view {A,B,C}), as it was not yet server - B now asks A for retransmission of #2 before it can deliver #3 (the new view) (- The retransmission kicks in ca. every 1 sec) - However, A is gone, so C will loop asking A to retransmit #3 and will therefore never install view B2 ! -- 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

11 years, 9 months

1
9
0 / 0

[JBoss JIRA] (LOGTOOL-54) Remove usage of JBL annotations

by James Perkins (JIRA)

James Perkins created LOGTOOL-54: ------------------------------------ Summary: Remove usage of JBL annotations Key: LOGTOOL-54 URL: https://issues.jboss.org/browse/LOGTOOL-54 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.1.0.Beta1 Currently the processor is directly using the JBoss Logging annotations. Using the AnnotationMirror will allow the annotations to be removed from the JBoss Logging project. -- 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

11 years, 9 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2012