bevarse Posted January 16, 2013 Report Posted January 16, 2013 We have a service A, that calls service B internally. The service B is giving an error(500- The server was unable to process the request due to an internal error.) ippudu twist yenti ante this error on service B is intermittent. yeppudu vastundo cheppalemu. i ran the same request about 100 times and got the error 2 times. to fix this issue i have 2 options 1. add a failover logic where service B is being called. (if error try again) 2. add tracing on service B to see why it is giving the internal error. yedi better antaru? okavela rendu waste aite inka yemi cheyyavachhu?
pikki Posted January 16, 2013 Report Posted January 16, 2013 pr0b src ento kanukkoni f!x cheyi ade better, leka pote malli pr0duct!0n lo !ssu'es vastayi kada...ATB ayina oka sari methods ni debug chesukovachu kada serv!ce cal! chese methods ni..or else un!t tests chesava anni meth0ds meda..bef0re runn!ng th0se serv!ce meth0ds...
bevarse Posted January 16, 2013 Author Report Posted January 16, 2013 [quote name='pikki' timestamp='1358355632' post='1303117040'] pr0b src ento kanukkoni f!x cheyi ade better, leka pote malli pr0duct!0n lo !ssu'es vastayi kada...ATB ayina oka sari methods ni debug chesukovachu kada serv!ce cal! chese methods ni..or else un!t tests chesava anni meth0ds meda..bef0re runn!ng th0se serv!ce meth0ds... [/quote] problem is in service B bhayya adi yela telusu ante, ninna prod lo wcftracing on service A on chesamu. so it captured the errors. all the errors were during the call to service B. so service B lo vunna method ni multiple times execute chesa DEV lo. it ran with no issues. soapui lo serviceB load chesi dev ki point chesi run chesa. oka 100 times. always passed, no error thrown. next prod ki point chesi run chesa, got error twice.
ChampakDas Posted January 16, 2013 Report Posted January 16, 2013 my guess would be it is not supporting multi threading....as you said if you get an error keep trying again is an option but there has to be some restriction for this for instance, after 3 tries it should be out of the tray and be logged...but its better to find the problem than giving this patch. web config lo service debug lo exception attribute true pettu it will give the exact error...
pikki Posted January 16, 2013 Report Posted January 16, 2013 [quote name='bevarse' timestamp='1358355966' post='1303117099'] problem is in service B bhayya adi yela telusu ante, ninna prod lo wcftracing on service A on chesamu. so it captured the errors. all the errors were during the call to service B. so service B lo vunna method ni multiple times execute chesa DEV lo. it ran with no issues. soapui lo serviceB load chesi dev ki point chesi run chesa. oka 100 times. always passed, no error thrown. next prod ki point chesi run chesa, got error twice. [/quote] emo mama mari nenu wcf meda ekkuva w0rk cheyaledu..kani s0ap ui manchi tool use chesuko...
bevarse Posted January 16, 2013 Author Report Posted January 16, 2013 [quote name='GatisKandis' timestamp='1358356211' post='1303117139'] my guess would be it is not supporting multi threading....as you said if you get an error keep trying again is an option but there has to be some restriction for this for instance, after 3 tries it should be out of the tray and be logged...but its better to find the problem than giving this patch. web config lo service debug lo exception attribute true pettu it will give the exact error... [/quote] aite maa tech lead gaadini adagadam better antava bhayya? manaki threading lu avi peddaga teleyavu.
MegaPowerRockstar Posted January 16, 2013 Report Posted January 16, 2013 Service B exception throw chesenappudu......service B hosted server lo event logs lo log authadhe ga issue,,... Akkada info untadhe,...
bevarse Posted January 16, 2013 Author Report Posted January 16, 2013 [quote name='MegaPowerRockstar' timestamp='1358359090' post='1303117692'] Service B exception throw chesenappudu......service B hosted server lo event logs lo log authadhe ga issue,,... Akkada info untadhe,... [/quote] event logging turned off bhayya
Jambhalheart Posted January 16, 2013 Report Posted January 16, 2013 dev lo ledu , production lo vastunnayi antunnav kabbati... 1. event logging... service B lo exact on which line ur gettin error ki try with any fault exception code and know in which method and line ur gettin error. 2. r u passin huge data from service A to service B ?? If yes, make sure that ur web.config of ur service B accepts behaviour with limit more than 2GB... correct ga event loggin process lekapothe chala kastam production loki vellina tharvata
ChampakDas Posted January 16, 2013 Report Posted January 16, 2013 neeku web.config chese rights untey chesi chudu lekapothey chepu mee lead ki ela chedam anukuntunnanu ani [quote name='bevarse' timestamp='1358357713' post='1303117419'] aite maa tech lead gaadini adagadam better antava bhayya? manaki threading lu avi peddaga teleyavu. [/quote]
Vaampire Posted January 16, 2013 Report Posted January 16, 2013 code lo edo issue undochu. or else edaina function time out avuthundochu. okkasari debug chesi choodu ey step valla time out vasthundo
MegaPowerRockstar Posted January 16, 2013 Report Posted January 16, 2013 Enabling evenlog its in the config only...no big change....so do it....eventlog is important anytime...dont disable it..atleast in prod if you are declaring any variables at the time of class initialization....and they are passed at the request time....also you might see this issue...
ILAQAT_MUFLIYA Posted January 16, 2013 Report Posted January 16, 2013 [quote name='pikki' timestamp='1358355632' post='1303117040'] pr0b src ento kanukkoni f!x cheyi ade better, leka pote malli pr0duct!0n lo !ssu'es vastayi kada...ATB ayina oka sari methods ni debug chesukovachu kada serv!ce cal! chese methods ni..or else un!t tests chesava anni meth0ds meda..bef0re runn!ng th0se serv!ce meth0ds... [/quote] pikki why u type like this ?
Recommended Posts