February 2009 - jopr-issues - Jboss List Archives

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

by Heiko W. Rupp (JIRA)

Be able to backup an existing package WAR/EAR during "Create new" operation ---------------------------------------------------------------------------- Key: JOPR-71 URL: https://jira.jboss.org/jira/browse/JOPR-71 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4 Affects Versions: 2.1, 2.2 Reporter: Heiko W. Rupp Assignee: Heiko W. Rupp 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, 10 months

1
1
0 / 0

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

by Heiko W. Rupp (JIRA)

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

[JBoss JIRA] Created: (JOPR-69) AS restart ops marked as void, but returns results

by Heiko W. Rupp (JIRA)

AS restart ops marked as void, but returns results -------------------------------------------------- Key: JOPR-69 URL: https://jira.jboss.org/jira/browse/JOPR-69 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 4 Affects Versions: 2.2 Reporter: Heiko W. Rupp Assignee: Heiko W. Rupp 2009-02-09 21:24:02,150 ERROR [OperationManager.invoker-1] (rhq.core.pc.operation.OperationInvocation)- Plugin erro r: Operation [restart] is defined as returning no results, but it returned non-null results: Configuration[id=0, op erationResult=Startup may have failed: java.lang.RuntimeException: Server failed to start: ++ dirname /devel/jboss- eap-4.3/jboss-as/bin/run.sh + DIRNAME=/devel/jboss-eap-4.3/jboss-as/bin ++ basename /devel/jboss-eap-4.3/jboss-as/bin/run.sh -- 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
5
0 / 0

[JBoss JIRA] Created: (JOPR-45) be able to delete a resource deployed on JBoss AS

by Rafael Torres Coelho Soares (JIRA)

be able to delete a resource deployed on JBoss AS ------------------------------------------------- Key: JOPR-45 URL: https://jira.jboss.org/jira/browse/JOPR-45 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5 Environment: Jopr 2.1 JBoss AS 4.x OS Linux Debian JDK 1.5 Reporter: Rafael Torres Coelho Soares Priority: Minor Some times is necessary to delete a resource deployed on JBoss AS, for example, a DataSource or WAR/JAR/EAR package unusable. Would be nice if we could do this delete operation through Jopr UI :) Regards. -- 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-68) JBossAS Start operation doesn't work for EAP instances w/ configSets other than 'production'

by Mark Burchard (JIRA)

JBossAS Start operation doesn't work for EAP instances w/ configSets other than 'production' -------------------------------------------------------------------------------------------- Key: JOPR-68 URL: https://jira.jboss.org/jira/browse/JOPR-68 Project: Jopr Issue Type: Bug Components: Plugin - RHQ Server Affects Versions: 2.1, 2.2, 2.3 Environment: N/A Reporter: Mark Burchard This is actually a bug with JBAS run.sh: if [ "$SWITCH" = "-c" ]; then Basically, JON/JOPR uses the --configuration switch to start appservers, but a bug in JBAS run.sh omits the long form as an option. JOPR fix is to use the short form -c A bug will be filed against JBAS to have this fixed at the source. -- 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
8
0 / 0

[JBoss JIRA] Created: (JOPR-63) java.lang.ClassCastException running 1.1.0.GA in 4.2.2.GA or 4.2.3.GA

by Tom Cunningham (JIRA)

