Bug 778397 (SOA-881)

Summary:	production/conf/jboss-service.xml different from EAP version
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Julian Coleman <jcoleman>
Component:	Build Process, Deployment	Assignee:	Len DiMaggio <ldimaggi>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 IR5
Target Milestone:	---
Target Release:	4.3 CR1
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-881
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Embedded SOA
Last Closed:	2008-10-23 16:22:06 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 Julian Coleman 2008-09-26 09:47:09 UTC

Date of First Response: 2008-09-28 02:04:48
project_key: SOA

production/conf/jboss-service.xml differs from all/conf/jboss-service.xml.  Note that It is
copied at build time from build-tools/resource/conf-skeleton/jboss-service-secure.xml.

Comment 1 Julian Coleman 2008-09-26 09:48:09 UTC

Link: Added: This issue related SOA-878

Comment 2 Julian Coleman 2008-09-26 09:51:55 UTC

Link: Added: This issue is related to SOA-495

Comment 3 Jim Ma 2008-09-28 06:04:48 UTC

The major differences between this two files are :

1) The ClientUserTransactionService in production/conf/jboss-service.xml  uses JRMP invoker ClientUserTransactionService in all /production/conf/jboss-service.xml uses UnifiedInvoker . 

2) there is an extra "80" after "<classpath codebase="${jboss.server.lib.url:lib}" archives="*"/>" in   /production/conf/jboss-service.xml

3) ScanPeriod value in /production/conf/jboss-service.xml  is 60000:  <attribute name="ScanPeriod">60000</attribute>  . 

From the comment for JBAS-5226 , we can see ClientUserTranscationService should use UnifiedInvoker . I suspect 2) is a typo from jboss-service-secure.xml. For 3) , it is the right difference because EAP also set like this. .  

This issue is introduced by the fix for SOA-131(copy the file from build-tools/resource/conf-skeleton/jboss-service-secure.xml and overwrite the production/conf/jboss-service.xml from EAP) . Since the EAP already contains the fix for this security issue , we should remove the patch for SOA-131.

Comment 4 Julian Coleman 2008-09-30 11:02:33 UTC

Fixed with revision 2031 of:
  build-tools/builders/eap/build.xml
  build-tools/resource/conf-skeleton/jboss-service-secure.xml

Commit message:

  Don't overwrite EAP's .../production/jboss-service.xml, as EAP now contains
  the fix for JIRA SOA-131.

Comment 5 Len DiMaggio 2008-10-23 16:22:06 UTC

Verified in CR1 (and in EAP 4.3)