You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by "Cwik, Jan" <Ja...@sabre-holdings.com> on 2007/10/18 15:45:09 UTC
Failures in bpel - need more information
Hi,
I wonder where could I find a little bit more about catching failures in
the ODE ?
I already read http://ode.apache.org/bpel-extensions.html and I know
that when "faultOnFailure=true" then failures are caught as faults by
means of "catchAll" or "ext:activityFailure". However, I don't know how
to find out what kind of failure occured. Is it possible upon catching
failure to get any information about it ? I mean something like failure
name, failure reason etc.
best regards
jan
RE: Timeout on JBI message exchange for ODE 1.1
Posted by "Cwik, Jan" <Ja...@sabre-holdings.com>.
thanks! I set up "org.apache.ode.jbi.sendSynch" to "true" and it works
fine.
regards
jan
-----Original Message-----
From: Alex Boisvert [mailto:boisvert@intalio.com]
Sent: Friday, October 19, 2007 2:55 PM
To: user@ode.apache.org
Subject: Re: Timeout on JBI message exchange for ODE 1.1
On 10/19/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
>
> I'm trying to use ODE 1.1 together with fuse-3.2.0-SNAPSHOT but
> immediately after invoking the very first service I'm getting "Timeout
> on JBI message exchange". When I'm using ODE 1.0 it works fine. Is it
a
> known issue ?
Looks like the async jbi invocation is broken (minor logic problem).
I've
created a tracker for this issue,
https://issues.apache.org/jira/browse/ODE-198
In the mean time, you can use the synchronous invocation by setting the
system property "org.apache.ode.jbi.sendSynch" to "true". I generally
recommend using JBI synchronous invokes unless you've determined that
you
have a scalability problem at the messaging layer, e.g. many outstanding
invokes taking a lot of time. In my experience, synchronous makes the
system easier to debug, more stable under load and slightly faster for
the
general case since it incurs no context-switching cost.
alex
Re: Timeout on JBI message exchange for ODE 1.1
Posted by Alex Boisvert <bo...@intalio.com>.
On 10/19/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
>
> I'm trying to use ODE 1.1 together with fuse-3.2.0-SNAPSHOT but
> immediately after invoking the very first service I'm getting "Timeout
> on JBI message exchange". When I'm using ODE 1.0 it works fine. Is it a
> known issue ?
Looks like the async jbi invocation is broken (minor logic problem). I've
created a tracker for this issue,
https://issues.apache.org/jira/browse/ODE-198
In the mean time, you can use the synchronous invocation by setting the
system property "org.apache.ode.jbi.sendSynch" to "true". I generally
recommend using JBI synchronous invokes unless you've determined that you
have a scalability problem at the messaging layer, e.g. many outstanding
invokes taking a lot of time. In my experience, synchronous makes the
system easier to debug, more stable under load and slightly faster for the
general case since it incurs no context-switching cost.
alex
Timeout on JBI message exchange for ODE 1.1
Posted by "Cwik, Jan" <Ja...@sabre-holdings.com>.
Hi,
I'm trying to use ODE 1.1 together with fuse-3.2.0-SNAPSHOT but
immediately after invoking the very first service I'm getting "Timeout
on JBI message exchange". When I'm using ODE 1.0 it works fine. Is it a
known issue ?
regards
jan
I'm using ODE version taken from http://ode.apache.org/getting-ode.html
- JBI Distribution - apache-ode-jbi-1.1.zip
The following are the debugs from invoking a service that timeouts
immediately :
DEBUG - ASSIGN - ASSIGN Writing variable
'OTA_TravelItineraryReadTransRefNum
ber' value '<?xml version="1.0" encoding="UTF-8"?>
<temporary-simple-type-wrapper>2</temporary-simple-type-wrapper>'
DEBUG - BpelProcess - INVOKING PARTNER:
partnerLink={PartnerLinkInstance partnerL
inkDecl=OPartnerLink#92,scopeInstanceId=0}, op=TravelItineraryAddInfoRQ
channel=InvokeResponseChanne
l#34)
DEBUG - BpelRuntimeContextImpl - INVOKE PARTNER (SEP):
sessionId=null partnerSessionId=null
DEBUG - BpelEngineImpl - Routed: svcQname
{https://webservices.sabre.com/websvc}Trav
elItineraryAddInfoService --> null
DEBUG - EndpointReferenceContextImpl - resolveEndpointReference:
<?xml version="1.0" encoding="UTF-8"?>
<service-ref>
<jbi:end-point-reference jbi:end-point-name="tpfc"
jbi:service-name="sns:TravelItineraryAddInfoService"
xmlns:sns="https://webservices.sabre.com/we
bsvc"/>
</service-ref>
DEBUG - MessageExchangeImpl - SET MEX property
org.apache.ode.jbi.msgmap.Mapper = org.apa
che.ode.jbi.msgmap.ServiceMixMapper
DEBUG - ServiceMixMapper - toNMS() normalized message
(doc-like):<?xml version="1.0" e
ncoding="UTF-8"?>
<TravelItineraryAddInfoRQ Version="2003A.TsabreXML1.4.1"
xmlns="http://webservices.sabre.com/sabreXML/2003/07"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance">
<POS>
<Source AgentSine="AWS" PseudoCityCode="IH9A"/>
</POS>
<CustomerInfo>
<PersonName RPH="1.1">
<GivenName>BRANDON</GivenName>
<Surname>STEELE</Surname>
</PersonName>
<PersonName RPH="2.1">
<GivenName>SILVIA</GivenName>
<Surname>REVELLO</Surname>
</PersonName>
<Telephone AreaCityCode="682" CountryAccessCode="011"
NameNumber="1.1" PhoneLocationType="B" PhoneNumber="6052187"/>
<Telephone AreaCityCode="817" CountryAccessCode="011"
NameNumber="1.1" PhoneLocationType="H" PhoneNumber="5551212"/>
<Telephone AreaCityCode="817" CountryAccessCode="011"
NameNumber="1.1" PhoneLocationType="H" PhoneNumber="5551212"/>
<Email EmailAddress="BRANDON.STEELE@SABRE.COM" NameNumber="1.1"/>
<Email EmailAddress="SILVIA.REVELLO@GMAIL.COM" NameNumber="2.1"/>
<CustomerIdentifier Identifier="1111111"/>
</CustomerInfo>
<AgencyInfo>
<Address>
<TPA_Extensions>
<AgencyName>ABC TRAVEL</AgencyName>
</TPA_Extensions>
<StreetNmbr>2147 RICHLAND</StreetNmbr>
<CityName>GRAPEVINE</CityName>
<PostalCode>76051</PostalCode>
<StateCountyProv StateCode="TX"/>
<CountryName Code="US"/>
</Address>
<Ticketing TicketType="7T-"/>
</AgencyInfo>
</TravelItineraryAddInfoRQ>
DEBUG - PartnerRoleMessageExchangeImpl - replyAsync
mex=4611686018427387904
DEBUG - BpelRuntimeContextImpl - Setting execution state on
instance 0
LICENSE FILE: <?xml version="1.0" encoding="UTF-8"?><ath
createTime="-4518343727503941503" directory
ID="0"
sessionMgrContextName="Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/"
sessionMgrDirectName="IC
ESMS\/STSB" sessionMgrLBName="ICESMSLB\/STS.LB"
sessionRecordID="380977"><securityLevel appLevel="1"
auditLevel="2" billingLevel="1" metricsLevel="1"
securityLevel="1"/><version major="1" minor="0"/><
securityContext><user affiliationcode="1" branch="2902" domain="AA"
group="7TZA" id="12345" station=
"925"/></securityContext><sessionContext activeTimeout="0"
createTime="1191499565" idleTimeout="900"
lastModifiedTime="1191499565" sequenceNumber="0"
transactionID="597920877"><sessionVersion major="1
" minor="0"/><tpfSession tpfClusterName="" tpfEnterprise=""
tpfIsConfigOverridden="false" tpfIsIceCr
eated="true" tpfLniata="5805920" tpfLockID="1905207154" tpfPoolType="0"
tpfProfileCity="" tpfProfile
Code="" tpfProfileKey="" tpfProfileName=""
tpfProtocol=""/></sessionContext></ath>
DEBUG - SimpleScheduler - CHECK STALE NODES started
WARN - OdeConsumerAsync - Timeout on JBI message exchange
ID:10.136.44.165-115b788290
1-2:0
DEBUG - PartnerRoleMessageExchangeImpl - replyWithFailure
mex=4611686018427387904 failureType=NO_RES
PONSE description=Response not received after 120000ms. details=null
DEBUG - PartnerRoleMessageExchangeImpl - create work event for
mex=4611686018427387904
DEBUG - InstanceLockManager - Thread[pool-3-thread-1,5,main]:
lock(iid=0, time=1MICROSECO
NDS)
DEBUG - InstanceLockManager - Thread[pool-3-thread-1,5,main]:
lock(iid=0, time=1MICROSECO
NDS)-->GRANTED
DEBUG - BpelProcess - >>
handleWorkEvent(jobData={type=INVOKE_RESPONSE, inmem=tru
e, mexid=4611686018427387904, channel=34, iid=0})
DEBUG - BpelRuntimeContextImpl - BpelRuntimeContextImpl created
for instance 0. INDEXED STAT
E={}
DEBUG - BpelProcess - InvokeResponse event for iid 0
DEBUG - BpelRuntimeContextImpl - Invoking message response for
mexid 4611686018427387904 and
channel 34
DEBUG - JacobVPU - injecting (...)
DEBUG - BpelRuntimeContextImpl - Triggering response
DEBUG - BpelDAOConnectionImpl - Removing mex
4611686018427387904 from memory store.