On Wed, 2008-03-05 at 18:09 +0530, Raghavendra SM wrote:
> Thanks Manjula,
> 
> But thats not a viable option for us. We would still want to continue 
> using axis2C-1.0 for some more time.

IMHO, changing from Axis2/C 1.0 to 1.3 is not a big issue. Because the
client API and the service API did not change much. Devs please correct
me if i am wrong. There are lot of new features, bug fixes and
performance improvements in 1.3 release.

-Manjula


>  
> 
> Are these dumps well known? And have they been specifically fixed in 
> axis2c-1.3? 
> 
> Regards,
> ~raghav
>  
> 
> -----Original Message-----
> From: Manjula Peiris [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, March 05, 2008 6:05 PM
> To: Apache AXIS C User List
> Subject: Re: Core dumps in Axis libraries
> 
> Hi raghav,
> 
> Axis2/C 1.3 was recently released. There are lots of new features and
> bug fixes in that release. Please try that.
> http://ws.apache.org/axis2/c/download.cgi
> 
> -Thanks,
> Manjula.
> 
> 
> On Wed, 2008-03-05 at 17:34 +0530, Raghavendra SM wrote:
> > All,
> > 
> > For a particular scenario, our module core dumps in some axis library 
> > functions consistently but with different back traces. I'm attaching 
> the 
> > dumps.log file that has as many as 4 different back-traces produced 
> for 
> > the same scenario.
> > Also, please find attached the log that has axis generated log for 
> both 
> > successful and erroneous times, axis.log.
> > 
> > To give you all a brief background,
> > + we are using axis2c-1.0.0
> > + the core dump appears during a particular scenario only. Eg: while 
> > trying to add a list of already existing users to my database. For 
> each 
> > user there is a SOAP request generated and the requests are 
> sequential, 
> > i.e the second request is sent only after the response for previous 
> > request is received.
> > + if I increase the log level of my own module that uses axis2c, there 
> 
> > is no dump. On increasing the log level, my module writes quite a bit 
> of 
> > information to my log file.
> > 
> > Since the back trace is pointing to the libraries(for which there is 
> no 
> > source code given), how can this be debugged and fixed? 
> > 
> > Any inputs will be of great help. Please reply.
> >  
> > 
> > Regards,
> > ~raghav
> >  
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to