cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Axis Error Axis:error in invocation:(407)Proxy Authentication Reqired

Former Member
0 Kudos

Hi Group,

i use a SOAP-AXIS receiver adapter with none authentication.

While sending a message, all handlers are passed successfully up to HTTPSender.

Although i dont use a authentication, the adapter fails because of:

Error Axis: error in invocation: (407)Proxy Authentication Required

Below is the stack trace out of the adapter engine message monitoring.

-

-


Fehler Axis: error in invocation: (407)Proxy Authentication Required

Fehler MP: Ausnahme aufgetreten mit Grund (407)Proxy Authentication Required

Fehler Ausnahme aufgetreten beim Adapter-Framework: (407)Proxy Authentication Required

Fehler Zustellung der Message an die Anwendung über SOAP_http://sap.com/xi/XI/System ist fehlgeschlagen weil:

com.sap.aii.af.ra.ms.api.RecoverableException: (407)Proxy Authentication Required:

(407)Proxy Authentication Required. Message wird auf 'fehlgeschlagen' gesetzt

Fehler Der Status der Message wurde auf FAIL gesetzt

Fehler Rückgabe der synchronen Fehler-Message an rufende Anwendung: com.sap.aii.af.ra.ms.api.RecoverableException:

(407)Proxy Authentication Required: (407)Proxy Authentication Required.

-

-


Here is my module configuration:

xireq->handler.type->java:com.sap.aii.axis.xi.XI30OutboundHandler

dreq->handler.type->java:com.sap.aii.axis.xi.XI30DynamicConfigurationHandler

dreq->key.b--

-


>write http://sap.com/xi/System/HTTP Cookie

dreq->location.b---->header

dreq->value.b--

-


>Cookie

rem-->handler.type->java:com.sap.aii.axis.soap.HeaderRemovalHandler

rem-->namespace->http://sap.com/xi/XI/Message/30

trp---->handler.type->java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender

trp---->module.pivot->true

xires->handler.type->java:com.sap.aii.axis.xi.XI30OutboundHandler

Why does Axis want to use a authentication against a proxy? Our proxy is configured as path through

without authentication. --> Tests with other applications succeeded.

Does anyone know how we have to solve this issue?

Any help would very appreciated.

Thanks and best regards,

Sigi

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Siggi,

we had this error before and it was always the proxy configuration. In our proxy you have to allow connection without authorization for each application. I would strongly suggest to analyze this further.

Best regards,

Nils

Former Member
0 Kudos

Hi Nils,

thanks for your answer. We have deployed the J2EE application on the same SAP Java WAS where all the PI-Java components are running.

In fact, there is definitely no proxy between the SOAP receiver adapter and the WebService of the J2EE application.

Best regards,

Sigi