esb 2.1 not booting anymore

[Harm Verhagen-4]

Hi,


I'm playing around with wso2esb v2.1
Now all of a sudden the app doesn't boot anymore. 

As far as I can rememnber I have just edited stuff via the webui, nothing on the filesystem itself.

During startup it keeps giving:

[2009-08-26 23:06:57,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService
[2009-08-26 23:07:07,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:07:17,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:07:27,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:07:37,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:07:47,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:07:57,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso

Any idea whats going on here ? 
rebooting PC does NOT help.
restoring synapse.xml to the original (as in the wso2esb release) does NOT help.
This is kinda scary stuff, (that the hole esb can stop working.)

version
wso2esb v2.1.0  on windows XP home, java sun  1.6.0_12

attached is the complete bootlog.
Note: There are quite some
WARN - TransportMBeanSupport Error registering a MBean with objectname .. in the bootlog.. although I remenber them beeing there before, while the system just booted fine.


Regards,
Harm

[2009-08-26 23:18:53,312]  INFO - Main Preparing environment for the Server startup...
[2009-08-26 23:19:03,031]  INFO - CarbonCoreActivator Starting WSO2 Carbon...
[2009-08-26 23:19:03,046]  INFO - CarbonCoreActivator Operating System : Windows XP 5.1, x86
[2009-08-26 23:19:03,046]  INFO - CarbonCoreActivator Java Home        : C:\Program Files\Java\jdk1.6.0_12\jre
[2009-08-26 23:19:03,046]  INFO - CarbonCoreActivator Java Version     : 1.6.0_12
[2009-08-26 23:19:03,046]  INFO - CarbonCoreActivator Java VM          : Java HotSpot(TM) Client VM 11.2-b01,Sun Microsystems Inc.
[2009-08-26 23:19:03,046]  INFO - CarbonCoreActivator Carbon Home      : C:\DOCUME~1\user\MYDOCU~1\path\esb\wso2esb-2.1.0\bin\..
[2009-08-26 23:19:03,046]  INFO - CarbonCoreActivator Java Temp Dir    : C:\DOCUME~1\user\MYDOCU~1\path\esb\wso2esb-2.1.0\bin\..\tmp
[2009-08-26 23:19:03,046]  INFO - CarbonCoreActivator User             : user, en-US, Europe/Berlin
[2009-08-26 23:19:48,859]  INFO - RegistryCoreServiceComponent Registry Root    : /
[2009-08-26 23:19:48,859]  INFO - RegistryCoreServiceComponent Registry Mode    : READ-WRITE
[2009-08-26 23:19:48,859]  INFO - RegistryCoreServiceComponent Registry Type    : embedded
[2009-08-26 23:19:51,859]  INFO - CarbonServerManager Starting Carbon initialization...
[2009-08-26 23:19:52,234]  INFO - ClusterBuilder Clustering has been disabled
[2009-08-26 23:19:52,437]  INFO - DeploymentInterceptor Deploying Axis2 module rampart-2.00
[2009-08-26 23:19:52,468]  INFO - DeploymentInterceptor Deploying Axis2 module savan-SNAPSHOT
[2009-08-26 23:19:52,500]  INFO - DeploymentInterceptor Deploying Axis2 module wso2caching-2.00
[2009-08-26 23:19:52,578]  INFO - DeploymentInterceptor Deploying Axis2 module wso2throttle-2.00
[2009-08-26 23:19:52,609]  INFO - DeploymentInterceptor Deploying Axis2 module rahas-2.00
[2009-08-26 23:19:52,734]  INFO - DeploymentInterceptor Deploying Axis2 module sandesha2-2.00
[2009-08-26 23:19:52,890]  INFO - DeploymentInterceptor Deploying Axis2 module addressing-1.5
[2009-08-26 23:19:53,046]  INFO - HttpCoreNIOSSLSender Loading Identity Keystore from : resources/security/wso2carbon.jks
[2009-08-26 23:19:53,109]  INFO - HttpCoreNIOSSLSender Loading Trust Keystore from : resources/security/client-truststore.jks
[2009-08-26 23:19:53,468]  INFO - HttpCoreNIOSender HTTPS Sender starting
[2009-08-26 23:19:53,500]  INFO - HttpCoreNIOSender HTTP Sender starting
[2009-08-26 23:19:53,687]  INFO - DeploymentInterceptor Deploying Axis2 service echo
[2009-08-26 23:19:56,187]  WARN - DefaultSchemaGenerator We don't support method overloading. Ignoring [getLogs]
[2009-08-26 23:19:56,984]  INFO - DeploymentInterceptor Deploying Axis2 service RegistryEventingService
[2009-08-26 23:19:59,640]  INFO - DeploymentInterceptor Deploying Axis2 service wso2carbon-sts
[2009-08-26 23:20:01,125]  INFO - DeploymentInterceptor Deploying Axis2 service XKMS
[2009-08-26 23:20:01,406]  INFO - CarbonServerManager Initializing transport descriptions and their associated parameters
[2009-08-26 23:20:01,890]  INFO - CarbonServerManager Initialized the transport listener description for vfs
[2009-08-26 23:20:02,125]  INFO - CarbonServerManager Repository       : C:\DOCUME~1\user\MYDOCU~1\path\esb\wso2esb-2.1.0\bin\../repository/
[2009-08-26 23:20:02,265]  INFO - ServiceBusInitializer Starting ESB...
[2009-08-26 23:20:02,421]  INFO - ServiceBusInitializer Initializing Apache Synapse...
[2009-08-26 23:20:02,437]  INFO - SynapseControllerFactory Using Synapse home : C:\DOCUME~1\user\MYDOCU~1\path\esb\wso2esb-2.1.0\.
[2009-08-26 23:20:02,437]  INFO - SynapseControllerFactory Using synapse.xml location : C:\DOCUME~1\user\MYDOCU~1\path\esb\wso2esb-2.1.0\.\conf\synapse.xml
[2009-08-26 23:20:02,437]  INFO - SynapseControllerFactory Using server name : localhost
[2009-08-26 23:20:02,484]  INFO - SynapseControllerFactory The timeout handler will run every : 15s
[2009-08-26 23:20:02,562]  INFO - Axis2SynapseController Initializing Synapse at : Wed Aug 26 23:20:02 CEST 2009
[2009-08-26 23:20:02,562]  INFO - Axis2SynapseController Loading mediator extensions...
[2009-08-26 23:20:02,578]  INFO - CarbonSynapseController Building the SynapseConfiguration
[2009-08-26 23:20:03,187]  INFO - Axis2SynapseController Deploying the Synapse service...
[2009-08-26 23:20:03,203]  INFO - Axis2SynapseController Deploying Proxy services...
[2009-08-26 23:20:03,203]  INFO - ProxyService Building Axis service for Proxy service : SCOFileReader
[2009-08-26 23:20:03,203]  INFO - ProxyService Adding service SCOFileReader to the Axis2 configuration
[2009-08-26 23:20:03,218]  INFO - DeploymentInterceptor Deploying Axis2 service SCOFileReader
[2009-08-26 23:20:03,359]  INFO - ProxyService Successfully created the Axis2 service for Proxy service : SCOFileReader
[2009-08-26 23:20:03,359]  INFO - Axis2SynapseController Deployed Proxy service : SCOFileReader
[2009-08-26 23:20:03,359]  INFO - Axis2SynapseController Deploying EventSources...
[2009-08-26 23:20:03,781]  INFO - MailTransportSender MAILTO Sender started
[2009-08-26 23:20:03,812]  INFO - JMSSender JMS Sender started
[2009-08-26 23:20:03,812]  INFO - JMSSender JMS Transport Sender initialized...
[2009-08-26 23:20:04,078]  WARN - TransportMBeanSupport Error registering a MBean with objectname ' org.apache.synapse:Type=Transport,ConnectorName=mailto-sender ' for JMX management
javax.management.InstanceAlreadyExistsException: org.apache.synapse:Type=Transport,ConnectorName=mailto-sender
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
        at org.apache.axis2.transport.base.TransportMBeanSupport.register(TransportMBeanSupport.java:91)
        at org.apache.axis2.transport.base.AbstractTransportSender.init(AbstractTransportSender.java:84)
        at org.apache.axis2.transport.mail.MailTransportSender.init(MailTransportSender.java:80)
        at org.apache.axis2.context.ConfigurationContextFactory.initTransportSenders(ConfigurationContextFactory.java:300)
        at org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:231)
        at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:93)
        at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
        at org.apache.synapse.mediators.builtin.CalloutMediator.init(CalloutMediator.java:184)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.config.xml.SwitchCase.init(SwitchCase.java:52)
        at org.apache.synapse.mediators.filters.SwitchMediator.init(SwitchMediator.java:50)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.mediators.base.SequenceMediator.init(SequenceMediator.java:181)
        at org.apache.synapse.config.SynapseConfiguration.init(SynapseConfiguration.java:909)
        at org.apache.synapse.Axis2SynapseController.createSynapseEnvironment(Axis2SynapseController.java:345)
        at org.apache.synapse.ServerManager.start(ServerManager.java:183)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:237)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:115)
        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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
        at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:228)
        at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:100)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:916)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
[2009-08-26 23:20:04,078]  INFO - MailTransportSender MAILTO Sender started
[2009-08-26 23:20:04,078]  WARN - TransportMBeanSupport Error registering a MBean with objectname ' org.apache.synapse:Type=Transport,ConnectorName=jms-sender ' for JMX management
javax.management.InstanceAlreadyExistsException: org.apache.synapse:Type=Transport,ConnectorName=jms-sender
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
        at org.apache.axis2.transport.base.TransportMBeanSupport.register(TransportMBeanSupport.java:91)
        at org.apache.axis2.transport.base.AbstractTransportSender.init(AbstractTransportSender.java:84)
        at org.apache.axis2.transport.jms.JMSSender.init(JMSSender.java:61)
        at org.apache.axis2.context.ConfigurationContextFactory.initTransportSenders(ConfigurationContextFactory.java:300)
        at org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:231)
        at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:93)
        at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
        at org.apache.synapse.mediators.builtin.CalloutMediator.init(CalloutMediator.java:184)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.config.xml.SwitchCase.init(SwitchCase.java:52)
        at org.apache.synapse.mediators.filters.SwitchMediator.init(SwitchMediator.java:50)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.mediators.base.SequenceMediator.init(SequenceMediator.java:181)
        at org.apache.synapse.config.SynapseConfiguration.init(SynapseConfiguration.java:909)
        at org.apache.synapse.Axis2SynapseController.createSynapseEnvironment(Axis2SynapseController.java:345)
        at org.apache.synapse.ServerManager.start(ServerManager.java:183)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:237)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:115)
        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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
        at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:228)
        at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:100)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:916)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
[2009-08-26 23:20:04,093]  INFO - JMSSender JMS Sender started
[2009-08-26 23:20:04,093]  INFO - JMSSender JMS Transport Sender initialized...
[2009-08-26 23:20:04,093]  WARN - TransportMBeanSupport Error registering a MBean with objectname ' org.apache.synapse:Type=Transport,ConnectorName=mailto-listener ' for JMX management
javax.management.InstanceAlreadyExistsException: org.apache.synapse:Type=Transport,ConnectorName=mailto-listener
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
        at org.apache.axis2.transport.base.TransportMBeanSupport.register(TransportMBeanSupport.java:91)
        at org.apache.axis2.transport.base.AbstractTransportListener.init(AbstractTransportListener.java:125)
        at org.apache.axis2.transport.base.AbstractPollingTransportListener.init(AbstractPollingTransportListener.java:47)
        at org.apache.axis2.transport.mail.MailTransportListener.init(MailTransportListener.java:89)
        at org.apache.axis2.engine.ListenerManager.init(ListenerManager.java:75)
        at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:161)
        at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:139)
        at org.apache.synapse.mediators.builtin.CalloutMediator.init(CalloutMediator.java:188)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.config.xml.SwitchCase.init(SwitchCase.java:52)
        at org.apache.synapse.mediators.filters.SwitchMediator.init(SwitchMediator.java:50)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.mediators.base.SequenceMediator.init(SequenceMediator.java:181)
        at org.apache.synapse.config.SynapseConfiguration.init(SynapseConfiguration.java:909)
        at org.apache.synapse.Axis2SynapseController.createSynapseEnvironment(Axis2SynapseController.java:345)
        at org.apache.synapse.ServerManager.start(ServerManager.java:183)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:237)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:115)
        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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
        at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:228)
        at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:100)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:916)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
[2009-08-26 23:20:04,250]  WARN - TransportMBeanSupport Error registering a MBean with objectname ' org.apache.synapse:Type=Transport,ConnectorName=mailto-sender ' for JMX management
javax.management.InstanceAlreadyExistsException: org.apache.synapse:Type=Transport,ConnectorName=mailto-sender
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
        at org.apache.axis2.transport.base.TransportMBeanSupport.register(TransportMBeanSupport.java:91)
        at org.apache.axis2.transport.base.AbstractTransportSender.init(AbstractTransportSender.java:84)
        at org.apache.axis2.transport.mail.MailTransportSender.init(MailTransportSender.java:80)
        at org.apache.axis2.context.ConfigurationContextFactory.initTransportSenders(ConfigurationContextFactory.java:300)
        at org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:231)
        at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:93)
        at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
        at org.apache.synapse.mediators.builtin.CalloutMediator.init(CalloutMediator.java:184)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.config.xml.SwitchCase.init(SwitchCase.java:52)
        at org.apache.synapse.mediators.filters.SwitchMediator.init(SwitchMediator.java:50)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.mediators.base.SequenceMediator.init(SequenceMediator.java:181)
        at org.apache.synapse.config.SynapseConfiguration.init(SynapseConfiguration.java:909)
        at org.apache.synapse.Axis2SynapseController.createSynapseEnvironment(Axis2SynapseController.java:345)
        at org.apache.synapse.ServerManager.start(ServerManager.java:183)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:237)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:115)
        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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
        at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:228)
        at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:100)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:916)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
[2009-08-26 23:20:04,265]  INFO - MailTransportSender MAILTO Sender started
[2009-08-26 23:20:04,265]  WARN - TransportMBeanSupport Error registering a MBean with objectname ' org.apache.synapse:Type=Transport,ConnectorName=jms-sender ' for JMX management
javax.management.InstanceAlreadyExistsException: org.apache.synapse:Type=Transport,ConnectorName=jms-sender
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
        at org.apache.axis2.transport.base.TransportMBeanSupport.register(TransportMBeanSupport.java:91)
        at org.apache.axis2.transport.base.AbstractTransportSender.init(AbstractTransportSender.java:84)
        at org.apache.axis2.transport.jms.JMSSender.init(JMSSender.java:61)
        at org.apache.axis2.context.ConfigurationContextFactory.initTransportSenders(ConfigurationContextFactory.java:300)
        at org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:231)
        at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:93)
        at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
        at org.apache.synapse.mediators.builtin.CalloutMediator.init(CalloutMediator.java:184)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.config.xml.SwitchCase.init(SwitchCase.java:52)
        at org.apache.synapse.mediators.filters.SwitchMediator.init(SwitchMediator.java:50)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.mediators.base.SequenceMediator.init(SequenceMediator.java:181)
        at org.apache.synapse.config.SynapseConfiguration.init(SynapseConfiguration.java:909)
        at org.apache.synapse.Axis2SynapseController.createSynapseEnvironment(Axis2SynapseController.java:345)
        at org.apache.synapse.ServerManager.start(ServerManager.java:183)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:237)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:115)
        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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
        at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:228)
        at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:100)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:916)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
[2009-08-26 23:20:04,265]  INFO - JMSSender JMS Sender started
[2009-08-26 23:20:04,265]  INFO - JMSSender JMS Transport Sender initialized...
[2009-08-26 23:20:04,281]  WARN - TransportMBeanSupport Error registering a MBean with objectname ' org.apache.synapse:Type=Transport,ConnectorName=mailto-listener ' for JMX management
javax.management.InstanceAlreadyExistsException: org.apache.synapse:Type=Transport,ConnectorName=mailto-listener
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
        at org.apache.axis2.transport.base.TransportMBeanSupport.register(TransportMBeanSupport.java:91)
        at org.apache.axis2.transport.base.AbstractTransportListener.init(AbstractTransportListener.java:125)
        at org.apache.axis2.transport.base.AbstractPollingTransportListener.init(AbstractPollingTransportListener.java:47)
        at org.apache.axis2.transport.mail.MailTransportListener.init(MailTransportListener.java:89)
        at org.apache.axis2.engine.ListenerManager.init(ListenerManager.java:75)
        at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:161)
        at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:139)
        at org.apache.synapse.mediators.builtin.CalloutMediator.init(CalloutMediator.java:188)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.config.xml.SwitchCase.init(SwitchCase.java:52)
        at org.apache.synapse.mediators.filters.SwitchMediator.init(SwitchMediator.java:50)
        at org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:106)
        at org.apache.synapse.mediators.base.SequenceMediator.init(SequenceMediator.java:181)
        at org.apache.synapse.config.SynapseConfiguration.init(SynapseConfiguration.java:909)
        at org.apache.synapse.Axis2SynapseController.createSynapseEnvironment(Axis2SynapseController.java:345)
        at org.apache.synapse.ServerManager.start(ServerManager.java:183)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:237)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:115)
        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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
        at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:228)
        at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:100)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:916)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
[2009-08-26 23:20:04,281]  INFO - ServerManager Server ready for processing...
[2009-08-26 23:20:04,296] FATAL - ServiceBusInitializer Couldn't initialize the ESB...
java.lang.NullPointerException
        at org.wso2.carbon.mediation.registry.WSO2Registry.calculatePath(WSO2Registry.java:628)
        at org.wso2.carbon.mediation.registry.WSO2Registry.getResource(WSO2Registry.java:603)
        at org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:380)
        at org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:382)
        at org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:382)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.createDefaultRegistryStructure(ServiceBusInitializer.java:314)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:250)
        at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:115)
        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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
        at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:228)
        at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:100)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:916)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
[2009-08-26 23:20:07,078]  INFO - CarbonUIServiceComponent Mgt Console URL  : https://192.168.154.1:9443/carbon/
[2009-08-26 23:20:10,546]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:20:20,546]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:20:30,546]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService,

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

[Harm Verhagen-4]

OK, something fishy is going on here.

I debugged it a bit and found the following.

* restoring the directory  database/    fixes the problem

* then by reapplying my synapse.xml by pasting the contents in the webui and hitting save. I can recreate the problem

If I then stop and start the application it fails to start.
So somehting in the synapse.xml  seems to cause this problem. Either there is a bug in this synapse.xml that triggers this behavior, or there's something wrong with wso2esb that it fails on a particular synapse.xml construct.

I tried intensively to narrow down what is wrong but I cant find any errors.

I currently have a simplified  synapse.xml and xslt file to reproduce this problem. They are attached to this mail [1] and [2]

[1] simplified synapse.xml that shows this problem
[2] xslt file required by this synapse file.

How to reproduce.
1) put test.xslt  in repository\registry\transform\test.xslt
2) past the contents of [1] in the webui synapse.
3) hit save  (all ok)
4) stop esb
5) start esb
-> et voila ......


