Erromessage throughout the default traces on all Server Processes

[Former Member]

Dear All,

I see the following error message throughout the default traces on all
Server Processes:

#2.#2014
09 30
09:31:35:579#+0200#Error#com.sap.engine.services.servlets_jsp.IS

E500#

com.sap.ASJ.web.000500###C00093A7325D21D800000008018B0052#103078250000000004#sap

.com/E-Sourcing-Server#com.sap.engine.services.servlets_jsp.ISE500#Guest#0##DA5E

79BE487211E48AE600000624D96A#3fb90eb4487311e4bfd400000624d96a#3fb90eb4487311e4bf

d400000624d96a#0#Thread[HTTP
Worker [@1070111540],5,Dedicated_Application_Thread

]#Plain##

500 Internal Server Error is returned for HTTP request
[https://pp49di00.eu.nova

rtis.net:51001/esourcing/fsbuyer/analysis/globalSearch,r:-2147483027:335]:

component [IMBOFrameworkServlet],

web module [esourcing],

application [sap.com/E-Sourcing-Server],

DC name [],

CSN component[],

problem categorization [],

Internal categorization [657040923].
com.sap.bc.proj.jstartup.fca.FCAException: Cannot get
OutBuffer: -7 connection to partner broken..

Will you please guide me mitigate / rectify this.

Thanks & Regards,

Joginder

[Former Member]

Hello Joginder,

    Can you please tell us what the actual problem is. Are you using the SAP Sourcing application and if so is there something that you see that is not working as installed/expected.

Prasad

[Former Member]

Dear Prasad,

Yes I am using SAP sourcing application. Many times it is observed that workflow gets locked and even mail queue are stuck. last option left is to  restart server.....

While checking logs one of the error message that keeps appearing is the mentioned above.

I presume that above mentioned error is linked to this problem.

Thanks

[Former Member]

Joginder,

   Please check the log files associated with the Sourcing application. They are the eso*.log and eso*.trc files. Netweaver log files found on the server process will not contain application logs relating to SAP Sourcing. The blog http://scn.sap.com/community/sourcing/blog/2013/11/26/debug-logs-and-logviewer-concepts-part-1 will provide addition details if needed..

Prasad

[Former Member]

Dear Prasad,

Thanks for info. Main problem here is this problem occurs on random basis and is not replicable in any other environment (happening only in production). it is not possible to put debug mode in production environment. it will have very severe impact.

Thanks

[Former Member]

I would suggest that you try to get the debug logs during off-peak hours create an OSS message and attach them to an OSS message. We will be able to investigate better with the debug logs.

Thanks

Prasad