February 2009 - jopr-issues - Jboss List Archives

[JBoss JIRA] Created: (JOPR-59) Update JOPR public and private documentation to include guide for setting up monitoring of ESBs under JOPR for SOA

by Mark Burchard (JIRA)

Update JOPR public and private documentation to include guide for setting up monitoring of ESBs under JOPR for SOA ------------------------------------------------------------------------------------------------------------------ Key: JOPR-59 URL: https://jira.jboss.org/jira/browse/JOPR-59 Project: Jopr Issue Type: Task Environment: N/A Reporter: Mark Burchard Priority: Minor The documentation already exists: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html-single/Ad... It just needs to be linked from or integrated into the online documentation and re-branded as JOPR. -- 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] Moved: (JOPR-79) Errors when deleting a webapp with vhosts

by Heiko W. Rupp (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-79?page=com.atlassian.jira.plugin... ] Heiko W. Rupp moved JBNADM-3486 to JOPR-79: ------------------------------------------- Project: Jopr (was: JBoss Network - Administration) Key: JOPR-79 (was: JBNADM-3486) Workflow: jira (was: JBoss Network Workflow v5) Component/s: Plugin - JBoss AS 4 (was: Plugins) Fix Version/s: (was: 2.1) Affects Version/s: 2.1 (was: 2.1) Security: (was: JBoss Internal) > Errors when deleting a webapp with vhosts > ----------------------------------------- > > Key: JOPR-79 > URL: https://jira.jboss.org/jira/browse/JOPR-79 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 4 > Affects Versions: 2.1 > Reporter: Heiko W. Rupp > Priority: Minor > > With the new vhost code of JBNADM-3469, a web app with multiple vhosts will create multiple resources. > Deleting all of them will result with failed delete requests as the first delete already removed the file, so the other deletes run into the empty. > Only deleting one war file entry will delete the underlying file, but the other vhosts will stay in inventory and be marked as down. -- 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

1
0
0 / 0

[JBoss JIRA] Moved: (JOPR-78) Base webapp monitoring only on context root

by Heiko W. Rupp (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-78?page=com.atlassian.jira.plugin... ] Heiko W. Rupp moved JBNADM-2194 to JOPR-78: ------------------------------------------- Project: Jopr (was: JBoss Network - Administration) Key: JOPR-78 (was: JBNADM-2194) Workflow: jira (was: JBoss Network Workflow v5) Component/s: Plugin - JBoss AS 4 (was: FX - Inventory) Affects Version/s: 2.1 (was: 2.0 beta 1) Security: (was: JBoss Internal) > Base webapp monitoring only on context root > ------------------------------------------- > > Key: JOPR-78 > URL: https://jira.jboss.org/jira/browse/JOPR-78 > Project: Jopr > Issue Type: Feature Request > Components: Plugin - JBoss AS 4 > Affects Versions: 2.1 > Reporter: Heiko W. Rupp > > In Jon 1.4, many parameters of webapp monitoring are determined by the name and/or location of the war file that forms the web app. > If a client a policy of deploying web apps with the archive name including the version > myApp-1.1.war, myApp-1.2.war and so on, then JON 1.4 will treat them as different apps, *even* when they > run at the same context-root of /myApp/. > We should make it easier for users to follow such a convention by identifying web apps by context-root. -- 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

1
0
0 / 0

[JBoss JIRA] Work started: (JOPR-77) JBAS restart op should be fail fast, otherwise you get dup processes started

by Heiko W. Rupp (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-77?page=com.atlassian.jira.plugin... ] Work on JOPR-77 started by Heiko W. Rupp. > JBAS restart op should be fail fast, otherwise you get dup processes started > ---------------------------------------------------------------------------- > > Key: JOPR-77 > URL: https://jira.jboss.org/jira/browse/JOPR-77 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 4 > Affects Versions: 2.1 > Environment: linux, postgres, upgraded install, jon2.1CR2 build > Reporter: Jeff Weiss > Assignee: Heiko W. Rupp > Priority: Critical > Fix For: 2.2 > > > Start EAP4.3 production, import the resource > Don't fix the connection property error, go to Operations, do a Restart. > It will eventually be shown "Success". > Check the process list on the machine and note there are now 2 EAP processes running - the first never got shut down properly because of the lack of auth credentials in the connection properties. > <joseph> lookin' at the code i think you're right. we blindly catch shutdown errors and continue start afterwards > kind of silly. all ops should be fail fast -- 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

1
0
0 / 0

[JBoss JIRA] Assigned: (JOPR-77) JBAS restart op should be fail fast, otherwise you get dup processes started