One other question:
- when I restore the directory  database/    why doesn't wso2esb read the contents of conf/synapse.xml..  Whenever I start the esb, it does not show any of the sequences of synapse.xml as if it doesn't read the file. When I then paste the contents in the webui,  the contents are taken into account (and hitting save, ready modifies _that_ file.
What is going on here ?  isn't the file conf/synapse.xml leading anymore ?


Regards,
Harm

On Wed, Aug 26, 2009 at 11:30 PM, Harm Verhagen <harm.verhagen@...> wrote:

Hi,


I'm playing around with wso2esb v2.1
Now all of a sudden the app doesn't boot anymore. 

As far as I can rememnber I have just edited stuff via the webui, nothing on the filesystem itself.

During startup it keeps giving:

[2009-08-26 23:06:57,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService
[2009-08-26 23:07:07,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:07:17,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:07:27,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:07:37,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:07:47,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso
2.carbon.mediation.initializer.services.SynapseEnvironmentService,
[2009-08-26 23:07:57,421]  WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso

Any idea whats going on here ? 
rebooting PC does NOT help.
restoring synapse.xml to the original (as in the wso2esb release) does NOT help.
This is kinda scary stuff, (that the hole esb can stop working.)

version
wso2esb v2.1.0  on windows XP home, java sun  1.6.0_12

attached is the complete bootlog.
Note: There are quite some
WARN - TransportMBeanSupport Error registering a MBean with objectname .. in the bootlog.. although I remenber them beeing there before, while the system just booted fine.


Regards,
Harm

<?xml version="1.0" encoding="UTF-8"?>
<syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse">
    <syn:registry provider="org.wso2.carbon.mediation.registry.WSO2Registry">
        <syn:parameter name="root">file:./repository/registry/</syn:parameter>
        <syn:parameter name="cachableDuration">1000</syn:parameter>
    </syn:registry>
    <syn:localEntry key="an_xslt" src="file:./repository/registry/transform/test.xslt"/>
    <syn:sequence name="log">
        <syn:log level="full"/>
    </syn:sequence>
    <syn:sequence name="main">
        <syn:in>
            <syn:log level="full"/>
            <syn:filter source="get-property('To')" regex="http://localhost:9000.*">
                <syn:send/>
            </syn:filter>
        </syn:in>
        <syn:out>
            <syn:send/>
        </syn:out>
    </syn:sequence>
    <syn:sequence name="fault">
        <syn:log/>
    </syn:sequence>
    <syn:sequence name="an_input" trace="disable">
        <syn:log separator=","/>
        <syn:property name="OUT_ONLY" value="true" scope="default"/>
        <syn:iterate xmlns:ns="http://org.apache.synapse/xsd" xmlns:ns2="http://org.apache.synapse/xsd" expression="//SCORelations/Relations/Relation">
            <syn:target to="" soapAction="" sequence="log"/>
        </syn:iterate>
        <syn:log/>
    </syn:sequence>
    <syn:sequence name="handle_entry" trace="enable">
        <syn:log level="full">
            <syn:property name="test" value="hallohallo"/>
        </syn:log>
        <syn:log>
            <syn:property xmlns:ns="http://org.apache.synapse/xsd" xmlns:ns2="http://org.apache.synapse/xsd" xmlns:nsi="http://webservice.service.platform.com/" name="result" expression="//nsi:findUserByPropertyResponse/return/resultCode"/>
        </syn:log>
        <syn:log level="full"/>
    </syn:sequence>
</syn:definitions>

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

[Ruwan Linton-3]

Hi Harm,

The issue is caused by a configuration error, I am not sure whether you
saw it or not there has to be an exception on the commandline console
when starting the ESB,

[2009-08-27 06:47:12,988] FATAL - ServiceBusInitializer Couldn't
initialize the ESB...
java.lang.NullPointerException
    at
org.wso2.carbon.mediation.registry.WSO2Registry.calculatePath(WSO2Registry.java:628)
    at
org.wso2.carbon.mediation.registry.WSO2Registry.getResource(WSO2Registry.java:603)
    at
org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:380)
    at
org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:382)

So it is because of the "root" parameter of the registry declaration.
Let me describe what causes this issue. The WSO2 Registry doesn't
support the file system, if you want the file system as the registry you
need to use the ESBRegistry instead of the WSO2Registry, but in the
configuration as the registry impl class you have specified the
WSO2Registry and the parameter root is invalid in that case.

Please remove the <syn:parameter
name="root">file:./repository/registry/</syn:parameter> from the
registry declaration from your configuration and use one of the
following ways to start the ESB, you will see the issue getting resolved.

I agree the exception is misleading, but clearly this is due to the
wrong configuration. I will get the error to be more descriptive in the
next release. On the other hand when you go into the web ui and paste a
full configuration it is equivalent to editing the synapse.xml file in
the file system :-), since it is a xml that you are pasting, the
validation that you get with the normal web ui like sequence editor
endpoint editor will not be there. Please note that this configuration
tab is for advanced users and has to be used carefully. If you screw the
synapse.xml you need to edit the file by hand.

But as you noted WSO2 ESB now stores the configuration in the registry
and at the first startup it loads the content from the synapse.xml
physical file and stores them in the registry for subsequent starts it
uses the configuration stored in the registry for the startup.

You could clean the stored configuration in the registry and force the
server to load the configuration from the file by passing the
-DuseSynapseXML flag when starting the server. So the startup command
will be;

./wso2server.bat -DuseSynapseXML

On the other hand if you clean the database then it will be picked from
the synapse.xml file for sure. Also note that if you need to cleanup the
full registry with all other stuff like user management and all, you may
use the --cleanRegistry option as well, which is not equivalent to
deleting database and starting up the server, but will cleanup the
registry space for the metadata for the server. So the command to clean
up the registry at startup is;

./wso2server.bat --cleanRegistry

One other thing is that when you delete the database and restarting the
server you better use the -Dsetup flag to let the server know that it
needs to setup the database, it will work without this flag as well, but
is recommended to use that; so the command will be;

./wso2server.sh -Dsetup

To answer your second question, as I explained earlier if you delete the
database, server MUST be reading the configuration from the
conf/synapse.xml for sure, if it is restarting without deleting the
database or without using any of the above options it will be loaded
from the registry. Unless you save the synapse configuration from the
configuration tab it will not be serailized to the file; So when you
paste the config and update the configuration the physical file will not
contain your updates unless you specifically save it, but is stored in
the registry.

Hope this explains it all...

Thanks,
Ruwan

Harm Verhagen wrote:

> OK, something fishy is going on here.
>
> I debugged it a bit and found the following.
>
> * restoring the directory  database/    fixes the problem
>
> * then by reapplying my synapse.xml by pasting the contents in the
> webui and hitting save. I can recreate the problem
>
> If I then stop and start the application it fails to start.
> So somehting in the synapse.xml  seems to cause this problem. Either
> there is a bug in this synapse.xml that triggers this behavior, or
> there's something wrong with wso2esb that it fails on a particular
> synapse.xml construct.
>
> I tried intensively to narrow down what is wrong but I cant find any
> errors.
>
> I currently have a simplified  synapse.xml and xslt file to reproduce
> this problem. They are attached to this mail [1] and [2]
>
> [1] simplified synapse.xml that shows this problem
> [2] xslt file required by this synapse file.
>
> How to reproduce.
> 1) put test.xslt  in repository\registry\transform\test.xslt
> 2) past the contents of [1] in the webui synapse.
> 3) hit save  (all ok)
> 4) stop esb
> 5) start esb
> -> et voila ......
>
>
> One other question:
> - when I restore the directory  database/    why doesn't wso2esb read
> the contents of conf/synapse.xml..  Whenever I start the esb, it does
> not show any of the sequences of synapse.xml as if it doesn't read the
> file. When I then paste the contents in the webui,  the contents are
> taken into account (and hitting save, ready modifies _that_ file.
> What is going on here ?  isn't the file conf/synapse.xml leading anymore ?
>
>
> Regards,
> Harm
>
>
> On Wed, Aug 26, 2009 at 11:30 PM, Harm Verhagen
> <harm.verhagen@... <mailto:harm.verhagen@...>> wrote:
>
>     Hi,
>
>
>     I'm playing around with wso2esb v2.1
>     Now all of a sudden the app doesn't boot anymore.
>
>     As far as I can rememnber I have just edited stuff via the webui,
>     nothing on the filesystem itself.
>
>     During startup it keeps giving:
>
>     [2009-08-26 23:06:57,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService
>     [2009-08-26 23:07:07,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:17,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:27,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:37,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:47,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:57,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>
>     Any idea whats going on here ?
>     rebooting PC does NOT help.
>     restoring synapse.xml to the original (as in the wso2esb release)
>     does NOT help.
>     This is kinda scary stuff, (that the hole esb can stop working.)
>
>     version
>     wso2esb v2.1.0  on windows XP home, java sun  1.6.0_12
>
>     attached is the complete bootlog.
>     Note: There are quite some
>     WARN - TransportMBeanSupport Error registering a MBean with
>     objectname .. in the bootlog.. although I remenber them beeing
>     there before, while the system just booted fine.
>
>
>     Regards,
>     Harm
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@...; cell: [phone]
blog: http://blog.ruwan.org



_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

[Harm Verhagen-4]

Thanks !

I thought it must be a configuration error somewhere. Just couldn't find what I did wrong. (as you only see things are really wrong, the next time you start the esb). Thanks for spotting.

ruwan wrote:
>Hope this explains it all...
Yes.

Regards,
Harm

On Thu, Aug 27, 2009 at 3:40 AM, Ruwan Linton <ruwan@...> wrote:

Hi Harm,

The issue is caused by a configuration error, I am not sure whether you
saw it or not there has to be an exception on the commandline console
when starting the ESB,

[2009-08-27 06:47:12,988] FATAL - ServiceBusInitializer Couldn't
initialize the ESB...
java.lang.NullPointerException
   at
org.wso2.carbon.mediation.registry.WSO2Registry.calculatePath(WSO2Registry.java:628)
   at
org.wso2.carbon.mediation.registry.WSO2Registry.getResource(WSO2Registry.java:603)
   at
org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:380)
   at
org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:382)

So it is because of the "root" parameter of the registry declaration.
Let me describe what causes this issue. The WSO2 Registry doesn't
support the file system, if you want the file system as the registry you
need to use the ESBRegistry instead of the WSO2Registry, but in the
configuration as the registry impl class you have specified the
WSO2Registry and the parameter root is invalid in that case.

Please remove the <syn:parameter
name="root">file:./repository/registry/</syn:parameter> from the
registry declaration from your configuration and use one of the
following ways to start the ESB, you will see the issue getting resolved.

I agree the exception is misleading, but clearly this is due to the
wrong configuration. I will get the error to be more descriptive in the
next release. On the other hand when you go into the web ui and paste a
full configuration it is equivalent to editing the synapse.xml file in
the file system :-), since it is a xml that you are pasting, the
validation that you get with the normal web ui like sequence editor
endpoint editor will not be there. Please note that this configuration
tab is for advanced users and has to be used carefully. If you screw the
synapse.xml you need to edit the file by hand.

But as you noted WSO2 ESB now stores the configuration in the registry
and at the first startup it loads the content from the synapse.xml
physical file and stores them in the registry for subsequent starts it
uses the configuration stored in the registry for the startup.

You could clean the stored configuration in the registry and force the
server to load the configuration from the file by passing the
-DuseSynapseXML flag when starting the server. So the startup command
will be;

./wso2server.bat -DuseSynapseXML

On the other hand if you clean the database then it will be picked from
the synapse.xml file for sure. Also note that if you need to cleanup the
full registry with all other stuff like user management and all, you may
use the --cleanRegistry option as well, which is not equivalent to
deleting database and starting up the server, but will cleanup the
registry space for the metadata for the server. So the command to clean
up the registry at startup is;

./wso2server.bat --cleanRegistry

One other thing is that when you delete the database and restarting the
server you better use the -Dsetup flag to let the server know that it
needs to setup the database, it will work without this flag as well, but
is recommended to use that; so the command will be;

./wso2server.sh -Dsetup

To answer your second question, as I explained earlier if you delete the
database, server MUST be reading the configuration from the
conf/synapse.xml for sure, if it is restarting without deleting the
database or without using any of the above options it will be loaded
from the registry. Unless you save the synapse configuration from the
configuration tab it will not be serailized to the file; So when you
paste the config and update the configuration the physical file will not
contain your updates unless you specifically save it, but is stored in
the registry.

Hope this explains it all...

Thanks,
Ruwan

