January 2009 - jopr-issues - Jboss List Archives

[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, 9 months

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, 9 months

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, 9 months

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, 9 months

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, 9 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, 9 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, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JOPR-56) Support Start/Shutdown operations

by Jay Shaughnessy (JIRA)

Support Start/Shutdown operations --------------------------------- Key: JOPR-56 URL: https://jira.jboss.org/jira/browse/JOPR-56 Project: Jopr Issue Type: Sub-task Affects Versions: 2.1 Reporter: Jay Shaughnessy Assignee: Fady Matar Fix For: 2.2 Start/Shutdown script operations should be supported for all OS's and supported Apache/EWS versions. If Tomcat provides MBean support for Shutdown then both script and MBean shutdown should be provided. Discovery already provides some support for the necessary properties, default script value, and operation definitions. But it remains to ensure all are working on the various configurations and that operation status values return appropriately. -- 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, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JOPR-28) Add option to configure JBoss AS login module (conf/login-config.xml) as we can do with datasources

by Joao Paulo Viragine (JIRA)

Add option to configure JBoss AS login module (conf/login-config.xml) as we can do with datasources --------------------------------------------------------------------------------------------------- Key: JOPR-28 URL: https://jira.jboss.org/jira/browse/JOPR-28 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5 Reporter: Joao Paulo Viragine Add option to configure JBoss AS login module (conf/login-config.xml) as we can do with datasources -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JOPR-47) capture the return code from scripts and mark the operation status appropriately

by Joseph Marques (JIRA)

capture the return code from scripts and mark the operation status appropriately -------------------------------------------------------------------------------- Key: JOPR-47 URL: https://jira.jboss.org/jira/browse/JOPR-47 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5 Affects Versions: 2.1 Reporter: Joseph Marques Assignee: Joseph Marques Fix For: 2.2 presently, there is no way for a script execution to fail based on the return code. we should capture this and mark the operation as either a success or failure as appropriate. -- 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, 10 months

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues January 2009