Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #8159 > unrolled thread

Java Webstart network bandwidth

Back to article view | Back to comp.lang.java.programmer

Contents

  Java Webstart network bandwidth bcr666 <bcr666@gmail.com> - 2011-09-19 14:00 -0700
    Re: Java Webstart network bandwidth Roedy Green <see_website@mindprod.com.invalid> - 2011-09-19 17:03 -0700
    Re: Java Webstart network bandwidth Lew <lewbloch@gmail.com> - 2011-09-19 19:07 -0700
      Re: Java Webstart network bandwidth Roedy Green <see_website@mindprod.com.invalid> - 2011-09-20 15:07 -0700

#8159 — Java Webstart network bandwidth

I have a JWS application that accesses EJBs on a Borland Deploymnet
Platform. The application runs fine when run locally, but very slowly
when the client is remote (VPN). The remote connection is only using
about 256Kbps. Is there a way to tell it to use more?

[toc] | [next] | [standalone]

#8165

On Mon, 19 Sep 2011 14:00:15 -0700 (PDT), bcr666 <bcr666@gmail.com>
wrote, quoted or indirectly quoted someone who said :

>I have a JWS application that accesses EJBs on a Borland Deploymnet
>Platform. The application runs fine when run locally, but very slowly
>when the client is remote (VPN). The remote connection is only using
>about 256Kbps. Is there a way to tell it to use more?

I would look for something in the configuration of the VPN.
-- 
Roedy Green Canadian Mind Products
http://mindprod.com
It is a lot easier to combine things later that 
have been too finely categorised than to split 
things later whose are categories are too coarse.

[toc] | [prev] | [next] | [standalone]

#8169

bcr666 wrote:
> I have a JWS application that accesses EJBs on a Borland Deploymnet
> Platform. The application runs fine when run locally, but very slowly
> when the client is remote (VPN). The remote connection is only using
> about 256Kbps. Is there a way to tell it to use more?

AIUI, Java WebStart is nothing but a delivery mechanism for an application to reach the client machine.  So another name for a "Java WebStart application" is a "Java application".  Look to your application for bad network habits.

Many network-separated applications manage the "Great Divide" between nodes very badly.  Common mistakes include doing to little with each crossing, causing communication overhead to dominate bandwidth; initiating a send from both ends to each other, instead of having one end be requester-only (the client) and the other responder-only (the server); and using file I/O as intermediate steps.

There are network factors beyond the program's control, of course.  The server connection just might be over a very thin pipe.

There's not enough information in your post for us to diagnose what your bottleneck is.  Run some diagnostics, such as a bandwidth test (or at least a ping) between the nodes involved.  If your bandwidth is only 256 Kbps between the nodes, nothing is going to go much faster over that link.  (You can play games with compression to increase the perceived bandwidth, but that comes at a cost of effort and complexity.)

Give us more data to work with, and look into what your application is doing with its bandwidth.

-- 
Lew

[toc] | [prev] | [next] | [standalone]

#8175

On Mon, 19 Sep 2011 19:07:08 -0700 (PDT), Lew <lewbloch@gmail.com>
wrote, quoted or indirectly quoted someone who said :

>AIUI, Java WebStart is nothing but a delivery mechanism for an application =
>to reach the client machine.  So another name for a "Java WebStart applicat=
>ion" is a "Java application".  Look to your application for bad network hab=
>its.

not quite. Java Web Start itself has some caching habits ,where it
downloads the *.jnlp file and possibly some jars that you want to be
aware of.

The Java Web Start App itself is often absolutely identical to the
standalone version.  

Run the app standalone to prove to yourself the JWSness is irrelevant.

-- 
Roedy Green Canadian Mind Products
http://mindprod.com
It is a lot easier to combine things later that 
have been too finely categorised than to split 
things later whose are categories are too coarse.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web