Error 502

Hello, there!

I'm having a "502 Proxy Error. The ISA Server denied the specified Uniform Resource Locator (URL)" error while trying to call an XI webservice from MII 12.0 using a "WebService XI" action.

Both MII and XI are on the same machine. I'm using a WSDL file that was exported from XI and stored as a local file.

I suppose it is a network issue.

Does anyone have a clue?

Thanks a lot!

SAP Managed Tags:
SAP Manufacturing Integration and Intelligence

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

Eduardo,

What do the XI logs show?

Mike

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Mike,

They show nothing, as the call doesn't get there.

Thanks!

Also it is possible the name is not resolving. Try using localhost.

What do the NW error logs show?

Mike

Mike,

The name gets resolved as we can ping it normally.

This is what NW logs show us:

SOAP Invoke Error For http://<server>:<port>/XISOAPAdapter/MessageServlet?channel=:WBI_Sender:CC_SND_SOAP_fromSOAP_toFile_...

[EXCEPTION]

java.lang.Exception: Status (502): Proxy Error ( The ISA Server denied the specified Uniform Resource Locator (URL). )

at com.sap.lhcommon.webservice.SoapClient.invoke(SoapClient.java:114)

at com.sap.xmii.xacute.actions.xi.WebServiceXIAction.getOutgoingXml(WebServiceXIAction.java:91)

at com.sap.xmii.xacute.actions.webservice.WebServiceAction.RawInvoke(WebServiceAction.java:474)

at com.sap.xmii.xacute.actions.webservice.WebServiceAction.Invoke(WebServiceAction.java:511)

at com.sap.xmii.xacute.core.Action.Process(Action.java:72)

at com.sap.xmii.xacute.engine.TransactionEngine.Process(TransactionEngine.java:104)

at com.sap.xmii.xacute.core.ActionSequence.Process(ActionSequence.java:25)

at com.sap.xmii.xacute.engine.TransactionEngine.Process(TransactionEngine.java:104)

at com.sap.xmii.xacute.core.ActionSequence.Process(ActionSequence.java:31)

at com.sap.xmii.xacute.engine.TransactionEngine.Process(TransactionEngine.java:104)

at com.sap.xmii.xacute.engine.TransactionEngine.Execute(TransactionEngine.java:48)

at com.sap.xmii.servlet.Runner.service(Runner.java:173)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)

at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:100)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Eduardo,

It sounds like ISA security is the problem. Or perhaps the XI configuration?

Mike

Mike, it really looks like a security problem.

Our MII machine runs under a proxy, which is configured on the "System Administration" screen.

Now I've tried to access another WebService on another machine and I still get the same error.

Any ideas?

Hi Eduardo,

I am not sure what the fix would be. But the security admin for NW should have some ideas. This is getting out of my area of expertise.

Mike

I've changed the WSDL file to point to <soap:address location="http://IP_ADDRESS:PORT/XISOAPAdapter..."> instead of <soap:address location="http://localhost:PORT/XISOAPAdapter...">.

I still can't load the WSDL when I run MII Workbench from my machine, but it runs well on a workmate's machine!

It looks like a DNS problem or something like that...

If you have any ideas, I would highly appreciate it.

Thanks again!

Eduardo,

As a temporary fix, you could modify your local host file (or use the explicit IP address). If that fixes the problem, it most likely is a DNS problem. Some other things to look at relative to your workmate's machine and your own:

java version

browser settings

clearing caches (java console and java webstart)

Not sure any of them would make a difference, but won't take long to check.

Good luck,

Mike

Edited by: Michael Appleby on Nov 11, 2008 7:27 PM

Mike,

Adding an entry on hosts file pointing to my machine on MII worked fine!

Thanks a lot!

Still, though, we get a misterious error message (Error invoking WebServices action: null) when we call the XI WebService. The call works fine, but still we get this message.

This is NW log for this:

Error Invoking Web Service Action

[EXCEPTION]

java.lang.NullPointerException

at com.sap.xmii.xacute.actions.webservice.WebServiceAction.RawInvoke(WebServiceAction.java:477)