Bug 581848

Summary: Log file with exception of failed to deploy jbossws.sar
Product: [Other] RHQ Project Reporter: Rajan Timaniya <rtimaniy>
Component: Core ServerAssignee: John Sanda <jsanda>
Status: CLOSED WORKSFORME QA Contact: Corey Welton <cwelton>
Severity: low Docs Contact:
Priority: high    
Version: 3.0.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-19 17:28:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 565628, 591531    
Attachments:
Description Flags
log file none

Description Rajan Timaniya 2010-04-13 12:26:07 UTC
Created attachment 406221 [details]
log file

Description of problem:
Log file with the exception for deploy failed for jbossws.sar on JON Server.

(Reference: https://jira.jboss.org/jira/browse/JBWS-2821)

Version-Release number of selected component (if applicable):
jon build #88 Revision: 10607  (http://hudson-qe.rhq.rdu.redhat.com:8080/job/jon/88/)

How reproducible:
Always

Steps to Reproduce:
1) Install JON on Oracle or Postgres and start server
2) Verify log file (../jon-server-2.4.0-SNAPSHOT/logsrhq-server-log4j.log) for jbossws.sar deploy 
  
Actual results:
Failed to deploy jbossws.sar with the exception:
[org.jboss.deployment.MainDeployer] Could not initialise deployment: file:../jon-server-2.4.0-SNAPSHOT/jbossas/server/default/deploy/jbossws.sar/
org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml for archive jbossws.sar

Additional info:
Please refer attached log file.

Comment 1 Charles Crouch 2010-04-27 17:49:37 UTC
Why is jbossws.sar even being deployed? How did this behave in 2.3? Since we're not supporting WS access in 2.4, can this service just be removed/disabled?

Comment 2 Charles Crouch 2010-05-18 04:55:04 UTC
First off lets check if this is still a problem, and if so make sure it wasnt a problem in 2.3.1

Comment 3 John Sanda 2010-05-19 15:32:28 UTC
I just deployed jbossws on a JON 2.3.1 installation without error. I verified that the RHQ web service is up by hitting http://localhost.localdomain:7080/rhq-rhq-enterprise-server-ejb3/WebservicesManagerBean?wsdl. I will investigate whether or not we can remove jbossws.

Comment 4 John Sanda 2010-05-19 15:32:39 UTC
I just deployed jbossws on a JON 2.3.1 installation without error. I verified that the RHQ web service is up by hitting http://localhost.localdomain:7080/rhq-rhq-enterprise-server-ejb3/WebservicesManagerBean?wsdl. I will investigate whether or not we can remove jbossws.

Comment 5 John Sanda 2010-05-19 17:28:18 UTC
I just deployed jbossws on an RHQ server built from my current HEAD (8d1c051fbb07765ea3e746754ae61aabe2257a12) without error. I verified that the RHQ web service is up by hitting http://localhost.localdomain:7080/rhq-rhq-enterprise-server-ejb3/WebservicesManagerBean?wsdl. 

And jbossws.sar is not deployed by default. It is deployed as jbossws.sar.rej; so, it is in fact disabled by default. I am going to close this bug out since I have not been able to produce any errors and since jbossws is disabled by default.