Try to globally engage the module (i.e. from axis2.xml).
Michele
On 6 Apr 2008, at 20:51, A Sunley wrote:
We're experiencing "java.net.SocketException: Too many open files"
exceptions
on the server. And I think it might be down to the module files in
the temp
folder.
When I list the open files for the tomcat process (lsof -a -p
28938) it
throws up many, many lines like the following:
java 28938 user 573r REG 8,2 37572 353018
/home/user/tomcat/apache-tomcat-webserver/temp/
axis226631addressing-1.2.mar
Is this abnormal behavior for Axis2? Any advice would be greatly
appreciated.
Regards,
Alan.
A Sunley wrote:
Greetings Axis users,
We are accessing a web service from within a jsp/servlet webapp
within a
Tomcat container, using Axis2-1.2. We also make use of the Rampart
security module.
I want to clarify how we should 'engage' module. At the moment we
do this
for every request to the webservice using:
client.engageModule(new QName("rampart"));
Do we have to do this for each and every request or can we delpoy the
module once for the web application?
I am noticing that for each request the following is printed to the
console: "Deploying module: rampart-1.2". In addition the Tomcat/temp
folder is chocker full of "axis264rampart-1.2.mar" files (each with a
different number). The temp file is now approaching one gigabyte
in size.
Is this normal behavior? I'm concerned that I might have not
configured
the Axis2 client correctly and may potentially cause performance
issues.
Is this that case?
Regards,
Alan.
--
View this message in context: http://www.nabble.com/Axis2-Client-
Engage-Module-tp16475749p16528660.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
