[jboss-jira] [JBoss JIRA] Created: (JBRULES-1506) RuleAgent will not read binary packages from Apache HTTP Server

David Stringer (JIRA) jira-events at lists.jboss.org
Fri Mar 14 18:22:28 EDT 2008


RuleAgent will not read binary packages from Apache HTTP Server
---------------------------------------------------------------

                 Key: JBRULES-1506
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1506
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: All
    Affects Versions: 4.0.4
         Environment: Rules Package is stored in SVN, accessed through Apache 2.0.52
Rules Agent is running within WAR on Jboss 4.0.5, Java 1.6
Both Servers are running on Cent-OS 4
            Reporter: David Stringer
         Assigned To: Mark Proctor


Hi,

We were hoping to deploy our rules packages in SVN fronted by Apache 2.0.52. The rule agent fails when trying to load the URI that resolves into the repository..

Exception is as follows:
2008-03-14 11:46:08,270 ERROR [STDERR] RuleAgent(MyConfig) INFO (Fri Mar 14 11:46:08 PDT 2008): Configuring package provider : URLScanner monitoring URLs:  http://vconfig.dev.alea.ca/alea/eco/rules/eco.pkg with local cache dir of /tmp
2008-03-14 11:46:08,583 ERROR [STDERR] RuleAgent(MyConfig) WARNING (Fri Mar 14 11:46:08 PDT 2008): Was an error contacting http://vconfig.dev.alea.ca/alea/eco/rules/eco.pkg. Reponse header: {null=[HTTP/1.1 200 OK], ETag=["360//alea/eco/rules/eco.pkg"], Date=[Fri, 14 Mar 2008 18:46:08 GMT], Last-Modified=[Fri, 14 Mar 2008 17:06:15 GMT], Keep-Alive=[timeout=15, max=100], Accept-Ranges=[bytes], Connection=[Keep-Alive], Content-Type=[application/octet-stream], Server=[Apache]}
2008-03-14 11:46:08,583 ERROR [STDERR] RuleAgent(MyConfig) WARNING (Fri Mar 14 11:46:08 PDT 2008): Falling back to local cache.

I believe the problem resides in "org.droos.agent.HttpClientImpl". It is looking for a http header field "lastModified", instead of the HTTP standard header field  "last-modified". Thus it never updates the lastUpdated field in "LastUpdatedPing", which means the server will never load the file.

It seems to me to be an easy fix, to check for both headers.. ?

Thanks,
David.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list