Hi all,
We are facing a rather strange but blocking issue after we upgraded our NetWeaver 7.0 environment to 7.4
When testing the Adobe Document Services, we found out they did not work.
As a first step, we checked the 'ConfigPort_Document' destination, but that was configured correctly. However, upon opening the containing <host>:<port>/inspection.wsil showed a shockingly empty WSIL except for the <wsil:inspection> header data...
When looking in wsnavigator, we found the total amount of 0 service endpoints, whereas we'd expect somewhere around 60+ or so...
In the logs we find traces like:
there is an error in publishing service definition : SOAPublicationObject{SOAObject{class='com.sap.esi.esp.lib.mass.entity.ServiceDefinition'soaObjectInfo=SOAObjectInfo
SOAObjectId
type = SERVICE_DEFINITION
local = sap.com~caf~eu~gp~model~ejb.com.sap.caf.eu.gp.model.gpws.uwl.GPWorkItemProviderVi
ns = sap.com/caf~eu~gp~model~eap
processingState = INITIAL
delete = false
(processingTraceId=null, processingLogId=null)
displayName=GPWorkItemProviderVi, description=GPWorkItemProviderVi
status=Active
systemObject=false, hiddenObject=false}'serviceRegistryStatus=UNKNOWN}
the SR returned : com.sap.esi.esp.lib.mm.config.exceptions.TechnicalException: com.sap.engine.interfaces.webservices.runtime.reverseproxy.WSReverseProxy
------------------------- Loader Info -------------------------
ClassLoader name: [service:tc~esi~esp~srv]
Loader hash code: 2555c789
Living status: alive
Direct parent loaders:
[system:Frame]
[library:engine.security.lib.facade]
[library:tc~esi~esp~lib]
[service:engine.security.facade]
[library:tc~esi~uddi~sr~persistence~lib]
[library:tc~je~sdo21~api]
[service:tc~esi~uddi~sr~cs~content~handler]
[library:tc~esi~esp~adm~be~model]
[service:engine.sld.facade]
[interface:tc~esi~esp~api]
Resources:
G:\usr\sap\DP1\J00\j2ee\cluster\bin\services\tc~esi~esp~srv\lib\tc~esi~esp~srv_api.jar
---------------------------------------------------------------
and
Error while publishing services:
[Service: KeystoreHelpVi, App: sap.com/com.sap.aii.sec.ws], Details: com.sap.esi.esp.lib.mm.config.exceptions.TechnicalException: com.sap.engine.interfaces.webservices.runtime.reverseproxy.WSReverseProxy
------------------------- Loader Info -------------------------
ClassLoader name: [service:tc~esi~esp~srv]
Loader hash code: 2555c789
Living status: alive
Direct parent loaders:
[system:Frame]
[library:engine.security.lib.facade]
[library:tc~esi~esp~lib]
[service:engine.security.facade]
[library:tc~esi~uddi~sr~persistence~lib]
[library:tc~je~sdo21~api]
[service:tc~esi~uddi~sr~cs~content~handler]
[library:tc~esi~esp~adm~be~model]
[service:engine.sld.facade]
[interface:tc~esi~esp~api]
Resources:
G:\usr\sap\DP1\J00\j2ee\cluster\bin\services\tc~esi~esp~srv\lib\tc~esi~esp~srv_api.jar
...for all the various services.
The recurring theme seems to boils down to a flakey WSReverseProxy class and or tc~esi~esp~srv_api.jar, but it might have an even deeper rootcause...
Any hints on why this behavior might happen and ultimately how we can solve it?
Any help will be much appreciated!
