Bug 780411 (SOA-2842)

Summary: KnowledgeAgent cannot use basic auth when accessing resource URL
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jiri Locker <jlocker>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.1.0.ER7CC: glamperi, kevin.conner
Target Milestone: ---   
Target Release: 5.1.0.ER8   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2842
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-17 07:44:05 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:

Description Jiri Locker 2011-01-24 17:10:52 UTC
project_key: SOA

Agent [insuranceconfig] Message [KnowledgeAgent exception while trying to deserialize KnowledgeDefinitionsPackage  ]
java.lang.RuntimeException: KnowledgeAgent exception while trying to deserialize KnowledgeDefinitionsPackage  
	at org.drools.agent.impl.KnowledgeAgentImpl.createPackageFromResource(KnowledgeAgentImpl.java:664)
	at org.drools.agent.impl.KnowledgeAgentImpl.addResourcesToKnowledgeBase(KnowledgeAgentImpl.java:889)
	at org.drools.agent.impl.KnowledgeAgentImpl.rebuildResources(KnowledgeAgentImpl.java:704)
	at org.drools.agent.impl.KnowledgeAgentImpl.buildKnowledgeBase(KnowledgeAgentImpl.java:584)
	at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:185)
	at org.jboss.internal.soa.esb.services.rules.DroolsRuleBaseHelper.createRuleAgent(DroolsRuleBaseHelper.java:230)
	at org.jboss.internal.soa.esb.services.rules.DroolsRuleService.getRuleBaseStateForRuleAgent(DroolsRuleService.java:332)
	at org.jboss.internal.soa.esb.services.rules.DroolsRuleService.executeStatelessRulesFromRuleAgent(DroolsRuleService.java:115)
	at org.jboss.internal.soa.esb.services.rules.RuleServiceCallHelper.executeStateless(RuleServiceCallHelper.java:286)
	at org.jboss.internal.soa.esb.services.rules.RuleServiceCallHelper.executeRulesService(RuleServiceCallHelper.java:270)
	at org.jboss.soa.esb.actions.BusinessRulesProcessor.executeRulesService(BusinessRulesProcessor.java:144)
	at org.jboss.soa.esb.actions.BusinessRulesProcessor.process(BusinessRulesProcessor.java:125)
	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649)
	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:603)
	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433)
	at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:550)
	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:636)
Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: http://127.0.0.1:8080/jboss-brms/org.drools.guvnor.Guvnor/package/soa/LATEST

The KnowledgeAgent applies a change set prepared by org.jboss.internal.soa.esb.services.rules.DroolsRuleAgentHelper, but the generated change set is corrupted as a result of error in processing the configuration properties.

Comment 1 Jiri Locker 2011-01-24 17:12:26 UTC
Link: Added: This issue depends JBESB-3563


Comment 2 Kevin Conner 2011-01-24 21:00:30 UTC
Updated in ESB codebase.

Comment 3 Jiri Locker 2011-01-28 10:03:03 UTC
Fixed in ER8. (/)

Comment 4 Dana Mison 2011-02-17 07:44:05 UTC
Release Notes Docs Status: Added: Not Required


Comment 5 Gary Lamperillo 2011-04-29 16:43:58 UTC
This appears to still be an issue.  It works with a changeset in the esb.xml.  I could not get a format of a properties file that works with the esb.xml

Comment 6 Gary Lamperillo 2011-04-29 16:44:34 UTC
SOA-P 5.1 and BRMS 5.1 that is.

Comment 7 Kevin Conner 2011-05-18 09:59:34 UTC
Checked Gary's example, it was missing the enableBasicAuthentication=true property.