Hide Forgot
project_key: SOA The juddiv3.war consists of multiple services defined by individual WSDL files. When the servlet is accessed for the first time it will cause the initialisation of the spring context, however this initialises all endpoints. When a second servlet is accessed this process repeats. The juddiv3.war consists of 11 services, which I believe results in 121 initialisations (11 * 11).
juddiv3.war modified to workaround SOA-2335
Attachment: Added: juddiv3.war.new
To see the issue do the following - deploy the attached jar - access a service URL (http://127.0.0.1:8080/juddiv3/services/custody-transfer?wsdl) to see all service endpoints being initialised - access a second service URL (http://127.0.0.1:8080/juddiv3/services/subscription-listener?wsdl) to see service endpoints being initialised again. - repeat with other service URLs It looks like each bus may initialise a spring configuration which consists of all endpoints within the deployment.
Upstream this initialisation process has been refactored, initially a backport appears too large so a EAP specific fix may be required for this one.
Please incorporate the jar in JBPAPP-5489
Resolved with revision 7500 of: build-tools/builders/eap/post-patch/patch_wscxf_jar.xml Commit message: SOA-2336 Replace jbossws-cxf-server.jar with jar from JBPAPP-5489.
Labels: Added: rn-not-needed
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage