Log http response

How do I view HTTP responses that PHP sends to my Flex app?
My RemoteObject throws an exception, because my PHP script prints some kind of error message. So how do I view that error?

You can define a fault handler for your RemoteObject component in Flex.
You can also use a tool like Charles or Fiddler in order to see the HTTP requests and responses.

Similar Messages

Adobe Document Services - http Response 500 - How to configure the logging?

We are building an application in Web Dynpro Java that fetches data from an R/3 system via an RFC connection and is then supposed to show said data in a pdf within an iview. For that task we want to use the InteractiveForm UIElement. We bind the data to its pdfSource in the iViewu2019s context. Currently the form only consists of a text field bound to one attribute element of the pdfSource context node.
The ADS webservice is configured according to the manuals found here:
http://help.sap.com/saphelp_nw70/helpdata/en/fa/0b700d6cfd4e03a8ec2186ba6ff4af/frameset.htm
and tested successfully under the following link
http://<portal_host>:<port>/AdobeDocumentServices/Config?style=document
However, when we execute the application, an error occurs in the webservice generating the pdf, namely Invalid Content-Type:text/html. The error occurs when the iView containing the form is shown for the first time, even before the attributes of the pdfSource context are filled with data (we expect to see an empty form).
As it seems the webservice is expected to return a MIME type of either application/pdf or text/xml (we donu2019t know for sure since the SAP manuals and forums are inconclusive here), but instead we get text/html. This seems to be due to the fact that the webservice exits with an http response 500 Internal Server Error (we used several network monitoring tools to confirm that such a response is sent). Since such http responses are but html files with an empty body, yet not xml or pdf, the aforementioned error does make sense to us, but we do not know what Internal Error has caused it.
The only help that SAP seems to provide for an error u201CInvalid Content-Type:text/htmlu201D in context with ADS points to an expiring password or otherwise poor configuration of the ADSUser, which (most certainly) is not our case here since, and as said above, the configuration was and can be tested successfully.
We then tried to view the logs for this error on the machine where the J2EE engine is running with ADS installed according to this (not very comprehensible) guide:
http://help.sap.com/saphelp_nw70/helpdata/de/97/ccfc3f0ac2c642e10000000a1550b0/frameset.htm
We cannot find anything relevant in the server.log of the Visual Administrator except this message (it is generated exactly when our error occurs u2013 the trace severity is set to ALL for all Adobe application elements according to manual):
Date , Time , Message , Severity , Category , Location , Application , User
12/08/2010 , 13:50:46:511 , application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to GENERATEPDF
Exception id: [0800274DA7ED00850000005B00000900000496E5919E28BA] , Error , /System/Server/WebRequests , com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl , sap.com/tcwddispwda , Guest
There is no error.pdf to be found on the file system and since neither have we known nor are we told by the error message, whether the underlying cause is is a render error or connection error or configuration error or what not, we donu2019t know whether the error.pdf is supposed to be generated at all.
Or could there be any other reason why generation didnu2019t take place?
Furthermore we canu2019t seem to be able to find any logs more verbose or detailed about this issue - at least not within the Visual Administrator or the portalu2019s nwa.
How is it possible to properly debug the webservice for pdf-generation or at least to retrieve a fully detailed log containing all notifications and exception stack traces etc.?
I am assuming that we are making some basic mistakes regarding the logging configuration - but what?
Our goal is to know what causes the 500 Internal Server Error response that causes the Incorrect Content-Type exception.
We are using a NetWeaver 7.01 portal installation with Adobe Document Services 7.01 installed on a Windows Server 2003 platform.
Any help is highly appreciated!
Serg

Have you tried restarting the Java PDF object in Visual Administrator? Once you do all of your config, you have to restart the PDF object (sao.com/tcwdpdfobject) for the changes to take place. I am assuming you've run all of the test programs in SAP (FP_TEST_00, FP_TEST_03, etc.). Is there any chance that the ADSUSER is locked somehow?

Deploying simple HTML page to WLS 10.3.6 fails with HTTP response code: 502

- I created a simple HTML page and want to test deployment to WLS 10.3.6 on Linux. I created WAR file and when using JDev 11.1.1.4.0 to deploy to WebLogic Server, it fails to deploy. Full errors/messages are:
[04:40:56 PM] ---- Deployment started. ----
[04:40:56 PM] Target platform is (Weblogic 10.3).
[04:40:59 PM] Retrieving existing application information
[04:40:59 PM] Running dependency analysis...
[04:40:59 PM] Building...
[04:40:59 PM] Deploying profile...
[04:40:59 PM] Wrote Web Application Module to C:\JDeveloper\mywork\Simpe_HTML\Project1\deploy\SimpleHTML.war
[04:41:01 PM] Deploying Application...
[04:41:01 PM] Weblogic Server Exception: weblogic.deploy.api.internal.utils.DeployerHelperException: The source 'C:\DOCUME~1\NGOLDR~1.LAT\LOCALS~1\Temp\SimpleHTML.war' for the application 'SimpleHTML' could not be loaded to the server 'http://dupe:7031/bea_wls_deployment_internal/DeploymentService'.
Server returned HTTP response code: 502 for URL: http://dupe:7031/bea_wls_deployment_internal/DeploymentService
[04:41:01 PM] See server logs or server console for more details.
[04:41:01 PM] weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260041]Unable to upload 'C:\JDeveloper\mywork\Simpe_HTML\Project1\deploy\SimpleHTML.war' to 't3://dupe:7031'
[04:41:01 PM] #### Deployment incomplete. ####
[04:41:01 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
- The Application Server connection is accessible within JDev. 'dupe' is my server name and it's running RH 5.4
- Any help or suggestions appreciated, although I've already asked Mr. Google without success.
Thanks in advance,
Neville

HTTP response code 502 means temporarily overloaded.
I would say that we have to check the deployment error on the weblogic server logs located at <Domain_Home>\servers\dupe\logs\dupe.log
Check for any errors like OutOfMemory etc OR any deployment failures.
If possible, try accessing the console at http://dupe:7031/console
Check if you are able to successfully deploy your application using the console.
From the error it looks like the "dupe" server might not be healthy. So, the log file would really help here to get clues into the root cause.
Arun

Windows Azure Pack - Server returned HTTP response code: 500 error while accessing the public tenant API

Hi,
We are facing the following error while trying to access the given Windows Azure Pack Public tenant API to query the virtual machines list along with network adaper details -
java.io.IOException: Server returned HTTP response code: 500 for URL: https://<hostname>:30006/<subscription-id>/services/systemcenter/vmm/VirtualMachines?$expand=VirtualNetworkAdapters&$top=10000&$skip=0
The response is proper when we access the following URL -
https://<hostname>:30006/<subscription-id>/services/systemcenter/vmm/VirtualMachines
Only on adding the $expand=VirtualNetworkAdapters, url parameter we are getting the above error.
Where can we check for the error logs on the Azure Pack server ? We checked for the logs using Windows Event Viewer but did not find any for the public tenant API.
What should be the cause for such an error and how can we fix this to get the proper data?
Thanks in advance.

Yes, we tried this, $top=10&$skip=0 works for the following url
https://<hostname>:30006/<subscription-id>/services/systemcenter/vmm/VirtualMachines?$top=10&$skip=0
It is only when we add $expand=VirtualNetworkAdapters,
the server returns the mentioned error response -
URL for which the server returns the 500 error -
https://<hostname>:30006/<subscription-id>/services/systemcenter/vmm/VirtualMachines?$expand=VirtualNetworkAdapters&$top=10&$skip=0
Can
you point to the error logs for Windows Azure Pack and SPF ?

2013 Exchange, Can't connect to Exchange Management Shell. It cannot determine the content type of the HTTP response from the destination computer.

The following error occurs.
         Welcome to the Exchange Management Shell!
Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List
Tip of the day #0:
Did you know that the Identity parameter is a "positional parameter"? That means you can use:
Get-Mailbox "user" instead of: Get-Mailbox -Identity "user"
It's a neat usability shortcut!
VERBOSE: Connecting to mail1.dorothy.local.
New-PSSession : [mail1.dorothy.local] Connecting to remote server mail1.dorothy.local failed with the following error
message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from
the destination computer. The content type is absent or invalid. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
Exception calling "GetComputerSite" with "0" argument(s): "The Specified directory object cannot be found."
At C:\Program Files\Microsoft\Exchange Server\V15\bin\ConnectFunctions.ps1:164 char:2
+     $localSite=[System.DirectoryServices.ActiveDirectory.ActiveDirectorySite]::GetC ...
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ActiveDirectoryObjectNotFoundException
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: mail1.dorothy.local
VERBOSE: Connecting to mail1.dorothy.local.
New-PSSession : [mail1.dorothy.local] Connecting to remote server mail1.dorothy.local failed with the following error
message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from
the destination computer. The content type is absent or invalid. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
Randy Cheek

Good Morning,
Log into the server with an account that has appropriate Exchange rights, not a local account.
Note: By default - Domain Admins don't have Exchange rights.
Dame Luthas, ITILv3, MCSE Messaging 2013, MCSA, MCITP
My Technical Blog: http://thelifestrategist.wordpress.com
Discipline is the Difference between Goals and Accomplishments
If this post is useful, please hit the green arrow on the left & if this is the answer hit "mark as answer"

TMS 14.3.2 - No HTTPS Response from devices (again) - Looks like permissions issues (but possibly down to NetBIOS over TCP/IP)

Hi All,
Sometime ago I posted regarding an issue I was seeing on our TMS , where most of the remote devices seemingly showed up as loosing remote connection (no HTTPS Response - https://supportforums.cisco.com/discussion/12290956/tms-lost-https-communciation-devices-not-really). However, I could not figure out the root cause of the error, and now I have managed to break things again - probably due to a Java upgrade which broke TMSPE (see https://supportforums.cisco.com/discussion/12404166/looks-latest-update-java-8-update-31-will-break-tmspe-11).
However, I thought I would look at little more closely this time to see if I could figure out the problem.
I am seeing a lot of entries in the Security Log in TMS that seem to indicated that my the account used from a TMSPE connection has a bad or invalid password (this is set in "Administrative Tools --> Configuration --> Provisioning Extension Settings", but this password is correct (I can log into TMS with this account, and reset and restarted services etc).
The computer attempted to validate the credentials for an account.
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account: tmspeconnect
Source Workstation: TMS
Error Code: 0xc0000064
and
An account failed to log on.
Subject:
Security ID: IIS APPPOOL\TMSNet40AppPool
Account Name: TMSNet40AppPool
Account Domain: IIS APPPOOL
Logon ID: 0x214b6
Logon Type: 8
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: tmspeconnect
Account Domain: TMS
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
Process Information:
Caller Process ID: 0x860
Caller Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Network Information:
Workstation Name: TMS
Source Network Address: 127.0.0.1
Source Port: 62114
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
I just wanted to check this like file/folder NTFS permissions, or any specific IIS permission . Is there a list of NTFS folder permissions for which the TMS required with regard to the "IIS APPPOOL", and perhaps what may need to be check in IIS?
Oddly, the error list above refers the our "TMSPEConnect" account from the TMS domain, however this is incorrect - TMS is the machine name. Still we ARE seeing similar error which reference the actual domain name, such as:
An account failed to log on.
Subject:
Security ID: IIS APPPOOL\TMSNet40AppPool
Account Name: TMSNet40AppPool
Account Domain: IIS APPPOOL
Logon ID: 0x49e55
Logon Type: 8
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: tmspeconnect
Account Domain: mydomain
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0xb18
Caller Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Network Information:
Workstation Name: TMS
Source Network Address: 1.1.1.1 (changed external IP)
Source Port: 47620
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Idea welcome.
Cheers
Chris

Hi all,
After a long a fraught weekend trying to fix things, I am not that much further on, but I am beginning to understand what it isn't........ I think :(
It looks as though the "DatabaseScanning" service, or anything that runs under the credentials of the "nt authority\network service" seems to have a problem.
The Audit log show lot of entries where services such as"TMSWebPublic" running under the ISS Application pool "tmsnet40apppool", and actions launched under our own credential appear to communicate just fine with the device, only for the 'network service' to time out the connection a short while later. The same goes for some (not all) of the Phone book updates, which also looks as though it runs under the credentials of the 'Network Service' account.
26/01/2015 08:30:54
nt authority\network service
Update
System
our-ctrl1
System status
NoResponse
TMSDatabaseScannerService
26/01/2015 08:30:54
nt authority\network service
Update
System
our-ctrl1
Connection status
NoHTTPSResponse
TMSDatabaseScannerService
26/01/2015 08:29:06
tmsnet40apppool
Update
System
our-ctr1l
System status
Idle
TMSWebPublic
26/01/2015 08:29:06
tmsnet40apppool
Update
System
our-ctrl1
Connection status
OK
TMSWebPublic
However, I still don't know at this point is this is related to the actual TMS front end, something to do with the domain and policies that have been applied to TMS, or the actual database, or even just communication with the back end database??? I did try running the services under a domain user (service) account, but then ran into other issues as I couldn't log into TMS.
BTW, removing TMS, and IIS and reinstalling did fix my second issue relating to the 'Communication Errors'.
Chris

How to see http response from an axis web service call (Eclipse)

Hello,
I would like to see the raw http response which is returned from web service calls. I have a dynamic web project in Eclipse which uses a local instance of Tomcat 6. I'm using all of the default setting for a top-down web service generated from a WSDL file. I've generated the client using the built-in "generate client" using default settings.
I've tried using the Eclipse plugin TCP/IP monitor and apache's TCPMON, but I am only able to see the http request, not the http response returned from the web server I am querying.
I've seen some sparse documentation outlining how to use logging handlers and a client-config.wsdd file, but I haven't been able to get that working.
So to recap, I'm looking for a way to view raw http responses using a web service client and server generated from a WSDL file in eclipse. I don't mind creating a new project using different code-generating libraries if someone has an easy way to do this using a different configuration.
Thanks very much,
Craig

908794 wrote:
Hello,
I would like to see the raw http response which is returned from web service calls.Why the HTTP response? Isn't the soap message body enough? If it is, you probably want to check out SoapUI.
A simple google query for "apache axis2 http response" also return this article:
http://blogs.cocoondev.org/dims/archives/004668.html
And finally, you did go through the Axis2 website right? It has a wiki with a rather staggering amount of articles in there.
http://wiki.apache.org/ws/FrontPage/Axis2/

Received HTTP response code 404 : Not Found

I am attempting to pass a file through XI into an IDoc to ECC. I have tested the mapping, and that works fine. I have also tested the configuration in the integration builder and it seems to be fine. However, when the file is picked up by XI from the directory, processed by XI, and then sent to ECC, an error occurs in the runtime workbench:
Transmitting the message to endpoint http://server:port/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 404 : Not Found.
The error leads me to believe that the system cannot be found, or there is a privelage issue with the service user attempting to log onto ECC. However I believe I have set up the RFC connection correctly, and the service user should be fine.
Does anyone know what may be causing this? I am using the IDoc adapter for the reciever communication channel. I have set the RFC destination (and tested it in SM59, works fine) and the port (I assume this is the port in WE21?). Not sure where to look...

Being that the error says:
Transmitting the message to endpoint http://server:port/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 404 : Not Found.
I am trying to understand what this means. Can anyone explain to me why the message is getting sent to this address? I assume that the AFW is coming into play because I am using the IDoc adapter, hence the adapter framework. Is this true? Should the AFW be showing up, or do you think there is another issue?
Mainly I want to know if this is more of a basis issue, or a configuration problem with the interface in XI?

HTTP response error :Connection reset

Hi all,
I am getting following error in log while sending message to the trading partner and the main problem is that once this error comes then after that I am not able to send any more message to any of my Trading Partners. Even if I try to send message to any other Trading Partner, nothing comes in the B2B log and report as well. After restarting the B2B I am able to send message again to other Trading Partners.
Can anyone please tell the reason for getting this error? I also want to know that after getting this error once, why am I not able to send message to any Trading Partner?
2008.12.12 at 06:41:07:647: Thread-13: B2B - (WARNING)
Message Transmission Transport Exception
Transport Error Code is OTA-HTTP-SEND-1006
StackTrace oracle.tip.transport.TransportException: [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.
at oracle.tip.transport.TransportException.create(TransportException.java:91)
at oracle.tip.transport.basic.HTTPSender.send(HTTPSender.java:627)
at oracle.tip.transport.b2b.B2BTransport.send(B2BTransport.java:311)
at oracle.tip.adapter.b2b.transport.TransportInterface.send(TransportInterface.java:980)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1744)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1147)
at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:137)
at oracle.tip.transport.basic.jms.JMSMonitor.processMessages(JMSMonitor.java:610)
at oracle.tip.transport.basic.jms.JMSMonitor.run(JMSMonitor.java:236)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at com.sun.net.ssl.internal.ssl.InputRecord.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_az.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_az.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_ax.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.j(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA12275)
at java.io.ByteArrayOutputStream.writeTo(ByteArrayOutputStream.java:112)
at HTTPClient.HTTPConnection.sendRequest(HTTPConnection.java:3018)
at HTTPClient.HTTPConnection.handleRequest(HTTPConnection.java:2843)
at HTTPClient.HTTPConnection.setupRequest(HTTPConnection.java:2635)
at HTTPClient.HTTPConnection.Post(HTTPConnection.java:1107)
at oracle.tip.transport.basic.HTTPSender.send(HTTPSender.java:590)
... 8 more
2008.12.12 at 06:41:07:647: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send Error in sending message
2008.12.12 at 06:41:07:648: Thread-13: B2B - (INFORMATION) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Request Message Transmission failed
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Enter
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Leave
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.
Connection reset
2008.12.12 at 06:41:07:651: Thread-13: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.12.12 at 06:41:07:652: Thread-13: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2008.12.12 at 06:41:07:656: Thread-13: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2008.12.12 at 06:41:07:656: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:notifyApp retry value <= 0, so sending exception to IP_IN_QUEUE
2008.12.12 at 06:41:07:658: Thread-13: B2B - (DEBUG) Engine:notifyApp Enter
2008.12.12 at 06:41:07:663: Thread-13: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = null
2008.12.12 at 06:41:07:663: Thread-13: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>0AF77A6111E29ED374E000001BDE3D60</b2bMessageId>
<errorCode>AIP-50079</errorCode>
<errorText>Transport error: [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.
Connection reset</errorText>
<errorDescription>
<![CDATA[Machine Info: (dys094w004)
Transport error: [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.
Connection reset ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2008.12.12 at 06:41:07:692: Thread-13: B2B - (DEBUG) Engine:notifyApp Exit
2008.12.12 at 06:41:07:693: Thread-13: B2B - (DEBUG) DBContext commit: Enter
2008.12.12 at 06:41:07:696: Thread-13: B2B - (DEBUG) DBContext commit: Transaction.commit()
2008.12.12 at 06:41:07:696: Thread-13: B2B - (DEBUG) DBContext commit: Leave
2008.12.12 at 06:41:07:696: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequest Exit
2008.12.12 at 06:41:07:696: Thread-13: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage:
***** REQUEST MESSAGE *****
Please help.
Thanks & Regards,
Anuj Dwivedi

Hi Sinkar,
Thanks for the reply. I confirmed it with my Trading Partner and their server is not running but still I want to know that why am I not able to send message to any other Trading Partner after getting this error once. And if I restart the server, it again acts normally and I am able to send message to other Trading Partners.
SSL is configured properly because I was able to communicate with this Trading Partner earlier when their server was up.
We are working on 10.1.2.3.0 with 7457066 MLR 5 patch. Please guide if any other patch required.
Thanks for the help.
Warm Regards,
Anuj Dwivedi

How to get the HTTP response body if the body is a malformed XML document

Hi,
I am using HTTP service with resultFormat = "e4x" set. What i
get in response is a malformed XML document in
some cases. Usually HTTPService throws a FaultEvent with the
fault detail set to faultCode:Client.CouldNotDecode
faultString:'Error #1091' or some other Error #1085 and so.
My client tries to log these errors on the server by using
another HTTP service again. But i would like to know
in the client code during run time what exact XML response
came in the first HTTP response.
How do i retrieve this information?
thanks,
Sunil

service capture or charles debug proxy can do the job.
flex builder 4 is rumored to include a traffic sniffer as
well, but that's next year.

HTTP response contains status code 404 ...

Hello,
My system sceanrio is:
R/3 -> idoc -> XI-1 -> xi adapter -> XI-2 -> idoc -> R/3.
When the message sent, I get a red flag in SXMB_MONI transaction of "XI-1" system :
'HTTP response contains status code 404 with the
description Not Found'
Here is the SOAP adapter of the Call Adapter:
=============================================
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b> 404 &nbsp Not Found</b></font></td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP J2EE Engine/6.40 </b></font></td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <br><br><br><br><br><br> <p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b> The requested resource does not exist.</b></font></p> <p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table><tr><td valign="top"><b> Details:</b></td><td valign="top"><PRE>Go to <A HREF="/" target="_parent">main page</A> of this application!</PRE></font></td></tr></table></font></p> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 404 with the description Not Found XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2005-04-12T06:52:37Z" wasRead="false">
<SAP:Engine type="IS">is.50.weaver</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
<SAP:MessageId>550806B7-DEED-FF42-96B1-6F33852373F1</SAP:MessageId>
<SAP:Info>MATMAS.0000000000214059:20050412085231</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2005-04-12T06:52:37Z" wasRead="false">
<SAP:Engine type="IS">is.50.weaver</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>550806B7-DEED-FF42-96B1-6F33852373F1</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:IDocInbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>200</SAP:MANDT>
<SAP:DOCREL>46C</SAP:DOCREL>
<SAP:DOCNUM>0000000000214059</SAP:DOCNUM>
<SAP:DIRECT>1</SAP:DIRECT>
<SAP:IDOCTYP>MATMAS04</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>MATMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPDEV</SAP:SNDPOR>
<SAP:SNDPRN>LOGDEV200</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>XI-TEST</SAP:RCVPOR>
<SAP:RCVPRN>LOGXID700</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL>20050412085231</SAP:SERIAL>
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>30</SAP:STATUS>
<SAP:OUTMOD>2</SAP:OUTMOD>
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>2005-04-12</SAP:CREDAT>
<SAP:CRETIM>08:52:31</SAP:CRETIM>
<SAP:ARCKEY />
</SAP:IDocInbound>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20050412</SAP:Date>
<SAP:Time>085237</SAP:Time>
<SAP:Host>weaver</SAP:Host>
<SAP:SystemId>XID</SAP:SystemId>
<SAP:SystemNr>50</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>MSSQL</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>014</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>ANNA</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>002</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal>XBTO3___0000</SAP:QIdInternal>
<SAP:CommitActor>A</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="700">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">DF010AB7129C425B7035011D</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID">DF013D07020C425B70300B0A</SAP:EOReferenceInbound>
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>16517</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>16517</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>16527</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>IDOC</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:RandomNumber>71</SAP:RandomNumber>
<SAP:AckStatus>071</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.471</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.471</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.471</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.642</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.642</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.674</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.674</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.814</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.814</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.939</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.939</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.971</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.971</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>B0E25658819A3AE888B48BAD55537C5E</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>DEV</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>XIT</SAP:ToServiceName>
<SAP:ToInterfaceName>MATMAS.MATMAS04</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">XIT</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">GeneratedReceiverChannel_XI</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:AdapterName>
<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0</SAP:MessageProtocolVersion>
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP</SAP:TransportProtocol>
<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">1.0</SAP:TransportProtocolVersion>
<SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:Attribute>
<SAP:Name>addressingMode</SAP:Name>
<SAP:Value>url</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>authenticationModeBasicAnon</SAP:Name>
<SAP:Value>anonymous</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>host</SAP:Name>
<SAP:Value>victor</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>httpDestination</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>isMessageSecurity</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonClient</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonLanguage</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonPassword</SAP:Name>
<SAP:Value isPassword="true" encryption="hw">AQ==</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonUser</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>passHopList</SAP:Name>
<SAP:Value>1</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>path</SAP:Name>
<SAP:Value>/sap/xi/engine?type=entry</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>56000</SAP:Value>
</SAP:Attribute>
</SAP:AdapterTypeData>
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 700</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = ANNA</Trace>
<Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 550806B7DEEDFF4296B16F33852373F1</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0010</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0010</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 700</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = ANNA</Trace>
<Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO3___0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 700</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = ANNA</Trace>
<Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">Interface Mapping urn:XI_to_XI_Simulation MATMAS04_MATMAS04</Trace>
<Trace level="1" type="T">*** APPLICATION TRACE TRUNCATED (for more details see LogViewer)***</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="1" type="T">processing the outbound binding</Trace>
<Trace level="1" type="T">search outbound bindings</Trace>
<Trace level="1" type="T">outbound bindings found</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="T">Sender: Header mapped to</Trace>
<Trace level="1" type="T">Party =</Trace>
<Trace level="1" type="T">Agency =</Trace>
<Trace level="1" type="T">Scheme =</Trace>
<Trace level="1" type="T">Service = DEV</Trace>
<Trace level="1" type="T">Receiver: Header mapped to</Trace>
<Trace level="1" type="T">Party =</Trace>
<Trace level="1" type="T">Agency =</Trace>
<Trace level="1" type="T">Scheme =</Trace>
<Trace level="1" type="T">Service = XIT</Trace>
<Trace level="1" type="T">Party denormalization: sender</Trace>
<Trace level="1" type="T">Sender target scheme =</Trace>
<Trace level="1" type="T">Sender target agency =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Party denormalization: receiver</Trace>
<Trace level="1" type="T">Receiver target scheme =</Trace>
<Trace level="1" type="T">Receiver target agency =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active

Hi,
The 'Communication Channel' in Integration Builder was not configured right in the 'Service Number' field. There was a J2EE port instead of HTTP port.
J2EE port: 5<instance number>00
HTTP port: 80<instance number>
Good luck to everyone,
Dimitry

HTTP Response code 404 - RFC Adapter des not connect to Integration engine

Hi,
I seem to have problem with XI Integration engine. My integration process does not go beyond adapter engine and it fails with the following error,
Begining of the erorr report -
2006-01-23 13:35:53 Success RFC adapter received sRFC for ZSCEN2_XI from <sysno>/<client>. Attempting to send message synchronously
2006-01-23 13:35:54 Success Application attempting to send an XI message synchronously using connection AFW.
2006-01-23 13:35:55 Success Trying to put the message into the call queue.
2006-01-23 13:35:55 Success Message successfully put into the queue.
2006-01-23 13:35:55 Success The message was successfully retrieved from the call queue.
2006-01-23 13:35:55 Success The message status set to DLNG.
2006-01-23 13:35:55 Error Returning synchronous error notification to calling application: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error Transmitting the message using connection http://<host>:55300/sap/xi/engine?type=entry failed, due to: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error The message status set to FAIL.
2006-01-23 13:35:55 Error Returning to application. Exception: Received HTTP response code 404 : Not Found
end of error report -
and the runtime workbench does not connect to Integration engine and fails with the following error,
begin error report -
javax.ejb.CreateException: Unable to log on to system XID in language en with user XIRWBUSER
     at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:374)
     at com.sap.aii.mdt.server.IntegrationEngineHomeImpl10.create(IntegrationEngineHomeImpl10.java:185)
     at com.sap.aii.mdt.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:56)
end of report -
Have anyone experienced the same issue?. Are we missing some post installation configuration?.
Thanks in advance
Regards,
Arul

HI Anulraja,
Your Adapter Engine searches the pipeline url of the integration engine from the SLD.
Check the Bussiness System in Sld , which you'll have defined for XI Server.
It should have ROLE : Integration Server And
pipeline url: http://ux0800:55300/sap/xi/engine?type=entry
should be this if your http port is 55300.
Check if this url is right in SLD-Bussiness System.
You can check the exact http port in transaction sxmb_adm.
Go to Integration engine configuration and then click on check icon(F7).
It should match with that provided in the BS in SLD.
By default it should be 8000.
Check all these things and then try.
Regards,
Yomesh

Error Transmitting the message to endpoint -Received HTTP response code 401

Hello Experts,
I am having a SOAP to Proxy scenario. We are using HTTPS without client Authentication.
Everything is running fine and well set on DEV system. After transporting to Test system, i am getting error as :
Error Transmitting the message to endpoint http://host:port/sap/xi/engine?type=entry using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized.
I get HTTP 200 Ok response in my soap client but the message is not reaching to Integration Engine. It is failing with above error. On CC monitoring for SOAP adapter it shows call completed successfully. But when I use the mesage ID from CC monitoring in Message monitoring i get the error as shown above in Audit log.
I have checked for Roles attached to my user on DEV and Test systems , I have same roles on both systems.
Any inputs to solve this problem will be very helpful to me. Let me know which service users i need to check for this issue?
Thanks in Advance,
XI Queries.

Hi Pinang,
Thanks for input.
1) Check Role -SAP_XI_APPL_SERV_USER is there in XIAPPLUSER or not.
->Done. Its Ok.
2) check tyour port entry is like J2EE port 5<System no> or not.
->Done. Its Ok.
3) If the error in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
->This note refers in case it happens with high load. I am just sending a small request and no one else is using / testing this interface. So no high load.
4) Check password for user XIISUSER
-> Basis team said they checked for all Xi users and they are not locked.
5) Check password for user XIAFUSER
-> Basis team said they checked for all Xi users and they are not locked.
Any other hints will be helpful.
Kind Regards,
Xi Queries.

Connection AFW failed, due to: Received HTTP response code 500

Hi,
I have tried to develop a file to file scenario in XI 3.0. The Sendor File adapter is reading the file but the message is not getting transfered to Integration engine.
The audit log for the message is as follows:
2005-05-07 04:10:24 Success Channel FileSendor: Send binary file "/tmp/xi_input.dat". Size 324 with QoS EO
2005-05-07 04:10:24 Success Application attempting to send an XI message asynchronously using connection AFW.
2005-05-07 04:10:24 Success Trying to put the message into the send queue.
2005-05-07 04:10:24 Success Message successfully put into the queue.
2005-05-07 04:10:24 Success The application sent the message asynchronously using connection AFW. Returning to application.
2005-05-07 04:10:24 Success Confirmation mode test found. File will be resent next time
2005-05-07 04:10:24 Success The message was successfully retrieved from the send queue.
2005-05-07 04:10:24 Success The message status set to DLNG.
2005-05-07 04:10:24 Error Transmitting the message to endpoint http://nadcp517:8020/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500..
Any suggestion...

hi
This problem comes due to the post installation steps might be at the time of post installation some wrong might be done.
step1 : In sxmb_adm configure the integration server by giving the path as http://<host>:<abapport>/sap/xi/engine?type=entry
step 2 : Check ur business system created at the time of post installation there u need to main the path as it as above.
Reward points if useful,
Regards,
Srinivas.D

Received HTTP response code 500 with acknowledgment

Hello,
This is my process : R/3 (Idoc) -> XI -> 3rdParty(CSV).
I use R/3 4.6C and XI 3.0 SP10
This work fine but there is a problem with the acknowledgment :
Transmitting the message to endpoint http://<server>:8000/sap/xi/engine/entry?action=execute using connection AFW failed, due to: Received HTTP response code 500..
I use this Weblog : /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
and all I can find in this forum.
What can I do ?
Thanks
Regards
Message was edited by: Christophe DUMONT

HTTP 500 is an error caused at the Web Server side. Any http connection happens in 4 steps:
1) Obtain the IP address from the URL - provied by DNS
2) Open Ip Socket for that IP
3) Use this socket to write data
4) Receive data stream back from the server.
This data stream which is passed by the server has status codes. If there is a status code 500, this is trapped only at the last level and client is not able to resolve the status.
You would want to look at the 4 points of faliure mentioned above. And it would help if u get someone on the Web Server side to look at the server logs. These logs are more descriptive and will provide a clue to set things right.
let us know if u are able to resolve the issue.

Log http response

Similar Messages

Maybe you are looking for