Bug 779361 (SOA-1751)

Summary: Bad WARNING Message during deployment
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Burr Sutter <burr.sutter>
Component: DeploymentAssignee: Kevin Conner <kevin.conner>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER5   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1751
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-04 09:32:41 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
http_gateway_burr.zip none

Description Burr Sutter 2009-12-21 23:35:35 UTC 
project_key: SOA

18:28:16,830 WARNING [config] Unable to process deployment descriptor for context '/Quickstart_http_gateway_burr'

Myself and another user have seen this message "Unable to process deployment descriptor" in Beta1.

However, the quickstart still deploys fine.  We have noticed this message when using the new http-gateway.  Attached is my quickstart (modified from http-gateway). 

I have not seen this message when deploying helloworld, just quickstarts involving the http gateway.
Comment 1 Burr Sutter 2009-12-21 23:38:07 UTC 
 a simplification of the http-gateway quickstart in beta1/ER5.  "ant deploy" will demonstrate the odd error message.
Comment 2 Burr Sutter 2009-12-21 23:38:07 UTC 
Attachment: Added: http_gateway_burr.zip
Comment 3 Burr Sutter 2009-12-21 23:43:39 UTC 
Deploying helloworld (ant deploy) provides its own WARN message:

18:39:38,786 WARN [ServiceMessageCounterLifecycleResource] Calling cleanup on e
xisting service message counters for identity ID-17

I think these WARN messages need to be removed if there is nothing the end-user (me) can do about them, they send the user chasing rabbits thinking there is a problem in their configuration (jboss-esb.xml).
Comment 4 Kevin Conner 2010-01-04 09:32:28 UTC 
Link: Added: This issue duplicates SOA-1664