Hi,
We have a multithreaded client for a particular Session Bean deployed on Pramati Server. In order to improve the performance, the server credentials are submitted and a single InitialContext object is obtained and within the run() method of the thread the Bean Lookup and method invocation are implemented with the above said InitialContext object.
Observations noted:
===================
1. The responsetime within single thread is at acceptable level but deteriorates as more threads are invoked.
2. Only few threads execute completely the Lookup+Method invocation while the others die with exceptions
Steps taken:
============
1. Bean Free pool size was increased to be closer to the number of threads
Results:
========
No improvements in results
Question:
=========
Do the app servers restrict the number of lookups per Context object? Or is there any other problem?
Configuration:
==============
App Server : Pramati 3.0
OS : Win2K
Clustered : No
No. of threads invoked : 100
Thanks in advance
Rgds
Muthu
We have a multithreaded client for a particular Session Bean deployed on Pramati Server. In order to improve the performance, the server credentials are submitted and a single InitialContext object is obtained and within the run() method of the thread the Bean Lookup and method invocation are implemented with the above said InitialContext object.
Observations noted:
===================
1. The responsetime within single thread is at acceptable level but deteriorates as more threads are invoked.
2. Only few threads execute completely the Lookup+Method invocation while the others die with exceptions
Steps taken:
============
1. Bean Free pool size was increased to be closer to the number of threads
Results:
========
No improvements in results
Question:
=========
Do the app servers restrict the number of lookups per Context object? Or is there any other problem?
Configuration:
==============
App Server : Pramati 3.0
OS : Win2K
Clustered : No
No. of threads invoked : 100
Thanks in advance
Rgds
Muthu