Re: BPJBI-6018:EndPoint Reference is not available from the JBI

  • From: Sherry Weng <Sherry.Weng@...>
  • To: Mei Wu <Mei.Wu@...>
  • Cc: neelsp@..., bpelengine-dev <bpelengine-dev@...>, Noel Ang <Noel.Ang@...>, dev@...
  • Subject: Re: BPJBI-6018:EndPoint Reference is not available from the JBI
  • Date: Thu, 15 May 2008 15:13:59 -0700
  • Mailing-list: contact dev-help@...; run by ezmlm

Sorry about the delay. Just got a chance to dig a little deeper into this problem. Looks like the issue is in the addressing header (captured below), and the server doesn't seem to recognize or support the <wsa:Action>
The SOAP header is added in the Metro layer, which in opinion, is correct, based on the WSDL.

Here is the snippet of the SOAP request header:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Header>
    <To xmlns="http://www.w3.org/2005/08/addressing">http://129.6.24.109:9080/axis2/services/xdsrepositoryb</To>
    <Action xmlns="http://www.w3.org/2005/08/addressing">urn:RetrieveDocumentSetRequest</Action>
    <ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
      <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
    </ReplyTo>
    <MessageID xmlns="http://www.w3.org/2005/08/addressing">uuid:3beaf46b-67f8-477c-98df-46abd96fc1a5</MessageID>
  </SOAP-ENV:Header>
  <SOAP-ENV:Body>
    <ns1:Retrieve
...

Here is the snippet of the WSDL definition where the wsa:Action is specified:
    <wsdl:portType name="xdsrepositorybPortType">
        <wsdl:operation name="RetrieveDocumentSetRequest">
           <wsdl:input message="ns1:RetrieveDocumentSetRequestRequest" wsaw:Action="urn:RetrieveDocumentSetRequest"/>
            <wsdl:output message="ns1:RetrieveDocumentSetRequestResponse" wsaw:Action="urn:RetrieveDocumentSetRequestResponse"/>
            <wsdl:input message="ns1:RetrieveDocumentSetRequestRequest"/>
            <wsdl:output message="ns1:RetrieveDocumentSetRequestResponse"/>
        </wsdl:operation>
    </wsdl:portType>


Here is the SOAP fault received on the request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
   <soapenv:Header>
      <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
      <wsa:RelatesTo>uuid:3beaf46b-67f8-477c-98df-46abd96fc1a5</wsa:RelatesTo>
      <wsa:FaultDetail>
         <wsa:ProblemAction>
            <wsa:Action>urn:RetrieveDocumentSetRequest</wsa:Action>
         </wsa:ProblemAction>
      </wsa:FaultDetail>
   </soapenv:Header>
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>wsa:ActionNotSupported</faultcode>
         <faultstring>The [action] cannot be processed at the receiver.</faultstring>
         <detail/>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>

But the Metro team (cc'ed here) has the expertise on this, so I will defer to their opinions.

Regards
--Sherry

Mei Wu wrote:
I changed the faulty connection on casa for the invoke, now it is able to make the invoke but the fault comes from soapaction expected by the provider:

[#|2008-05-12T15:52:54.438-0400|FINE|sun-appserver9.1|com.sun.jbi.httpsoapbc.OutboundMessageProcessor|_ThreadID=30;_ThreadName=HTTPBC-OutboundReceiver-1;ClassName=com.sun.jbi.httpsoapbc.OutboundMessageProcessor;MethodName=dispatch;Context=context;_RequestID=d4f3f9f5-cd3b-484d-92e6-79b00dae01ac;|A fault occured, possibly a specified service fault.
javax.xml.ws.soap.SOAPFaultException: The [action] cannot be processed at the receiver.
    at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:187)
    at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:108)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:187)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:206)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:986)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.dispatch(OutboundMessageProcessor.java:1016)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:661)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:243)
    at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
|#]

I think Noel or Sherry will have more on this one. The modified projects are attached, please use TestCase3 in mmmCA.

Thanks
Mei


Mei Wu wrote:
Hi, NP,

Yes, I tried your project, in fact the input in the testcase is missing root element, the input should conform to mymtominput.xsd, the correct input is like below:
<soapenv:Envelope xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mym="http://xml.netbeans.org/schema/mymtominput" xmlns:urn="urn:ihe:iti:xds-b:2007">
  <soapenv:Body>
    <mym:mymtominput>
      <mym:inputelem>
  <urn:RetrieveDocumentSetRequest>

 

        <urn:DocumentRequest>

  <urn:HomeCommunityId></urn:HomeCommunityId>

        <urn:RepositoryUniqueId>1.19.6.24.109.42.1</urn:RepositoryUniqueId>

        <urn:DocumentUniqueId>129.6.58.91.19217</urn:DocumentUniqueId>

            </urn:DocumentRequest>

              <urn:DocumentRequest>

          <urn:HomeCommunityId></urn:HomeCommunityId>

        <urn:RepositoryUniqueId>1.19.6.24.109.42.1</urn:RepositoryUniqueId>

        <urn:DocumentUniqueId>129.6.58.91.19218</urn:DocumentUniqueId>

            </urn:DocumentRequest>

      </urn:RetrieveDocumentSetRequest>                 
      </mym:inputelem>
    </mym:mymtominput>
  </soapenv:Body>
