OSB - log SOAP messages

Hi!
I would like to check the outbound and inbound SOAP messages, can I do it?
So I have got a business service which calls remote webservice (OSB is a client here), i have to check the content of SOAP message (i use WS-security policy: digital signature, username+password)
Thank You very mucH!
Viktor

Hi Anuj!
Thank You for Your answer!
I have got a Routing action in my proxy service (which calls a business service), I see this on test console after I call the proxy service:
RouteNode1
Routed Service
+$outbound+
+$body+
+$header+
+$attachments+
Message Context Changes
added $outbound
changed $body
changed $attachments
changed $inbound
changed $header
So after the Message Context Changes I can see the eventual SOAP header which OSB will send?
I think I can't because the changed $body contains this XML:
+<soap:Body ...>+
+<soap:Fault>+
+<faultcode>code:FailedAuthentication</faultcode>+
+<faultstring>The security token could not be authenticated or authorized</faultstring>+
+<faultactor>https://...</faultactor>+
+</soap:Fault>+
+</soap:Body>+
I get this message back from remote webservice so the header above belongs to remote ws as well.
Or do I think badly?
Thanks!

Similar Messages

Logging SOAP messages

I need help on how to use handlers in Weblogic Workshop web services. I have the following logging handler from the bea documentation site.
Now, if I want to log my SOAP messages on the server side, do I just need to put the annotation:
* @jws:handler operation="handler.ConsoleLoggingHandler"
at the top of my JWS file? If that is the case, I don't see any messages being logged. Any help will be greatly appreciated.
Thanks.
gtata
package handler;
import java.util.Iterator;
import javax.xml.rpc.handler.MessageContext;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import javax.xml.soap.SOAPElement;
// for readability, using weblogic API instead of javax.xml.rpc.handler.GenericHandler
// See http://edocs.beasys.com/wls/docs81/webserv/interceptors.html#1060763
import weblogic.webservice.GenericHandler;
* Purpose: Log all messages to the Server console
public class ConsoleLoggingHandler extends GenericHandler
* Handles incoming web service requests and outgoing callback requests
public boolean handleRequest(MessageContext mc)
logSoapMessage(mc, "handleRequest");
return true;
* Handles outgoing web service responses and incoming callback responses
public boolean handleResponse(MessageContext mc)
this.logSoapMessage(mc, "handleResponse");
return true;
* Handles SOAP Faults that may occur during message processing
public boolean handleFault(MessageContext mc)
this.logSoapMessage(mc, "handleFault");
return true;
* Log the message to the server console using System.out
protected void logSoapMessage(MessageContext mc, String eventType)
try
System.out.println("*****************************");
System.out.println("Event: "+eventType);
System.out.println("Endpoint Method: " + getMethodName(mc));
System.out.println("Soap message is: \n " +
com.bea.wlw.runtime.jws.soap.util.SAAJUtil.SOAPPart2String(
((SOAPMessageContext)mc).getMessage() ) + "\n");
System.out.println("*****************************");
catch( Exception e )
e.printStackTrace();
* Get the method Name from a SOAP Payload.
protected String getMethodName(MessageContext mc)
String operationName = null;
try
SOAPMessageContext messageContext = (SOAPMessageContext) mc;
// assume the operation name is the first element
// after SOAP:Body element
Iterator i = messageContext.
getMessage().getSOAPPart().getEnvelope().getBody().getChildElements();
while ( i.hasNext() )
Object obj = i.next();
if(obj instanceof SOAPElement)
SOAPElement e = (SOAPElement) obj;
operationName = e.getElementName().getLocalName();
break;
catch(Exception e)
e.printStackTrace();
return operationName;
}

You can use the logging and tracing functionality to write log statements anywhere in BPEL. refer http://wiki.open-esb.java.net/Wiki.jsp?page=LoggingFromWSBPELActivityInABusinessProcess . But you should keep in mind these are not soap messages that you log. They will be abstract WSDL message instances. If you want to log specifically the soap messages you need the support in HTTP-BC.
If you turn on logging you should see the line number of BPEL where it fails. That should give you some indication. I am not 100% sure, but in the logs, we should be logging the variable which was not initialized. I can't think of any other way to find out which variable caused this exception.
-Kiran Bhumana

Logging soap messages invoked by BPEL process

Hi,
Is there any way to log the SOAP messages sent from an invoke? A receive?
Also, is there a way to capture which variable is throwing an uninitializedVariable exception?
J

You can use the logging and tracing functionality to write log statements anywhere in BPEL. refer http://wiki.open-esb.java.net/Wiki.jsp?page=LoggingFromWSBPELActivityInABusinessProcess . But you should keep in mind these are not soap messages that you log. They will be abstract WSDL message instances. If you want to log specifically the soap messages you need the support in HTTP-BC.
If you turn on logging you should see the line number of BPEL where it fails. That should give you some indication. I am not 100% sure, but in the logs, we should be logging the variable which was not initialized. I can't think of any other way to find out which variable caused this exception.
-Kiran Bhumana

Log soap messages

I am using call.invoke() method for sending soap requests to a remote server..is there any way to log the soap request message i send and receive....

I am using call.invoke() method for sending soap requests to a remote server..is there any way to log the soap request message i send and receive....

OSB Log file

OSB logging using message flow logs the messages to domain admin server log file.
is it possible to route the OSB logs to a central logging system such as sys logs?

You will need to create some Java classes that implement the log4j framework and expose some static methods that will have logger statements.
For ex: Create One java class call SBLogger. This should have the implementation for a log4j logger by reading a log4j.xml or log4j.properties file. And create one static method like logMessage(str LoggerName, strLogMessage, strLogLevel). Inside this method create a logger with the strLoggerName and then have the corresponding logger.debug() or logger.info() type statements based on the log level. Or you can create different methods one each for debug, info , etc... log levels like logDebugMessage(message).
Once you have tested this externally, create a jar file (with the *.class of the log4j implementation) and upload this to the osb console are jar. Ensure that you place the log4j properties file in the config folder of the osb domain, so that osb will be able to load it when it starts up. [After placing the log4j.xml file, you will need to restart the domain for it take effect]
Now using java callout, you can invoke the corresponding logging methods, which will log into the files depending on the log4j.properties appender configuration.
For changing the loglevels on the fly you can refer to a solution given by Ananth @ http://ananthkannan.blogspot.com/2009/10/how-to-change-log-levels-on-fly-using.html
Hope this information will help you to proceed with the implementation. Do let me know in case you run into issues.
Thanks,
Patrick

Log SOAP traces

Hi,
I'm using weblogic 9 and weblogic web services. I would like to know how to configure weblogic for logging SOAP messages to a file/console. I have had a look at weblogic's log4j configuration but could'nt get any result.
Thanks a lot!

Hi,
I'm using weblogic 9 and weblogic web services. I would like to know how to configure weblogic for logging SOAP messages to a file/console. I have had a look at weblogic's log4j configuration but could'nt get any result.
Thanks a lot!

Logging SOAP Envelope in ADF

Dear All,
I wanted to log all my SOAP traffic so I created my own SOAPProvider for my Web Service Data Control.
I used below code
public class MySoapProvider extends SOAPProvider
     private static final ADFLogger logger = ADFLogger.createADFLogger(MySoapProvider.class);
     @Override
     public void handleRequest(SOAPMessage soapMessage)
     throws AdapterException
       logSOAPMessage(soapMessage, "REQUEST");
       super.handleRequest(soapMessage);
     @Override
     protected void handleResponse(SOAPMessage message) throws AdapterException {
          logSOAPMessage(message, "RESPONSE");
          super.handleResponse(message);
     private void logSOAPMessage(SOAPMessage message, String origin){
       ByteArrayOutputStream out = new ByteArrayOutputStream();
          try {
               message.writeTo(out);
          } catch (Exception e) {
               e.printStackTrace();
          logger.info("SOAP Message :: " + origin + " :: " +out.toString());
}But it prints this line.
<SSSOAPProvider> <logSOAPMessage> Logging SOAP Message :: REQUEST :: oracle.j2ee.ws.saaj.soap.soap11.Message11@1466e35I am not sure, but how do you logged the SOAP envelope in ADF? I am expecting to print the soap header and soap body actually
Thanks

Thanks,
that set me in the right direction - I had tried the third parm before but must not have been just right being that there are multiple namespaces given. Appears I have to always use the namespace parm to accurately obtain the data. To conclude - this is what I ended up with to get this returning data properly:
SELECT
EXTRACTVALUE(VALUE(d),'/Destination/DestinationId', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"') AS ID,
Get_Point(EXTRACTVALUE(VALUE(d),'/Destination/Longitude', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"'),
EXTRACTVALUE(VALUE(d),'/Destination/Latitude', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"')) AS geom,
EXTRACTVALUE(VALUE(p),'/Provider/ProviderName', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"') AS provider_name,
EXTRACTVALUE(VALUE(p),'/Provider/ProviderSpecific/HospitalInformation/whoAvainFlu', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"') AS avaianflu,
VALUE(p) AS xmlb
FROM X_MEDAIRE xml
,TABLE (xmlsequence(EXTRACT(xml.object_value,
'/soap:Envelope/soap:Body/*', 'xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"'
))) e
,TABLE (xmlsequence(EXTRACT(VALUE(e),
'/long/path/after/soap', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"' ))) d
,TABLE (xmlsequence(EXTRACT(VALUE(d),
'/Destination/ProviderList/Provider', 'xmlns="http://xxx.xxx.xxx.xxx/some_ws/"' ))) p
WHERE
EXTRACTVALUE(VALUE(p),'/Provider/ProviderType', 'xmlns="http://xxx.xxx.xxx.xxx/some_ws/"') = 'Hospital'

OSB - Couldn't create SOAP message due to exception: Unable to create StAX

Hi,
If I call 2 webservices via OSB 10Rg3 in quick succession I get the following fault on the second response :
<May 6, 2010 5:25:14 PM CEST> <Error> <ALSB Logging> <BEA-000000> < [null, null, null, ERROR] <soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/e
nvelope/"/><S:Body xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
<faultcode>S:Client</faultcode>
<faultstring>Couldn't create SOAP message due to exception: Unable to create StAX reader or writer</faultstring>
</S:Fault>
</S:Body><con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380001</con:errorCode>
<con:reason>Internal Server Error</con:reason>
<con:location>
<con:node>RouteToTestService</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>>
Any ideas what could cause this? The provider web services are working fine... and there is no problem if there is a long time delay between calling the 2 web services.

It seems that one of the providers was mis-configured (the first service called) :
HTTP Transport Configuration
Follow HTTP redirects      DISABLED
Use Chunked Streaming Mode      ENABLED
when I enabled the HTTP redirect then the problem went away...
HTTP Transport Configuration
Follow HTTP redirects      ENABLED
Use Chunked Streaming Mode      DISABLED

Logging of SOAP messages at server side, Axis 1.2, NO SoapMonitor / TCPMon.

Hello,
I�m looking for a way to log all SOAP communication at a Axis Server.
I want to log the messages into my logdatabase or to files at least.
I am not interrested af SOAPMonitor or TCPMonitor, those are good tools but not for my purposes.
Anyone can help me out?

Hi,
You should have a look at the Axis users guide, under "More deployment - Handlers and Chains". This part describes a LogHandler to be included in the WSDD that basically logs information about the requests and/or responses.
Also look at the class org.apache.axis.handlers.LogHandler

[OSB] SOAP Message Body Deleted in Routing Process

Hello Folks,
I'm using Oracle Services Bus 11g and I have the following scenario:
A Business Services that is a client of a WebService. This WebService has an operation that return in its Soap Message a field with special characters (an encripted password).
So, I've created an Proxy Service that route the request message to above business service, but when the message returned by Business service is routing back to Proxy Service the body of the message is deleted.
Checking out the trace of the call, it says "Body was deleted" ! And so the message is returned by Proxy service without body !
I suspected that problem is something about encoding !
Someone could help me resolve this problem ?
Thanks in advanced!

Hi,
I am facing some similar issues with OSB 10gR3 where the Message body gets deleted and i get empty soap body as response when i make continuous calls to a business service without any time delay between the calls.
Though surprisingly i get the correct response from the business service for the first time but only on consecutive calls without any time delay between two calls i get empty soap body. Later if i try to call the business service leaving a gap of 15 sec after my first call, i get the correct response.
I initially thought it might be a problem with the business service itself but when i try to make continuous calls to the Business service without any timedelay directly from SOAPUI , I am getting correct response everytime.
Hence this seems to be a problem only when i invoke the business service via the OSB proxy and thsi deletes the response body wehn i make continuous calls.Not sure whether this is a bug with OSB or encoding issues.
Pls help me to know if this has anything to do with the caching or any setting in OSB server.
Thank you
Preetha
Edited by: 893969 on 31-Oct-2011 06:25
Edited by: 893969 on 31-Oct-2011 06:27

Logging inbound SOAP Message in SALT 2.0

Is there a way to log the inbound SOAP message [valid or invalid] in SALT 2.0. We have a situation where the client is sending a SOAP message that we want to be able to intercept and log. The client is reporting that the SALT gateway is reporting an invalid SOAP message, we want to be able to log this message so we can let them know what we are receiving.
Thanks

Ram--
Everywhere in XI, the acronym "LCR" is synonymous with "SLD", System Landscape Directory. It seems like it may be a term they used early on, or maybe it's the German equivalent. The LCR acronym is sprinkled throughout SAP's underlying code.
In your error message, it's complaining about the Business System entry in the SLD.
My first thought would be that either the source or target business system is not configured in the SLD, or you haven't defined the business system properly in the SOAP adapter configuration. See the "XI20 Adapter Engine" manual for instructions on how to configure the SOAP adapter.
NOTE: You may be able to configure the SLD to make this solution work on your own, but for long-term usage, you're going to want an expert to model your system landscape and configure the SLD properly.
--Dan King
Capgemini

How to Write Soap Message to Log File

Hello users,
Is there a config setting that causes soap messages to be written to the server log. I'm using JBoss/Turnkey. I found a reference in the JBoss documentation (Ch 5 J2EE Web Services) that offers this guidance:
(5.4. Monitoring webservices requests)
When processing web services requests, it is often useful to be able to observe the actual messages being passed between the client and the server. JBoss logs this information in the org.jboss.axis.transport.http.AxisServlet category.
To enable web services logging, add the following debug category to the log4j.xml file:
<category name="org.jboss.axis.transport.http.AxisServlet">
<priority value="DEBUG"/>
</category>
When enabled, all SOAP requests and responses will be logged to the server.log file.
Tried it but not working yet. Thanks for any help.
Jesse

http://www.google.com/search?q=java+web+service+tutorial&meta=

SAAJServet error when sending a SOAP message on 10.1.2

Hi,
We have deployed a server application in OC4J 10.1.2 with a servlet listening for SOAP messages (SAAJ 1.2). If we use Standalone OC4J with SSL enabled and HTTPS communication between client app and server, it works fine, but when we move it to an Application Server environment where client goes HTTPS to the frontend HTTP_Server and then AJP to the OC4J, the following exception appears on the application.log:
07/03/27 17:48:36 application/gpm-0.1: Servlet error
javax.servlet.ServletException: SAAJ POST failed Unable to internalize message
at com.sun.xml.messaging.soap.server.SAAJServlet.doPost(SAAJServlet.java:212)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind
Any ideas what can go wrong here, or where else to look?
Message was edited by:
[email protected]

The standalone OC4J is 10.1.3, sorry. Nevertheless, we include all the libraries we use (saaj and dependencies) in the appliaction .ear archive that we deploy in both environments. May be a configuration issue?

ApplicationResponseFault with namespace longer than 60 in sync soap message

Hi,
we are on pi 7.0 and our scenario is a async-sync bpm. In the sync soap message, the webservice raise an application error. In the response soap message we get the following detail tag:
<detail><ApplicationResponseFault xmlns="http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10"><DocumentResponse xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"><Response><ResponseCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">BusinessReject</ResponseCode></Response></DocumentResponse></ApplicationResponseFault></detail>
In sxi_monitor this application error isn't caught and a system error is generated.
In the system error message we get:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at com.sap.aii.adapter.xi.ms.XIMessage.updateHeaders(XIMessage.java:4271) at com.sap.aii.adapter.xi.ms.XIMessage.getTransportHeaders(XIMessage.java:572) at com.sap.aii.af.ra.ms.impl.ServerConnectionImpl.request(ServerConnectionImpl.java:212) at
In defaulttrace.trc we get ","<sap:ApplicationFaultMessageNamespace> is longer than 60 characters: http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10",":
"09/04/2009","10:22:43:421","unable to generate the header map","Error","","com.sap.aii.adapter.xi.ms.XIMessage.getHeaderMap()","sap.com/com.sap.aii.af.app","SAPEngine_Application_Thread[impl:3]_14","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE005E00005F2300000A6C000472BC344957CC","com.sap.aii.adapter.xi.ms.XIMessage","","","n/a","b82f88e0992b11dea4d8001a64317eee","","0","0","","0","","","0","com.sap.aii.adapter.xi.ms.XIMessage","SAPEngine_Application_Thread[impl:3]_14","","J2EE_GUEST",
"09/04/2009","10:22:43:421","<sap:ApplicationFaultMessageNamespace> is longer than 60 characters: http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10","Error","","com.sap.aii.messaging.mo.xmb.XMBErrorHeader.marshal(XMLWriter)","sap.com/com.sap.aii.af.app","SAPEngine_Application_Thread[impl:3]_14","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE005E00005F2200000A6C000472BC34495771","com.sap.aii.messaging.mo.xmb.XMBErrorHeader","http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10,","http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10,","n/a","b82f88e0992b11dea4d8001a64317eee","","0","0","","1","","","0","com.sap.aii.messaging.mo.xmb.XMBErrorHeader","SAPEngine_Application_Thread[impl:3]_14","","J2EE_GUEST",
"09/04/2009","10:22:43:421","Could not process message from 192.168.130.21 due to java.lang.NullPointerException.","Error","","com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(HttpServletRequest, HttpServletResponse)","sap.com/com.sap.aii.af.ms.app","SAPEngine_Application_Thread[impl:3]_55","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE0083000072F700000A6C000472BC344955F3","com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet","192.168.130.21,java.lang.NullPointerException,","192.168.130.21,java.lang.NullPointerException,","SAPDES_TPI_34103150","1d72b100992c11dec67f001a64317eee","PIISUSER","0","0","","1","","","15337","com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet","SAPEngine_Application_Thread[impl:3]_55","","PIISUSER",
"09/04/2009","10:22:43:421","The SAP XI Adapter Framework Messaging Service caught an exception during rendering an XML Message. Details can be found in the trace file for Location com.sap.aii.messaging.mo.xmb. Action: Please contact SAP Support and provide the trace file.","Error","/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK","com.sap.aii.messaging.mo.xmb.XMBErrorHeader.marshal(XMLWriter)","sap.com/com.sap.aii.af.app","SAPEngine_Application_Thread[impl:3]_14","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE005E00005F2000000A6C000472BC3449559F","com.sap.aii.messaging.mo.xmb.XMBErrorHeader","","","n/a","b82f88e0992b11dea4d8001a64317eee","","0","0","","0","/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK","","0","com.sap.aii.messaging.mo.xmb.XMBErrorHeader","SAPEngine_Application_Thread[impl:3]_14","","J2EE_GUEST",
So I think the problem is due to the namespace length. I'm right?
We can't change the consumed webservice to reduce namespace length and our customer ask us to solve it in PI. Is there any way to change the namespace before to be treated and get a correct application error?
Thanks in advance,
Marc
Edited by: Marc Mauri on Sep 5, 2009 12:06 PM

Hi Neetesh,
we developed our own adapter module. We use it in our receiver soap adapter, module tab, before and after the standard module sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean.
In this audit log secuence you can see that the problem seems not to be solved, because the error is triggered when processing response message inside adapter module sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean, so our module is not called and the problem remains.
2009-09-22 19:06:41 Success Message successfully received by messaging system. Profile: XI URL: http://sapdes:50300/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2009-09-22 19:06:41 Success The message status set to DLNG.
2009-09-22 19:06:41 Success Delivering to channel: CC_WS_DOS
2009-09-22 19:06:41 Success MP: Entering module processor
2009-09-22 19:06:41 Success MP: Processing local module *localejbs/AM_OWN_MODULE*
2009-09-22 19:06:41 Success GetHostName: Module called
2009-09-22 19:06:41 Warning Inside my own adapter Module <-- THIS IS A TRACE MESSAGE CODED INSIDE OUR MODULE
2009-09-22 19:06:41 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2009-09-22 19:06:41 Success SOAP: request message entering the adapter with user J2EE_GUEST
2009-09-22 19:06:41 Success SOAP: Web Services Security processing...
2009-09-22 19:06:41 Success SOAP: apply Web Services Security...
2009-09-22 19:06:41 Success SOAP: Web Services Security applied.
2009-09-22 19:06:42 Success SOAP: completed the processing
2009-09-22 19:06:42 Success SOAP: continuing to response message 4d2c88e0-a79a-11de-9ffa-001a64317eee
2009-09-22 19:06:42 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault <----
THIS ERROR IS DUE TO NAMESPACE LENGHT (WE CAN SEE THIS ERROR IN DEFAULT_TRACE.LOG)
2009-09-22 19:06:42 Success MP: Processing local module localejbs/AM_OWN_MODULE
2009-09-22 19:06:42 Success MP: Leaving module processor
2009-09-22 19:06:43 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System. 2009-09-22 19:06:43 Success The message status set to DLVD.
Any suggestion?
Thanks in advance,

High delay in deserializing soap message in Flex 3.0

We are developing a middle sized application using Flex and Axis Webservices. On the client side we AS code generated using Flex Builder 3.0 and the WSDL. On the server side we have Java code generated with Axis 1.3 using the same WSDL. The problems occurs when the server sends a 290Kb response to the Client. Flex spends 10 seconds (obtained from mx.rpc.* log facility) in deserialing this SOAP message. My question is:
¿Could I improve the performance of the deserialization?
Due to the fact that this is an unaceptable delay and that we have a code of 70.000 lines ¿what choices we have? ¿Should we use remote objects?
Thank you

Yes I think your app will perform better using remote objects, there's
a great app to test that named Census you can get it and do your own
tests or play with it on James Ward's blog.
Sincerely,
Michael
El 22/04/2009, a las 12:24, ijmarrero <[email protected]> escribió:
>
We are developing a middle sized application using Flex and Axis
Webservices. On the client side we AS code generated using Flex
Builder 3.0 and the WSDL. On the server side we have Java code
generated with Axis 1.3 using the same WSDL. The problems occurs
when the server sends a 290Kb response to the Client. Flex spends 10
seconds (obtained from mx.rpc.* log facility) in deserialing this
SOAP message. My question is:
>
¿Could I improve the performance of the deserialization?
>
Due to the fact that this is an unaceptable delay and that we have a
code of 70.000 lines ¿what choices we have? ¿Should we use remote ob
jects?
>
Thank you
>

OSB - log SOAP messages

Similar Messages

Maybe you are looking for