java.lang.ClassCastException running 1.1.0.GA in 4.2.2.GA or 4.2.3.GA --------------------------------------------------------------------- Key: JOPR-63 URL: https://jira.jboss.org/jira/browse/JOPR-63 Project: Jopr Issue Type: Bug Components: Plugin - RHQ Server Reporter: Tom Cunningham Seeing the following ClassCastException when running emb jopr 1.1.0.GA in either 4.2.2.GA or 4.2.3.GA. I see it on startup and also when logging in to admin-console. 12:44:26,343 WARN [RuntimeDiscoveryExecutor] Failed to execute runtime discovery for Resources of type ResourceType[id=0, category=Service, name=JBossMQ, plugin=JBossAS] java.lang.ClassCastException: org.jboss.mq.server.JMSDestinationManager at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.getVersionFromSource(AbstractMessagingDiscoveryComponent.java:107) at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.discoverResources(AbstractMessagingDiscoveryComponent.java:72) at org.rhq.plugins.jbossas.JBossMQDiscoveryComponent.discoverResources(JBossMQDiscoveryComponent.java:44) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.executeComponentDiscovery(RuntimeDiscoveryExecutor.java:246) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.discoverForResource(RuntimeDiscoveryExecutor.java:218) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.runtimeDiscover(RuntimeDiscoveryExecutor.java:136) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:97) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:54) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:65) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:168) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) 12:44:26,394 INFO [ContentManager] Discovered 1 new packages for Resource with id [-33]. 12:44:26,412 INFO [ContentManager] Discovered 1 new packages for Resource with id [-34]. 12:44:26,421 INFO [ContentManager] Discovered 1 new packages for Resource with id [-35]. -- 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-50) Specifying wrong jnp port when connecting to JBAS doesn't prevent plugin config from being saved

by Charles Crouch (JIRA)

Specifying wrong jnp port when connecting to JBAS doesn't prevent plugin config from being saved ------------------------------------------------------------------------------------------------ Key: JOPR-50 URL: https://jira.jboss.org/jira/browse/JOPR-50 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 4 Reporter: Charles Crouch Priority: Critical Fix For: 2.2 I thought previously we would get an exception when updating the plugin config if we couldnt connect to the server with the new settings. e.g. specifying "jnp://127.0.0.1:23499" results in "Connection properties updated. ", but no new services are discovered because we can't actually connect on that port. -- 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
2
0 / 0

[JBoss JIRA] Created: (JOPR-61) Allow to monitor c3p0 datasources

by Heiko W. Rupp (JIRA)

Allow to monitor c3p0 datasources --------------------------------- Key: JOPR-61 URL: https://jira.jboss.org/jira/browse/JOPR-61 Project: Jopr Issue Type: Feature Request Affects Versions: 2.1 Reporter: Heiko W. Rupp See forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205850#4205850 -- 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
2
0 / 0

[JBoss JIRA] Created: (JOPR-67) Support c3p0 datasources

by Gabriel Goïc (JIRA)

Support c3p0 datasources ------------------------ Key: JOPR-67 URL: https://jira.jboss.org/jira/browse/JOPR-67 Project: Jopr Issue Type: Feature Request Affects Versions: 2.1 Environment: JBoss 4.2.2, Java 5 update 17, Linux Reporter: Gabriel Goïc c3p0 datasources are always reported as 'down' see the JBoss Forum's thread about this problem -- 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-64) No support for multiple content sources providing the same content

by Charles Crouch (JIRA)

No support for multiple content sources providing the same content ------------------------------------------------------------------ Key: JOPR-64 URL: https://jira.jboss.org/jira/browse/JOPR-64 Project: Jopr Issue Type: Bug Affects Versions: 2.1 Reporter: Charles Crouch Example of what I mean: 1) Create a content source pointing at a QA CSP feed. 2) Sync the content source and review the packages. Select a package and see the downloadUrl is pointing at the QA CSP infrastructure 3) Create a content source pointing at the Prod CSP feed. 4) Sync the content source and review the packages. Select a package and see the downloadUrl is still pointing at the QA CSP infrastructure. This means that even if you create a channel associated with the Prod content source and then subscribe a resource to this channel you will still end up trying to download a QA package when you try to apply a patch. I think the logical thing here is have each channel have its own unique packages, even though that means the rhq_package/rhq_package_version tables would need to change to take into account channel. This seems somewhat wasteful if you have a lot of identical packages across two content sources, but the current situation: What you have in your channel is determined by what old content sources you have deployed, doesn't seem tenable. -- 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
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues February 2009