[
https://jira.jboss.org/browse/EMBJOPR-280?page=com.atlassian.jira.plugin....
]
Ian Springer commented on EMBJOPR-280:
--------------------------------------
And here is what AS 5.1 has of type {MCBean:JTA}:
+++ ManagedComponent(name=TransactionManager, type=(ComponentType{type=MCBean,
subtype=JTA}), compName=TransactionManager, attachment:
com.arjuna.ats.jbossatx.jta.TransactionManagerServiceMBean
++++++ properties: [rollbackCount, XATerminator, transactionCount, state,
propagateFullContext, transactionStatusManagerInetAddress, timedoutCount,
runningTransactionCount, transactionManager, transactionSynchronizationRegistry,
transactionStatusManagerPort, userTransaction, nestedTransactonCount, transactionTimeout,
socketProcessIdPort, commitCount, statisticsEnabled, applicationRollbackCount,
objectStoreDir, recoveryPort, heuristicCount, recoveryInetAddress, runInVMRecoveryManager,
resourceRollbackCount]
So, to summarize the changes since 5.1, the component that has the tx stats we are
interested has been renamed from "TransactionManager" to
"TransactionStatistics". On top of that, each of the individual properties has
been renamed as well (commitCount -> numberOfCommittedTransactions, etc.). In addition,
a new component of the same type but named "TransactionManager" has been added.
This component has a completely different set of properties, which is not good. I
don't think the Profile Service should even allow multiple components of the same type
but with different sets of properties and/or operations to be deployed. A management
client should be able to rely on the component's type to know which properties and/or
operations should be present. In this case, the name must be used in addition to type to
figure that out. I also think that the AS team should try, if at all possible, to keep the
managed components APIs backwards-compatible (i.e. so clients written for older versions
(such as RHQ) will not break).
jboss-as-5 plugin: JTA Metrics not found during discovery scan
---------------------------------------------------------------
Key: EMBJOPR-280
URL:
https://jira.jboss.org/browse/EMBJOPR-280
Project: Embedded Jopr
Issue Type: Bug
Components: Plugin
Affects Versions: 1.3.2
Environment: Embedded Jopr version: 1.4.0-20100120.135921-68
Reporter: Shelly McGowan
Assignee: Ian Springer
Fix For: 1.3.3, 1.4.0
Attachments: embjopr280-140CR1.txt
Original Estimate: 4 hours
Remaining Estimate: 4 hours
Performing manual testing of the admin-console snapshot deployed to AS 6,
IllegalStateException was thrown during a runtime discovery scan when obtaining JTA
metrics, specifically:
17:07:47,657 INFO [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] Running runtime
discovery scan rooted at [platform]
17:07:51,717 INFO [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] Scanned [0]
servers and found [0] total descendant Resources.
17:08:11,996 ERROR [org.rhq.plugins.jbossas5.ApplicationServerComponent] Failed to obtain
metric 'MCBean|JTA|*|transactionCount'.: java.lang.IllegalStateException: Property
named 'transactionCount' not found for ManagedComponent
[org.jboss.profileservice.management.client.ManagedComponentDelegate@1de64f6].
at
org.rhq.plugins.jbossas5.util.ManagedComponentUtils.getSimplePropertyValue(ManagedComponentUtils.java:80)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.getValues(ApplicationServerComponent.java:256)
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:525)
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)
17:08:11,996 ERROR [org.rhq.plugins.jbossas5.ApplicationServerComponent] Failed to obtain
metric 'MCBean|JTA|*|rollbackCount'.: java.lang.IllegalStateException: Property
named 'rollbackCount' not found for ManagedComponent
[org.jboss.profileservice.management.client.ManagedComponentDelegate@1de64f6].
at
org.rhq.plugins.jbossas5.util.ManagedComponentUtils.getSimplePropertyValue(ManagedComponentUtils.java:80)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.getValues(ApplicationServerComponent.java:256)
17:08:12,000 ERROR [org.rhq.plugins.jbossas5.ApplicationServerComponent] Failed to obtain
metric 'MCBean|JTA|*|commitCount'.: java.lang.IllegalStateException: Property
named 'commitCount' not found for ManagedComponent
[org.jboss.profileservice.management.client.ManagedComponentDelegate@1de64f6].
at
org.rhq.plugins.jbossas5.util.ManagedComponentUtils.getSimplePropertyValue(ManagedComponentUtils.java:80)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.getValues(ApplicationServerComponent.java:256)
JBoss TS 4.9.0.GA was integrated into AS 6.0.0.M2 (see: JBAS-7022).
Need to investigate further as I had several apps deployed at the time the error was
thrown.
--
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