Eclipse Community Forums: Standard Widget Toolkit (SWT)

Home » Eclipse Projects » Standard Widget Toolkit (SWT) » SWT & JNLP

Tue, 31 August 2004 03:28

Eclipse User

Evening,
I'm having a problem that seems to be unique to SWT and Windows
platform (I have no linux so I can't test it there). I used the
following tutorial:
http://www-106.ibm.com/developerworks/opensource/library/os- jws/

It's for deploying SWT remotely using JNLP. I get the same behavior with
any SWT application that I deploy using JNLP. It leaves a rogue
javaw.exe behind. I have to go in to my process explorer and kill the
process manually every time. I've checked with Sun's jnlp examples on
their site and javaw.exe closes every time :/. I've checked the code of
their jnlp launched apps and I don't see anything special about closing
an app.

Has anybody else observed this behavior?

This should work for both Windows and Linux systems. It's the
implementation of the link above.

http://www.4xdamage.com/public/fileviewer/index.html

The Java Webstart Demos are at:

http://java.sun.com/products/javawebstart/demos.html

I'd appreciate any help I can get.

Sincerely,
Vic Hanson

Re: SWT & JNLP [message #442256 is a reply to message #442253]

Tue, 31 August 2004 04:45

Eclipse User

Hi Vic,
i successfully deployed many SWT applications using java webstart and
I've never seen javaw.exe hanging around.

But as an habit i put a System.exit(0); when i want my application to
exit, not trusting the simple exit from the main method. With a
System.exit() call you force the JVM to exit gracefully, but still force
all the live Threads to die, while a running Thread would keep the JVM
live also after the main method returns. Maybe this makes a difference?

Ciao,
Simone Gianni

Vic Hanson wrote:

> Evening,
> I'm having a problem that seems to be unique to SWT and Windows
> platform (I have no linux so I can't test it there). I used the
> following tutorial:
> http://www-106.ibm.com/developerworks/opensource/library/os- jws/
>
> It's for deploying SWT remotely using JNLP. I get the same behavior with
> any SWT application that I deploy using JNLP. It leaves a rogue
> javaw.exe behind. I have to go in to my process explorer and kill the
> process manually every time. I've checked with Sun's jnlp examples on
> their site and javaw.exe closes every time :/. I've checked the code of
> their jnlp launched apps and I don't see anything special about closing
> an app.
>
> Has anybody else observed this behavior?
>
> This should work for both Windows and Linux systems. It's the
> implementation of the link above.
>
> http://www.4xdamage.com/public/fileviewer/index.html
>
> The Java Webstart Demos are at:
>
> http://java.sun.com/products/javawebstart/demos.html
>
> I'd appreciate any help I can get.
>
> Sincerely,
> Vic Hanson

Re: SWT & JNLP [message #442266 is a reply to message #442256]

Tue, 31 August 2004 09:49

Eclipse User

I haven't noticed any javaw.exe left behind when everything works
correctly. When something goes wrong and an interface doesn't even show
up, I have noticed that an orphaned javaw.exe keeps running.

Simone Gianni wrote:

> Hi Vic,
> i successfully deployed many SWT applications using java webstart and
> I've never seen javaw.exe hanging around.

> But as an habit i put a System.exit(0); when i want my application to
> exit, not trusting the simple exit from the main method. With a
> System.exit() call you force the JVM to exit gracefully, but still force
> all the live Threads to die, while a running Thread would keep the JVM
> live also after the main method returns. Maybe this makes a difference?

> Ciao,
> Simone Gianni

> Vic Hanson wrote:

> > Evening,
> > I'm having a problem that seems to be unique to SWT and Windows
> > platform (I have no linux so I can't test it there). I used the
> > following tutorial:
> > http://www-106.ibm.com/developerworks/opensource/library/os- jws/
> >
> > It's for deploying SWT remotely using JNLP. I get the same behavior with
> > any SWT application that I deploy using JNLP. It leaves a rogue
> > javaw.exe behind. I have to go in to my process explorer and kill the
> > process manually every time. I've checked with Sun's jnlp examples on
> > their site and javaw.exe closes every time :/. I've checked the code of
> > their jnlp launched apps and I don't see anything special about closing
> > an app.
> >
> > Has anybody else observed this behavior?
> >
> > This should work for both Windows and Linux systems. It's the
> > implementation of the link above.
> >
> > http://www.4xdamage.com/public/fileviewer/index.html
> >
> > The Java Webstart Demos are at:
> >
> > http://java.sun.com/products/javawebstart/demos.html
> >
> > I'd appreciate any help I can get.
> >
> > Sincerely,
> > Vic Hanson

Re: SWT & JNLP [message #442293 is a reply to message #442256]

Tue, 31 August 2004 11:44

Eclipse User

That made all the difference in the world. Amazing that I would forget
something so simple. As for the Threads, I suspected that may have been
the problem as the current interface I designed uses a background thread
to run along side the UI and display.asynchExec. However, I tested this
with an older interface (that doesn't use Thread creation) I did and I
had the same problem. Placing the System.exit(0) at the end of each
after I dispose of the display cleanly shuts down my rogue javaw.exe.
Thanks very much, Simone.

Simone Gianni wrote:
> But as an habit i put a System.exit(0); when i want my application to
> exit, not trusting the simple exit from the main method. With a
> System.exit() call you force the JVM to exit gracefully, but still force
> all the live Threads to die, while a running Thread would keep the JVM
> live also after the main method returns. Maybe this makes a difference?

Previous Topic:	Right alignement in Text widget
Next Topic:	How to expedite Mouse handling ?

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 17 13:44:34 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter