axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20260] - SimpleAxisServer's bugs
Date Tue, 27 May 2003 11:56:42 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20260>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20260

SimpleAxisServer's bugs





------- Additional Comments From taherkordy@dpi2.dpi.net.ir  2003-05-27 11:56 -------
I've made some changes to SimpleAxisServer to fix the bugs,
the changes are:

1.
Added a LRU based session cleanup mechanism:
I've used a simple LRU cleanup mechanism for sessions,
I've utilized jakarta commons org.apache.commons.collections.LRUMap .
(needs to add commons-collections.jar to the Axis)

2.
Added a thread pooling mechanism:
org.apache.axis.transport.http.ThreadPool
org.apache.axis.transport.http.BlockingQueue

3.
modified getAxisServer() method's accessibility
from "protected" to "public"

4.
Commented the following line of code from stop() mehotd:
System.exit(0);
No need to kill the JVM(this help us to use SimpleAxisServer 
in a service based architecture without any problem)

5.
Added two new options to be used in starting
SimpleAxisServer from command line:
-t for maximum thread pool size(default value is 100)
-m for maximum session count(default value is 100)
example:
java org.apache.axis.transport.http.SimpleAxisServer -t 150 -m 1000 


--Alireza

Mime
View raw message