Http server code 503 reason Service Unavailable explanation Service Unavail

Hi all
I am trying to send data to a HTTP SITE.
I am getting the following error.
Could somebody guide me how to solve this.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Oxalate</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>503</SAP:P1>
<SAP:P2>Service Unavailable</SAP:P2>
<SAP:P3>Service Unavailable</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 503 reason Service Unavailable explanation Service Unavailable</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thankyou

Same errors are comming up.
Could not do a RFC connection to website.

Similar Messages

HTTP server code 404 reason Not Found explanation Not Found

Hi all
I am facing this error "HTTP server code 404 reason Not Found explanation Not Found" during a asynchronous xml message sent to a buisiness service
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>404</SAP:P1>
<SAP:P2>Not Found</SAP:P2>
<SAP:P3>Not Found</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 404 reason Not Found explanation Not Found</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
could you provide an explanation on this error.

Hi
Go through this
Error: 404 Not Found
Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404
404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.
**********Reward points if usefulll.**********

Simple HTTP Receiver - HTTP server code 405 reason Not Allowed explanation

Hi, I am using simple HTTP Receiver to receive the XML file from the below url http://www.bank-ua.com/export/currrate.xml
But receiving the below error in SXMB_MONI
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>405</SAP:P1>
<SAP:P2>Not Allowed</SAP:P2>
<SAP:P3><html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.4.1</center> </body> </html></SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 405 reason Not Allowed explanation <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.4.1</center> </body> </html></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Initially the same URL was working could you advice what to change to make this working?
Thanks,
Dhill

Hi Senthil,
There is a way, you can expose the function module HTTP_GET as an rfc-enabled FM and use it to call the webservice. Here is a POC I made before:
Proof of Concept: An Alternative HTTP GET using a Remote-Enabled Version of the Function Module HTTP_GET
Another is to create a UDF that uses an HTTP Client class to call the webservice.
Regards,
Mark

HTTP server code 400 reason Bad Request explanation Bad Request

hello everybody,
i'm working with SAP PI 7.1
I designed my interface IDOC-PI-HTTP.
when i send idoc from R3 i see this message in PI monitor:
HTTP server code 400 reason Bad Request explanation Bad Request
i tried to configure a HTTP port in SM59 and use it in my Communication Channell, but when i test connection i have same error.
I'm using a https address.
have you any suggestion?
thanks
Alex

Hello,
I already verify with 3 party developer. He confirmed me he is expecting i send data by POST.
Yes, but how does the HTTP Body looks like?See sample webservice below:
http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx?op=GetQuickQuote and scroll down to see how an HTTP POST looks like
Content type is a String
Normally, the content-type for an http post is application/x-www-form-urlencoded. But then, you need to know the prolog and epilog in the http body.
he gave me a url address https://.......
where i need set the parameter HTTPS??
https (http with ssl) is configured in mm59 type G (external server). To enable https, you need to select the SSL folder in which you have installed the CA (certificate authority) certs. Make sure that once you have installed the CA certs, you have performend an ICM Restart.
Hope this helps,
Mark
Edited by: Mark Dihiansan on Jul 25, 2011 11:21 AM

Http server code 401 reason Unauthorized explanation Unauthorized

Hello to you all,
I have a SRM-XI-SUS scenario and I try to connect to SUS with XI but I am facing the follwoing issue:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="<b>PLAINHTTP_ADAPTER</b>"><b>ATTRIBUTE_SERVER</b></SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>Unauthorized</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack><b>Http server code 401 reason Unauthorized explanation Unauthorized</b></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can someone guide me towards a solution?
Kind regards,
Kamran

I am not intimate with the SRM-SUS integration via XI, but based on the business scenario configuration guide (https://service.sap.com/~sapidb/011000358700002897402004E/ServiceProcurementNEW.pdf) it seems that communication between SRM and SUS via XI takes place via proxies. Assuming that's what you're trying to do, to communicate to SUS via proxies, you would need to use the adapter type (XI). The communication is still technically over HTTP, but using the XI messaging protocol.
The use of an sm59 destination is optional. The XI type communication channel allows addressing types of "URL Addressing" or "HTTP Destination". If you choose the latter, you would need a sm59 destination of type H and then refer to it from the channel.
Try using a XI type receiver channel instead. If you run into additional problems, check the "XI Settings" section of the guide above.
Regards,
Jin

HTTP server code 500 reason Internal Server Error explanation Error during

Hi,
I am trying to connect to SAP TM (Tranportation Management) System using HTTP adapter using PI 7.0.The scenario is
ECC ->PI->SAP TM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP TM on PI. I have encountered the following error after executing the scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Kiran

Error during parsing of SOAP header
Can you mention what are the settings done in Receiver HTTP channel.....the request that you send to target is not in proper format.
One reason could be incorrect Content Type.....is it text/XML ?
Regards,
Abhishek.

HTTP server code 500 reason Internal Server Error

HI,
I am getting following error in Call Adapter
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Internal Server Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Internal Server Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have a Business system that is sending the material master data to a different Business System via XI. The message is received by XI correctly. XI correctly performs the transformation and identifies the message interface and selects correct receiver for the message. XI communicates with the receiving business system via the appropriate communication channel.
The message "fails" in the receiving system with the following error:
HTTP server code 500 reason Internal Server Exception explanation Error parsing of SOAP header.
The channel is using HTTP Adapter type, and i cross checked the communication channel details like Addressing type, target host, service number, path, user name, user password.......each and every detail is correct.
Please help me out to find the solution to the problem.
Points will be gladly awarded.
Edited by: Ashish Soni on Sep 24, 2008 9:02 PM

try sending the same XML message picking from moni and check whether you are getting same error or not?
if you get same error then check at web server for logs there you can find exact error.

Http server code 401 reason Unauthorized

Hi,
I am trying to setup a scenario of sending an IDOC from R/3 to XI and then sending it further to a 3rd party program using the HTTP Channel.
If I go to transaction IDX5 in XI, I can see my IDOC sitting there as Inbound. When I check the error message on it, I get the message "Http server code 401 reason Unauthorized explanation Unauthorized" Also further along on the screen it says that the error category is "PLAINHTTP_ADAPTER" and Error ID is "ATTRIBUTE_SERVER".
Can someone guide me towards a solution?
Thanks in Advance!
Miguel

Hi Rekha,
I have checked the settings and they appear to be correct.
Here is a piece of the trace of the monitor where the error occurs:-
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Plain HTTP Adapter Outbound----</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_HTTP_PLAIN_OUTBOUND-ENTER_PLSRV">
<Trace level="3" type="T">Quality of Service EO</Trace>
<Trace level="1" type="T">Get XML-Dokument from the Message-Objekt</Trace>
<Trace level="2" type="T">HTTP-Destination : SBO_ITK</Trace>
<Trace level="3" type="T">Server pgsap09.sap.pg.co.za</Trace>
<Trace level="3" type="T">Service-Nr. 80</Trace>
<Trace level="3" type="T">URL /SBOWebService/xi</Trace>
<Trace level="3" type="T">~request_method POST</Trace>
<Trace level="3" type="T">~server_protocol HTTP/1.0</Trace>
<Trace level="3" type="T">accept: /</Trace>
<Trace level="3" type="T">content-type: text/xml</Trace>
<Trace level="3" type="T">msgguid: 2F7389425DBE1711E100000082010B5A</Trace>
<Trace level="3" type="T">service: DR0</Trace>
<Trace level="3" type="T">interface namespace: http://sap.com/xi/SBO</Trace>
<Trace level="3" type="T">interface name: MasterDataFunctionModule__vendorMasterUpdate</Trace>
<Trace level="3" type="T">quality of service: EO</Trace>
<Trace level="3" type="T">Header-Fields</Trace>
<Trace level="3" type="T">Prolog conversion Codepage: UTF-8</Trace>
<Trace level="3" type="T">Epilog conversion Codepage: UTF-8</Trace>
<Trace level="3" type="T">content-length 3273</Trace>
<Trace level="2" type="T">HTTP-Response :</Trace>
<Trace level="2" type="T">Code : 401</Trace>
<Trace level="2" type="T">Reason: Unauthorized</Trace>
<Trace level="2" type="T">Code : 401</Trace>
<Trace level="2" type="T">Reason: Unauthorized</Trace>
</Trace>
From this it appears that it is complaining about the user name into the external program, although when I do a test connection in SM59, I get a positive response?
Thanks,
Miguel

HTTP server code 405 reason Method Not Allowed exception

I get a 405 method not allowed exception in synchronous http receiver. However I have verified that a http post is expected by the receiver system.
Is there anythin else I could check or what could cause the error?

Hi,
what is the receiving system? Usually, you get this error when you try to do POST on static page. In the HTTP header of response you should get the list of allowed methods. You can try to check this list. I would contact an administrator of that system if he can check logs for errors.
Cheers

Http server code 403 in SXMB_MONI

*Hello All,*
*When I am posting an IDoc from R/3 to XI I get the following in SXMB_MONI in the Call Adapter.*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>403</SAP:P1>
<SAP:P2>Forbidden</SAP:P2>
<SAP:P3>Forbidden</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 403 reason Forbidden explanation Forbidden</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Could anyone please comment on what could be the possible reason and how can we handle this.
Thanks in Advance..!!
Regards,
Smita

Hi,
Check this
Error: HTTP 403 Forbidden
Description: The server understood the request, but is refusing to fulfill it
Possible Tips:
Path sap/xi/engine not active
HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
Because of Inactive Services in ICF Go to SICF transaction and activate the services. Refer SAP Note -517484
Error in RWB/Message Monitoring- because of J2EE roles Refer SAP Note -796726
Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. Because of the URL is incorrect or the adapter is not correctly deployed.
Regards
Seshagiri

Error executing RDS command. Status Code : 503 , Reason : Service Unavailable

Hi,
I am being trying to connect a Flex desktop application with a Java application running in Tomcat (6.0.29), and I get this error message when trying to use the Data wizard to connect with Blaze DS.
I have read all the tutorials and everything looks good from the server side. This is what appears in the server log:
2011-01-27 16:02:33,030 [ INFO] - RemotingDestinationExporter - Created remoting destination with id 'accounts'
2011-01-27 16:02:33,046 [ INFO] - RemotingDestinationExporter - Remoting destination 'accounts' has been started started successfully.
2011-01-27 16:02:33,046 [ INFO] - RemotingDestinationExporter - Created remoting destination with id 'customers'
2011-01-27 16:02:33,046 [ INFO] - RemotingDestinationExporter - Remoting destination 'customers' has been started started successfully.
2011-01-27 16:02:33,061 [ INFO] - FrameworkServlet - FrameworkServlet 'flex': initialization completed in 3887 ms
2011-01-27 16:02:50,813 [ INFO] - MessageBrokerHandlerAdapter - Channel endpoint my-amf received request.
2011-01-27 16:43:42,897 [ INFO] - MessageBrokerHandlerAdapter - Channel endpoint my-amf received request.
(The last two lines appears when I put the AMF channel's URI in a browser).
Below is what appears in the Event log from Eclipse.
java.lang.RuntimeException: java.lang.RuntimeException: RDS server message:
Error executing RDS command. Status Code : 503 , Reason : Service Unavailable
at com.adobe.flexbuilder.services.j2eeservice.J2EEServicePage.setVisible(J2EEServicePage.jav a:149)
at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1171)
at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1149)
at org.eclipse.jface.wizard.WizardDialog$5.run(WizardDialog.java:1138)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1136)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:830)
at com.adobe.flexbuilder.DCDService.ui.wizard.ServiceWizardDialog.nextPressed(ServiceWizardD ialog.java:93)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at com.adobe.flexbuilder.DCDService.ui.wizard.ServiceWizard.show(ServiceWizard.java:190)
at com.adobe.flexbuilder.DCDService.ui.wizard.ServiceWizard.createService(ServiceWizard.java :152)
at com.adobe.flexbuilder.dcrad.views.ServiceExplorerView$1.handleEvent(ServiceExplorerView.j ava:528)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012)
at org.eclipse.swt.widgets.Link.wmNotifyChild(Link.java:1004)
at org.eclipse.swt.widgets.Control.wmNotify(Control.java:4877)
at org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:1757)
at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:4507)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4000)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2314)
at org.eclipse.swt.widgets.Link.callWindowProc(Link.java:172)
at org.eclipse.swt.widgets.Widget.wmLButtonUp(Widget.java:1917)
at org.eclipse.swt.widgets.Control.WM_LBUTTONUP(Control.java:4301)
at org.eclipse.swt.widgets.Link.WM_LBUTTONUP(Link.java:842)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3982)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2411)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3501)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: java.lang.RuntimeException: RDS server message:
Error executing RDS command. Status Code : 503 , Reason : Service Unavailable
at com.adobe.flexbuilder.services.j2eeservice.J2EEServicePage.initialize(J2EEServicePage.jav a:187)
at com.adobe.flexbuilder.services.j2eeservice.J2EEServicePage.setVisible(J2EEServicePage.jav a:136)
... 61 more
Any help wolud be appreciated.
Thanks

