Bug 779650 (SOA-2019)
Summary: | RuleAgent could not get the RuleBase (BRMS5+SOA5) can't find properties file | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Burr Sutter <burr.sutter> | ||||||||
Component: | JBossESB | Assignee: | Default User <jbpapp-maint> | ||||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | high | ||||||||||
Version: | 5.0.0 GA | CC: | kevin.conner, ratnamadhumita | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
URL: | http://jira.jboss.org/jira/browse/SOA-2019 | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: |
Windows7 Java 1.6 32-bit - JBDS 3.0, BRMS 5.0, SOA 5.0
|
|||||||||
Last Closed: | 2010-09-22 15:54:34 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: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Burr Sutter
2010-03-30 17:13:34 UTC
Attachment: Added: ESBTestBRMS.zip Attachment: Added: repository_export(5).zip Attachment: Added: ESBTestBRMS.esb Workaround Description: Added: Drop the .properties files into jbrules.esb, then it all works well. java.lang.NullPointerException java.util.Properties$LineReader.readLine(Properties.java:435) java.util.Properties.load0(Properties.java:354) java.util.Properties.load(Properties.java:342) org.drools.agent.RuleAgent.loadFromProperties(RuleAgent.java:299) org.drools.agent.RuleAgent.newRuleAgent(RuleAgent.java:273) This seems to have been caused by two issues, the fact that the drools code base did not refer to the TCCL and the fact that the initial http support caused the esb deployment to be scoped. In SOA 5.1 we parse the properties ourselves and we have created a separate deployment for the http/ebws aspects. |