jopr-issues November 2012

jopr-issues@lists.jboss.org

1 participants
4 discussions

[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-105) ManagedComponetComponent.invokeOperation() assumes there is only one ManagedOperation with a given name, which may not be true

by Ian Springer (JIRA)

ManagedComponetComponent.invokeOperation() assumes there is only one ManagedOperation with a given name, which may not be true ------------------------------------------------------------------------------------------------------------------------------ Key: JOPR-105 URL: https://jira.jboss.org/jira/browse/JOPR-105 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 5 Affects Versions: 2.1 Reporter: Ian Springer Assignee: Ian Springer Fix For: 2.2 The ManagedComponent could have more than one operation with a given name (i.e. overloaded operations), so we need to examine the parameters too to figure out the correct operation to invoke. Here's an email I sent to Scott: Ian Springer wrote: > Scott- > > Quick question. Will ManagedComponent.getOperations() ever return multiple operations with the same name (i.e. overloaded operations)? > > Thanks, > Ian Yes, it should. -- 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

3
3
0 / 0

[JBoss JIRA] (JOPR-248) add integration tests for JVM Resource Types

by Filip Drabek (JIRA)

[ https://issues.jboss.org/browse/JOPR-248?page=com.atlassian.jira.plugin.s... ] Filip Drabek updated JOPR-248: ------------------------------ Assignee: (was: Filip Drabek) > add integration tests for JVM Resource Types > -------------------------------------------- > > Key: JOPR-248 > URL: https://issues.jboss.org/browse/JOPR-248 > Project: Jopr > Issue Type: Sub-task > Components: Plugin - JBoss AS 5 > Reporter: Ian Springer > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JOPR-273) JBossCache v3 plugin throws MalformedObjectNameException during discovery when running on Java5

by Filip Drabek (JIRA)

[ https://issues.jboss.org/browse/JOPR-273?page=com.atlassian.jira.plugin.s... ] Filip Drabek updated JOPR-273: ------------------------------ Assignee: (was: Filip Drabek) > JBossCache v3 plugin throws MalformedObjectNameException during discovery when running on Java5 > ----------------------------------------------------------------------------------------------- > > Key: JOPR-273 > URL: https://issues.jboss.org/browse/JOPR-273 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 5 > Affects Versions: 2.2 > Environment: Java5 > Reporter: Charles Crouch > Priority: Minor > Labels: 560, embjopr > Fix For: 2.3 > > > Deploy a copy of the embedded console with the jboss cache plugin in into default config of EAP5 and log in. In the console you will see the following exception: > 19:30:28,678 INFO [DConnection] Found 954 MBeans, starting load > 19:30:30,115 WARN [InventoryManager] Failure during discovery for [Jboss Cache] Resources - failed after 0 ms. > java.lang.Exception: Discovery component invocation failed. > at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory > .java:264) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) > at java.util.concurrent.FutureTask.run(FutureTask.java:123) > 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:595) > Caused by: java.lang.RuntimeException: Illegal ObjectName *:*,jmx-resource=* > at org.mc4j.ems.impl.jmx.connection.DConnection.queryBeans(DConnection.java:328) > at org.rhq.plugins.jbosscache5.JBossCacheDiscoveryComponent.discoverResources(JBossCacheDiscoveryComponent.java:49) > at sun.reflect.GeneratedMethodAccessor284.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory > .java:260) > ... 5 more > Caused by: javax.management.MalformedObjectNameException: Invalid character '*' in value part of property > at javax.management.ObjectName.construct(ObjectName.java:529) > at javax.management.ObjectName.<init>(ObjectName.java:1304) > at org.mc4j.ems.impl.jmx.connection.DConnection.queryBeans(DConnection.java:323) > ... 10 more > 19:30:30,834 WARN [InventoryManager] Failure during discovery for [Jboss Cache] Resources - failed after 16 ms. > java.lang.Exception: Discovery component invocation failed. > at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory > .java:264) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) > at java.util.concurrent.FutureTask.run(FutureTask.java:123) > 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:595) > Caused by: java.lang.RuntimeException: Illegal ObjectName *:*,jmx-resource=* > at org.mc4j.ems.impl.jmx.connection.DConnection.queryBeans(DConnection.java:328) > at org.rhq.plugins.jbosscache5.JBossCacheDiscoveryComponent.discoverResources(JBossCacheDiscoveryComponent.java:49) > at sun.reflect.GeneratedMethodAccessor284.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory > .java:260) > ... 5 more > Caused by: javax.management.MalformedObjectNameException: Invalid character '*' in value part of property > at javax.management.ObjectName.construct(ObjectName.java:529) > at javax.management.ObjectName.<init>(ObjectName.java:1304) > at org.mc4j.ems.impl.jmx.connection.DConnection.queryBeans(DConnection.java:323) > ... 10 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

← Newer
1
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues November 2012