by Heiko W. Rupp (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-77?page=com.atlassian.jira.plugin... ] Heiko W. Rupp reassigned JOPR-77: --------------------------------- Assignee: Heiko W. Rupp > JBAS restart op should be fail fast, otherwise you get dup processes started > ---------------------------------------------------------------------------- > > Key: JOPR-77 > URL: https://jira.jboss.org/jira/browse/JOPR-77 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 4 > Affects Versions: 2.1 > Environment: linux, postgres, upgraded install, jon2.1CR2 build > Reporter: Jeff Weiss > Assignee: Heiko W. Rupp > Priority: Critical > Fix For: 2.2 > > > Start EAP4.3 production, import the resource > Don't fix the connection property error, go to Operations, do a Restart. > It will eventually be shown "Success". > Check the process list on the machine and note there are now 2 EAP processes running - the first never got shut down properly because of the lack of auth credentials in the connection properties. > <joseph> lookin' at the code i think you're right. we blindly catch shutdown errors and continue start afterwards > kind of silly. all ops should be fail fast -- 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

1
0
0 / 0

[JBoss JIRA] Moved: (JOPR-77) JBAS restart op should be fail fast, otherwise you get dup processes started

by Heiko W. Rupp (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-77?page=com.atlassian.jira.plugin... ] Heiko W. Rupp moved JBNADM-3542 to JOPR-77: ------------------------------------------- Project: Jopr (was: JBoss Network - Administration) Key: JOPR-77 (was: JBNADM-3542) Workflow: jira (was: JBoss Network Workflow v5) Component/s: Plugin - JBoss AS 4 (was: FX - Operations) Fix Version/s: 2.2 (was: 2.2) Affects Version/s: 2.1 (was: 2.1) Security: (was: JBoss Internal) > JBAS restart op should be fail fast, otherwise you get dup processes started > ---------------------------------------------------------------------------- > > Key: JOPR-77 > URL: https://jira.jboss.org/jira/browse/JOPR-77 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 4 > Affects Versions: 2.1 > Environment: linux, postgres, upgraded install, jon2.1CR2 build > Reporter: Jeff Weiss > Priority: Critical > Fix For: 2.2 > > > Start EAP4.3 production, import the resource > Don't fix the connection property error, go to Operations, do a Restart. > It will eventually be shown "Success". > Check the process list on the machine and note there are now 2 EAP processes running - the first never got shut down properly because of the lack of auth credentials in the connection properties. > <joseph> lookin' at the code i think you're right. we blindly catch shutdown errors and continue start afterwards > kind of silly. all ops should be fail fast -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JOPR-75) Allow creation of .bak files in content subsystem for ear/war too

by Heiko W. Rupp (JIRA)

Allow creation of .bak files in content subsystem for ear/war too ----------------------------------------------------------------- Key: JOPR-75 URL: https://jira.jboss.org/jira/browse/JOPR-75 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4 Affects Versions: 2.1, 2.2 Reporter: Heiko W. Rupp Ear/war file versions deployed through the content subsytem should have a .bak created as described in JOPR-37 to be able to revert as in JOPR-39 -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JOPR-74) Link ear/war backup creation into content subsystem

by Heiko W. Rupp (JIRA)

Link ear/war backup creation into content subsystem --------------------------------------------------- Key: JOPR-74 URL: https://jira.jboss.org/jira/browse/JOPR-74 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4 Affects Versions: 2.1, 2.2 Reporter: Heiko W. Rupp The new way of creating backup files for war/ear from JOPR-37 needs to be linked into the content subsystem, so that the new versions will appear there too. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JOPR-38) be able to create other packages suported by JBoss AS

by Rafael Soares (JIRA)

be able to create other packages suported by JBoss AS ----------------------------------------------------- Key: JOPR-38 URL: https://jira.jboss.org/jira/browse/JOPR-38 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5 Affects Versions: 2.1, 2.2 Reporter: Rafael Soares Priority: Minor Be able to create other package's types supported by JBoss AS deployers like SAR, JAR, HAR, WSR, *-service.xml (for MBeans definition). -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JOPR-72) Be able to create other packages suported by JBoss AS5

by Heiko W. Rupp (JIRA)

Be able to create other packages suported by JBoss AS5 ------------------------------------------------------ Key: JOPR-72 URL: https://jira.jboss.org/jira/browse/JOPR-72 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5 Affects Versions: 2.1, 2.2 Reporter: Heiko W. Rupp Priority: Minor Be able to create other package's types supported by JBoss AS deployers like SAR, JAR, HAR, WSR, *-service.xml (for MBeans definition). -- 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

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues February 2009