March 2009 - jopr-issues - Jboss List Archives

[JBoss JIRA] Created: (JOPR-91) TC5: Connector availability does not go red when stopped

by Heiko W. Rupp (JIRA)

TC5: Connector availability does not go red when stopped -------------------------------------------------------- Key: JOPR-91 URL: https://jira.jboss.org/jira/browse/JOPR-91 Project: Jopr Issue Type: Bug Components: Plugin - Tomcat Affects Versions: 2.2 Reporter: Heiko W. Rupp According to test case 5448 it should go red when stopped -- 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

17 years

2
2
0 / 0

[JBoss JIRA] Created: (JOPR-92) TC5: failure on shutdown operation (NPE)

by Heiko W. Rupp (JIRA)

TC5: failure on shutdown operation (NPE) ---------------------------------------- Key: JOPR-92 URL: https://jira.jboss.org/jira/browse/JOPR-92 Project: Jopr Issue Type: Bug Components: Plugin - Tomcat Affects Versions: 2.2 Reporter: Heiko W. Rupp Fix For: 2.2 Issued a shutdown operation TC Server is shutting down, but the operation returns a failure I get a failure to shut down: ava.lang.NullPointerException at org.jboss.on.plugins.tomcat.TomcatServerOperationsDelegate.shutdownViaScript(TomcatServerOperationsDelegate.java:276) at org.jboss.on.plugins.tomcat.TomcatServerOperationsDelegate.shutdown(TomcatServerOperationsDelegate.java:247) at org.jboss.on.plugins.tomcat.TomcatServerOperationsDelegate.invoke(TomcatServerOperationsDelegate.java:117) at org.jboss.on.plugins.tomcat.TomcatServerComponent.invokeOperation(TomcatServerComponent.java:366) Reason is that results.exitCode is null and if (results.getExitCode() != 0) { throw new RuntimeException("Error executing shutdown script while stopping Tomcat instance. Exit code [" + results.getExitCode() + "]"); } the comparision in getExitCode != 0 tries to do an implicit intValue() on it which results in a NPE -- classical boxing 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

17 years

2
2
0 / 0

[JBoss JIRA] Created: (JOPR-93) Bogus deployment descriptor

by Heiko W. Rupp (JIRA)

Bogus deployment descriptor --------------------------- Key: JOPR-93 URL: https://jira.jboss.org/jira/browse/JOPR-93 Project: Jopr Issue Type: Bug Components: Plugin - Tomcat Affects Versions: 2.2 Reporter: Heiko W. Rupp Priority: Minor Fix For: 2.2 2009-03-11 14:50:33,704 ERROR [OperationManager.invoker-1] (rhq.core.pc.operation.OperationInvocation)- Plugin error: Operation [start] is defined as returning no results, but it returned non-null results: Configuration[id=0, operationResult=Server has been started.] -- 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

17 years

2
3
0 / 0

[JBoss JIRA] Created: (JOPR-87) JBossAS Plugin: add support for deployment of new "Jar Library" packages

by Ian Springer (JIRA)

JBossAS Plugin: add support for deployment of new "Jar Library" packages ------------------------------------------------------------------------ Key: JOPR-87 URL: https://jira.jboss.org/jira/browse/JOPR-87 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4 Affects Versions: 2.1 Reporter: Ian Springer The place where this would be implemented is in JBossASServerComponent.deployPackages(), which currently contains the following code: } else if (packageTypeName.equals(PACKAGE_TYPE_LIBRARY)) { throw new UnsupportedOperationException("Deployment of new libraries is not supported by the plugin."); } -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JOPR-54) Standalone Tomcat plugin that is Apache and JBoss EWS compatible

by Jay Shaughnessy (JIRA)

Standalone Tomcat plugin that is Apache and JBoss EWS compatible ---------------------------------------------------------------- Key: JOPR-54 URL: https://jira.jboss.org/jira/browse/JOPR-54 Project: Jopr Issue Type: Feature Request Affects Versions: 2.1 Reporter: Jay Shaughnessy Assignee: Jay Shaughnessy Fix For: 2.2 Complete work on a Standalone Tomcat plugin that can manage both JBoss EWS and Apache tomcat instances. The design page for this work is here: https://www.jboss.org/community/docs/DOC-13257 -- 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

17 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JOPR-55) Tomcat plugin Discovery

by Jay Shaughnessy (JIRA)

Tomcat plugin Discovery ----------------------- Key: JOPR-55 URL: https://jira.jboss.org/jira/browse/JOPR-55 Project: Jopr Issue Type: Sub-task Affects Versions: 2.1 Reporter: Jay Shaughnessy Assignee: Jay Shaughnessy Fix For: 2.2 This is to track the Discovery portion of the Standalone Tomcat plugin. This encompasses Server/Service hierarcrhy definition, resource definition ( including properties, metrics..), process discovery etc.. -- 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

17 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JOPR-66) Support Response time metrics in Tomcat plugin

by Jay Shaughnessy (JIRA)

Support Response time metrics in Tomcat plugin ---------------------------------------------- Key: JOPR-66 URL: https://jira.jboss.org/jira/browse/JOPR-66 Project: Jopr Issue Type: Sub-task Reporter: Jay Shaughnessy Assignee: Jay Shaughnessy Fix For: 2.2 This is to track work for implementing response time metrics for web apps in the Tomcat plugin. -- 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

17 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JOPR-86) use unfiltered versions of i18n files so project can re-brand without storing its own copies

by John Mazzitelli (JIRA)

use unfiltered versions of i18n files so project can re-brand without storing its own copies -------------------------------------------------------------------------------------------- Key: JOPR-86 URL: https://jira.jboss.org/jira/browse/JOPR-86 Project: Jopr Issue Type: Task Affects Versions: 2.2 Reporter: John Mazzitelli Assignee: John Mazzitelli The upstream rhq project now keeps unfiltered copies of the files that need to get re-branded (see RHQ-1747). Fix the build scripts to use these so Jopr doesn't have to maintain its own copies. -- 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

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JOPR-84) Make JBAS availability check take account of which actual instance is responding on jnp url

by Charles Crouch (JIRA)

Make JBAS availability check take account of which actual instance is responding on jnp url ------------------------------------------------------------------------------------------- Key: JOPR-84 URL: https://jira.jboss.org/jira/browse/JOPR-84 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4 Affects Versions: 2.1 Reporter: Charles Crouch Fix For: 2.2 Use case: I have 2 JBAS instances on a box. Sometimes i run one instance, sometimes I run another, based on what application version I have deployed. Both instances have different install paths but share ip and port settings (which is fine because they dont both run at the same time) Over time a JON agent running on this box will detect both instances so they can be added to the inventory. The issue is that in JON both resources will show as available because they both have the same jnp url. The suggestion would be to make the getAvailabilityCheck be smarter so that the component recognizes when its querying an instance that its not associated with, e.g. on JBossASServerComponent public AvailabilityType getAvailability() { try { EmsConnection connection = loadConnection(); EmsBean bean = connection.getBean("jboss.system:type=ServerConfig"); File serverHomeViaJNP = (File) bean.getAttribute("ServerHomeDir").refresh(); if (this.configPath.equals(serverHomeViaJNP)) return AvailabilityType.UP; else // a different server must have been started on our jnp url return AvailabilityType.DOWN; } catch (Exception e) { return AvailabilityType.DOWN; } } This is going to break existing resources (they will show red availability) where the configPath no longer matches where the instance is actually installed, though script/filesystem based operations (e.g. start, deploy apps) would already be broken for these resources. Re-inventorying the resources should fix this. -- 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

17 years, 1 month

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues March 2009