Simply deactivating-redeploying-activating is not the ideal solution. It
should be;
maintenace-mode(service_foo)-redeploy(service_foo)-normal-mode(service_foo)
In maintenance mode, a service will not accept new requests, but will
complete servicing existing requests. So, there is a difference
If we do it the way Deepal had worked on a while ago, the downtime is VERY
low. Basically, what we need to do is to mark the AxisService as old (or
inactive) and then that immediately stops new messages from being delivered
to it. Any already dispatched service is not at all affected - as the
Afkham Azeez wrote:
Simply deactivating-redeploying-activating is not the ideal solution.
It should be;
maintenace-mode(service_foo)-redeploy(service_foo)-normal-mode(service_foo)
In maintenance mode, a service will not accept new requests, but will
complete servicing existing requests. So,
Sanjiva Weerawarana wrote:
If we do it the way Deepal had worked on a while ago, the downtime is
VERY low. Basically, what we need to do is to mark the AxisService as
old (or inactive) and then that immediately stops new messages from
being delivered to it. Any already dispatched service is
On Sun, Aug 30, 2009 at 5:18 PM, Deepal jayasinghe deep...@gmail.comwrote:
Yes a few bugs, first if the service create any connection like DB or
file and put into ConFigCTX then those will not be removed when we do
the undeployment since service does not know that. Second, if they add
any
AbstractJSONDataSource#getJSONString() and buffering
Key: AXIS2-4480
URL: https://issues.apache.org/jira/browse/AXIS2-4480
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
JAX-WS Marshaling is not optimized if xsi:type is requested
---
Key: AXIS2-4481
URL: https://issues.apache.org/jira/browse/AXIS2-4481
Project: Axis 2.0 (Axis2)
Issue Type: Bug
