February 2009 - jopr-issues - Jboss List Archives

[JBoss JIRA] Created: (JOPR-73) Add support for changing arguments passed to start/stop operations

by Charles Crouch (JIRA)

Add support for changing arguments passed to start/stop operations ------------------------------------------------------------------ Key: JOPR-73 URL: https://jira.jboss.org/jira/browse/JOPR-73 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5 Reporter: Charles Crouch Comes out of case: 264527 Right now if you change the start/stop scripts used by a JBAS instance the new scripts have to understand the same arguments which the default jbas ones takes, e.g. for shutdown thats: --server=jnp://localhost:1099 --user=myuser --password=mypassword --shutdown Given we enable people to specify their own scripts for these operations we should enable them to configure the arguments we pass to the scripts, just like we do when executing a JBAS script resource. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JOPR-39) possibility to rollback application to previously backuped WAR/EAR

by Joao Paulo Viragine (JIRA)

possibility to rollback application to previously backuped WAR/EAR ------------------------------------------------------------------ Key: JOPR-39 URL: https://jira.jboss.org/jira/browse/JOPR-39 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5 Affects Versions: 2.1 Reporter: Joao Paulo Viragine Priority: Optional It would be nice if we could rollback application to previously backuped WAR/EAR (like we can do with configurations) This issue depends on https://jira.jboss.org/jira/browse/JOPR-37 -- 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

15 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JOPR-37) be able to backup an existing package WAR/EAR during "Create new" operation

by Rafael Soares (JIRA)

be able to backup an existing package WAR/EAR during "Create new" operation ---------------------------------------------------------------------------- Key: JOPR-37 URL: https://jira.jboss.org/jira/browse/JOPR-37 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4 Affects Versions: 2.1, 2.2 Reporter: Rafael Soares Priority: Optional When a new package is created by "Create new" operation if the package already exists (is deployed) into deploy directory make a backup before replace it. Something like a new deployment option "Backup if package already exists". In this case a backup directory need be informed... -- 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

15 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JOPR-32) Deleting a WAR/EAR resource deletes the underlying file but doesn't actually undeploy it from JBAS

by Charles Crouch (JIRA)

Deleting a WAR/EAR resource deletes the underlying file but doesn't actually undeploy it from JBAS -------------------------------------------------------------------------------------------------- Key: JOPR-32 URL: https://jira.jboss.org/jira/browse/JOPR-32 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 4 Affects Versions: 2.1 Reporter: Charles Crouch Fix For: 2.2 This causes problems for Embedded (EMBJOPR-45) but should also show up when monitoring EAP instances with JON. Steps to reproduce the problem before the fix: 1) Setup an EAP instance, make sure you have the jmx-console.war deployed. I picked EAP because by default its deployment scanner is set for 60mins, iirc, but an JBAS instance where the deployment scanner has a long delay or is disabled should show this. 2) Inventory the instance, including the jmx-console.war 3) check you can hit the jmx-console: http://localhost:8080/jmx-console 4) Go to the Inventory tab of the EAP instance in JON and delete (not uninventory) the jmx-console.war. This should succeed. 5) Check the jmx-console.war is no longer in the /deploy folder 6) Check the EAP log and you should not see any entries talking about undeploying jmx-console 7) Check you can hit the jmx-console again: http://localhost:8080/jmx-console After the fix: 1).. 6) Check the EAP log and you *should* see entries talking about undeploying jmx-console 7) Check you *cannot* hit the jmx-console again: http://localhost:8080/jmx-console -- 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

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JOPR-25) JBossAS5 plugin: add missing props to Topic and Queue config defs and get config create/load/update and metrics working for Topics and Queues

by Ian Springer (JIRA)

JBossAS5 plugin: add missing props to Topic and Queue config defs and get config create/load/update and metrics working for Topics and Queues --------------------------------------------------------------------------------------------------------------------------------------------- Key: JOPR-25 URL: https://jira.jboss.org/jira/browse/JOPR-25 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 5 Affects Versions: 2.1 Reporter: Ian Springer Assignee: Ian Springer Fix For: 2.2 -- 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

15 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JOPR-34) need to incorporate new logo

by John Mazzitelli (JIRA)

need to incorporate new logo ---------------------------- Key: JOPR-34 URL: https://jira.jboss.org/jira/browse/JOPR-34 Project: Jopr Issue Type: Task Reporter: John Mazzitelli Priority: Minor Attachments: jopr_logo_200px.png Installer shows the JBoss(tm) logo Server UI shows the RHQ logo. We should incorporate the new logo (see attached) -- 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

15 years, 2 months

2
2
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

15 years, 2 months

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

15 years, 2 months

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

15 years, 2 months

2
4
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

15 years, 2 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues February 2009