You might want to checkout from oder registry and checkin to the new registry.
Samisa... On Tue, Mar 2, 2010 at 4:02 PM, Cappa Roberto < roberto.ca...@guest.telecomitalia.it> wrote: > Hi, > > I upgraded the ESB form 2.1.1 to 2.1.3 in test environment, but it doesn't > work. > > First, I copied all database files from the older version to the new, > assuming that the DB format is unchanged (I cannot found any documentation > about it) > Then, I configured the ESB to access the same extrenal registry of the > older version (GREG 3.0.1). > > After startup, all proxyes are disabled and, after enabling, they don't > preserve their status after restart. Also, at startup time, this exception > is thrown: > > 2010-03-02 09:58:47,062 [-] [Framework Event Dispatcher] ERROR > STSServiceComponent Error occured while updating carbon STS service > org.apache.axis2.AxisFault: The system is attempting to access an inactive > service: wso2carbon-sts > at > org.apache.axis2.engine.AxisConfiguration.getService(AxisConfiguration.java:929) > at > org.wso2.carbon.sts.STSDeploymentInterceptor.updateSTSService(STSDeploymentInterceptor.java:80) > at > org.wso2.carbon.sts.internal.STSServiceComponent.activate(STSServiceComponent.java:53) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230) > at > org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140) > at > org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330) > at > org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560) > at > org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182) > at > org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292) > at > org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226) > at > org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124) > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930) > at > org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220) > at > org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149) > at > org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757) > at > org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712) > at > org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129) > at > org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206) > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506) > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524) > at > org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:123) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230) > at > org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140) > at > org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330) > at > org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560) > at > org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182) > at > org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292) > at > org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226) > at > org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124) > > Are there any guidelines for a correct migration of the ESB? > > Thanks > > > ________________________________________ > Da: carbon-dev-boun...@wso2.org [carbon-dev-boun...@wso2.org] per conto di > Ughetti Marco [marco.ughe...@telecomitalia.it] > Inviato: lunedì 1 marzo 2010 16.38 > A: carbon-dev@wso2.org > Oggetto: [Carbon-dev] Upgrading wso2 esb from 2.1.1 to 2.1.3 with remore > registry configuration > > Hi all, > We are going to upgrade our wso2 esb deployment from 2.1.1 to 2.1.3 > Our esb uses a remote registry that stores metadata and synapse > configuration. > At the moment we are still using the default configuration for the users > database, as far as I know it is not possible to use the remote registry to > store esb users. > So which is the best way in order to update the esb and to safely migrate > the esb users? > > Thanks in advance > > Marco > > > ------------------------------------------------------------------ > Telecom Italia > Marco Ughetti > TI Lab > Vertical Platform & VAS > Vertical Platforms Innovation > Via G. Reiss Romoli, 274 - 10148 Torino > + 39 011 2285654 > + 39 331 6001596 > > Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle > persone indicate. La diffusione, copia o qualsiasi altra azione derivante > dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora > abbiate ricevuto questo documento per errore siete cortesemente pregati di > darne immediata comunicazione al mittente e di provvedere alla sua > distruzione, Grazie. > > This e-mail and any attachments is confidential and may contain privileged > information intended for the addressee(s) only. Dissemination, copying, > printing or use by anybody else is unauthorised. If you are not the intended > recipient, please delete this message and any attachments and advise the > sender by return e-mail, Thanks. > > [cid:00000000000000000000000000000001@TI.Disclaimer]Rispetta l'ambiente. > Non stampare questa mail se non è necessario. > > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://wso2.com/ - "lean . enterprise . middleware"
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
