Hi,
the first error does not contain any information about the reason, the
second and third error indicated some network troubles (no route to
host, please make sure that all services are available). The fourth
error is a but in ODE 1.3.3, please give our release candidate for 1.3.4
a try: http://people.apache.org/~rr/ode/
Best,
Tammo
On 22.05.2010 15:10, Adnan wrote:
> thank you.
>
> If you don't mind would please look into the following error as well...
> I got this after fixing the previous.
> When I send the soap request I am getting 3 similar responses... seems
> to be of endpoint but could not sort out...
>
> 58:53-DEBUG [MyRoleMessageExchangeImpl] Received myrole mex response
> callback
> 58:53-WARN [ODEService] MEX produced a fault
> {MyRoleMex#hqejbhcnphr5anefnsakft [Client hqejbhcnphr5anefnsakfs]
> calling {http://test123Proc}test123Wsdl.test123WsdlOPT
> <http://test123Proc%7Dtest123Wsdl.test123WsdlOPT>(...)}
> org.apache.ode.axis2.OdeFault: Message exchange failure due to: Error
> sending message to Axis2 for ODE mex
> {PartnerRoleMex#hqejbhcnphr5anefnsakfw [PID
> {http://test123Proc}test123Proc-18
> <http://test123Proc%7Dtest123Proc-18>] calling null.addOperation(...)}
> at
> org.apache.ode.axis2.util.SoapMessageConverter.createOdeFault(SoapMessageConverter.java:570)
> ......
>
> 03:57-DEBUG [MyRoleMessageExchangeImpl] Received myrole mex response
> callback
> 03:57-WARN [ODEService] MEX produced a fault
> {MyRoleMex#hqejbhcnphr5anefnsakg1 [Client hqejbhcnphr5anefnsakg0]
> calling {http://test123Proc}test123Wsdl.test123WsdlOPT
> <http://test123Proc%7Dtest123Wsdl.test123WsdlOPT>(...)}
> org.apache.ode.axis2.OdeFault: Message exchange failure due to: Error
> sending message (mex={PartnerRoleMex#hqejbhcnphr5anefnsakg4 [PID
> {http://test123Proc}test123Proc-18
> <http://test123Proc%7Dtest123Proc-18>] calling
> [email protected](...)}): The
> host did not accept the connection within timeout of 60000 ms
> at
> org.apache.ode.axis2.util.SoapMessageConverter.createOdeFault(SoapMessageConverter.java:570)
> ......
>
> 58:15-DEBUG [MyRoleMessageExchangeImpl] Received myrole mex response
> callback
> 58:15-WARN [ODEService] MEX produced a fault
> {MyRoleMex#hqejbhcnphr5anefnsakfl [Client hqejbhcnphr5anefnsakfk]
> calling {http://test123Proc}test123Wsdl.test123WsdlOPT
> <http://test123Proc%7Dtest123Wsdl.test123WsdlOPT>(...)}
> org.apache.ode.axis2.OdeFault: Message exchange failure due to: Error
> sending message (mex={PartnerRoleMex#hqejbhcnphr5anefnsakfo [PID
> {http://test123Proc}test123Proc-18
> <http://test123Proc%7Dtest123Proc-18>] calling
> [email protected](...)}): No
> route to host
> at
> org.apache.ode.axis2.util.SoapMessageConverter.createOdeFault(SoapMessageConverter.java:570)
> .....
> 58:53-DEBUG [MessageExchangeImpl] SET MEX property invokeCheckJobId =
> hqejbhcnphr5anefnsakfx
> 58:53-ERROR [ExternalService] Error sending message to Axis2 for ODE mex
> {PartnerRoleMex#hqejbhcnphr5anefnsakfw [PID
> {http://test123Proc}test123Proc-18
> <http://test123Proc%7Dtest123Proc-18>] calling null.addOperation(...)}
> org.apache.axis2.AxisFault: Two services cannot have same name. A
> service with the
> axis_service_for_{http://add.soco}Add#AddHttpSoap11Endpoint_hqejbhcnphr5anefnsakfb
> <http://add.soco%7DAdd#AddHttpSoap11Endpoint_hqejbhcnphr5anefnsakfb>
> name already exists in the system.
> at
> org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:172)
> .....
>
> any idea...
> thx
>
> *----
> AL*
>
>
> ------------------------------------------------------------------------
> *From:* Tammo van Lessen <[email protected]>
> *To:* [email protected]
> *Sent:* Fri, 21 May, 2010 18:23:47
> *Subject:* Re: Continously getting selectionFailure, help
>
> Hi,
>
> looks like your overriding the "input" variable with
>
>> <bpel:from>
>> <bpel:literal xml:space="preserve">
>>
>>
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>> <aComp />
>> <bComp />
>> </p:add>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to part="parameters" variable="input"/>
>
> and later you are trying to access
>
>> <bpel:from> $input.parameters/xsd:aComp </bpel:from>
>
> If the 'xsd' namespace is not equal to the default name space, this is
> most likely causing the selectionFailure. If not, please check the
> logfiles. They should contain line number information where the
> selection failure happens. If not, please increase the loglevel to debug.
>
> HTH,
> Tammo
>
>
> On 21.05.2010 17:37, Adnan wrote:
>> Sorry did not attach. The process
>> ------------
>>
>> suppressJoinFailure="yes" xmlns:tns="http://test123Proc";
>> xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable";
>> xmlns:wsdl2="http://add.soco"; xmlns:wsdl3="http://inv.soco";
> xmlns:xsd="http://test123Sch/"; >
>>
>>
>> importType="http://schemas.xmlsoap.org/wsdl/"; />
>>
>> importType="http://schemas.xmlsoap.org/wsdl/"; />
>> <bpel:import location="test123ProcArtifacts.wsdl"
>> namespace="http://test123Proc";
> importType="http://schemas.xmlsoap.org/wsdl/"; />
>>
>> <bpel:partnerLinks>
>> <!-- The 'client' role represents the requester of this
> service. -->
>> <bpel:partnerLink name="test123WsdlPLT"
>> partnerLinkType="tns:test123Proc" myRole="test123ProcRole" />
>> <bpel:partnerLink name="InversePLT_PL"
>> partnerLinkType="tns:InversePLT" partnerRole="InverseRole" />
>> <bpel:partnerLink name="addPLT_PL" partnerLinkType="tns:addPLT"
>> partnerRole="addRole" />
>> </bpel:partnerLinks>
>>
>> <bpel:variables>
>> <!-- Reference to the message passed as input during initiation -->
>> <bpel:variable name="input" messageType="tns:test123WsdlInput_" />
>> <bpel:variable name="output"
> messageType="tns:test123WsdlOutput_" />
>> <bpel:variable name="addRequestIn"
> messageType="wsdl2:addRequest" />
>> <bpel:variable name="addResponseOut"
> messageType="wsdl2:addResponse" />
>> <bpel:variable name="InverseSignRequestIn"
> messageType="wsdl3:InverseSignRequest" />
>> <bpel:variable name="InverseSignResponseOut"
>> messageType="wsdl3:InverseSignResponse" />
>> </bpel:variables>
>>
>> <bpel:sequence name="main">
>>
>> <!--
>> Receive input from requester. Note: This maps to operation
> defined in
>> test123Proc.wsdl
>> -->
>> <bpel:receive name="receiveInput" partnerLink="test123WsdlPLT"
>> portType="tns:test123WsdlPT" createInstance="yes"
> operation="test123WsdlOPT"
>> variable="input" />
>>
>> <!-- Generate reply to synchronous request -->
>> <bpel:assign validate="no" name="addAssign">
>>
>> <bpel:copy>
>>
>> <bpel:from>
>> <bpel:literal xml:space="preserve">
>>
>>
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>> <aComp />
>> <bComp />
>> </p:add>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to part="parameters" variable="input"/>
>>
>> </bpel:copy>
>> <bpel:copy>
>> <bpel:from>
>> <bpel:literal xml:space="preserve"><ns:addResponse
>> xmlns:ns="http://add.soco";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; />
>>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to part="parameters" variable="addResponseOut"/>
>> </bpel:copy>
>>
>> <bpel:copy>
>> <bpel:from>
>> <bpel:literal
> xml:space="preserve"><ns:InverseSignResponse
>> xmlns:ns="http://inv.soco";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; />
>>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to variable="InverseSignResponseOut"
> part="parameters" />
>> </bpel:copy>
>>
>>
>> <bpel:copy>
>> <bpel:from>
>> <bpel:literal xml:space="preserve"><ns:InverseSign
>> xmlns:ns="http://inv.soco";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; />
>>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to variable="InverseSignRequestIn"
> part="parameters" />
>> </bpel:copy>
>>
>> <bpel:copy>
>> <bpel:from>
>> <bpel:literal xml:space="preserve">
>>
>>
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; />
>>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to part="parameters" variable="addRequestIn" />
>> </bpel:copy>
>>
>> <bpel:copy keepSrcElementName="no" ignoreMissingFromData="no">
>> <bpel:from> $input.parameters/xsd:aComp </bpel:from>
>> <bpel:to> $addRequestIn.parameters/a </bpel:to>
>> </bpel:copy>
>> <bpel:copy keepSrcElementName="no" ignoreMissingFromData="no">
>> <bpel:from> $input.parameters/xsd:bComp </bpel:from>
>> <bpel:to> $addRequestIn.parameters/b </bpel:to>
>> </bpel:copy>
>>
>>
>> </bpel:assign>
>>
>> <bpel:invoke partnerLink="addPLT_PL" name="addInvoke"
>> suppressJoinFailure="yes" operation="add"
> portType="wsdl2:AddPortType"
>> inputVariable="addRequestIn" outputVariable="addResponseOut" />
>>
>> <bpel:assign validate="no" name="InverseAssign"
>> suppressJoinFailure="yes">
>> <bpel:copy keepSrcElementName="no" ignoreMissingFromData="no">
>> <bpel:from> $addResponseOut.parameters/return </bpel:from>
>> <bpel:to> $InverseSignRequestIn.parameters/a </bpel:to>
>> </bpel:copy>
>> </bpel:assign>
>>
>> <bpel:invoke partnerLink="InversePLT_PL"
> portType="wsdl3:InversePortType"
>> operation="InverseSign" name="InverseInvoke"
> suppressJoinFailure="yes"
>> inputVariable="InverseSignRequestIn"
> outputVariable="InverseSignResponseOut" />
>>
>> <bpel:assign validate="no" name="InverseAssign2"
>> suppressJoinFailure="yes">
>> <bpel:copy>
>> <bpel:from>
>> <bpel:literal xml:space="preserve">
>>
>> <returnComp></returnComp>
>> </p:InverseSignResponse>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to variable="output" part="parameters"></bpel:to>
>> </bpel:copy>
>> <bpel:copy keepSrcElementName="no" ignoreMissingFromData="no">
>> <bpel:from> $InverseSignResponseOut.parameters/return
> </bpel:from>
>> <bpel:to> $output.parameters/xsd:returnComp </bpel:to>
>> </bpel:copy>
>>
>> </bpel:assign>
>>
>> <bpel:reply name="replyOutput" partnerLink="test123WsdlPLT"
>> operation="test123WsdlOPT" portType="tns:test123WsdlPT"
> variable="output" />
>>
>> </bpel:sequence>
>> </bpel:process>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----
>> AL
>>
>>
>>
>>
>> ________________________________
>> From: Adnan <[email protected] <mailto:[email protected]>>
>> To: Apache ODE Forum <[email protected] <mailto:[email protected]>>
>> Sent: Fri, 21 May, 2010 17:34:35
>> Subject: Continously getting selectionFailure, help
>>
>>
>> Hi.
>>
>> I think i have initialized the all variables and using document
> literal binding. I have a separate schema file that uses another schema
> file, which contains the types. I am pasting my process here. Will
> appreciate the reply.
>>
>> I am getting the following reply from there server.
>>
>>
>>
> soapenv:Server'>http://schemas.xmlsoap.org/soap/envelope/";>soapenv:Server
>> <faultstring>axis2ns2:selectionFailure</faultstring>
>> <detail/>
>> </SOAP-ENV:Fault>
>>
>>
>> thank you.
>>
>> ----
>> AL
>>
>>
>>
>
> --
> Tammo van Lessen - http://www.taval.de
>
--
Tammo van Lessen - http://www.taval.de
