Red Hat Bugzilla – Bug 908326
AS 7 web connector discovery ends with wrong resource type
Last modified: 2013-09-03 10:43:45 EDT
Description of problem:
New AS7 instance discovery ends with wrong resource type for web connectors
Version-Release number of selected component (if applicable):
Last master build (4.6-SNAPSHOT)
Steps to Reproduce:
1. Start a new AS 7 instance
2. Import the server in discovery queue
3. Find your http connector resource ID (as7 instance > web > http in resources tree)
4. Execute this SQL query:
select t.name from rhq_resource_type t, rhq_resource r where r.resource_type_id = t.id and r.id = #http-connector-resourceid#;
"General JCA connectors"
This may also affect other services
master commit 20381597861b30716daecd4db9ad6ce88de98a78
Fix a bug in the ResourceType pojo to ResourceType entity conversion code.
Criteria String matching is *fuzzy* (i.e. substring matching) by default. This
needs to have the Criteria.setStrict(true) added to make it exact.
In the end I got rid of the Criteria query in favor of an existing NamedQuery,
for a possible perf boost as the query could be executed many times during a
large inventory merge.
Note that this was not an issue with AS7 plugin discovery, it was a server-side issue that could affect plugins with type A and type B, where type A's name was a substring of type B's name.
This problem was never in any release, it was only a regression in the 4.6 development phase.
Bulk closing of issues in old RHQ releases that are in production for a while now.
Please open a new issue when running into an issue.