Hide Forgot
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.
Link: Added: This issue related SOA-878
Link: Added: This issue is related to SOA-495
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.
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.
Verified in CR1 (and in EAP 4.3)