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 Dejan Milošević <de...@kombank.com> on 2006/12/25 15:00:15 UTC
jars locked forever
Once axis2 servlet is started in a servlet container it locks all the jars
that are in the WEB-INF/lib folder of the webapp that contains the axis2.
These locks are not released until the whole application server is stopped.
I have problem with this, since I use some common jars for many services,
and these jars need to be updated sometimes (so I put them in WEB-INF/lib),
but I don't want to restart the whole server (which is serving other apps as
well) just because of these jars!
Is this a bug? Any solutions?
Re: Re[2]: jars locked forever
Posted by Davanum Srinivas <da...@gmail.com>.
Please give some information on the app server, jdk, which jars/mars?
something???
-- dims
On 12/27/06, Dejan Milošević <de...@kombank.com> wrote:
> Logged... (AXIS2-1916)
>
> -----Original Message-----
> From: Thilina Gunarathne [mailto:csethil@gmail.com]
> Sent: Wednesday, December 27, 2006 2:43 AM
> To: axis-user@ws.apache.org
> Subject: Re: Re[2]: jars locked forever
>
> It appears to be a bug.. Please log a Jira...
> http://issues.apache.org/jira/browse/AXIS2
>
> Thanks,
> Thilina
>
> On 12/26/06, Dejan Milošević <de...@kombank.com> wrote:
> >
> >
> >
> >
> > With auto deploy its even worse. Tomcat at first undeploys the app, but
> > since it cannot delete the jars during undeployment, they apear to be
> > deployed when autodeploy mechanism rereads the webapps folder, so
> > application is listed as 'running' again after a few seconds! Application
> is
> > damaged (web.xml, all the JSPs, images, etc. are deleted) so that it
> cannot
> > be used but jars remain! Of course that jars are locked by classloader,
> but
> > I don't know how. When I would want to make such a webapp that makes
> tomcat
> > lock a jar even after undeployment I wouldn't know how.
> >
> >
> >
> > I cannot believe that this is not a bug and that I'm the only one that has
> a
> > problem with it.
> >
> >
> >
> > -----Original Message-----
> > From: Ivan Latysh [mailto:IvanLatysh@yahoo.ca]
> > Sent: Monday, December 25, 2006 6:33 PM
> > To: axis-user@ws.apache.org
> > Subject: Re[2]: jars locked forever
> >
> >
> >
> >
> > Hello Dejan,
> >
> >
> >
> > Monday, December 25, 2006, 11:50:29 AM, you wrote:
> >
> >
> >
> > > Thanx for the quick reply, but the bug that I pointed remains. I know
> how
> > to undeploy a regular webapp from Tomcat
> >
> > > (or WebSphere), but when I try the same method on the axis2 webapp all
> the
> > jars remain locked until I restart Tomcat
> >
> > > (the same with WebSphere). Application seems to be undeployed, but I
> > cannot delete files from the file system
> >
> > > (windows) until web server is stopped. And I tried it with the clean
> > sample war that ant builds from axis2-1.1 distribution (webapp\build.xml),
> > without any of my jars!
> >
> > To be precise, jars are locked by classloader not by Axis (or any other
> > module).
> >
> > I would suggest you to do a small test. Launch Tomcat without your
> > application, and make sure that auto deploy is on,
> >
> > now add your application and wait until tomcat load the classes, when you
> > application deployed check if it is working
> >
> > fine, now you can un-deploy your application and you should be able to
> > update any jars.
> >
> > If it will work for you it means that when you start Tomcat with your
> > application some of the classes has been picked up
> >
> > by the Tomcat classloader, so you need to figure out the way around.
> >
> > But you should remember that classloader resources are not recyclable, so
> > after a few dozen (or less) redeployment of
> >
> > your application you may simply run out of the memory. Considering this, I
> > will not advice you to update application
> >
> > without restarting container on production servers.
> >
> >
> >
> > --
> >
> > Best regards,
> >
> > Ivan mailto:IvanLatysh@yahoo.ca
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> >
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >
> > For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
> --
> Thilina Gunarathne
> WSO2, Inc.; http://www.wso2.com/
> Home page: http://webservices.apache.org/~thilina/
> Blog: http://thilinag.blogspot.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
RE: Re[2]: jars locked forever
Posted by Dejan Milošević <de...@kombank.com>.
Logged... (AXIS2-1916)
-----Original Message-----
From: Thilina Gunarathne [mailto:csethil@gmail.com]
Sent: Wednesday, December 27, 2006 2:43 AM
To: axis-user@ws.apache.org
Subject: Re: Re[2]: jars locked forever
It appears to be a bug.. Please log a Jira...
http://issues.apache.org/jira/browse/AXIS2
Thanks,
Thilina
On 12/26/06, Dejan Milošević <de...@kombank.com> wrote:
>
>
>
>
> With auto deploy its even worse. Tomcat at first undeploys the app, but
> since it cannot delete the jars during undeployment, they apear to be
> deployed when autodeploy mechanism rereads the webapps folder, so
> application is listed as 'running' again after a few seconds! Application
is
> damaged (web.xml, all the JSPs, images, etc. are deleted) so that it
cannot
> be used but jars remain! Of course that jars are locked by classloader,
but
> I don't know how. When I would want to make such a webapp that makes
tomcat
> lock a jar even after undeployment I wouldn't know how.
>
>
>
> I cannot believe that this is not a bug and that I'm the only one that has
a
> problem with it.
>
>
>
> -----Original Message-----
> From: Ivan Latysh [mailto:IvanLatysh@yahoo.ca]
> Sent: Monday, December 25, 2006 6:33 PM
> To: axis-user@ws.apache.org
> Subject: Re[2]: jars locked forever
>
>
>
>
> Hello Dejan,
>
>
>
> Monday, December 25, 2006, 11:50:29 AM, you wrote:
>
>
>
> > Thanx for the quick reply, but the bug that I pointed remains. I know
how
> to undeploy a regular webapp from Tomcat
>
> > (or WebSphere), but when I try the same method on the axis2 webapp all
the
> jars remain locked until I restart Tomcat
>
> > (the same with WebSphere). Application seems to be undeployed, but I
> cannot delete files from the file system
>
> > (windows) until web server is stopped. And I tried it with the clean
> sample war that ant builds from axis2-1.1 distribution (webapp\build.xml),
> without any of my jars!
>
> To be precise, jars are locked by classloader not by Axis (or any other
> module).
>
> I would suggest you to do a small test. Launch Tomcat without your
> application, and make sure that auto deploy is on,
>
> now add your application and wait until tomcat load the classes, when you
> application deployed check if it is working
>
> fine, now you can un-deploy your application and you should be able to
> update any jars.
>
> If it will work for you it means that when you start Tomcat with your
> application some of the classes has been picked up
>
> by the Tomcat classloader, so you need to figure out the way around.
>
> But you should remember that classloader resources are not recyclable, so
> after a few dozen (or less) redeployment of
>
> your application you may simply run out of the memory. Considering this, I
> will not advice you to update application
>
> without restarting container on production servers.
>
>
>
> --
>
> Best regards,
>
> Ivan mailto:IvanLatysh@yahoo.ca
>
>
>
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>
> For additional commands, e-mail: axis-user-help@ws.apache.org
--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Re[2]: jars locked forever
Posted by Thilina Gunarathne <cs...@gmail.com>.
It appears to be a bug.. Please log a Jira...
http://issues.apache.org/jira/browse/AXIS2
Thanks,
Thilina
On 12/26/06, Dejan Milošević <de...@kombank.com> wrote:
>
>
>
>
> With auto deploy its even worse. Tomcat at first undeploys the app, but
> since it cannot delete the jars during undeployment, they apear to be
> deployed when autodeploy mechanism rereads the webapps folder, so
> application is listed as 'running' again after a few seconds! Application is
> damaged (web.xml, all the JSPs, images, etc. are deleted) so that it cannot
> be used but jars remain! Of course that jars are locked by classloader, but
> I don't know how. When I would want to make such a webapp that makes tomcat
> lock a jar even after undeployment I wouldn't know how.
>
>
>
> I cannot believe that this is not a bug and that I'm the only one that has a
> problem with it.
>
>
>
> -----Original Message-----
> From: Ivan Latysh [mailto:IvanLatysh@yahoo.ca]
> Sent: Monday, December 25, 2006 6:33 PM
> To: axis-user@ws.apache.org
> Subject: Re[2]: jars locked forever
>
>
>
>
> Hello Dejan,
>
>
>
> Monday, December 25, 2006, 11:50:29 AM, you wrote:
>
>
>
> > Thanx for the quick reply, but the bug that I pointed remains. I know how
> to undeploy a regular webapp from Tomcat
>
> > (or WebSphere), but when I try the same method on the axis2 webapp all the
> jars remain locked until I restart Tomcat
>
> > (the same with WebSphere). Application seems to be undeployed, but I
> cannot delete files from the file system
>
> > (windows) until web server is stopped. And I tried it with the clean
> sample war that ant builds from axis2-1.1 distribution (webapp\build.xml),
> without any of my jars!
>
> To be precise, jars are locked by classloader not by Axis (or any other
> module).
>
> I would suggest you to do a small test. Launch Tomcat without your
> application, and make sure that auto deploy is on,
>
> now add your application and wait until tomcat load the classes, when you
> application deployed check if it is working
>
> fine, now you can un-deploy your application and you should be able to
> update any jars.
>
> If it will work for you it means that when you start Tomcat with your
> application some of the classes has been picked up
>
> by the Tomcat classloader, so you need to figure out the way around.
>
> But you should remember that classloader resources are not recyclable, so
> after a few dozen (or less) redeployment of
>
> your application you may simply run out of the memory. Considering this, I
> will not advice you to update application
>
> without restarting container on production servers.
>
>
>
> --
>
> Best regards,
>
> Ivan mailto:IvanLatysh@yahoo.ca
>
>
>
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>
> For additional commands, e-mail: axis-user-help@ws.apache.org
--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/
RE: Re[2]: jars locked forever
Posted by Dejan Milošević <de...@kombank.com>.
With auto deploy its even worse. Tomcat at first undeploys the app, but
since it cannot delete the jars during undeployment, they apear to be
deployed when autodeploy mechanism rereads the webapps folder, so
application is listed as 'running' again after a few seconds! Application is
damaged (web.xml, all the JSPs, images, etc. are deleted) so that it cannot
be used but jars remain! Of course that jars are locked by classloader, but
I don't know how. When I would want to make such a webapp that makes tomcat
lock a jar even after undeployment I wouldn't know how.
I cannot believe that this is not a bug and that I'm the only one that has a
problem with it.
-----Original Message-----
From: Ivan Latysh [mailto:IvanLatysh@yahoo.ca]
Sent: Monday, December 25, 2006 6:33 PM
To: axis-user@ws.apache.org
Subject: Re[2]: jars locked forever
Hello Dejan,
Monday, December 25, 2006, 11:50:29 AM, you wrote:
> Thanx for the quick reply, but the bug that I pointed remains. I know how
to undeploy a regular webapp from Tomcat
> (or WebSphere), but when I try the same method on the axis2 webapp all the
jars remain locked until I restart Tomcat
> (the same with WebSphere). Application seems to be undeployed, but I
cannot delete files from the file system
> (windows) until web server is stopped. And I tried it with the clean
sample war that ant builds from axis2-1.1 distribution (webapp\build.xml),
without any of my jars!
To be precise, jars are locked by classloader not by Axis (or any other
module).
I would suggest you to do a small test. Launch Tomcat without your
application, and make sure that auto deploy is on,
now add your application and wait until tomcat load the classes, when you
application deployed check if it is working
fine, now you can un-deploy your application and you should be able to
update any jars.
If it will work for you it means that when you start Tomcat with your
application some of the classes has been picked up
by the Tomcat classloader, so you need to figure out the way around.
But you should remember that classloader resources are not recyclable, so
after a few dozen (or less) redeployment of
your application you may simply run out of the memory. Considering this, I
will not advice you to update application
without restarting container on production servers.
--
Best regards,
Ivan mailto:IvanLatysh@yahoo.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re[2]: jars locked forever
Posted by Ivan Latysh <Iv...@yahoo.ca>.
Hello Dejan,
Monday, December 25, 2006, 11:50:29 AM, you wrote:
> Thanx for the quick reply, but the bug that I pointed remains. I know how to undeploy a regular webapp from Tomcat
> (or WebSphere), but when I try the same method on the axis2 webapp all the jars remain locked until I restart Tomcat
> (the same with WebSphere). Application seems to be undeployed, but I cannot delete files from the file system
> (windows) until web server is stopped. And I tried it with the clean sample war that ant builds from axis2-1.1 distribution (webapp\build.xml), without any of my jars!
To be precise, jars are locked by classloader not by Axis (or any other module).
I would suggest you to do a small test. Launch Tomcat without your application, and make sure that auto deploy is on,
now add your application and wait until tomcat load the classes, when you application deployed check if it is working
fine, now you can un-deploy your application and you should be able to update any jars.
If it will work for you it means that when you start Tomcat with your application some of the classes has been picked up
by the Tomcat classloader, so you need to figure out the way around.
But you should remember that classloader resources are not recyclable, so after a few dozen (or less) redeployment of
your application you may simply run out of the memory. Considering this, I will not advice you to update application
without restarting container on production servers.
--
Best regards,
Ivan mailto:IvanLatysh@yahoo.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: jars locked forever
Posted by Dejan Milošević <de...@kombank.com>.
Hello Martin,
Thanx for the quick reply, but the bug that I pointed remains. I know how to undeploy a regular webapp from Tomcat (or WebSphere), but when I try the same method on the axis2 webapp all the jars remain locked until I restart Tomcat (the same with WebSphere). Application seems to be undeployed, but I cannot delete files from the file system (windows) until web server is stopped. And I tried it with the clean sample war that ant builds from axis2-1.1 distribution (webapp\build.xml), without any of my jars!
Maybe you’re thinking of axis1? I used it some time ago and i think that there are no such problems in that version.
_____
From: Martin Gainty [mailto:mgainty@hotmail.com]
Sent: Monday, December 25, 2006 4:32 PM
To: axis-user@ws.apache.org
Subject: Re: jars locked forever
Hello Dejan
referencing the manager capabilities from tomcat located at
http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Undeploy%20an%20Existing%20Application
to undeploy AxisServlet (which is originally deployed as webapp labeled axis one must specify path=/axis) as in this example
http://localhost:8080/manager/undeploy?path=/axis
Martin --
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------------
Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message -----
From: Dejan <ma...@kombank.com> Milošević
To: axis-user@ws.apache.org
Sent: Monday, December 25, 2006 10:01 AM
Subject: RE: jars locked forever
Hello Martin,
I don’t know about other app servers, but for WebSphere there are obvious options ’update application’, ’uninstall’, ’install’, ’start’, ’stop’ which I use often for other web apps and would like to use for the app that’s holding my web services (axis2 app). So the answer is: jars should be reloaded when application is restarted (next level could be ’when application is reinstalled’, and even that doesn’t work (next_next level ’when app server is restarted’ works, but that’s almost as bad as ’when windows is restarted’ :-) )).
One thought: how can one JUST UNINSTALL this phantom axis servlet without stopping the entire servlet container?
_____
From: Martin Gainty [mailto:mgainty@hotmail.com]
Sent: Monday, December 25, 2006 3:27 PM
To: axis-user@ws.apache.org
Subject: Re: jars locked forever
Good Morning Dejan
If the jars were unlocked (and updateable) when would these (updated) jars for AxisServlet (or any servlet) be re-loaded or re-deployed?
Martin --
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------------
Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message -----
From: Dejan <ma...@kombank.com> Milošević
To: axis-user@ws.apache.org
Sent: Monday, December 25, 2006 9:00 AM
Subject: jars locked forever
Once axis2 servlet is started in a servlet container it locks all the jars that are in the WEB-INF/lib folder of the webapp that contains the axis2. These locks are not released until the whole application server is stopped. I have problem with this, since I use some common jars for many services, and these jars need to be updated sometimes (so I put them in WEB-INF/lib), but I don’t want to restart the whole server (which is serving other apps as well) just because of these jars!
Is this a bug? Any solutions?
Re: jars locked forever
Posted by Martin Gainty <mg...@hotmail.com>.
Hello Dejan
referencing the manager capabilities from tomcat located at
http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Undeploy%20an%20Existing%20Application
to undeploy AxisServlet (which is originally deployed as webapp labeled axis one must specify path=/axis) as in this example
http://localhost:8080/manager/undeploy?path=/axis
Martin --
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------------
Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message -----
From: Dejan Milošević
To: axis-user@ws.apache.org
Sent: Monday, December 25, 2006 10:01 AM
Subject: RE: jars locked forever
Hello Martin,
I don’t know about other app servers, but for WebSphere there are obvious options ’update application’, ’uninstall’, ’install’, ’start’, ’stop’ which I use often for other web apps and would like to use for the app that’s holding my web services (axis2 app). So the answer is: jars should be reloaded when application is restarted (next level could be ’when application is reinstalled’, and even that doesn’t work (next_next level ’when app server is restarted’ works, but that’s almost as bad as ’when windows is restarted’ J )).
One thought: how can one JUST UNINSTALL this phantom axis servlet without stopping the entire servlet container?
------------------------------------------------------------------------------
From: Martin Gainty [mailto:mgainty@hotmail.com]
Sent: Monday, December 25, 2006 3:27 PM
To: axis-user@ws.apache.org
Subject: Re: jars locked forever
Good Morning Dejan
If the jars were unlocked (and updateable) when would these (updated) jars for AxisServlet (or any servlet) be re-loaded or re-deployed?
Martin --
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------------
Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message -----
From: Dejan Milošević
To: axis-user@ws.apache.org
Sent: Monday, December 25, 2006 9:00 AM
Subject: jars locked forever
Once axis2 servlet is started in a servlet container it locks all the jars that are in the WEB-INF/lib folder of the webapp that contains the axis2. These locks are not released until the whole application server is stopped. I have problem with this, since I use some common jars for many services, and these jars need to be updated sometimes (so I put them in WEB-INF/lib), but I don’t want to restart the whole server (which is serving other apps as well) just because of these jars!
Is this a bug? Any solutions?
RE: jars locked forever
Posted by Dejan Milošević <de...@kombank.com>.
Hello Martin,
I don’t know about other app servers, but for WebSphere there are obvious options ’update application’, ’uninstall’, ’install’, ’start’, ’stop’ which I use often for other web apps and would like to use for the app that’s holding my web services (axis2 app). So the answer is: jars should be reloaded when application is restarted (next level could be ’when application is reinstalled’, and even that doesn’t work (next_next level ’when app server is restarted’ works, but that’s almost as bad as ’when windows is restarted’ :-) )).
One thought: how can one JUST UNINSTALL this phantom axis servlet without stopping the entire servlet container?
_____
From: Martin Gainty [mailto:mgainty@hotmail.com]
Sent: Monday, December 25, 2006 3:27 PM
To: axis-user@ws.apache.org
Subject: Re: jars locked forever
Good Morning Dejan
If the jars were unlocked (and updateable) when would these (updated) jars for AxisServlet (or any servlet) be re-loaded or re-deployed?
Martin --
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------------
Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message -----
From: Dejan <ma...@kombank.com> Milošević
To: axis-user@ws.apache.org
Sent: Monday, December 25, 2006 9:00 AM
Subject: jars locked forever
Once axis2 servlet is started in a servlet container it locks all the jars that are in the WEB-INF/lib folder of the webapp that contains the axis2. These locks are not released until the whole application server is stopped. I have problem with this, since I use some common jars for many services, and these jars need to be updated sometimes (so I put them in WEB-INF/lib), but I don’t want to restart the whole server (which is serving other apps as well) just because of these jars!
Is this a bug? Any solutions?
Re: jars locked forever
Posted by Martin Gainty <mg...@hotmail.com>.
Good Morning Dejan
If the jars were unlocked (and updateable) when would these (updated) jars for AxisServlet (or any servlet) be re-loaded or re-deployed?
Martin --
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------------
Le présent message électronique (y compris les pieces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractere privé ou confidentiel. Si vous n'etes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message -----
From: Dejan Milošević
To: axis-user@ws.apache.org
Sent: Monday, December 25, 2006 9:00 AM
Subject: jars locked forever
Once axis2 servlet is started in a servlet container it locks all the jars that are in the WEB-INF/lib folder of the webapp that contains the axis2. These locks are not released until the whole application server is stopped. I have problem with this, since I use some common jars for many services, and these jars need to be updated sometimes (so I put them in WEB-INF/lib), but I don't want to restart the whole server (which is serving other apps as well) just because of these jars!
Is this a bug? Any solutions?