• 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

Lookup time is very high in WS 5.0

 
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
In WebSphere 5.0 I have noticed that the time required to lookup any resources or ejb's from a client is very slow as compared to any other AppServer.
It takes about more than 1 min in P-III 512 MB RAM m/c.
Thanks in advance,
Subhash
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
That's probably not a WAS problem -- lookup on my machine is virtually instantaneous. Now, my question is; are you using the launchClient.bat file to start your program? If not, then it's not REALLY a WebSphere client and you're in a heap of trouble -- slow lookup being just one of many...
Kyle
 
Subhash Namboodiri
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Kyle,
In the case of LaunchClient.bat it requires an ear as an input parameter. But our Application requirement is that we have a simple java client doing a lookup to the SessionBeans or other resources remotely.
Can such activities be done using LanuchClient.bat, where we have not client ears deployed and also no ear to be passed as parameter to LanuchClient.bat.
Also you have mentioned, not using LaunchClient.bat could lead to many problems. Is there any way we could do lookup without LaunchCleint.bat by doing some configuration?
Thanks in advance,
Subhash
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The ONLY way we support Java clients in WebSphere is to follow the J2EE specification -- e.g. build an EAR with a client JAR and use LaunchClient. That's it. Period. End of Story.
This isn't a "Requirement", it's a preference. You can distributed client EARs just as easily as you can other Java client types.
Kyle
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic