Hi Sergey, Thanks for the suggestion. I have make the changes like different objects with @XMLRootElement removed WebServiceContext @Resource
i am still monitoring the logs, when i get to see anything will let u know. As far as the monitoring, we notice when the application hit the java heap space. The maxclient trend to go up and no request is accepted onwards. can you guess what will be the reason for the java heap space? usually this happens after 3-4 days of restarting the tomcat. The System comes to normal once you restart the tomcat. Hope the ablove information are clear. Waiting for your reply. Regards, Priya Sergey Beryozkin-2 wrote: > > Hi > > > > Of if you'd like me to investigate then please create a test project and > attach it to JIRA - that's probably the only way I can help with the > actual analysis > > - but I'm hoping may be you can help me a bit in getting to the bottom > of a problem :-) > > > > Cheers, Sergey > > > > ________________________________ > > From: Sergey Beryozkin > Sent: 04 December 2008 12:41 > To: '[email protected]' > Cc: 'jagapriya s' > Subject: RE: Apache maxClient reaches max > > > > Hi, > > > >> Media object - xml > > > > So, as far as I understand, you use JAXB on the input and possibly on > the output. > > > >> I don't do any (de)serialize > > > > Default JAXBElementProvider then - it does not keep any intermediate > state as far as I'm aware but it keeps > > a static map of JAXB contexts. Are you dealing with the next to > unlimited number of different objects with @XMLRootElement > > class annotations ? If yes then I guess using ObjectFactory should limit > a number of possible JAXB contexts to just 1. > > > >> i use WebServiceContext @Resource to fetch the bean object. > > So do you combine JAXWS and JAXRS ? > > In JAXRS-only services WebServiceContext is not available. > > > > So I'd appreciate if you could try 3 different approaches in trying to > narrow the problem > > > > - Eliminate JAXBProvider out of the picture - I honestly see no > reasons for it be a cause unless you do with thousands of disparate > types and no ObjectFactory involved. Try using a plain String instead, > just as a temp measure - you can copy the simple code from JAXBProvider > which creates a local JAXBContext, without caching it, and then create > marshaller/unmarshaller and do serialize/deserialize in your code > > - Eliminate WebServiceContext @Resource out of the picture > > - Give your own application code a check - temporarily avoid > using some external sources, etc, try to use some sample values when > replying, etc > > > > Cheers, Sergey > > > > > > ________________________________ > > From: jagapriya s [mailto:[EMAIL PROTECTED] > Sent: 04 December 2008 12:16 > To: Sergey Beryozkin > Subject: Re: Apache maxClient reaches max > > > > Hi, > > Implementation part i just followed: > http://cwiki.apache.org/CXF20DOC/jax-rs-jsr-311.html > > Media object - xml > I don't do any (de)serialize > i use WebServiceContext @Resource to fetch the bean object. > > KeepAlive is set to off. > > do you need any more info? > > Regards, > Priya > > > > On Thu, Dec 4, 2008 at 7:37 PM, Sergey Beryozkin <[EMAIL PROTECTED]> > wrote: > > Hi, > > It actually does, the next question is where is the source, somewhere in > the JAXRS runtime or even earlier in the HTTP transport layer ? > > - What sort of objects do you pass to/retrieve from your JAXRS service ? > - What media types are involved - can help me to check with providers > are involved, JAXB or JSON for ex > - Do you use any custom providers which (de)serialize > - Do you use @Context annotations on fields ? > > And please check for Keep-Alive too > > Cheers, Sergey > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 04 December 2008 11:15 > To: Sergey Beryozkin > Subject: RE: Apache maxClient reaches max > > Hi, > > Thanks a lot for the advice. will try it out. > From the log i am able to find > > Exception in thread "pool-5-thread-476" java.lang.OutOfMemoryError: Java > heap space > > Is this has some thing to do with the cxf memory leak. > > Regards, > Priya > > Sergey Beryozkin-2 wrote: >> >> Hi >> >> Can be it that perhaps your HTTP client code requires Keep-Alive ? >> You might want to try to use some tcptrace utility to check, I like > this >> one for ex : http://www.pocketsoap.com/tcptrace/, it's an old one but >> very simple and effective >> Not sure how this effect can be explain otherwise... >> >> Cheers, Sergey >> >> -----Original Message----- >> From: priya j [mailto:[EMAIL PROTECTED] >> Sent: 04 December 2008 03:10 >> To: [email protected] >> Subject: Apache maxClient reaches max >> >> >> Hi All, >> >> I using the rest service of the cxf for my application. When deployed > to >> the >> server, there is not much of traffic. I often face the MaxClient in >> Apache >> reaching max. want to confirm is there any issue with the > implementation >> of >> the cxf or do i need to close the connection. >> >> I just followed the link below for my implementation: >> http://cwiki.apache.org/CXF20DOC/jax-rs-jsr-311.html >> >> Please suggest. >> >> Regards, >> Priya >> -- >> View this message in context: >> > http://www.nabble.com/Apache-maxClient-reaches-max-tp20826444p20826444.h >> tml >> Sent from the cxf-user mailing list archive at Nabble.com. >> >> >> > Quoted from: > http://www.nabble.com/Apache-maxClient-reaches-max-tp20826444p20831123.h > tml > <http://www.nabble.com/Apache-maxClient-reaches-max-tp20826444p20831123. > html> > > > > > -- View this message in context: http://www.nabble.com/Apache-maxClient-reaches-max-tp20826444p20947915.html Sent from the cxf-user mailing list archive at Nabble.com.
