>From what I gather from my experience is that it may have something to do with >Rampart. The other thing to watch is whether or not a new context, i.e., >ConfigurationContext, is created every time you make a call, e.g. create a >context, then create a stub and make a SOAP call.
HTH -----Original Message----- From: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com] Sent: 24 July 2012 08:41 To: java-user@axis.apache.org Subject: Re: [Axis2] how to unlock and delete temporary files Can you also monitor mentioned temp folder for sometime and identify under which conditions (actions) it create new temp Jar files ? Thanks ! On Tue, Jul 24, 2012 at 1:05 PM, Zanelli Franco <fzane...@tecnosens.it> wrote: > My application is a cctv management software for Onvif cameras, and I > use to frequently connect and disconnect cameras. Each time I connect > a camera I open a SOAP session and I use this code: > > username = "username"; > password = "password"; > ConfigurationContext ctx = > ConfigurationContextFactory.createConfigurationContextFromFileSystem( > null, > "./axis2.xml"); > sc = new ServiceClient(ctx, null); > > where axis2.xml is the following > > <axisconfig name="AxisJava2.0"> > <module ref="rampart" /> > <parameter name="OutflowSecurity"> > <action> > <items>UsernameToken</items> > </action> > </parameter> > > <parameter name="hotdeployment" locked="false">true</parameter> > <parameter name="hotupdate" locked="false">true</parameter> > > <messageReceiver mep="INOUT" > class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/> > > <transportSender name="http" > class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"> > <parameter name="PROTOCOL" locked="false">HTTP/1.0</parameter> > </transportSender> > > <phaseOrder type="InFlow"> > <!-- System pre defined phases --> > <phase name="Transport"> > <handler name="RequestURIBasedDispatcher" > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"> > <order phase="Dispatch"/> > </handler> > <handler name="SOAPActionBasedDispatcher" > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"> > <order phase="Dispatch"/> > </handler> > </phase> > <phase name="Security"/> > <phase name="PreDispatch"/> > <phase name="Dispatch" > class="org.apache.axis2.engine.DispatchPhase"> > <handler name="RequestURIBasedDispatcher" > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/> > <handler name="SOAPActionBasedDispatcher" > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/> > <handler name="RequestURIOperationDispatcher" > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/> > <handler name="SOAPMessageBodyBasedDispatcher" > > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/> > > <handler name="HTTPLocationBasedDispatcher" > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/> > </phase> > <!-- System pre defined phases --> > <!-- After Postdispatch phase module author or or service author > can add any phase he want --> > <phase name="OperationInPhase"/> > <phase name="soapmonitorPhase"/> > </phaseOrder> > <phaseOrder type="OutFlow"> > <!-- user can add his own phases to this area --> > <phase name="soapmonitorPhase"/> > <phase name="OperationOutPhase"/> > <!--system predefined phase--> > <!--these phase will run irrespective of the service--> > <phase name="PolicyDetermination"/> > <phase name="MessageOut"/> > <phase name="Security"/> > </phaseOrder> > <phaseOrder type="InFaultFlow"> > <phase name="PreDispatch"/> > <phase name="Dispatch" > class="org.apache.axis2.engine.DispatchPhase"> > <handler name="RequestURIBasedDispatcher" > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/> > <handler name="SOAPActionBasedDispatcher" > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/> > <handler name="RequestURIOperationDispatcher" > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/> > <handler name="SOAPMessageBodyBasedDispatcher" > > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/> > > <handler name="HTTPLocationBasedDispatcher" > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/> > </phase> > <!-- user can add his own phases to this area --> > <phase name="OperationInFaultPhase"/> > <phase name="soapmonitorPhase"/> > <phase name="Security"/> > </phaseOrder> > <phaseOrder type="OutFaultFlow"> > <!-- user can add his own phases to this area --> > <phase name="soapmonitorPhase"/> > <phase name="OperationOutFaultPhase"/> > <phase name="PolicyDetermination"/> > <phase name="MessageOut"/> > <phase name="Security"/> > </phaseOrder> > > </axisconfig> > > It seems that everytime I call this code in a running application it > creates a new file. > > thanks > > > > Il 21/07/2012 09:56, Sagara Gunathunga ha scritto: > > I tried on both Ubuntu 12.04 and Windows 7 ( Java 6 u33, > apache-tomcat-7.0.26 and Axis2/Rampart 1.6.2 ) but I can't reproduce > your original issue. During the server run I only can see same set of > temp files and folder size also remains same. Could you provide exact > and detailed description about your configuration so that I can try again. > > FYI followings found on apache-tomcat-7.0.26\temp directory. > > ├── axis2-tmp-402461891410668354.tmp > │ ├── axis21314472422694690389sample02.aar > │ ├── axis21542750312318073943sample01.aar > │ ├── axis22272459040834308700ping-1.6.2-SNAPSHOT.mar > │ ├── axis22639826696280010430axis2-jaxws-mar-1.6.2-SNAPSHOT.mar > │ ├── axis23676318719154391135version-1.6.2-SNAPSHOT.aar > │ ├── axis2384307141943523944mex-1.6.2-SNAPSHOT.mar > │ ├── axis24170305247321540800addressing-1.6.2-SNAPSHOT.mar > │ ├── axis24691797839292807234scripting-1.6.2-SNAPSHOT.mar > │ ├── axis26364987682968736391soapmonitor-1.6.2-SNAPSHOT.mar > │ ├── axis26381918337066202975mtompolicy-1.6.2-SNAPSHOT.mar > │ ├── axis2643854423296824589rampart-1.6.2.mar > │ ├── axis28057310721759389693 > │ └── axis28091149457053540894addressing-1.6.2.mar > └── axis2-tmp-402461891410668354.tmp.lck > > Thanks ! > > On Mon, Jul 16, 2012 at 1:39 PM, Sagara Gunathunga > <sagara.gunathu...@gmail.com> wrote: >> >> Usually I work on Linux but will try on Windows7 to reproduce this >> issue, but I can't provide any exact time line. Most probably if this >> is reproducible will fix for 1.7.0 release. >> >> Thanks ! >> >> On Thu, Jul 12, 2012 at 12:10 PM, Zanelli Franco >> <fzane...@tecnosens.it> >> wrote: >>> >>> I'm working on Windows 7 and this is an example of list file names; >>> they are locked until the application is running: >>> >>> 12/07/2012 08:34 <DIR> . >>> 12/07/2012 08:34 <DIR> .. >>> 11/07/2012 14:44 9.229 >>> axis21416912558469186102rampart-1.6.1.jar >>> 11/07/2012 14:32 9.229 >>> axis21509415437238259318rampart-1.6.1.jar >>> 11/07/2012 14:46 9.229 >>> axis21966863075365099860rampart-1.6.1.jar >>> 11/07/2012 14:14 9.229 >>> axis22303908513742725464rampart-1.6.1.jar >>> 11/07/2012 14:46 9.229 >>> axis22424953883953097823rampart-1.6.1.jar >>> 11/07/2012 14:13 2.285.245 >>> axis22438746523922262446axis2-1.6.1.jar >>> 11/07/2012 14:46 9.229 >>> axis2304716139404310737rampart-1.6.1.jar >>> 11/07/2012 13:34 9.229 >>> axis23280640091967599099rampart-1.6.1.jar >>> 11/07/2012 14:39 9.229 >>> axis23289131501227431942rampart-1.6.1.jar >>> 11/07/2012 14:32 9.229 >>> axis23623477711224233594rampart-1.6.1.jar >>> 11/07/2012 14:45 9.229 >>> axis24064159888117717366rampart-1.6.1.jar >>> 11/07/2012 14:46 2.285.245 >>> axis24138362837334899395axis2-1.6.1.jar >>> 11/07/2012 14:32 9.229 >>> axis24169225200500972588rampart-1.6.1.jar >>> 11/07/2012 14:12 9.229 >>> axis24196920701274949215rampart-1.6.1.jar >>> 11/07/2012 14:13 9.229 >>> axis24312174956140386583rampart-1.6.1.jar >>> 11/07/2012 14:32 2.285.245 >>> axis24314571673869116798axis2-1.6.1.jar >>> 11/07/2012 14:13 2.285.245 >>> axis24506103510380709545axis2-1.6.1.jar >>> 11/07/2012 14:13 9.229 >>> axis24647890395603079538rampart-1.6.1.jar >>> 11/07/2012 14:39 9.229 >>> axis24690330867633166334rampart-1.6.1.jar >>> 11/07/2012 14:13 2.285.245 >>> axis24707312552747513185axis2-1.6.1.jar >>> 11/07/2012 14:32 2.285.245 >>> axis24752902450719382616axis2-1.6.1.jar >>> 11/07/2012 14:32 9.229 >>> axis2513921642284968659rampart-1.6.1.jar >>> 11/07/2012 14:32 2.285.245 >>> axis25144058483045372983axis2-1.6.1.jar >>> 11/07/2012 14:44 2.285.245 >>> axis25476714304412646090axis2-1.6.1.jar >>> 11/07/2012 14:32 2.285.245 >>> axis25503851350480281698axis2-1.6.1.jar >>> 11/07/2012 14:13 9.229 >>> axis25519301193443871234rampart-1.6.1.jar >>> 11/07/2012 13:34 2.285.245 >>> axis25524069298591810328axis2-1.6.1.jar >>> 11/07/2012 14:13 9.229 >>> axis25627308659529533243rampart-1.6.1.jar >>> 11/07/2012 14:46 2.285.245 >>> axis2568169813775070191axis2-1.6.1.jar >>> 11/07/2012 14:13 9.229 >>> axis25726694343012261384rampart-1.6.1.jar >>> 11/07/2012 14:13 2.285.245 >>> axis25834963843840517915axis2-1.6.1.jar >>> 11/07/2012 14:32 2.285.245 >>> axis26637531347642113441axis2-1.6.1.jar >>> 11/07/2012 14:46 9.229 >>> axis26752209726427078226rampart-1.6.1.jar >>> 11/07/2012 14:46 2.285.245 >>> axis26806424145360728047axis2-1.6.1.jar >>> 11/07/2012 14:45 2.285.245 >>> axis27145119278349429680axis2-1.6.1.jar >>> 11/07/2012 14:39 2.285.245 >>> axis2721928032583987680axis2-1.6.1.jar >>> 11/07/2012 14:39 9.229 >>> axis27291519028719687325rampart-1.6.1.jar >>> 11/07/2012 14:13 2.285.245 >>> axis27308655973731804611axis2-1.6.1.jar >>> 11/07/2012 14:46 9.229 >>> axis27445862635933375468rampart-1.6.1.jar >>> 11/07/2012 14:42 2.285.245 >>> axis27578542695752557570axis2-1.6.1.jar >>> 11/07/2012 14:46 2.285.245 >>> axis27638278631414098896axis2-1.6.1.jar >>> 11/07/2012 14:32 9.229 >>> axis27907547743081275382rampart-1.6.1.jar >>> 11/07/2012 14:13 9.229 >>> axis2791744208349861365rampart-1.6.1.jar >>> 11/07/2012 14:12 2.285.245 >>> axis2792995400271337688axis2-1.6.1.jar >>> 11/07/2012 14:46 9.229 >>> axis27993871858773185067rampart-1.6.1.jar >>> 11/07/2012 14:39 2.285.245 >>> axis28016023195092974008axis2-1.6.1.jar >>> 11/07/2012 14:46 2.285.245 >>> axis28364359533639293482axis2-1.6.1.jar >>> 11/07/2012 14:13 2.285.245 >>> axis28448109074789470944axis2-1.6.1.jar >>> 11/07/2012 14:46 2.285.245 >>> axis2846714489711230357axis2-1.6.1.jar >>> 11/07/2012 14:32 2.285.245 >>> axis28502070331645871025axis2-1.6.1.jar >>> 11/07/2012 14:14 2.285.245 >>> axis2852100564070407843axis2-1.6.1.jar >>> 11/07/2012 14:32 9.229 >>> axis28983640441331724657rampart-1.6.1.jar >>> 11/07/2012 14:39 2.285.245 >>> axis29071605408256628513axis2-1.6.1.jar >>> 11/07/2012 14:42 9.229 >>> axis29194904091299873891rampart-1.6.1.jar >>> >>> thanks >>> >>> Il 11/07/2012 18:14, Sagara Gunathunga ha scritto: >>> >>> Can you provide list file names you found on temporary directory >>> during runtime. In Linux tree utility provide nice list of content. >>> >>> Thanks ! >>> >>> On Wed, Jul 11, 2012 at 7:30 PM, Zanelli Franco >>> <fzane...@tecnosens.it> >>> wrote: >>> >>> I'm using axis2 1.6.1 with rampard and I experienced that my >>> application creates many temporary files named >>> "axis.....axis2-1.6.1.jar" on folder "...\Temp\axis2-tmp-....tmp" . >>> These files are deleted only when I restart the application, but my >>> application needs to be always running. >>> I checked in the mailing lists for a solution but I didn't find it. >>> Is there a way to delete these temporary files without close the >>> application and avoid a disk full error? >>> >>> thank you >>> >>> Zanelli Franco >>> >>> -------------------------------------------------------------------- >>> - To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org >>> For additional commands, e-mail: java-user-h...@axis.apache.org >>> >>> >>> >> >> >> >> -- >> Sagara Gunathunga >> >> Blog - http://ssagara.blogspot.com >> Web - http://people.apache.org/~sagara/ >> LinkedIn - http://www.linkedin.com/in/ssagara > > > > > -- > Sagara Gunathunga > > Blog - http://ssagara.blogspot.com > Web - http://people.apache.org/~sagara/ > LinkedIn - http://www.linkedin.com/in/ssagara > > > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ LinkedIn - http://www.linkedin.com/in/ssagara --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org The content of this e-mail (and any attachment to it) is confidential. Any views or opinions do not represent the views or opinions of Infoshare Ltd. If you have received this e-mail in error please notify the sender and delete it. You may not use, copy or disclose the information in any way. Infoshare Ltd monitors incoming and outgoing e-mails. Please consider the environment. Do you really need to print this email? --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
