• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

jnlpx.remove property?

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am researching a problem and found that one of the differences between my setup and the customer setup is that mine has jnlpx.remove=true whereas theirs has jnlpx.remove=false. I have been searching for any documentation on that property and not having much luck. I only found one hit and that mentions the possibility of it being related to caching but even that entry was speculating.

I have no idea how this property is set and passed because I know our application isn't doing it. The customer is using the IBM JRE/JVM and we have tested with both the Sun and the IBM versions (all at 1.4.2_x).

The customer runs 'ps aux | grep java' and sees over 100 processes listed whereas when I run the same thing, I only see the one currently active instance of my application.

Can anyone point me to some documentation on the jnlpx.remove property so that I see if this is the source of our difference/problem?

Thanks in advance,
Mike

 
rubbery bacon. rubbery tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic