On 03/29/2012 04:45 PM, Sathish V wrote:
Hi All,

We are running our application in Virgo 3.0.1 which also has Spring DM
.We have a Web application bundle with context
path /xxx . Our main motto is not to have any outage at all.When I tried
upgrading the version of my Web bundle
and deploy in virgo,I get an error Saying a web application with context
already exists.

Caused by: org.eclipse.gemini.web.core.spi.ContextPathExistsException:
Context path '/xxx' already exists
     at
org.eclipse.gemini.web.tomcat.internal.TomcatServletContainer.checkContextPathIsFree(TomcatServletContainer.java:204)
     at
org.eclipse.gemini.web.tomcat.internal.TomcatServletContainer.startWebApplication(TomcatServletContainer.java:116)
     at
org.eclipse.gemini.web.internal.StandardWebApplication.start(StandardWebApplication.java:90)

How can I overcome this error and upgrade my bundle without loosing any
exising requests/activity in my older web bundle.

Regards



_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

Hi,

I think the use-case "high-availability" here has not yet been dealt with correctly at all (at least not in any implementation I saw). Currently, the update of a WAB should bring all its services down and then up again. If really install a second bundle (just having a higher version) at the pure framework level it will try to install it as usual.

The important thing is now how the WAB-level integration works. I don't know if Virgo really supports your use-case.

You are probably better off asking there first.

However, if I understand you correctly than what you want is this:

1.) WAB X 1.0 is installed and running with context /xxx
2.) update WAB X to 1.1
3.) active requests in the pipeline still use old version
4.) new requests use the new version

This is not demanded by the current WAB specification and is not documented anywhere I can think of. However, this is a very valid use case. Could be candidate for the next enterprise spec.

I would definitively vote for it! :)

Cheers,

        ancoron

_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to