Thx for help...
I think i'm already in this situation, async service is retrieved
through the following class:

public class ProxyAsync {
    public ProxyAsync(){}
    public static ProxyAsync getInstance(){return new ProxyAsync();}
    public  CCN_WS_WrapNaviInMareAsync getServiceWsNaviInMare() {
        // Create the client proxy. Note that although you are
creating the
        // service interface proper, you cast the result to the
asynchronous
        // version of
        // the interface. The cast is always safe because the
generated proxy
        // implements the asynchronous interface automatically.
        CCN_WS_WrapNaviInMareAsync service =
(CCN_WS_WrapNaviInMareAsync) GWT.
        create(CCN_WS_WrapNaviInMare.class);
        // Specify the URL at which our service implementation is
running.
        // Note that the target URL must reside on the same domain and
port from
        // which the host page was served.
        //
        ServiceDefTarget endpoint = (ServiceDefTarget) service;
        String moduleRelativeURL = GWT.getModuleBaseURL()
+"ccn_ws_wrapnaviinmare";
        endpoint.setServiceEntryPoint(moduleRelativeURL);
        return service;
    }

were you saying that?
thx, have a nice day,
Michela

On 2 Mar, 09:05, Алексей Циунчик <[email protected]> wrote:
> Hi Koalina,
>
> We have similar issue in our app. In our case we use static field to hold
> RPC service reference. In your case  please check whether
>  proxyAsync.getServiceWsNaviInMare() return always the same instance of RPC
> service, or not. If it is always the same, refector your code to return
> always new object something like:
>
> proxyAsync.getServiceWsNaviInMare() {
>    return GWT.create(.....);
>
> }
>
> In our case this helps.
>
> 2009/2/27 koalina <[email protected]>
>
>
>
> > Hi all,
> > i'm developing a tracking application. I think that there's a memory
> > leak issue when a rpc is called inside a timer repeating.
> > the code is semplified as follow:
>
> >  public void onModuleLoad() {
> >        startRefreshInfoSupp();
> > }
> >  where the startRefreshInfoSupp is
>
> >  final AsyncCallback asyncCallback = new AsyncCallback() {
>
> >                    public void onFailure(Throwable caught) {
> >                        ......
> >                    }
>
> >                    public void onSuccess(Object result) {
> >                        GWT.log("Ricevute seguenti informazioni
> > supplementari: "+(String) result, null);
> >                        ..
> >                            }
> >                        }
> >                    }
>
> >                };
>
> >        Timer t = new Timer() {
>
> >            public void run() {
>
> >                proxyAsync.getServiceWsNaviInMare().
> >                getInfoSupp(asyncCallback);
>
> >            }
>
> >        };
> >        t.scheduleRepeating(MainEntryPoint.refreshLastUpdatePeriod);
> >    }
>
> > this code as is, make the memory usage increase and increase.
> > I'm working with gwt 1.5.3 and ie7
> > no problem on ff
>
> > have you got any idea? any known issue?
> > pls help, thx
> > have a nice day,
> > Michela
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to