[JBoss JIRA] Created: (JOPR-97) TC5: Connector operations fail with exception
by Heiko W. Rupp (JIRA)
TC5: Connector operations fail with exception
---------------------------------------------
Key: JOPR-97
URL: https://jira.jboss.org/jira/browse/JOPR-97
Project: Jopr
Issue Type: Bug
Components: Plugin - Tomcat
Affects Versions: 2.2
Environment: QA-7408
Reporter: Heiko W. Rupp
Priority: Critical
Fix For: 2.2
I was trying to invoke the stop operation on the connector at 8080. Operation failed (connector is not shut down ) and the failure screen shows the stack trace below.
Note that the connector shows as up nicely and is also reporting metrics correctly.
org.mc4j.ems.connection.EmsInvocationException: Exception on invocation of [stop]java.lang.reflect.UndeclaredThrowableException
at org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:127)
at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:507)
at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:478)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy39.invoke(Unknown Source)
at org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:111)
... 12 more
Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:128)
at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1001)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.mc4j.ems.impl.jmx.connection.support.providers.proxy.JMXRemotingMBeanServerProxy.invoke(JMXRemotingMBeanServerProxy.java:61)
... 14 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:310)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:176)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:163)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:381)
at java.net.Socket.connect(Socket.java:537)
at java.net.Socket.connect(Socket.java:487)
at java.net.Socket.<init>(Socket.java:384)
at java.net.Socket.<init>(Socket.java:198)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:146)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
... 25 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, 2 months
[JBoss JIRA] Moved: (JOPR-111) AS5 plugin: Unsetting a property value for a Topic or Queue during a config update results in an "UndeclaredThrowableException"
by Ian Springer (JIRA)
[ https://jira.jboss.org/jira/browse/JOPR-111?page=com.atlassian.jira.plugi... ]
Ian Springer moved EMBJOPR-111 to JOPR-111:
-------------------------------------------
Project: Jopr (was: Embedded Jopr)
Key: JOPR-111 (was: EMBJOPR-111)
Component/s: Plugin - JBoss AS 5
(was: Web App/Integration)
Fix Version/s: 2.2
(was: 1.2)
> 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
> 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, 2 months
[JBoss JIRA] Created: (JOPR-110) Create new package error
by senthurkumaran masilamani (JIRA)
Create new package error
------------------------
Key: JOPR-110
URL: https://jira.jboss.org/jira/browse/JOPR-110
Project: Jopr
Issue Type: Bug
Affects Versions: 2.1
Environment: CentOS, JON 2.1, JBoss AS 4.2.3, JDK 1.5_12
Reporter: senthurkumaran masilamani
Unable to create new package with full resource permissions.
Getting the following error.
Failed to associate package [AutoAudit.war] with channel ID [500550]. Cause: org.rhq.enterprise.server.authz.PermissionException:Subject [websupport] is not authorized for [MANAGE_INVENTORY]: invocation: method=public void org.rhq.enterprise.server.content.ChannelManagerBean.addPackageVersionsToChannel(org.rhq.core.domain.auth.Subject,int,int[]) throws java.lang.Exception,context-data={}
Permissions assigned to the user is Modify,Delete, Create Children, Alert, measure, Content, Control, Configure.
Please look into this issue .
thanks & regards
Senthur
--
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, 2 months
[JBoss JIRA] Created: (JOPR-90) jboss-as plugin: webapps with the distributable tag in web.xml are not autodiscovered
by Ian Springer (JIRA)
jboss-as plugin: webapps with the distributable tag in web.xml are not autodiscovered
-------------------------------------------------------------------------------------
Key: JOPR-90
URL: https://jira.jboss.org/jira/browse/JOPR-90
Project: Jopr
Issue Type: Bug
Components: Plugin - JBoss AS 4
Affects Versions: 2.1
Reporter: Ian Springer
Clustered webapps (i.e. webapps whose web.xml contain the distributable tag) are not discovered by the jboss-as plugin. It looks like this is most likely due to the jboss.web:...type=Manager MBean not being present for clustered webapps...
All our webapps are deployed in the "deploy" directory. All our webapps match the "jboss.management.local:J2EEApplication=null,J2EEServer=Local,j2eeType=WebModule,name=..." pattern in the jmx-console (even those with the distributable tag), but we can see only 12 out of our 14 webapps.
The DeploymentUtility.getVhosts returns the list of the mbeans corresponding to the pattern : "jboss.web:host=%host%,path=" + WarDiscoveryHelper.getContextPath(contextRoot) + ",type=Manager".
There is no clustered webapp corresponding to this pattern.
Eg : in the jboss.web domain, we have
host=localhost,name=SecurityAssociationValve,path=/bsweb-siren,type=Valve
host=localhost,name=SecurityAssociationValve,path=/distri-web-1.0,type=Valve
host=localhost,name=SecurityAssociationValve,path=/doclistener,type=Valve
...
host=localhost,path=/distri-web-1.0,type=Manager
host=localhost,path=/doclistener,type=Manager
bsweb-siren is distributable and there is no "host=localhost,path=/bsweb-siren,type=Manager". So, getVHosts returns an empty list.
--
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, 2 months
[JBoss JIRA] Created: (JOPR-103) EWS/Tomcat detection logic ambiguous (namespace collision?)
by corey welton (JIRA)
EWS/Tomcat detection logic ambiguous (namespace collision?)
-----------------------------------------------------------
Key: JOPR-103
URL: https://jira.jboss.org/jira/browse/JOPR-103
Project: Jopr
Issue Type: Bug
Components: Plugin - Tomcat
Affects Versions: 2.2
Reporter: corey welton
Priority: Blocker
1. Install RHN Satellite on a box
2. Install JON Agent on same box; begin monitoring.
3. View inventory, noting "JBoss EWS Tomcat" in the inventory.
4. Go to Inventory > Connection tab for this tomcat server
5. Observe "Installation Home" value
Current results:
The value for "Installation home" used by RHN Satellite is "/usr/share/tomcat5". This is the string that is used to identify EWS. However, this is not an EWS Tomcat install. End result: This is detected/displayed as "JBoss EWS Tomcat" in jopr, even though it actually isn't.
Expected results:
a non EWS-labelled value returned
--
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, 2 months
[JBoss JIRA] Created: (JOPR-104) Oracle XA Datasource Creation through JON - Wrong template
by senthurkumaran masilamani (JIRA)
Oracle XA Datasource Creation through JON - Wrong template
----------------------------------------------------------
Key: JOPR-104
URL: https://jira.jboss.org/jira/browse/JOPR-104
Project: Jopr
Issue Type: Bug
Components: Plugin - JBoss AS 4
Affects Versions: 2.1
Environment: OS: CentOS, jon-server-2.1.2.GA, JBoss AS 4.2.3 Oracle 10g
Reporter: senthurkumaran masilamani
JON Server Currently creates Oracle XA datasource with the following format.
<?xml version="1.0" encoding="UTF-8"?>
<xa-datasource>
<jndi-name>test</jndi-name>
<connection-url>jdbc:oracle:oci8:@tc</connection-url>
<user-name>a</user-name>
b
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<no-tx-separate-pools>true</no-tx-separate-pools>
<driver-class>oracle.jdbc.xa.client.OracleXADataSource</driver-class>
</xa-datasource>
It should follow the standard template as given in the jca examples(oracle-xa-ds.xml).
Due to this the XA datasources created through JON doesn't work properly. We are trying to implement complete JBoss AS admin. through JON Server. This issue leads manual effort to configure the XA DS.
Thanks & Regards
Senthur
--
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, 2 months