Bug 724164 (BRMS-107)

Summary: KnowledgeAgent not picking up last modified date always (and thus not picking up changes)
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Michael Neale <michael.neale>
Component: BRE (Expert, Fusion)Assignee: trev <tkirby>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: urgent    
Version: 5.0.0 IR2   
Target Milestone: ---   
Target Release: 5.0.1   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-107
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-02 12:10:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
BRMS-107.patch none

Description Michael Neale 2009-05-05 05:14:58 UTC 
Affects: Release Notes
Date of First Response: 2009-09-02 08:10:44
Workaround Description: If this is a problem, can use RuleAgent for the moment as it uses a header that definitely works.
securitylevel_name: Public

Referring to: https://jira.jboss.org/jira/browse/JBRULES-2083
Comment 1 Michael Neale 2009-05-05 05:22:06 UTC 
Ideally would like this applied to drools-core (unless a newer tag of core is taken).
Comment 2 Michael Neale 2009-05-05 05:22:06 UTC 
Attachment: Added: BRMS-107.patch
Comment 3 Michael Neale 2009-05-14 11:20:36 UTC 
Workaround Description: Added: If this is a problem, can use RuleAgent for the moment as it uses a header that definitely works.
Comment 4 trev 2009-05-18 16:30:21 UTC 
Affects: Added: [Release Notes]
Comment 5 trev 2009-06-30 12:47:52 UTC 
Link: Added: This issue is a dependency of JBRULES-2083
Comment 6 Jaroslaw Kijanowski 2009-09-02 12:10:44 UTC 
Commit verified in 5.0.1 CR1
Comment 7 Dana Mison 2009-09-25 09:11:54 UTC 
Added to the BRMS 5.0 CP01 release notes as resolved:

The assets belonging to KnowledgeAgent did not always update to the most current version. This was because UrlResource.getLastModified() was not correctly determining the last modified date. This has been corrected.