March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7134) Modifying ManagedOperation to return either a composite value containing a Boolean and a String

by Noam Malki (JIRA)

Modifying ManagedOperation to return either a composite value containing a Boolean and a String ----------------------------------------------------------------------------------------------- Key: JBAS-7134 URL: https://jira.jboss.org/jira/browse/JBAS-7134 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Noam Malki Assignee: Jesper Pedersen Priority: Minor Returning a composite value containing a Boolean and a String would be useful. For example, when invoking a test operation it would be useful to get a String with the specific failure message if the operation failed (please see JOPR-324). -- 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

14 years, 10 months

5
4
0 / 0

[JBoss JIRA] Updated: (JBAS-1436) Improved management

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-1436?page=com.atlassian.jira.plug... ] Jesper Pedersen updated JBAS-1436: ---------------------------------- Fix Version/s: Backlog (was: JBossAS-6.0.0.M3) Put this into the "Backlog" category - new management and statistics features should be done with the new JCA implementation, but this JIRA can serve as a discussion starting point in the forum. > Improved management > ------------------- > > Key: JBAS-1436 > URL: https://jira.jboss.org/jira/browse/JBAS-1436 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-5.1.0.GA > Reporter: Adrian Brock > Assignee: Jesper Pedersen > Fix For: Backlog > > > Forum Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48682 > **This is a holder issue. Each section should be raised as a new issue as it is > developed with a link from this issue.** > There are a number of areas in JCA that need better management capabilities. > Some of these stats may also reveal the need for new configuration/tuning parameters. > In core JCA: > 1) Better visibility on the ManagedConnectionFactory. > This is currently a DynamicMBean that provides basic config parameters, but we could also > provide a proxy/wrapper to provide statistics of operations on the factory and its > ManagedConnections. > a) createManagedConnections > b) matchManagedConnections > c) events on from the listeners > 2) Better visibility of the Pool(s) > Only top level statistics are provided (you cannot see the subpools). > The statistics are also not synchronized with the pool (for performance reasons > and also the fact that each stat is retrieved on individual MBean getAttribute requests) > Additional statistics could include wait times when requests are waiting on an empty pool, > idle time of unused connections, etc. > 3) Better visibility of the ConnectionManager > Currently this has no visibility for management. > Its main responsibilties are transactions enlistment and security. > e.g. This could show how long is wasted because <track-connection-by-tx/> does not > return the connection the pool until transaction completion. > 4) JDBC resource adapter > PreparedStatementCache stats > Query time stats > etc. > 5) JMS resource adapter > Message send/receive stats > 6) Inbound messaging > Stats for message delivery > 7) Transaction inflow > Stats for transaction inflow and also display a list of current inbound transactions > 8) Work management > Stats for the work management pools and timers -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6074) Investigate Pool MBean removal

by Anil Saldhana (JIRA)

Investigate Pool MBean removal ------------------------------ Key: JBAS-6074 URL: https://jira.jboss.org/jira/browse/JBAS-6074 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB2, JMX Affects Versions: JBossAS-5.0.0.CR2 Reporter: Anil Saldhana Assignee: Alexey Loubyansky Fix For: JBossAS-5.0.0.GA Forum Thread for details. -- 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

14 years, 10 months

5
8
0 / 0

[JBoss JIRA] Created: (JBAS-3632) Too early checking of not closing connections

by Adrian Brock (JIRA)

Too early checking of not closing connections --------------------------------------------- Key: JBAS-3632 URL: http://jira.jboss.com/jira/browse/JBAS-3632 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.CR1 Reporter: Adrian Brock Assigned To: Weston Price Priority: Minor In the case where a transaction is ended early, e.g. JBossTM rollsback transactions at a timeout immediately, the cached connection manager is firing connection not closed events. This is because the ejb is still in the invocation with the connection open but the transaction synchronization is fired by the rollback/timeout. -- 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

14 years, 10 months

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-7791) Enhance MBean operation JBossManagedConnectionPool.testConnection to use subject

by Scott Marlow (JIRA)

Enhance MBean operation JBossManagedConnectionPool.testConnection to use subject -------------------------------------------------------------------------------- Key: JBAS-7791 URL: https://jira.jboss.org/jira/browse/JBAS-7791 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Scott Marlow Assignee: Jesper Pedersen Priority: Minor Fix For: JBossAS-6.0.0.M3 -- 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

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-226) Allow multiple deployments to change state at once

by Thomas Diesler (JIRA)

Allow multiple deployments to change state at once -------------------------------------------------- Key: JBDEPLOY-226 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-226 Project: JBoss Deployers Issue Type: Feature Request Components: deployer Reporter: Thomas Diesler Fix For: JBDEPLOY-2.2.x Currently the BundleManager can only reslove bundles one-by-one deployerClient.change(unit.getName(), DeploymentStages.CLASSLOADER); deployerClient.checkComplete(unit.getName()); bundleState.changeState(Bundle.RESOLVED); this results in uglyness in PackageAdmin int resolved = 1; while (resolved > 0) { resolved = 0; Iterator<OSGiBundleState> it = resolvableBundles.iterator(); while (it.hasNext()) { OSGiBundleState bundleState = it.next(); if (bundleManager.resolveBundle(bundleState, false)) { it.remove(); resolved++; } } } PackageAdmin should be able to use an API that resolves multiple deployemnts at once. -- 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

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-5897) Web Profile Prototype

by Adrian Brock (JIRA)

Web Profile Prototype --------------------- Key: JBAS-5897 URL: https://jira.jboss.org/jira/browse/JBAS-5897 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: Adrian Brock Assignee: Adrian Brock This is a holder task for prototype of the "web profile". This is a JBossAS configuration that looks forward to the JavaEE6 Web Profile. The initial prototype work will be done in the testsuite to validate the dependencies and make sure it works. -- 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

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-6558) Factor out system-jmx into core mc and deployers projects

by Adrian Brock (JIRA)

Factor out system-jmx into core mc and deployers projects --------------------------------------------------------- Key: JBAS-6558 URL: https://jira.jboss.org/jira/browse/JBAS-6558 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: MicroContainer bus Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-6.0.0.Alpha1 The ServiceController and its associated deployers should be moved into the relevant MC projects. i.e. the jmx model should be in a jmx-mc-int project and the "ServiceDeployers" should be in the deployers project. -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6578) Move the jmx deployers to the jboss-deployers project

by Adrian Brock (JIRA)

Move the jmx deployers to the jboss-deployers project ----------------------------------------------------- Key: JBAS-6578 URL: https://jira.jboss.org/jira/browse/JBAS-6578 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-6.0.0.Alpha1 -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5339) Support for JMX annotations

by Galder Zamarreno (JIRA)

Support for JMX annotations --------------------------- Key: JBAS-5339 URL: http://jira.jboss.com/jira/browse/JBAS-5339 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Fix For: JBossAS-5.0.1.CR1 Provide support for JSR-255 JMX annotations (@ManagedResource, @ManagedAttribute, @ManagedOperation...etc) until Java 7 is supported. -- 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

14 years, 10 months

4
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010