Hi,
I see the issue now... XFire doesn't clean up after itself in that case
:-( I created a JIRA:
http://jira.codehaus.org/browse/XFIRE-723
I just committed a fix for it in SVN if you would like to test it! I
will upload a new build sometime tomorrow too if you want to wait and
try that.
Cheers,
- Dan
Jones, Zack (SAIC) wrote:
Thatcher,
Thanks for the reply.
The issue I was describing below is a server-side problem, but it is a
client issue as well. If possible, I would appreciate an example of how to
add a handler to the OutHandler list on the server-side. In the meantime, we
will try to figure out how to do this on our own. Thanks for the help!
-Zack
-----Original Message-----
From: Chris Thatcher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 9:15 AM
To: [email protected]
Subject: RE: [xfire-user] RESEND: [xfire-user] SoapEnvelope attachments
when using MTOM are not cleaned up.
Hi Zack,
I'm not sure if this will help you, but ideally I think this would be best
managed by writing a handler whose job it is to clean up any attachments in
the attachment directory (which can be configured as noted
http://xfire.codehaus.org/MTOM here). Then just add this handler to your
clients InHandler list, which should default to the 'user' phase, which
should be fine. If this doesn't make sense let me know and Ill try to
create
a simple example handler that does this.
Thatcher
-----Original Message-----
From: Jones, Zack (SAIC) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 8:11 AM
To: '[email protected]'
Subject: RE: [xfire-user] RESEND: [xfire-user] SoapEnvelope attachments when
using MTOM are not cleaned up.
Dan,
Thanks for the reply.
We did read that section, and do follow the cleanup procedure for certain
methods that apply, but here is the dilemma:
If you have a service method like:
public Car[] getAllCars()
and the returned Car array is very large (and possible containing many
fields), the resulting SOAP Envelope is saved to disk as an attachment
without our code having any control over it. It would seem that Xfire
decides
that the SOAP envelope returned exceeds some threshold, and saves the SOAP
Evelope as an attachment to disk and does not clean up after its delivered
to
the client. I don't see where we can control this behavior in our code.
Is our understanding wrong?, or is this a legitimate problem.
Thanks,
Zack Jones
-----Original Message-----
From: Dan Diephouse [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 1:08 AM
To: [email protected]
Subject: Re: [xfire-user] RESEND: [xfire-user] SoapEnvelope attachments when
using MTOM are not cleaned up.
Hi Zack,
Did you read the part about cleaning up attachments in the manual?
http://xfire.codehaus.org/MTOM
Cheers,
- Dan
Jones, Zack (SAIC) wrote:
If anyone has any insight to this, it would be really appreciated!
-----Original Message-----
From: Jones, Zack (SAIC) [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 2:40 PM
To: '[email protected]'
Subject: [xfire-user] SoapEnvelope attachments when using MTOM are not
cleaned up.
Hi,
We are using Xfire 1.2-RC1 with MTOM enabled. We have an Xfire
service
that
returns an array of objects. This objects contain nothing more than
simple getters and setters. The array returned can be very large in
size.
We have noticed that the SOAPEnvelope containing the response is saved
as
an
att*.tmp both in the server's local tmp directory and the client's
local
tmp
directory. Unforunatley, becuase these files are not cleaned up, they
eventually cause the disk space to fill up in the tmp directory.
In our services.xml file, we have set MTOM-enabled to true. We are
not setting the attachment-threshold or the attachment-dir properties,
as they do no seem to make a difference for non DataHandler/Datasource
attachments.
Our question is, is there any way to configure XFire so that it either
does
not create the tmp files, or cleans them up. We noticed that turning
off MTOM resolves this issue, but is not an acceptable solution as we
require MTOM services.
Also, we can remove the client-side tmp files without a problem, but
we cannot remove the server-side tmp files unless we shut down the web
server (weblogic 9.2). This would suggest that the InputStreams on
the
server-side
attachments are not being closed.
Any suggestions?
-Zack
____________________________
http://www.pragmatics.com
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
____________________________
http://www.pragmatics.com
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
