FileExchangeStore || Content not allowed in prolog

33 views
Skip to first unread message

tsamru...@gmail.com

unread,
Dec 28, 2016, 4:56:27 AM12/28/16
to membrane-monitor
Hi Guys,

Requesting your support to fine a solution which am facing fileexchange store.

I am using Membrane as a middleware proxy between my client APIs and my original servers.


Everything works as smoothly expect an error in FileEchnageStore, it giving me an error Content cannot allowed in prolog and only Request exchanges are saving but response exchange comes blank.

However, I can see the request and response in web console call tab.

I have tried to find any invalid characters in the begging of xml but couldn't find anything unusual. As well this is happening all different APIs (6+) I configured.

Below the sample configuration in proxy  - Attaching the content screen shot.
------------------------------------------

      <fileExchangeStore id="Client" dir="/LOGs/Client" raw="false" saveBodyOnly="false" />
      <fileExchangeStore id="Client2" dir="/LOGs/Client2" raw="true" saveBodyOnly="false" />

      <serviceProxy name= "API-1" port="10027">
        <path>/XISOAPAdapter</path>
        <ssl>
          <keystore
                    location="../conf/Cert.jks"
                    password="Changeit" keyPassword="Changeit" />
          <truststore
                    location="../conf/Cert.jks" password="Changeit" />
        </ssl>
        <exchangeStore name="Client" />
        <target host="192.168.2.215" port="8020">
        </target>
      </serviceProxy>
     
      <!-- Second One-->
      <serviceProxy name= "API-2" port="10028">
        <path>/path2</path>
        <ssl>
          <keystore
                    location="../conf/Cert.jks"
                    password="Changeit" keyPassword="Changeit" />
          <truststore
                    location="../conf/Cert.jks" password="Changeit" />
        </ssl>
        <exchangeStore name="Client2" />
        <target host="externalentities.com" port="443">
          <ssl />
        </target>
      </serviceProxy>

I understand that there is some issue in response xml, but is there any way to skip rather requesting client check it?

Thanks
Amrutha.
Client1-Screenshot-Body.PNG
Client1-Screenshot-Raw.PNG
Client2-Screenshot-Body.PNG
Client2-Screenshot-Raw.PNG

tsamru...@gmail.com

unread,
Jan 7, 2017, 5:39:18 AM1/7/17
to membrane-monitor
Hi friends,

Any helps?

Also can any one help what I can do with membrane response  HTTP/1.1 100 Continue   ?  or how to override this in proxy level ?

Client application in .Net, even they set <servicePointManager expect100Continue="false"/>  in config file the service is working intermittently.

Please help...

regards, Amrutha.
Reply all
Reply to author
Forward
0 new messages