axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Walker, Jeff" <Jeff.Wal...@fmr.com>
Subject RE: Hot Update and ServiceLifeCycle shutdown method
Date Mon, 22 Oct 2007 13:17:19 GMT
scope="application"
I think.
-jeff
 

-----Original Message-----
From: sgopal [mailto:srinivasan.gopalakrishnan@us.icap.com] 
Sent: Monday, October 22, 2007 8:20 AM
To: axis-user@ws.apache.org
Subject: RE: Hot Update and ServiceLifeCycle shutdown method


Hi,
What is your scope set to in the service.xml for this service?

Thanks
srinivasan


dreamryder wrote:
> 
> Ok, I lied.
> ServiceLifecycle.destroy() does get called for me, after each request
is
> satisfied. (I missed it amongst all of my debug output).
> -jeff
>  
> 
> -----Original Message-----
> From: Walker, Jeff 
> Sent: Friday, October 19, 2007 11:31 AM
> To: axis-user@ws.apache.org
> Subject: RE: Hot Update and ServiceLifeCycle shutdown method
> 
> I have a question for you.
> Are you trying to use javax.xml.rpc.server.ServiceLifecycle, and
> expecting init() and destroy() to be called?
> 
> I get init() called when a request comes in, I can then call various
web
> services methods, but destroy() is NEVER called. Having said that, how
> can it determine that destroy() must be called and no more calls will
be
> made? By the way, I am using WebSphere's JAX-RPC implementation for
this
> web service.
> 
> Even when I shutdown the web service (in WebSphere 6.1 that can be
done
> by unloaded the project from the server) and still destroy() is never
> called.
> -jeff
> 
>  
> 
> -----Original Message-----
> From: sgopal [mailto:srinivasan.gopalakrishnan@us.icap.com] 
> Sent: Friday, October 19, 2007 10:50 AM
> To: axis-user@ws.apache.org
> Subject: Hot Update and ServiceLifeCycle shutdown method
> 
> 
> Hi,
> I have a service running with a request scope and I have a
> servicelifecycle
> class for the service.
> In the startup method of the LifeCycle I initialized a connection to
the
> server using a singleton 
> and in the shutdown method I cleaned up the connection.
> 
> Everything worked fine until I tried the hot update feature.
> 
> The shutdown method was never called . So the cleanup never happened.
> 
> We have a constraint that there can be only one connection to the
server
> from the axis application.
> 
> Axis went and deployed the new AAR file.
> The old connection was never cleaned up and the  web service calls go
to
> the
> new AAR that was deployed
> which says there are no connections to the server.
> 
> How do I resolve this issue.
> 
> Thanks 
> Srinivasan
> 
> 
> 
> 
> -- 
> View this message in context:
>
http://www.nabble.com/Hot-Update-and-ServiceLifeCycle-shutdown-method-tf
> 4653738.html#a13296024
> 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
> 
> 
> 
> ---------------------------------------------------------------------
> 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/Hot-Update-and-ServiceLifeCycle-shutdown-method-tf
4653738.html#a13342148
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


Mime
View raw message