jopr-issues July 2010

jopr-issues@lists.jboss.org

1 participants
5 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

12 years, 2 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

12 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JOPR-95) EWS TC5 web.xml is missing a <filter-mapping/> section

by Heiko W. Rupp (JIRA)

EWS TC5 web.xml is missing a <filter-mapping/> section ------------------------------------------------------ Key: JOPR-95 URL: https://jira.jboss.org/jira/browse/JOPR-95 Project: Jopr Issue Type: Bug Components: Plugin - Tomcat Affects Versions: 2.2 Reporter: Heiko W. Rupp Priority: Blocker Fix For: 2.2 EWS tC 5 web.xml has a <filter> section for the Rtfilter, but is missing a <filter-mapping/> section Only enabling the <filter> section and restarting TC results in a unusable server <filter-mapping> <filter-name>RhqRtFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> -- 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

13 years, 2 months

4
15
0 / 0

[JBoss JIRA] Resolved: (JOPR-339) ERROR [InventoryManager] Call to getAvailablity() on ResourceComponent ... type=Service Binding Manager, ... failed.

by Ian Springer (JIRA)

[ https://jira.jboss.org/browse/JOPR-339?page=com.atlassian.jira.plugin.sys... ] Ian Springer resolved JOPR-339. ------------------------------- Assignee: Ian Springer Resolution: Cannot Reproduce Bug I haven't been able to reproduce this on recent EAP/EWP 5.1. Ondra, if you see it again, please reopen this issue and include as many details as possible to help us reproduce it. > ERROR [InventoryManager] Call to getAvailablity() on ResourceComponent ... type=Service Binding Manager, ... failed. > -------------------------------------------------------------------------------------------------------------------- > > Key: JOPR-339 > URL: https://jira.jboss.org/browse/JOPR-339 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 5 > Affects Versions: 2.2 > Environment: EAP 5 branch > EmbJopr r 623 > Reporter: Ondrej Žižka > Assignee: Ian Springer > Fix For: 2.4 > > > This causes SBM to appear as DOWN, however, SBM itself works fine. > ERROR [InventoryManager] Call to getAvailablity() on ResourceComponent for Resource[id=-43, type=Service Binding Manager, key=ServiceBindingManager, name=Service Binding Manager, parent=JBoss EAP 5 (default)] failed. > java.lang.IllegalStateException: Failed to find [ComponentType{type=MCBean, subtype=ServiceBindingManager}] ManagedComponent named [ServiceBindingManager]. > at org.rhq.plugins.jbossas5.ManagedComponentComponent.getManagedComponent(ManagedComponentComponent.java:367) > at org.rhq.plugins.jbossas5.serviceBinding.ManagerComponent.getAvailability(ManagerComponent.java:78) > at sun.reflect.GeneratedMethodAccessor317.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.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) > 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) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JOPR-426) Datasource incorrectly flagged as unavailable

by Ian Springer (JIRA)

[ https://jira.jboss.org/browse/JOPR-426?page=com.atlassian.jira.plugin.sys... ] Ian Springer resolved JOPR-426. ------------------------------- Fix Version/s: (was: 2.3.1) Resolution: Done The underlying JBAS issue (JBPAPP-4332) has been fixed in EAP 5.1.0.CR1. > Datasource incorrectly flagged as unavailable > --------------------------------------------- > > Key: JOPR-426 > URL: https://jira.jboss.org/browse/JOPR-426 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 5 > Affects Versions: 2.3 > Reporter: Lami Akagwu > Assignee: Ian Springer > > For clustered nodes, where datasources are deployed to the farm directory of one instance, the datasources, when viewed in the GUI are flagged as being unavailable in the second node even though the server logs from both instances indicate the datasources were successfully deployed. > The problem also occurs if the datasources are deployed to the farm directory after the instances have already been started. > Test Case 1: > - Make two copies of the 'all' config (named node1 and node2) > - Copy multiple datasources to node2/farm > - Using the service binding manager, startup both instances > ./run.sh -c node1 -Djboss.service.binding.set=ports-01 > ./run.sh -c node2 -Djboss.service.binding.set=ports-02 > - Import the resources into the repository ( the datasource will appear as unavailable in one of the nodes) > Test Case 2 : > Add new datasources to node2/farm (the Server GUI wouldn't reflect the availability of the new datasource in node1) > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

← Newer
1
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues July 2010