The ESB don´t pass the security header to the AS. This is the major problem.

The error:

2011-07-13 03:02:39,093 [-] [HttpServerWorker-1] ERROR AxisEngine The
endpoint reference (EPR) for the Operation not found is
https://localhost:8243/services/ProxyHelloService15 and the WSA Action =
http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT. If this EPR was
previously reachable, please contact the server administrator.
org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
not found is https://localhost:8243/services/ProxyHelloService15 and the WSA
Action = http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT. If this EPR
was previously reachable, please contact the server administrator.
        at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java
:102)
        at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
        at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
        at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
        at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HT
TPTransportUtils.java:172)
        at
org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod
(ServerWorker.java:408)
        at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:259)
        at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerP
ool.java:173)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja
va:886)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
08)
        at java.lang.Thread.run(Thread.java:619)
2011-07-13 03:02:39,281 [-] [HttpServerWorker-1] ERROR ServerWorker Error
processing POST request 
org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
not found is https://localhost:8243/services/ProxyHelloService15 and the WSA
Action = http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT. If this EPR
was previously reachable, please contact the server administrator.
        at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java
:102)
        at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
        at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
        at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
        at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HT
TPTransportUtils.java:172)
        at
org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod
(ServerWorker.java:408)
        at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:259)
        at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerP
ool.java:173)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja
va:886)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
08)
        at java.lang.Thread.run(Thread.java:619)
2011-07-13 03:02:39,906 [-] [https-Listener I/O dispatcher-1] ERROR
ServerHandler I/O error: Se ha forzado la interrupción de una conexión
existente por el host remoto
java.io.IOException: Se ha forzado la interrupción de una conexión existente
por el host remoto
        at sun.nio.ch.SocketDispatcher.read0(Native Method)
        at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
        at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
        at sun.nio.ch.IOUtil.read(IOUtil.java:206)
        at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236)
        at
org.apache.http.impl.nio.reactor.SSLIOSession.receiveEncryptedData(SSLIOSess
ion.java:248)
        at
org.apache.http.impl.nio.reactor.SSLIOSession.isAppInputReady(SSLIOSession.j
ava:274)
        at
org.apache.http.impl.nio.SSLServerIOEventDispatch.inputReady(SSLServerIOEven
tDispatch.java:229)
        at
org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:1
61)
        at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIORe
actor.java:335)
        at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOR
eactor.java:315)
        at
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor
.java:275)
        at
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:10
4)
        at
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(Abs
tractMultiworkerIOReactor.java:542)
        at java.lang.Thread.run(Thread.java:619)

The endpoint is OK.


Saludos,
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
Fac. 5.
UCI.

De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
nombre de Hiranya Jayathilaka
Enviado el: martes, 12 de julio de 2011 0:22
Para: carbon-dev@wso2.org
Asunto: Re: [Carbon-dev] Issue with useOriginalwsdl in ESB 4.0

Hi Jorge,
On Tue, Jul 12, 2011 at 3:11 AM, Jorge Infante Osorio <jorg...@uci.cu>
wrote:
Folks, any idea on this??!! It´s a ESB issue or a misconfiguration in my
setup?

Looks like a bug to me. Your configuration looks ok. Can you please raise a
JIRA for this? We will take a look and see what needs to be done to fix
this.

Also could you please mention whether the mediation/routing works regardless
of the issue in the published WSDL? That is does the ESB pass the security
headers properly to the Hello service?

Thanks,
Hiranya


Saludos,
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
Fac. 5.
UCI.
-----Mensaje original-----
De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
nombre de Jorge Infante Osorio
Enviado el: viernes, 08 de julio de 2011 23:30
Para: carbon-dev@wso2.org
Asunto: [Carbon-dev] Issue with useOriginalwsdl in ESB 4.0

Hi folks.
NOTE: this is the same issue of thread: "[Architecture] Issues with Proxys
Sevices  in ESB 4.0.0."

I have this scenario:

In AS 4.1.0 I setup the HelloService with UT security. In ESB 4.0.0 I
created a proxy service with the template “Pass Through Proxy” that redirect
to the HelloService in AS. This service don´t have security.

The problem is that in the ESB the binding in the wsdl don´t show the
reference to the UTOverTransport policy.

You can see the service wsdl in AS, the proxy configuration and the proxy
wsdl in the file attach.


NOTE: If I use the older version of ESB all work fine.

The binding in AS:

    <wsdl:binding name="HelloServiceSoap12Binding"
type="ns:HelloServicePortType">
        <wsp:PolicyReference
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";
URI="#UTOverTransport" />
        <soap12:binding transport="http://schemas.xmlsoap.org/soap/http";
style="document" />
        <wsdl:operation name="greet">
            <soap12:operation soapAction="urn:greet" style="document" />
            <wsdl:input>
                <soap12:body use="literal" />
            </wsdl:input>
            <wsdl:output>
                <soap12:body use="literal" />
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>


The proxy configuration:

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"; name="ProxyHelloService15"
transports="https" startOnLoad="true" trace="disable">
    <target inSequence="log_UT_bypass">
        <endpoint>
            <address uri="https://localhost:9443/services/HelloService"/>
        </endpoint>
        <outSequence>
            <send/>
        </outSequence>
    </target>
    <publishWSDL uri="https://localhost:9443/services/HelloService?wsdl"/>
    <parameter name="useOriginalwsdl">true</parameter>
</proxy>

The binding in ESB 4.0.0:

  <wsdl:binding name="HelloServiceSoap11Binding"
type="ns:HelloServicePortType">
    <soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"; />
    <wsdl:operation name="greet">
      <soap:operation soapAction="urn:greet" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>

Saludos,
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
Fac. 5.
UCI.

_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev



-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to