Hi Sudharma, did both ODE instances operate on the same deploy directory? Or do they have their own? The basic assumption is that both share the same, synchronized data, thus I'd recommend to either use a symlink or configure the path by setting the "ode-axis2.deploy.dir" property in WEB-INF/conf/ode-axis2.properties.
Best, Tammo On Tue, May 5, 2015 at 5:18 PM, sudharma subasinghe <[email protected]> wrote: > Hi, > > I checked the behavior of ODE using two tomcat servers when deploying same > HelloWorld2 sample. Following are the things I could observe. > > > - > > deployed HelloWorld2-1 in Tomcat-1 server → Active state > - > > deployed HelloWorld2-2 in Tomcat-2 server → Active state > - > > deployed HelloWorld2-3 in Tomcat-1 server → HelloWorld2-1 Retired from > Active state > - > > undeployed HelloWorld2-3 → but still in the database in Active state > - > > deployed HelloWorld2-4 in Tomcat-2 server → HelloWorld2-2 Retired from > Active state > - > > All these details are shared by the two ode engines. > > 1) I can't undeploy a process through the browser. So I removed the whole > folder and .deployed file. But in the shared database that process is still > in the Active state. > > 2) Though HelloWorld2-1, is deployed in Tomcat-1 server and HelloWorld2-2, > HelloWorld2-4 are deployed in Tomcat-2 server all the deployed details are > shown in both browsers. > > Can you explain reasons for 1) and 2) ? > > Thank you > -- Tammo van Lessen - http://www.taval.de
