You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by A Sunley <al...@gmail.com> on 2008/04/04 00:59:02 UTC
Axis2 Client Engage Module
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-tp16475749p16475749.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 Client Engage Module
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 Client Engage Module
Posted by A Sunley <al...@gmail.com>.
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 Client Engage Module
Posted by A Sunley <al...@gmail.com>.
Thanks Dimuthu,
By engaging the module with each request, do you think this represents any
significant difference in performance?
Regards,
Alan.
Dimuthu-2 wrote:
>
> Hi,
>
> When you engage the module to client it has to be engaged each time you
> instantiate a new ServiceClient. Each time the module is engaged it will
> be extracted into the temp folder to do class loading much faster.
>
> You can avoid this by engaging the module to the
> ConfigurationContext[1]. Then it will be done only once.
>
> Thank you,
> Dimuthu
>
> [1]
> ConfigurationContext ctx =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem(path,
> path + "/conf/axis2.xml");
> ctx.getAxisConfiguration().engageModule("rampart");
>
> On Thu, 2008-04-03 at 15:59 -0700, 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.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Axis2-Client-Engage-Module-tp16475749p16490209.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 Client Engage Module
Posted by Dimuthu Leelarathne <mu...@apache.org>.
Hi,
When you engage the module to client it has to be engaged each time you
instantiate a new ServiceClient. Each time the module is engaged it will
be extracted into the temp folder to do class loading much faster.
You can avoid this by engaging the module to the
ConfigurationContext[1]. Then it will be done only once.
Thank you,
Dimuthu
[1]
ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(path, path + "/conf/axis2.xml");
ctx.getAxisConfiguration().engageModule("rampart");
On Thu, 2008-04-03 at 15:59 -0700, 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org