File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes Lookup time is very high in WS 5.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Lookup time is very high in WS 5.0" Watch "Lookup time is very high in WS 5.0" New topic
Author

Lookup time is very high in WS 5.0

Subhash Namboodiri
Ranch Hand

Joined: Jan 02, 2003
Posts: 30
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
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3879
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


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Subhash Namboodiri
Ranch Hand

Joined: Jan 02, 2003
Posts: 30
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
Ranch Hand

Joined: Aug 10, 2001
Posts: 3879
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
 
jQuery in Action, 2nd edition
 
subject: Lookup time is very high in WS 5.0
 
Similar Threads
IDE Support for Tiger
Implementing security in WAS 4.0.4
No. of connections are not increasing
getCallerPrincipal from JNDI call
Why should I take SCJP 6 while Java EE is still version 5