Hi There,
I am getting the same error. can anyone tell me what could be problem?

Error: Server returned HTTP response code: 503

Hi All,
I am trying to import a web service WSDL (which is not a BPEL or ESB service) on creating a partnerlink in BPEL. I am getting following error while importing,
"java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
Does anyone know the cause and fix for this issue.
Thanks,
Rizwan

Hi,
Have u tried to open the wsdl url in browser. If it is giving the same error than u have to look into the server hosting this service.
The HTTP response code 503 says: The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.

Server returned HTTP response code: 503 for URL

I was deploy my webcenter application and was working fine, but I updated my Webcenter Framework plugin in Jdeveloper to version 11.1.2.0.091030.1847 and now when I try deploy my application error 503 occurr:
[05:06:55 PM] Weblogic Server Exception: weblogic.deploy.api.internal.utils.DeployerHelperException: The source 'C:\Users\nmaia\AppData\Local\Temp\app8.ear' for the application 'app8#V2.0' could not be loaded to the server 'http://it7-srv-lnx-wcenter:7002/bea_wls_deployment_internal/DeploymentService'.
Server returned HTTP response code: 503 for URL: http://it7-srv-lnx-wcenter:7002/bea_wls_deployment_internal/DeploymentService
[05:06:55 PM] See server logs or server console for more details.
[05:06:55 PM] weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260041]Unable to upload 'F:\Desenvolvimento\JDev\Application8\deploy\app8.ear' to 't3://it7-srv-lnx-wcenter:7002'
[05:06:55 PM] #### Deployment incomplete. ####
[05:06:55 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
My Weblogic is version 11g(10.3), can anyone help me?
Thanks,

To solve my problemn I do these steps:
- Uninstall jdeveloper;
- Delete jdeveloper folder;
- Install Jdeveloper, version 11.1.1.2;
- Downloaded the plugin to Webcenter: http://download.oracle.com/otn/java/jdeveloper/1112/extensions/oracle.webcenter.framework_bundle.zip
- Remove my proxy from Jdev ( Tools -> Preferences -> Web Browser and Proxy)
And works fine.
Thks anyway.
[]'s

NetBeans with Tomcat Help - Server returned HTTP response code: 503

Hi all, I wasn't sure where to post this.. but anyhow, my problem is as follows:
Earlier in the day, I was able to successfully deploy my application to the Tomcat server by simply running the application from NetBeans. A couple of hours away from my computer and I returned to find this error when I ran my application:
In-place deployment at C:\xxx
Server returned HTTP response code: 503 for URL: http://localhost:8081/manager/deploy?config=file:/C:/xxx
C:\xxx\nbproject\build-impl.xml:634: Deployment error:
The module has not been deployed.
See the server log for details.
BUILD FAILED (total time: 36 seconds)
Any ideas on how to solve this? I've tried reinstalling NetBeans, Tomcat, reconfiguring NetBeans but to no avail. I should also mention that I am able to successfully deploy the application sometimes when I select a different server to deploy to. >_<
Gurus out there, please help..

Solved my own solution.. It had to do with one of my Hibernate named queries. =x Found that out when I switched to SUN Application Server for awhile. ^_^

Error in scenario "FILE to HTTP(with SSL)" - HTTP client code 110 reason.

Hi friends,
Our scenario is as follows:
We are trying to send XML file from our SAP-XI to external tool "COMMunix XC" (a multi-protocol EDI platform tool).
We have configured " FILE TO HTTP(with SSL)" scenario (trying to connect HTTPS/port)
1. We have created RFC destination of type G and refered the same RFC in Communication channel (Adapter type: HTTP)
2. We have send the SSL Server certificate to other party and ensure that they have imported at thier end.
3. We have included the certificates from other party in our SAP XI STRUST under SSL Client (Standard) node.
4. We have tried " CONNECTION TEST " in the RFC destination created in type G (in STEP 1) and it shows the GREEN TICK at bottom, no other message nor any error message
When we trigger the communication we recieve the error: HTTP client code 110 reason in SXMB_MONI.
Please let us know if we have missed out some step.
What does error message indicate,
Regards,
Rehan

Hi Rehan,
I see that the PROCTIMEOUT was already at a very high value.
Does this occur for messages of a particularly large size? If yes, you could increase the parameter
icm/HTTP/max_request_size_KB = 2097152
This would need to be done in the sender/receiver system as well as XI.
Otherwise you could try reproducing the issue and checking the dev_icm log in the work directory, or go to SMICM -> Goto -> Display trace file
check for errors like NIECONN_REFUSED or "no service for protocol HTTPS" which can often be related to this type of issue.
Kind regards,
Sarah

Http server code 503 reason Service Unavailable explanation Service Unavail

Similar Messages

Maybe you are looking for