</soapenv:Envelope>

However, using this input does invoke the bp but the instance is failed :

[#|2008-05-12T15:04:44.675-0400|WARNING|sun-appserver9.1|com.sun.jbi.httpsoapbc.OutboundMessageProcessor|_ThreadID=30;_ThreadName=HTTPBC-OutboundReceiver-1;Context=context;_RequestID=d4f3f9f5-cd3b-484d-92e6-79b00dae01ac;|HTTPBC-E00759: An exception occured while processing a reply message. HTTP Status-Code 404: Not Found - Not Found
com.sun.xml.ws.client.ClientTransportException: HTTP Status-Code 404: Not Found - Not Found
    at com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:239)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:151)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:88)
    at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:116)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.client.Stub.process(Stub.java:248)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:180)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:206)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:986)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.dispatch(OutboundMessageProcessor.java:1016)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:661)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:243)
    at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
|#]

This is due to :
[#|2008-05-12T15:04:44.642-0400|WARNING|sun-appserver9.1|com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor|_ThreadID=29;_ThreadName=httpWorkerThread-9080-3;/casaService2/casaPort2;9080;_RequestID=24c76233-cf95-4aeb-9786-dd7a0f0f08bb;|HTTPBC-W00652: No web service mapping found for requested URL /casaService2/casaPort2, port 9,080|#]

--Mei

neelsp@... wrote:
Hi Mei,

I had uploaded my project. Please let me know if you need any further information.

Any help in this regard is greatly appreciated as there is not enough info out there.

Thanks
NP
Mei Wu-2 wrote:
  
Hi, NP,
I created a simple project to look at the issue (last mail), if you can 
create a CompositeApp for the project the way you do for your own 
project and make a test case, it will be easier for us to see what is 
wrong with your project.

Thanks
Mei

learnopenesb wrote:
    
Thanks for pointing that out. Actually, the error was in my input...

But now I get the following exception.

<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
  <S:Body>
    <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"
xmlns="">
      <faultcode>S:Server</faultcode>
      <faultstring>javax.jbi.messaging.MessagingException: HTTPBC-E00798:
Message normalization failed</faultstring>
    </S:Fault>
  </S:Body>
</S:Envelope>

Any ideas? I tested it using web-service testing project and it works
with
that. 

Thanks
NP



Philip Varghese-2 wrote:
  
      
 From the error, looks like your external web service cannot be found. 
The http-bc call to the external web-service failed.
Could you check your external service?

/(partnerLink=xdsbrepositorylink,
portType={http://serviceclasses.ws.registry.nist.gov}xdsrepositorybPortType,
*   Caused by: HTTP Status-Code 404: Not Found - Not Found</detailText>*
/



learnopenesb wrote:
    
        
Yes, the problem was 'no connection'. not sure why, but my service
assembly
did not show up with the soap binding component for the external web
service
call.

I added that manually to the CA and now get a soap-fault as below. Any
ideas
what could be causing this?

<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Body>
    <SOAP-ENV:Fault>
      <faultcode xmlns="">SOAP-ENV:Server</faultcode>
      <faultstring xmlns="">BPCOR-6135:A fault was not handled in the
process scope; Fault Name is
{http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
Fault Data is &amp;lt;?xml version=&amp;quot;1.0&amp;quot;
encoding=&amp;quot;UTF-8&amp;quot;?&amp;gt;&amp;lt;jbi:message
xmlns:sxeh=&amp;quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&amp;quot;
type=&amp;quot;sxeh:faultMessage&amp;quot;
version=&amp;quot;1.0&amp;quot;
xmlns:jbi=&amp;quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&amp;quot;&amp;gt;&amp;lt;jbi:part&amp;gt;HTTP
Status-Code 404: Not Found - Not
Found&amp;lt;/jbi:part&amp;gt;&amp;lt;/jbi:message&amp;gt;. Sending
errors
for the pending requests in the process scope before terminating the
process
instance</faultstring>
      <faultactor xmlns="">sun-bpel-engine</faultactor>
      <detail xmlns="">
        <detailText>BPCOR-6135:A fault was not handled in the process
scope;
Fault Name is
{http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
Fault Data is &amp;lt;?xml version=&amp;quot;1.0&amp;quot;
encoding=&amp;quot;UTF-8&amp;quot;?&amp;gt;&amp;lt;jbi:message
xmlns:sxeh=&amp;quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&amp;quot;
type=&amp;quot;sxeh:faultMessage&amp;quot;
version=&amp;quot;1.0&amp;quot;
xmlns:jbi=&amp;quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&amp;quot;&amp;gt;&amp;lt;jbi:part&amp;gt;HTTP
Status-Code 404: Not Found - Not
Found&amp;lt;/jbi:part&amp;gt;&amp;lt;/jbi:message&amp;gt;. Sending
errors
for the pending requests in the process scope before terminating the
process
instance
   Caused by: BPCOR-6131:An Error status was received while doing an
invoke
(partnerLink=xdsbrepositorylink,
portType={http://serviceclasses.ws.registry.nist.gov}xdsrepositorybPortType,
operation=RetrieveDocumentSetRequest)
BPCOR-6129:Line Number is 34
BPCOR-6130:Activity Name is Invoke1
   Caused by: HTTP Status-Code 404: Not Found - Not Found</detailText>
      </detail>
    </SOAP-ENV:Fault>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Thanks
NP



Murali Pottlapelli wrote:
  
      
          
Binding component end point for Invoke activity "Invoke1" is not 
available. BP instance is failing at this invoke.


open "Service Assembly" in your composite application connection  from 
PartnerLink2 to BC.

The issue could be caused either by
1. No connection - CASA establishes connections between internal end 
points in  most scenarios with few exceptions, your scenario might be 
one of them. You need to create connection manually.
2. There might be some error in deployment, you may need to look at
the 
logs at the time of deployment. If you do not have log, undeploy and 
deploy the application.

Regards
Murali


learnopenesb wrote:
    
        
            
Hi,

I have a bpel orchestration from which I am invoking an external
web-service. When I run the junit test, it gives me the following
error.

Any idea what does this error mean?

BPCOR-6135:A fault was not handled in the process scope; Fault Name
is
{http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
Fault Data is &amp;lt;?xml version=&amp;quot;1.0&amp;quot;
encoding=&amp;quot;UTF-8&amp;quot;?&amp;gt;&amp;lt;jbi:message
xmlns:sxeh=&amp;quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&amp;quot;
type=&amp;quot;sxeh:faultMessage&amp;quot;
version=&amp;quot;1.0&amp;quot;
xmlns:jbi=&amp;quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&amp;quot;&amp;gt;&amp;lt;jbi:part&amp;gt;BPJBI-6018:EndPoint
Reference is not available from the JBI corresponding to the service
name
{http://enterprise.netbeans.org/bpel/myMtomModule/myMtombpel}PartnerLink2
and endpoint name
xdsrepositorybRole_partnerRole&amp;lt;/jbi:part&amp;gt;&amp;lt;/jbi:message&amp;gt;.
Sending errors for the pending requests in the process scope before
terminating the process instance
   Caused by: BPCOR-7131:A fatal exception has occurred
BPCOR-6129:Line Number is 29
BPCOR-6130:Activity Name is Invoke1
   Caused by: BPJBI-6018:EndPoint Reference is not available from the
JBI
corresponding to the service name
{http://enterprise.netbeans.org/bpel/myMtomModule/myMtombpel}PartnerLink2
and endpoint name xdsrepositorybRole_partnerRole</detailText>

Thanks
NP


  
      
          
              
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...



    
        
            
  
      
          
    
        
  
      
    
Quoted from: 
http://www.nabble.com/BPJBI-6018%3AEndPoint-Reference-is-not-available-from-the-JBI-tp17129298p17151783.html

  


Re: BPJBI-6018:EndPoint Reference is not available from the JBI

Sherry Weng 05/15/2008

Re: BPJBI-6018:EndPoint Reference is not available from the JBI

RamaPulavarthi 05/16/2008

Re: BPJBI-6018:EndPoint Reference is not available from the JBI

Sherry Weng 05/16/2008

Re: BPJBI-6018:EndPoint Reference is not available from the JBI

RamaPulavarthi 05/16/2008

Re: BPJBI-6018:EndPoint Reference is not available from the JBI

Sherry Weng 05/16/2008

Re: BPJBI-6018:EndPoint Reference is not available from the JBI

Sherry Weng 05/16/2008

Message not available

Re: BPJBI-6018:EndPoint Reference is not available from the JBI

Sherry Weng 05/20/2008

Re: BPJBI-6018:EndPoint Reference is not available from the JBI

RamaPulavarthi 05/21/2008

Re: BPJBI-6018:EndPoint Reference is not available from the JBI

Sherry Weng 05/21/2008

Message not available

Re: BPJBI-6018:EndPoint Reference is not available from the JBI

Sherry Weng 05/27/2008
Terms of Use; Privacy Policy; Copyright ©2013-2014 (revision 20140418.2d69abc)
 
 
Close
loading
Please Confirm
Close