Bug 1042713 - Discovery component invocation failed [Query Cache] - discovery component is longer than the maximum length (500)
Summary: Discovery component invocation failed [Query Cache] - discovery component is ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Agent
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: JON 3.3.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
: 1035373 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 07:53 UTC by Filip Brychta
Modified: 2015-06-12 17:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-22 17:13:50 UTC
Type: Bug


Attachments (Terms of Use)

Description Filip Brychta 2013-12-13 07:53:57 UTC
Description of problem:
See the exception bellow. The cause of this issue should be clear. This exception was thrown to the agent log when all resources were imported (but relevant is probably only RHQ Server resource) and platform's operation 'Manual Autodiscovery' was invoked.

Version-Release number of selected component (if applicable):
Version :	
3.2.0.GA
Build Number :	
dcb8b6f:734bd56

How reproducible:
1/1

Steps to Reproduce:
1. Install jon32GA with all plugins (having all plugins installed is maybe not significant)
2. Import all resources
3. Run platform's operation 'Manual Autodiscovery'

Actual results:
Following exception is thrown to the agent log:

2013-12-13 02:16:45,556 WARN  [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Failure during discovery for [Query Cache] Resources - failed after 72 ms.
java.lang.Exception: Discovery component invocation failed.
	at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:309)
	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:722)
Caused by: java.lang.IllegalArgumentException: Plugin error: Resource key [deployment=rhq.ear,subdeployment=rhq-core-domain-ejb3.jar,subsystem=jpa,hibernate-persistence-unit=rhq.ear/rhq-core-domain-ejb3.jar#rhqpu,query-cache=SELECT_space_COUNT_left_paren__star__right_paren__newline_FROM_space_AlertDefinition_space_alertdefinition_newline_WHERE_space__left_paren__space_alertdefinition.group.id_space_IN_space__left_paren__space__colon_resourceGroupIds_space__right_paren__space__newline_AND_space_alertdefinition.deleted_space__equal__space__colon_deleted_space__right_paren__newline_] specified by [ResourceType[id=0, name=Query Cache, plugin=JBossAS7, category=Service]] discovery component is longer than the maximum length (500).
	at org.rhq.core.pluginapi.inventory.DiscoveredResourceDetails.setResourceKey(DiscoveredResourceDetails.java:143)
	at org.rhq.core.pluginapi.inventory.DiscoveredResourceDetails.<init>(DiscoveredResourceDetails.java:95)
	at org.rhq.modules.plugins.jbossas7.SubsystemDiscovery.discoverResources(SubsystemDiscovery.java:158)
	at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:305)
	... 5 more


Expected results:
No exceptions

Comment 2 Thomas Segismont 2014-08-22 17:13:50 UTC
In 3.3, the "Query Cache" resource is gone. Now users can run the "View Queries" operation on the "Hibernate Persistence Unit" resource.

Comment 3 Thomas Segismont 2014-08-22 17:14:38 UTC
*** Bug 1035373 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.