Harm Verhagen wrote:
> OK, something fishy is going on here.
>
> I debugged it a bit and found the following.
>
> * restoring the directory  database/    fixes the problem
>
> * then by reapplying my synapse.xml by pasting the contents in the
> webui and hitting save. I can recreate the problem
>
> If I then stop and start the application it fails to start.
> So somehting in the synapse.xml  seems to cause this problem. Either
> there is a bug in this synapse.xml that triggers this behavior, or
> there's something wrong with wso2esb that it fails on a particular
> synapse.xml construct.
>
> I tried intensively to narrow down what is wrong but I cant find any
> errors.
>
> I currently have a simplified  synapse.xml and xslt file to reproduce
> this problem. They are attached to this mail [1] and [2]
>
> [1] simplified synapse.xml that shows this problem
> [2] xslt file required by this synapse file.
>
> How to reproduce.
> 1) put test.xslt  in repository\registry\transform\test.xslt
> 2) past the contents of [1] in the webui synapse.
> 3) hit save  (all ok)
> 4) stop esb
> 5) start esb
> -> et voila ......
>
>
> One other question:
> - when I restore the directory  database/    why doesn't wso2esb read
> the contents of conf/synapse.xml..  Whenever I start the esb, it does
> not show any of the sequences of synapse.xml as if it doesn't read the
> file. When I then paste the contents in the webui,  the contents are
> taken into account (and hitting save, ready modifies _that_ file.
> What is going on here ?  isn't the file conf/synapse.xml leading anymore ?
>
>
> Regards,
> Harm
>
>
> On Wed, Aug 26, 2009 at 11:30 PM, Harm Verhagen

> <harm.verhagen@... <mailto:harm.verhagen@...>> wrote:
>
>     Hi,
>
>
>     I'm playing around with wso2esb v2.1
>     Now all of a sudden the app doesn't boot anymore.
>
>     As far as I can rememnber I have just edited stuff via the webui,
>     nothing on the filesystem itself.
>
>     During startup it keeps giving:
>
>     [2009-08-26 23:06:57,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService
>     [2009-08-26 23:07:07,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:17,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:27,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:37,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:47,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:57,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>
>     Any idea whats going on here ?
>     rebooting PC does NOT help.
>     restoring synapse.xml to the original (as in the wso2esb release)
>     does NOT help.
>     This is kinda scary stuff, (that the hole esb can stop working.)
>
>     version
>     wso2esb v2.1.0  on windows XP home, java sun  1.6.0_12
>
>     attached is the complete bootlog.
>     Note: There are quite some
>     WARN - TransportMBeanSupport Error registering a MBean with
>     objectname .. in the bootlog.. although I remenber them beeing
>     there before, while the system just booted fine.
>
>
>     Regards,
>     Harm
>
>

> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user


--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@...; cell: [phone]
blog: http://blog.ruwan.org



_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

[Harm Verhagen-4]

Ruwan wrote:
>The issue is caused by a configuration error,
Indeed the configuration was wrong.
Trying to fix it although showed that its not all that simple.

I can't seem to use the ESBRegistry at all.
Not in combination with WSO2Registry and not instead of WSO2Registry.

When using ESBRegistry instead of WSO2Registry

  <syn:registry provider="org.wso2.carbon.mediation.registry.ESBRegistry">
        <syn:parameter name="root">file:repository/registry</syn:parameter>
        <syn:parameter name="cachableDuration">1000</syn:parameter>
    </syn:registry>

where file:repository/registry/transform  contains some custom xslt files. (rest empty)

I get errors like:
[2009-08-27 11:51:45,312] ERROR - ESBRegistry Parent folder: esb-resources does not exists.
[2009-08-27 11:51:45,312] ERROR - ESBRegistry Error when adding a new resource

I'm not referencing esb-resources/endpoints from my synapse.xml, So I guess this is something wso2esb internal.


When I use the ESBRegistry in combination with the WSO@Registry:
    <syn:registry provider="org.wso2.carbon.mediation.registry.WSO2Registry">
        <syn:parameter name="cachableDuration">1000</syn:parameter>
    </syn:registry>
   <syn:registry provider="org.wso2.carbon.mediation.registry.ESBRegistry">
        <syn:parameter name="root">file:repository/registry</syn:parameter>
        <syn:parameter name="cachableDuration">1000</syn:parameter>
    </syn:registry>
I get errors like:
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
[2009-08-27 11:36:46,359] FATAL - ServiceBusInitializer Couldn't initialize the ESB...
org.apache.synapse.SynapseException: Could not initialize Synapse : Only one remote registry can be defined within a con
figuration

(all using ./wso2server.bat -DuseSynapseXML)

What I was looking for is a way to refer to xslt files, that you can just edit on disk, and that get automatically reloaded by the esb.  I thought I could use WSO2Registry for this.
How should I use WSO2Registry ?   I think I miss some understanding how this is supposed to be used.

Harm

On Thu, Aug 27, 2009 at 3:40 AM, Ruwan Linton <ruwan@...> wrote:

Hi Harm,

The issue is caused by a configuration error, I am not sure whether you
saw it or not there has to be an exception on the commandline console
when starting the ESB,

[2009-08-27 06:47:12,988] FATAL - ServiceBusInitializer Couldn't
initialize the ESB...
java.lang.NullPointerException
   at
org.wso2.carbon.mediation.registry.WSO2Registry.calculatePath(WSO2Registry.java:628)
   at
org.wso2.carbon.mediation.registry.WSO2Registry.getResource(WSO2Registry.java:603)
   at
org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:380)
   at
org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:382)

So it is because of the "root" parameter of the registry declaration.
Let me describe what causes this issue. The WSO2 Registry doesn't
support the file system, if you want the file system as the registry you
need to use the ESBRegistry instead of the WSO2Registry, but in the
configuration as the registry impl class you have specified the
WSO2Registry and the parameter root is invalid in that case.

Please remove the <syn:parameter
name="root">file:./repository/registry/</syn:parameter> from the
registry declaration from your configuration and use one of the
following ways to start the ESB, you will see the issue getting resolved.

I agree the exception is misleading, but clearly this is due to the
wrong configuration. I will get the error to be more descriptive in the
next release. On the other hand when you go into the web ui and paste a
full configuration it is equivalent to editing the synapse.xml file in
the file system :-), since it is a xml that you are pasting, the
validation that you get with the normal web ui like sequence editor
endpoint editor will not be there. Please note that this configuration
tab is for advanced users and has to be used carefully. If you screw the
synapse.xml you need to edit the file by hand.

But as you noted WSO2 ESB now stores the configuration in the registry
and at the first startup it loads the content from the synapse.xml
physical file and stores them in the registry for subsequent starts it
uses the configuration stored in the registry for the startup.

You could clean the stored configuration in the registry and force the
server to load the configuration from the file by passing the
-DuseSynapseXML flag when starting the server. So the startup command
will be;

./wso2server.bat -DuseSynapseXML

On the other hand if you clean the database then it will be picked from
the synapse.xml file for sure. Also note that if you need to cleanup the
full registry with all other stuff like user management and all, you may
use the --cleanRegistry option as well, which is not equivalent to
deleting database and starting up the server, but will cleanup the
registry space for the metadata for the server. So the command to clean
up the registry at startup is;

./wso2server.bat --cleanRegistry

One other thing is that when you delete the database and restarting the
server you better use the -Dsetup flag to let the server know that it
needs to setup the database, it will work without this flag as well, but
is recommended to use that; so the command will be;

./wso2server.sh -Dsetup

To answer your second question, as I explained earlier if you delete the
database, server MUST be reading the configuration from the
conf/synapse.xml for sure, if it is restarting without deleting the
database or without using any of the above options it will be loaded
from the registry. Unless you save the synapse configuration from the
configuration tab it will not be serailized to the file; So when you
paste the config and update the configuration the physical file will not
contain your updates unless you specifically save it, but is stored in
the registry.

Hope this explains it all...

Thanks,
Ruwan

