Hello,
Case 1:
I created my proxy service xml and dropped at:
\wso2esb-3.0.0\repository\conf\synapse-config\proxy-services\proxy123.xml
Case 2:
I created proxy service form UI
In both cases, after couple of restarts of the ESB server, the xml (of course the service from UI) disappear. This is really scary !!!!
Please let me know if I have to setup some configuration to survive my service after restarts.
I'll appreciate your response!
Thanks,
Which version of WSo2 ESB you
Which version of WSo2 ESB you are using...
I was able to add proxy service XML(not from UI) and i don't see this problem....
But I was not able to add from UI...
Thanks,
Vinod
Thanks for reply! Actually
Thanks for reply! Actually this is not get reproduce every time. some time after 3-4 times it breaks down (I see this more when i try to see the source from UI and save it with trace enable etc...). You can add from UI by going to "Manage>>Add>Proxy Service" and see the source also. Actually I have one more problem I can not see the LOG Message at all for example here is my proxy file
<target>
<endpoint name="endpoint_urn_uuid_1DE1F" >
<log level="full"/>
<address uri="jms:/wa.atp.tasresponse?transport.jms.ConnectionFactoryJNDIName=../>
</endpoint>
<outSequence>
<log level="full"/>
<send/>
</outSequence>
</target>
<parameter name="transport.jms.ConnectionFactory">myQueueConnectionFactory</parameter>
<parameter name="transport.jms.UserName">Userr</parameter>
<parameter name="transport.jms.Password">User</parameter>
<parameter name="transport.jms.DestinationType">queue</parameter>
<parameter name="transport.jms.Destination">SampleQ1</parameter>
</proxy>
I have experienced this as
I have experienced this as well. I find that it happens when I make an edit from source view and save. I've also noticed that sometimes the xml from my proxy ends up in the in the synapse.xml file that is in the syanpse-config folder. So when I try and re-add my proxy to the proxy-services folder I get an error about a duplicate proxy.
These issues related to the
These issues related to the hot update logic in ESB. We have fixed most of them and in the process of releasing the version 3.0.1. You'll need to check once the release is out.
Rajika