jopr-issues December 2008

jopr-issues@lists.jboss.org

1 participants
24 discussions

[JBoss JIRA] Created: (JOPR-30) have server plugin expose comm layer calltime data

by John Mazzitelli (JIRA)

have server plugin expose comm layer calltime data -------------------------------------------------- Key: JOPR-30 URL: https://jira.jboss.org/jira/browse/JOPR-30 Project: Jopr Issue Type: Feature Request Reporter: John Mazzitelli Assignee: John Mazzitelli Priority: Minor Have the rhq server plugin expose the metrics that will be introduced here: http://jira.rhq-project.org/browse/RHQ-1199 -- 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

16 years

1
3
0 / 0

[JBoss JIRA] Moved: (JOPR-33) jboss-as plugin: when creating or updating a Topic or Queue, what is entered for the JNDI Name resource config prop is ignored and overwritten w/ "/topic/<topic-name>" or "/queue/<queue-name>"

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-33?page=com.atlassian.jira.plugin... ] Charles Crouch moved JBMANCON-439 to JOPR-33: --------------------------------------------- Project: Jopr (was: JBoss AS 5.0 Management Console) Key: JOPR-33 (was: JBMANCON-439) Component/s: Plugin - JBoss AS 4 (was: Plugins) Fix Version/s: 2.2 (was: 1.0 GA) Affects Version/s: 2.1 (was: 1.0 Beta 1) > jboss-as plugin: when creating or updating a Topic or Queue, what is entered for the JNDI Name resource config prop is ignored and overwritten w/ "/topic/<topic-name>" or "/queue/<queue-name>" > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JOPR-33 > URL: https://jira.jboss.org/jira/browse/JOPR-33 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 4 > Affects Versions: 2.1 > Reporter: Ian Springer > Assignee: Ian Springer > Fix For: 2.2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Moved: (JOPR-31) Easy management of multiple JBoss AS instance for process isolation

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-31?page=com.atlassian.jira.plugin... ] Charles Crouch moved EMBJOPR-43 to JOPR-31: ------------------------------------------- Project: Jopr (was: Embedded Jopr) Key: JOPR-31 (was: EMBJOPR-43) > Easy management of multiple JBoss AS instance for process isolation > ------------------------------------------------------------------- > > Key: JOPR-31 > URL: https://jira.jboss.org/jira/browse/JOPR-31 > Project: Jopr > Issue Type: Feature Request > Reporter: Francisco Jose Peredo Noguez > > Since java has no real process isolation, a misbehaved JEE application can bring down an entire server (if it has a bug with an infinite-loop for example, or simply because each time applications are undeployed the JVM is no able to really reclaim all the memory spaced because of bugs inherent in the JVM design). In OAS (Oracle Application Server) this problem is solved by using multiple instances, this is of course possible in JBoss (nobody prevents you from running several instances of Jboss in your server) but has to be done manually. I would like to see an option in Jopr UI where I could just click a button saying: "Create new JBoss Instance" and then be able to "Tranfer selected applications to another Jboss Instance" that way related applications can be kept in the same instance, and unrelated ones can be kept in different instances that can be restarted independently if the misbehave. -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JOPR-29) Jars without Manifest can't be handled

by Heiko W. Rupp (JIRA)

Jars without Manifest can't be handled -------------------------------------- Key: JOPR-29 URL: https://jira.jboss.org/jira/browse/JOPR-29 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 4 Affects Versions: 2.1 Reporter: Heiko W. Rupp Assignee: Heiko W. Rupp Fix For: 2.2 It seems that the failing line is this: String version = jf.getManifest().getMainAttributes().getValue(Attributes.Name.IMPLEMENTATION_VERSION); The result is that no packages are retrieved for the JBoss AS instance being monitored. Surrounding the block of code that attempts to retrieve the manifest solves this issue. -- 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

16 years

1
1
0 / 0

← Newer
1
2
3
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues December 2008