March 2009 - jopr-issues - Jboss List Archives

[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, 1 month

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, 1 month

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, 1 month

4
15
0 / 0

[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] Assigned: (JOPR-111) AS5 plugin: Unsetting a property value for a Topic or Queue during a config update results in an "UndeclaredThrowableException"

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-111?page=com.atlassian.jira.plugi... ] Charles Crouch reassigned JOPR-111: ----------------------------------- Assignee: Ian Springer > AS5 plugin: Unsetting a property value for a Topic or Queue during a config update results in an "UndeclaredThrowableException" > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JOPR-111 > URL: https://jira.jboss.org/jira/browse/JOPR-111 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 5 > Environment: JBoss AS Branch_5_x r86203, embjopr r251 > Reporter: Farah Juma > Assignee: Ian Springer > Fix For: 2.2 > > > Steps to reproduce: > Click on the "Configuration" tab for a Queue or Topic. Attempt to unset a property (eg. "Redelivery Delay"). The update fails with the following error: > java.lang.reflect.UndeclaredThrowableException at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.set(KernelBusRuntimeComponentDispatcher.java:91) at org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1097) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aop.generatedproxies.AOPProxy$1.updateComponent(AOPProxy$1.java) at org.rhq.plugins.jbossas5.ManagedComponentComponent.updateComponent(ManagedComponentComponent.java:174) at org.rhq.plugins.jbossas5.AbstractManagedComponent.updateResourceConfiguration(AbstractManagedComponent.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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:449) 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: javax.management.ReflectionException at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:189) at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:140) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103) at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461) at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:617) at org.jboss.system.microcontainer.ServiceControllerContext.set(ServiceControllerContext.java:182) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus$2.dispatch(BasicKernelBus.java:79) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus$2.dispatch(BasicKernelBus.java:83) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:54) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.set(BasicKernelBus.java:75) at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.set(KernelBusRuntimeComponentDispatcher.java:87) at org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1097) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aop.generatedproxies.AOPProxy$1.updateComponent(AOPProxy$1.java) at org.rhq.plugins.jbossas5.ManagedComponentComponent.updateComponent(ManagedComponentComponent.java:174) at org.rhq.plugins.jbossas5.AbstractManagedComponent.updateResourceConfiguration(AbstractManagedComponent.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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:449) 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) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) ... 18 more Caused by: java.lang.IllegalArgumentException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:136) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103) at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461) at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:617) at org.jboss.system.microcontainer.ServiceControllerContext.set(ServiceControllerContext.java:182) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus$2.dispatch(BasicKernelBus.java:79) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus$2.dispatch(BasicKernelBus.java:83) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:54) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.set(BasicKernelBus.java:75) at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.set(KernelBusRuntimeComponentDispatcher.java:87) at org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1097) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) ... 18 more -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JOPR-102) jboss-as plugin: add support for discovering/monitoring EJB 2.x stateful session beans

by Ian Springer (JIRA)

jboss-as plugin: add support for discovering/monitoring EJB 2.x stateful session beans -------------------------------------------------------------------------------------- Key: JOPR-102 URL: https://jira.jboss.org/jira/browse/JOPR-102 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4 Affects Versions: 2.1 Reporter: Ian Springer Assignee: Ian Springer We had support for stateful session beans in JON 1.x and somehow neglected to carry it over into JON 2.x. -- 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
9
0 / 0

[JBoss JIRA] Created: (JOPR-94) TC5: war file create works, but war does not show up in inventory of the parent vhost

by Heiko W. Rupp (JIRA)

TC5: war file create works, but war does not show up in inventory of the parent vhost ------------------------------------------------------------------------------------- Key: JOPR-94 URL: https://jira.jboss.org/jira/browse/JOPR-94 Project: Jopr Issue Type: Bug Affects Versions: 2.2 Reporter: Heiko W. Rupp Fix For: 2.2 See screen shot. War file is 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

3
9
0 / 0

[JBoss JIRA] Created: (JOPR-108) Add support for local-tx connection factories

by Ian Springer (JIRA)

Add support for local-tx connection factories --------------------------------------------- Key: JOPR-108 URL: https://jira.jboss.org/jira/browse/JOPR-108 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 We have support for XA and no-tx ones, we should add local-tx. This page describes the different varieties: http://www.jboss.org/community/docs/DOC-9326 I based the Resource types I exposed off of the ConnectionFactoryTypes enum from org.jboss.deployers.spi.management.KnownComponentTypes: /** * Enums for generic ConnectionFactory types */ public enum ConnectionFactoryTypes { XA("ConnectionFactory", "XA"), NoTx("ConnectionFactory", "NoTx"); private final String type; private final String subtype; private ConnectionFactoryTypes(String type, String subtype) { this.type = type; this.subtype = subtype; } public String type() { return type; } public String subtype() { return subtype; } public ComponentType getType() { return new ComponentType(type, subtype); } }; If there is also a LocalTX type, then this enum should be updated. A JBAS issue has been created for Scott to review the KnownComponentTypes enums: https://jira.jboss.org/jira/browse/JBAS-6646 -- 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
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues March 2009