Harm Verhagen wrote:
> OK, something fishy is going on here.
>
> I debugged it a bit and found the following.
>
> * restoring the directory  database/    fixes the problem
>
> * then by reapplying my synapse.xml by pasting the contents in the
> webui and hitting save. I can recreate the problem
>
> If I then stop and start the application it fails to start.
> So somehting in the synapse.xml  seems to cause this problem. Either
> there is a bug in this synapse.xml that triggers this behavior, or
> there's something wrong with wso2esb that it fails on a particular
> synapse.xml construct.
>
> I tried intensively to narrow down what is wrong but I cant find any
> errors.
>
> I currently have a simplified  synapse.xml and xslt file to reproduce
> this problem. They are attached to this mail [1] and [2]
>
> [1] simplified synapse.xml that shows this problem
> [2] xslt file required by this synapse file.
>
> How to reproduce.
> 1) put test.xslt  in repository\registry\transform\test.xslt
> 2) past the contents of [1] in the webui synapse.
> 3) hit save  (all ok)
> 4) stop esb
> 5) start esb
> -> et voila ......
>
>
> One other question:
> - when I restore the directory  database/    why doesn't wso2esb read
> the contents of conf/synapse.xml..  Whenever I start the esb, it does
> not show any of the sequences of synapse.xml as if it doesn't read the
> file. When I then paste the contents in the webui,  the contents are
> taken into account (and hitting save, ready modifies _that_ file.
> What is going on here ?  isn't the file conf/synapse.xml leading anymore ?
>
>
> Regards,
> Harm
>
>
> On Wed, Aug 26, 2009 at 11:30 PM, Harm Verhagen

> <harm.verhagen@... <mailto:harm.verhagen@...>> wrote:
>
>     Hi,
>
>
>     I'm playing around with wso2esb v2.1
>     Now all of a sudden the app doesn't boot anymore.
>
>     As far as I can rememnber I have just edited stuff via the webui,
>     nothing on the filesystem itself.
>
>     During startup it keeps giving:
>
>     [2009-08-26 23:06:57,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService
>     [2009-08-26 23:07:07,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:17,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:27,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:37,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:47,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     [2009-08-26 23:07:57,421]  WARN - StartupFinalizerServiceComponent
>     Waiting for required OSGi services: org.wso
>
>     Any idea whats going on here ?
>     rebooting PC does NOT help.
>     restoring synapse.xml to the original (as in the wso2esb release)
>     does NOT help.
>     This is kinda scary stuff, (that the hole esb can stop working.)
>
>     version
>     wso2esb v2.1.0  on windows XP home, java sun  1.6.0_12
>
>     attached is the complete bootlog.
>     Note: There are quite some
>     WARN - TransportMBeanSupport Error registering a MBean with
>     objectname .. in the bootlog.. although I remenber them beeing
>     there before, while the system just booted fine.
>
>
>     Regards,
>     Harm
>
>

> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user


--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@...; cell: [phone]
blog: http://blog.ruwan.org



_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

[Ruwan Linton-3]

The exact same configuration that you have earlier attached will do it.
But if you want the XSLT to be dynamically loaded then you need to use
the WSO2Registry, in which case you are keeping the file in the Registry
on in the file system.

It seems file system based registry is having an issue, as per your
below experience, I will have a look at that.

Thanks,
Ruwan

Harm Verhagen wrote:

> Ruwan wrote:
> >The issue is caused by a configuration error,
> Indeed the configuration was wrong.
> Trying to fix it although showed that its not all that simple.
>
> I can't seem to use the ESBRegistry at all.
> Not in combination with WSO2Registry and not instead of WSO2Registry.
>
> When using ESBRegistry instead of WSO2Registry
>
>   <syn:registry provider="org.wso2.carbon.mediation.registry.ESBRegistry">
>         <syn:parameter
> name="root">file:repository/registry</syn:parameter>
>         <syn:parameter name="cachableDuration">1000</syn:parameter>
>     </syn:registry>
>
> where file:repository/registry/transform  contains some custom xslt
> files. (rest empty)
>
> I get errors like:
> [2009-08-27 11:51:45,312] ERROR - ESBRegistry Parent folder:
> esb-resources does not exists.
> [2009-08-27 11:51:45,312] ERROR - ESBRegistry Error when adding a new
> resource
>
> I'm not referencing esb-resources/endpoints from my synapse.xml, So I
> guess this is something wso2esb internal.
>
>
> When I use the ESBRegistry in combination with the WSO@Registry:
>     <syn:registry
> provider="org.wso2.carbon.mediation.registry.WSO2Registry">
>         <syn:parameter name="cachableDuration">1000</syn:parameter>
>     </syn:registry>
>    <syn:registry
> provider="org.wso2.carbon.mediation.registry.ESBRegistry">
>         <syn:parameter
> name="root">file:repository/registry</syn:parameter>
>         <syn:parameter name="cachableDuration">1000</syn:parameter>
>     </syn:registry>
> I get errors like:
>         at
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
> [2009-08-27 11:36:46,359] FATAL - ServiceBusInitializer Couldn't
> initialize the ESB...
> org.apache.synapse.SynapseException: Could not initialize Synapse :
> Only one remote registry can be defined within a con
> figuration
>
> (all using ./wso2server.bat -DuseSynapseXML)
>
> What I was looking for is a way to refer to xslt files, that you can
> just edit on disk, and that get automatically reloaded by the esb.  I
> thought I could use WSO2Registry for this.
> How should I use WSO2Registry ?   I think I miss some understanding
> how this is supposed to be used.
>
> Harm
>
>
>
> On Thu, Aug 27, 2009 at 3:40 AM, Ruwan Linton <ruwan@...
> <mailto:ruwan@...>> wrote:
>
>     Hi Harm,
>
>     The issue is caused by a configuration error, I am not sure
>     whether you
>     saw it or not there has to be an exception on the commandline console
>     when starting the ESB,
>
>     [2009-08-27 06:47:12,988] FATAL - ServiceBusInitializer Couldn't
>     initialize the ESB...
>     java.lang.NullPointerException
>        at
>     org.wso2.carbon.mediation.registry.WSO2Registry.calculatePath(WSO2Registry.java:628)
>        at
>     org.wso2.carbon.mediation.registry.WSO2Registry.getResource(WSO2Registry.java:603)
>        at
>     org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:380)
>        at
>     org.wso2.carbon.mediation.registry.WSO2Registry.newResource(WSO2Registry.java:382)
>
>     So it is because of the "root" parameter of the registry declaration.
>     Let me describe what causes this issue. The WSO2 Registry doesn't
>     support the file system, if you want the file system as the
>     registry you
>     need to use the ESBRegistry instead of the WSO2Registry, but in the
>     configuration as the registry impl class you have specified the
>     WSO2Registry and the parameter root is invalid in that case.
>
>     Please remove the <syn:parameter
>     name="root">file:./repository/registry/</syn:parameter> from the
>     registry declaration from your configuration and use one of the
>     following ways to start the ESB, you will see the issue getting
>     resolved.
>
>     I agree the exception is misleading, but clearly this is due to the
>     wrong configuration. I will get the error to be more descriptive
>     in the
>     next release. On the other hand when you go into the web ui and
>     paste a
>     full configuration it is equivalent to editing the synapse.xml file in
>     the file system :-), since it is a xml that you are pasting, the
>     validation that you get with the normal web ui like sequence editor
>     endpoint editor will not be there. Please note that this configuration
>     tab is for advanced users and has to be used carefully. If you
>     screw the
>     synapse.xml you need to edit the file by hand.
>
>     But as you noted WSO2 ESB now stores the configuration in the registry
>     and at the first startup it loads the content from the synapse.xml
>     physical file and stores them in the registry for subsequent starts it
>     uses the configuration stored in the registry for the startup.
>
>     You could clean the stored configuration in the registry and force the
>     server to load the configuration from the file by passing the
>     -DuseSynapseXML flag when starting the server. So the startup command
>     will be;
>
>     ./wso2server.bat -DuseSynapseXML
>
>     On the other hand if you clean the database then it will be picked
>     from
>     the synapse.xml file for sure. Also note that if you need to
>     cleanup the
>     full registry with all other stuff like user management and all,
>     you may
>     use the --cleanRegistry option as well, which is not equivalent to
>     deleting database and starting up the server, but will cleanup the
>     registry space for the metadata for the server. So the command to
>     clean
>     up the registry at startup is;
>
>     ./wso2server.bat --cleanRegistry
>
>     One other thing is that when you delete the database and
>     restarting the
>     server you better use the -Dsetup flag to let the server know that it
>     needs to setup the database, it will work without this flag as
>     well, but
>     is recommended to use that; so the command will be;
>
>     ./wso2server.sh -Dsetup
>
>     To answer your second question, as I explained earlier if you
>     delete the
>     database, server MUST be reading the configuration from the
>     conf/synapse.xml for sure, if it is restarting without deleting the
>     database or without using any of the above options it will be loaded
>     from the registry. Unless you save the synapse configuration from the
>     configuration tab it will not be serailized to the file; So when you
>     paste the config and update the configuration the physical file
>     will not
>     contain your updates unless you specifically save it, but is stored in
>     the registry.
>
>     Hope this explains it all...
>
>     Thanks,
>     Ruwan
>
>     Harm Verhagen wrote:
>     > OK, something fishy is going on here.
>     >
>     > I debugged it a bit and found the following.
>     >
>     > * restoring the directory  database/    fixes the problem
>     >
>     > * then by reapplying my synapse.xml by pasting the contents in the
>     > webui and hitting save. I can recreate the problem
>     >
>     > If I then stop and start the application it fails to start.
>     > So somehting in the synapse.xml  seems to cause this problem. Either
>     > there is a bug in this synapse.xml that triggers this behavior, or
>     > there's something wrong with wso2esb that it fails on a particular
>     > synapse.xml construct.
>     >
>     > I tried intensively to narrow down what is wrong but I cant find any
>     > errors.
>     >
>     > I currently have a simplified  synapse.xml and xslt file to
>     reproduce
>     > this problem. They are attached to this mail [1] and [2]
>     >
>     > [1] simplified synapse.xml that shows this problem
>     > [2] xslt file required by this synapse file.
>     >
>     > How to reproduce.
>     > 1) put test.xslt  in repository\registry\transform\test.xslt
>     > 2) past the contents of [1] in the webui synapse.
>     > 3) hit save  (all ok)
>     > 4) stop esb
>     > 5) start esb
>     > -> et voila ......
>     >
>     >
>     > One other question:
>     > - when I restore the directory  database/    why doesn't wso2esb
>     read
>     > the contents of conf/synapse.xml..  Whenever I start the esb, it
>     does
>     > not show any of the sequences of synapse.xml as if it doesn't
>     read the
>     > file. When I then paste the contents in the webui,  the contents are
>     > taken into account (and hitting save, ready modifies _that_ file.
>     > What is going on here ?  isn't the file conf/synapse.xml leading
>     anymore ?
>     >
>     >
>     > Regards,
>     > Harm
>     >
>     >
>     > On Wed, Aug 26, 2009 at 11:30 PM, Harm Verhagen
>     > <harm.verhagen@... <mailto:harm.verhagen@...>
>     <mailto:harm.verhagen@... <mailto:harm.verhagen@...>>>
>     wrote:
>     >
>     >     Hi,
>     >
>     >
>     >     I'm playing around with wso2esb v2.1
>     >     Now all of a sudden the app doesn't boot anymore.
>     >
>     >     As far as I can rememnber I have just edited stuff via the
>     webui,
>     >     nothing on the filesystem itself.
>     >
>     >     During startup it keeps giving:
>     >
>     >     [2009-08-26 23:06:57,421]  WARN -
>     StartupFinalizerServiceComponent
>     >     Waiting for required OSGi services: org.wso
>     >    
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService
>     >     [2009-08-26 23:07:07,421]  WARN -
>     StartupFinalizerServiceComponent
>     >     Waiting for required OSGi services: org.wso
>     >    
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     >     [2009-08-26 23:07:17,421]  WARN -
>     StartupFinalizerServiceComponent
>     >     Waiting for required OSGi services: org.wso
>     >    
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     >     [2009-08-26 23:07:27,421]  WARN -
>     StartupFinalizerServiceComponent
>     >     Waiting for required OSGi services: org.wso
>     >    
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     >     [2009-08-26 23:07:37,421]  WARN -
>     StartupFinalizerServiceComponent
>     >     Waiting for required OSGi services: org.wso
>     >    
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     >     [2009-08-26 23:07:47,421]  WARN -
>     StartupFinalizerServiceComponent
>     >     Waiting for required OSGi services: org.wso
>     >    
>     2.carbon.mediation.initializer.services.SynapseEnvironmentService,
>     >     [2009-08-26 23:07:57,421]  WARN -
>     StartupFinalizerServiceComponent
>     >     Waiting for required OSGi services: org.wso
>     >
>     >     Any idea whats going on here ?
>     >     rebooting PC does NOT help.
>     >     restoring synapse.xml to the original (as in the wso2esb
>     release)
>     >     does NOT help.
>     >     This is kinda scary stuff, (that the hole esb can stop working.)
>     >
>     >     version
>     >     wso2esb v2.1.0  on windows XP home, java sun  1.6.0_12
>     >
>     >     attached is the complete bootlog.
>     >     Note: There are quite some
>     >     WARN - TransportMBeanSupport Error registering a MBean with
>     >     objectname .. in the bootlog.. although I remenber them beeing
>     >     there before, while the system just booted fine.
>     >
>     >
>     >     Regards,
>     >     Harm
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Esb-java-user mailing list
>     > Esb-java-user@... <mailto:Esb-java-user@...>
>     > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
>
>     --
>     Ruwan Linton
>     Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>     WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org
>     email: ruwan@... <mailto:ruwan@...>; cell: [phone]
>     blog: http://blog.ruwan.org
>
>
>
>     _______________________________________________
>     Esb-java-user mailing list
>     Esb-java-user@... <mailto:Esb-java-user@...>
>     https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>  

--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@...; cell: [phone]
blog: http://blog.ruwan.org



_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user