[JBoss JIRA] Created: (JOPR-107) jboss-as-5 plugin: Attempt to create new XA ConnectionFactory Resource fails with ClassCastException while converting "config-property" property from ManagedProperty to RHQ Property
by Ian Springer (JIRA)
jboss-as-5 plugin: Attempt to create new XA ConnectionFactory Resource fails with ClassCastException while converting "config-property" property from ManagedProperty to RHQ Property
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JOPR-107
URL: https://jira.jboss.org/jira/browse/JOPR-107
Project: Jopr
Issue Type: Bug
Components: Plugin - JBoss AS 5
Affects Versions: 2.1
Reporter: Ian Springer
Assignee: Ian Springer
Fix For: 2.2
Here's the full stack:
13:43:23,812 INFO [CreateResourceRunner] Creating resource through report: CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=XA Con
nectionFactory, plugin=JBossAS5]], ResourceKey=[null]
13:43:23,844 DEBUG [ApplicationServerComponent] BEFORE CREATE:
Properties for DeploymentTemplateInfo [TxConnectionFactoryTemplate]:
name=allocation-retry, mappedName=null, viewUse=NONE, required=false, value= SimpleMetaType:java.lang.Integer:0
name=allocation-retry-wait-millis, mappedName=null, viewUse=NONE, required=false, value= SimpleMetaType:java.lang.Long:5000
* name=background-validation, mappedName=null, viewUse=NONE, required=true, value= SimpleMetaType:java.lang.Boolean:false
name=background-validation-millis, mappedName=null, viewUse=NONE, required=false, value= SimpleMetaType:java.lang.Long:0
* name=blocking-timeout-millis, mappedName=null, viewUse=NONE, required=true, value= SimpleMetaType:java.lang.Long:30000
name=config-property, mappedName=null, viewUse=NONE, required=false, type=SimpleMetaType, value= <<<null>>>
* name=connection-definition, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
name=depends, mappedName=null, viewUse=NONE, required=false, type=CollectionMetaType, value= <<<null>>>
* name=idle-timeout-minutes, mappedName=null, viewUse=NONE, required=true, value= SimpleMetaType:java.lang.Integer:30
name=interleaving, mappedName=null, viewUse=NONE, required=false, type=SimpleMetaType, value= <<<null>>>
* name=isSameRM-override-value, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
* name=jmx-invoker-name, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
* name=jndi-name, mappedName=null, viewUse=NONE, required=true, value= SimpleMetaType:java.lang.String:
* name=local-transaction, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
* name=max-pool-size, mappedName=null, viewUse=NONE, required=true, value= SimpleMetaType:java.lang.Integer:10
name=metadata, mappedName=null, viewUse=NONE, required=false, type=MutableCompositeMetaType, value= <<<null>>>
* name=min-pool-size, mappedName=null, viewUse=NONE, required=true, value= SimpleMetaType:java.lang.Integer:0
* name=no-tx-separate-pools, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
* name=prefill, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
* name=rar-name, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
name=security-domain, mappedName=null, viewUse=NONE, required=false, type=GenericMetaType, value= <<<null>>>
* name=statistics-formatter, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
name=track-connection-by-tx, mappedName=null, viewUse=NONE, required=false, value= SimpleMetaType:java.lang.Boolean:true
* name=type-mapping, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
* name=use-java-context, mappedName=null, viewUse=NONE, required=true, value= SimpleMetaType:java.lang.Boolean:true
* name=use-strict-min, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
* name=validate-on-match, mappedName=null, viewUse=NONE, required=true, value= SimpleMetaType:java.lang.Boolean:true
* name=xa-resource-timeout, mappedName=null, viewUse=NONE, required=true, value= SimpleMetaType:java.lang.Integer:0
* name=xa-transaction, mappedName=null, viewUse=NONE, required=true, type=SimpleMetaType, value= <<<null>>>
13:43:23,859 DEBUG [ConversionUtils] Converting property PropertyMap[id=0, name=config-property, map={}] with definition PropertyDefinitionMap[id=0, name=config
-property, config=XA ConnectionFactory, group=advanced] to MetaValue with type CollectionMetaType{type=org.jboss.metatype.api.values.CompositeValue elementType=
MutableCompositeMetaType{org.jboss.resource.metadata.mcf.ManagedConnectionFactoryPropertyMetaData}...
13:43:23,859 ERROR [ApplicationServerComponent] Unable to process create request
java.lang.ClassCastException: org.rhq.core.domain.configuration.PropertyMap cannot be cast to org.rhq.core.domain.configuration.PropertyList
at org.rhq.plugins.jbossas5.adapter.impl.configuration.PropertyListToCollectionValueAdapter.convertToMetaValue(PropertyListToCollectionValueAdapter.java
:48)
at org.rhq.plugins.jbossas5.util.ConversionUtils.convertConfigurationToManagedProperties(ConversionUtils.java:281)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:209)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:131)
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:597)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
13:43:23,859 WARN [CreateResourceRunner] Throwable was found in creation report for request [1]: java.lang.ClassCastException: org.rhq.core.domain.configuratio
n.PropertyMap cannot be cast to org.rhq.core.domain.configuration.PropertyList - Enable DEBUG logging to see the stack trace.
13:43:23,859 INFO [CreateResourceRunner] Sending create response to server: CreateResourceResponse[RequestId=1, Status=Failure]
--
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] Updated: (JOPR-9) Cannot handle multiple JBossAS connections with different credentials
by Ian Springer (JIRA)
[ https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin.... ]
Ian Springer updated JOPR-9:
----------------------------
Component/s: Plugin - JBoss AS 4
> Cannot handle multiple JBossAS connections with different credentials
> ---------------------------------------------------------------------
>
> Key: JOPR-9
> URL: https://jira.jboss.org/jira/browse/JOPR-9
> Project: Jopr
> Issue Type: Bug
> Components: Plugin - JBoss AS 4
> Affects Versions: 2.1
> Reporter: Greg Hinkle
> Assignee: Ian Springer
> Fix For: 2.2
>
>
> Opened from RHQ-1030...
> Basically, the JBoss JNP context factory is storing principal and credentials in thread-locals so that we can have two stubs to different AS instances that require different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded, but that will only let you support different connections in different threads.
> After some testing, it looks like we can just have EMS setup the SecurityAssociation before every call into the stub. It should be fairly easy since EMS uses dynamic proxies around the stubs.
> SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-"));
> SecurityAssociation.setCredential("-credentials-");
--
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-99) Delete war for user with r/o right succeeds pyhsically, but is flagged as errror
by Heiko W. Rupp (JIRA)
Delete war for user with r/o right succeeds pyhsically, but is flagged as errror
--------------------------------------------------------------------------------
Key: JOPR-99
URL: https://jira.jboss.org/jira/browse/JOPR-99
Project: Jopr
Issue Type: Bug
Components: Plugin - Tomcat
Affects Versions: 2.2
Reporter: Heiko W. Rupp
Connect to the TC instance with a user that has r/o rights in the jmx-remote configuration.
Then delete a war file from within Jopr.
The delete will succeed on disk , but will show a failure:
Close Window
org.mc4j.ems.connection.EmsInvocationException: Exception on invocation of [stop]java.lang.SecurityException: Access denied! Invalid access level for requested MBeanServer operation.
at org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:127)
at org.jboss.on.plugins.tomcat.TomcatWarComponent.invokeOperation(TomcatWarComponent.java:358)
at org.jboss.on.plugins.tomcat.TomcatWarComponent.deleteApp(TomcatWarComponent.java:730)
at org.jboss.on.plugins.tomcat.TomcatWarComponent.deleteResource(TomcatWarComponent.java:720)
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.SecurityException: Access denied! Invalid access level for requested MBeanServer operation.
at com.sun.jmx.remote.security.MBeanServerFileAccessController.checkAccessLevel(MBeanServerFileAccessController.java:266)
at com.sun.jmx.remote.security.MBeanServerFileAccessController.checkWrite(MBeanServerFileAccessController.java:196)
at com.sun.jmx.remote.security.MBeanServerAccessController.invoke(MBeanServerAccessController.java:450)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1449)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:90)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1284)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1389)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:807)
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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
at sun.rmi.transport.Transport$1.run(Transport.java:177)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
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)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:273)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:251)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:160)
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)
at $Proxy39.invoke(Unknown Source)
at org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:111)
... 13 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-89) Manager URL not pre-populated for TC5
by Heiko W. Rupp (JIRA)
Manager URL not pre-populated for TC5
-------------------------------------
Key: JOPR-89
URL: https://jira.jboss.org/jira/browse/JOPR-89
Project: Jopr
Issue Type: Bug
Components: Plugin - Tomcat
Affects Versions: 2.2
Reporter: Heiko W. Rupp
The TC5 plugin is relying on the manager url to determine how to connect to the TC instance
The plugin is looking for -Dcom.sun.management.jmxremote.port on the command line which is by default not set in EWS-TC5
So the connection fails and the server stays marked as down.
I think we need to either talk to the ews guys to populate this property by default or have an operation to set it - or at least mention this on description of the manager url
--
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-101) response time filter fails when dropped into standalone Tomcat 6
by Jay Shaughnessy (JIRA)
response time filter fails when dropped into standalone Tomcat 6
----------------------------------------------------------------
Key: JOPR-101
URL: https://jira.jboss.org/jira/browse/JOPR-101
Project: Jopr
Issue Type: Bug
Affects Versions: 2.2
Environment: Tomcat6, EWS Tomcat6
Reporter: Jay Shaughnessy
Priority: Critical
Fix For: 2.2
Tomcat6 restructured their logging approach for a smaller footprint and, I think, less configuration collisions for commons logging/log4j. The response time filter assumes availability of commons logging in the classpath. This is no longer there by default in TC6 so the rtfilter immediately fails with class not found issues.
The simplest solution may be to include a commons logging jar in the connector-rtfilter.zip and let the unzip deliver both the filter and logging jar. It would have to be compatible with the various versions of Tomcat. Or, we could document the instructions for getting the common logging jar for TC6.
Dropping the version of commons-logging packaged in EWS TC5 seems to work for EWS TC6.
Opinions?
--
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-88) TC5 not discovered due to NPE
by Heiko W. Rupp (JIRA)
TC5 not discovered due to NPE
-----------------------------
Key: JOPR-88
URL: https://jira.jboss.org/jira/browse/JOPR-88
Project: Jopr
Issue Type: Bug
Components: Plugin - Tomcat
Affects Versions: 2.2
Reporter: Heiko W. Rupp
Fix For: 2.2
TC5 of EWS is not discovered:
2009-03-11 10:59:36,622 INFO [RHQ Agent Prompt Input Thread] (org.rhq.enterprise.agent.AgentMain)- {AgentM
ain.prompt-command-invoked}Prompt command invoked: [discovery, --full]
2009-03-11 10:59:36,622 INFO [InventoryManager.discovery-1] (rhq.core.pc.inventory.AutoDiscoveryExecutor)-
Executing server discovery scan...
2009-03-11 10:59:36,739 INFO [InventoryManager.discovery-1] (rhq.core.pc.inventory.AutoDiscoveryExecutor)-
Process scan auto-detected new server resource: scan=[ProcessScan: query=[process|basename|match=^java.*,a
rg|org.apache.catalina.startup.Bootstrap|match=.*], name=[Tomcat]], discovered-process=[process: pid=[2937]
, name=[/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java], ppid=[1]]
2009-03-11 10:59:36,739 WARN [InventoryManager.discovery-1] (jboss.on.plugins.tomcat.TomcatDiscoveryCompon
ent)- Version script file not found in expected location: null/bin/version.sh
2009-03-11 10:59:36,740 ERROR [InventoryManager.discovery-1] (jboss.on.plugins.tomcat.TomcatDiscoveryCompon
ent)- Error creating discovered resource for process: ProcessScanResult: scan=[ProcessScan: query=[process|
basename|match=^java.*,arg|org.apache.catalina.startup.Bootstrap|match=.*], name=[Tomcat]], info=[process:
pid=[2937], name=[/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java], ppid=[1]]
java.lang.NullPointerException
at java.util.regex.Matcher.getTextLength(Matcher.java:1151)
at java.util.regex.Matcher.reset(Matcher.java:308)
at java.util.regex.Matcher.<init>(Matcher.java:228)
at java.util.regex.Pattern.matcher(Pattern.java:905)
at org.jboss.on.plugins.tomcat.TomcatDiscoveryComponent.isEWS(TomcatDiscoveryComponent.java:199)
at org.jboss.on.plugins.tomcat.TomcatDiscoveryComponent.parseTomcatProcess(TomcatDiscoveryComponent
.java:158)
at org.jboss.on.plugins.tomcat.TomcatDiscoveryComponent.discoverResources(TomcatDiscoveryComponent.
java:111)
--
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