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 <[email protected]>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 >
test.xslt
Description: Binary data
<?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 [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
