Re: FIX Session creation with the message delivery endpoint.

Yes (if the initiator is up and running) or as soon as the initiator comes up (we can start the fix engine by defining the acceptor sessions so quickfix will connect automatically). FIX users wants to make sure **all** his/her FIX sessions are up and healthy before trade starts. Asanka A. Hir

Re: FIX Session creation with the message delivery endpoint.

Hi Asanka, Do you suggest that we should create the session with the acceptor at Synapse start up? Thanks Best Regards, Hiranya On Fri, Jun 27, 2008 at 11:05 AM, Asanka Abeysinghe <[EMAIL PROTECTED]> wrote: > Hi, > > Synapse maintain two FIX sessions to connect FIX endpoints (see the > attache

FIX Session creation with the message delivery endpoint.

Hi, Synapse maintain two FIX sessions to connect FIX endpoints (see the attached diagram, session A and session B). Session with initiator (session A) created in the startup process of synapse (if the initiator up and running) or as soon as the initiator comes up. But the session with the acc

[jira] Created: (SYNAPSE-379) Documentation doesn't describe FIX transport parameters

Documentation doesn't describe FIX transport parameters Key: SYNAPSE-379 URL: https://issues.apache.org/jira/browse/SYNAPSE-379 Project: Synapse Issue Type: Bug Components:

AW: Possible Causes for "Connection reset by peer" when using NIO

Hi all, unfortunately decreasing the synapse (nhttp) socket timeout to 25000 ms did not change anything to the current situation. I'm also thinking about what may be the difference between Hessain and SOAP in this regard. Reading RFC 2068 Appendix 19.7: "However, a persistent connection wit

Re: SOAP11 and SOAP12 binding

Hi Ruwan, I tried the same first time and it did not work. Please find attached the file I am using. When I use the parameter name "useOriginalwsdl", I could not query the wsdl. But when I use the parameter name "useOriginalWsdl" with a upper case "W", I am able to query the wsdl but the paramete

Re: File suffix for Synapse extension archives

I think that the suffix should end with AR so that the file type is easily recognizable as JAR like. Since 3 letters look better than 4 and SAR is already taken, this would leave us with XAR. The fact that this suffix is already used by Excel Autorecovery files should not be too annoying be

Re: SOAP11 and SOAP12 binding

Hi Murali, Please try adding the following two parameters to the proxy configuration; true false It will work. Thanks, Ruwan On Thu, Jun 26, 2008 at 8:55 PM, cmurali <[EMAIL PROTECTED]> wrote: > > Does this parameter work in synapse 1.1? I am using synapse 1.1 and it does > not work even if I

Re: File suffix for Synapse extension archives

Andreas Initially I proposed SXAR for Synapse eXtension ARchive, but after giving it some thought, I believe that XAR sounds better. I would like to have the opinion of the developer and user community on this. Any comments and suggestions are welcome! I didn't like SXAR since it feels too lon

Re: Improving performance even more :)

On Thu, Jun 26, 2008 at 8:11 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote: > > Cool, I think this would be interesting. So we need a mechanism to find > > whether the AXIOM tree is modified or not when we send the message out. > > Ok so we can do this I guess by looking to see if the root has been

Re: SOAP11 and SOAP12 binding

Does this parameter work in synapse 1.1? I am using synapse 1.1 and it does not work even if I add this parameter. I tried true and SOAPUI was not able to query the wsdl successfully. When I used true SOAPUI queries wsdl fine but I see both the bindings. Muralidaran Chakravarthy -- View th

Re: Improving performance even more :)

> Cool, I think this would be interesting. So we need a mechanism to find > whether the AXIOM tree is modified or not when we send the message out. Ok so we can do this I guess by looking to see if the root has been built at all. If it hasn't been built then the message is still untouched. That wo

Re: SOAP11 and SOAP12 binding

Hi Murali, On Thu, Jun 26, 2008 at 7:36 PM, cmurali <[EMAIL PROTECTED]> wrote: > > Hi, > > Please see attached my wsdl, schema files and the screen shots of SOAPUI > querying my wsdl. My WSDL only has SOAP1.1 binding defined. There is no > SOAP12 binding defined in my WSDL as you can see. But whe

Re: Improving performance even more :)

Hi Paul, On Wed, Jun 25, 2008 at 8:13 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote: > The recent performance testing we did on the WSO2 ESB applies exactly > to Synapse (http://wso2.org/library/3740), and looking at those > figures, it would be nice to improve the routing performance when > there

SOAP11 and SOAP12 binding

Hi, Please see attached my wsdl, schema files and the screen shots of SOAPUI querying my wsdl. My WSDL only has SOAP1.1 binding defined. There is no SOAP12 binding defined in my WSDL as you can see. But when I deploy these in synapse1.1 and query the wsdl using SOAPUI or a browser, I see both SOA

Re: File suffix for Synapse extension archives

I agree 3 character extension is always better than any other extensions :-) But I found XAR to be a little common extension for example it is being used by MS-Excel as Excel AutoRecover Fileand there are some other media types which refers with the XAR exte

File suffix for Synapse extension archives

Hi all, With the improvements I proposed in SYNAPSE-377 it will become possible to deploy (including hot deployment) Synapse extensions, i.e. mediators and startups, not only in the form of simple JAR files, but also in the form of archive files with embedded JARs, meaning that the extens

Re: Proposal to improve the XSLT performance

Hi Andreas, I have created a JIRA issue for this. https://issues.apache.org/jira/browse/SYNAPSE-378 Thanks, Ruwan On Thu, Jun 26, 2008 at 2:15 PM, Ruwan Linton <[EMAIL PROTECTED]> wrote: > Hi Andreas, > > On Wed, Jun 25, 2008 at 11:39 PM, Andreas Veithen < > [EMAIL PROTECTED]> wrote: > >> I'm

[jira] Created: (SYNAPSE-378) Improve the performance of the XSLT mediator

Improve the performance of the XSLT mediator Key: SYNAPSE-378 URL: https://issues.apache.org/jira/browse/SYNAPSE-378 Project: Synapse Issue Type: Improvement Components: Core Affects

[jira] Commented: (SYNAPSE-377) Improve MediatorDeployer to support Startups and embedded JARs

[ https://issues.apache.org/jira/browse/SYNAPSE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608391#action_12608391 ] Ruwan Linton commented on SYNAPSE-377: -- This sounds interesting, but please note that

Re: Possible Causes for "Connection reset by peer" when using NIO

Hi Eric I think this is a good idea.. as we will close the session on our own without an exception, and then BEA can close it from that side Ok, then I will go ahead and try this out. Is there a way to check whether this property has been applied properly by Synapse? Some JMX-monitoring po

RE: Possible Causes for "Connection reset by peer" when using NIO

Hi Asankha, > I think this is a good idea.. as we will close the session on our own > without an exception, and then BEA can close it from that side Ok, then I will go ahead and try this out. Is there a way to check whether this property has been applied properly by Synapse? Some JMX-monitoring

Re: Possible Causes for "Connection reset by peer" when using NIO

Hi Eric This brings me to a new idea and I what like to hear what you think about. What if I would decrease the value for http.socket.timeout to 2 for Synapse, so to be definitely lower than the one on the server side. What would be the expected result? Would I see another exception, if the t

[jira] Updated: (SYNAPSE-360) Dynamic load balancing

[ https://issues.apache.org/jira/browse/SYNAPSE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez updated SYNAPSE-360: - Attachment: axis2Server.patch axis2Server.patch addresses the listener starting order issue > D

[jira] Reopened: (SYNAPSE-360) Dynamic load balancing

[ https://issues.apache.org/jira/browse/SYNAPSE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reopened SYNAPSE-360: -- We need to start the listeners at last, so that in dynamic LB, the LB can start sending messages

RE: Possible Causes for "Connection reset by peer" when using NIO

Hi Asankha, thanks for your reply as well! Please see my comments below! > One thing you could analyze is the TCP socket timeout times in the > different environments.. Hmm, TCP socket timeout should be the same, but I will investigate. Also our response times are pretty low. Average of 10-15 ms

Re: Possible Causes for "Connection reset by peer" when using NIO

Hi Eric, > > > > > I do not know Hessian well enough protocol to comment on it. > I also can't see any logical relation to the application protocol used on > top of the transport protocol. Yes, for Oleg you can assume it to be just a byte stream the protocol does not matter I guess. > > > If

Re: Proposal to improve the XSLT performance

Hi Andreas, On Wed, Jun 25, 2008 at 11:39 PM, Andreas Veithen <[EMAIL PROTECTED]> wrote: > I'm still trying to understand why StaxSource causes a performance > degradation. I don't see why serializing the message to a byte array and > then parsing it again gives better performance than pulling a

RE: Possible Causes for "Connection reset by peer" when using NIO

Oleg, thanks a lot for your reply! Please see my comments inline! > > The problem is I don't understand the cause of this exception. It occurs > during the read on a Socket-Channel. So I think the server might close the > connection while the ESB is reading. But maybe internally some kind of > po