Yes, Axis2 will solve the memory spike issues. -- dims
On 9/15/06, Aoife Kavanagh (Ext. 987) <[EMAIL PROTECTED]> wrote:
Investigating an upgrade to Axis2 is an option but I would only want to go that route if I know for sure it will fix the problem as based on work done by one of my colleagues I know that there are alot of changes between Axis 1.x and Axis 2 and so this upgrading will result in the need for alot of other changes. Thanks, Aoife -----Original Message----- From: Neil Aggarwal [mailto:[EMAIL PROTECTED] Sent: 15 September 2006 15:33 To: [email protected] Subject: RE: Large PDFs and Memory Usage Hello: Does Axis2 fix the large memory usage issues with Axis 1? Thanks, Neil -- Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com FREE! Eliminate junk email and reclaim your inbox. Visit http://www.spammilter.com for details. > -----Original Message----- > From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED] > Sent: Friday, September 15, 2006 8:23 AM > To: '[email protected]' > Subject: Large PDFs and Memory Usage > > Hi, > > We have a service running where the reutrn value from the > service invocation > is sent as String using SOAP over JMS. We are encountering > problems with > memory consumption when that String is large, eg 1M or > greater. It is not a > case of just increasing heap size, it is just that the amount > of memory > being used is can be anything from 1.3GB to 2.7GB. We've > used hprof to > determine that the majority of this memory usage is occurring > in the Axis > (1.3)/Xerces code. > > I'm looking to see if there is anything that we can do to try > to reduce > this. One thought is to return the data using xsd:base64Binary or > xsd:hexBinary but it seems that the encoding data in to base64Binary > consumes memory and can cause trouble at the receiving end > with the XML > parser, so I'm not sure if it is worth proceeding down this route. > > Another thought is to send the data as MIME attachment (of > which I honestly > don't know much) but it's not clear to me, based on some > initial mailing > searches, if this approach will work any better, or if it even works > properly in Axis 1.3. > > >From what I can see in the lists plenty of people have > experienced this > memory spike problem and I'm just wondering if there are any > clear solutions > out there. > > Thanks, > Aoife > > __________________________________________________________ > The information contained in this e-mail is confidential, may > be privileged and is intended > only for the user of the recipient named above. If you are > not the intended recipient or a > representative of the intended recipient, you have received > this e-mail in error and must > not copy, use or disclose the contents of this e-mail to > anybody else. > > If you have received this e-mail in error, please notify the > sender immediately by return > e-mail and permanently delete the copy you received. This > e-mail has been swept for > computer viruses. However, you should carry out your own > virus checks. > Registered in Ireland, No. 205721. http://www.FINEOS.com > __________________________________________________________ > > > --------------------------------------------------------------------- > 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]
-- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
