Trying to throw fault from one BPEL process to another

Question

We are trying to throw a fault from one BPEL process to another and apparently are experiencing a common problem. That is, the invoking process times out and never receives the fault.
Likely a beginner's mistake is at fault (pun intended).
Below are samples of a simple "Hello World" process that tries to throw the fault.
snippet of pbel file....
<process name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://helloworldjavaproject/"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<faultHandlers>
<catchAll>
<sequence name="Sequence_1">
<assign name="Assign_3">
<copy>
<from expression="12345"/>
<to variable="FaultVar" part="code"/>
</copy>
<copy>
<from expression="'Hello fault summary'"/>
<to variable="FaultVar" part="summary"/>
</copy>
<copy>
<from expression="'Hello test detail'"/>
<to variable="FaultVar" part="detail"/>
</copy>
</assign>
<throw name="Throw_2" faultName="client:myFault"
faultVariable="FaultVar"/>
</sequence>
HelloJavaWorldSynchronous.wsdl file
<definitions
name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://schemas.oracle.com/bpel/extension"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
>
<import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl";/>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous" schemaLocation="HelloJavaWorldSynchronous.xsd";/>
</schema>
</types>
<message name="HelloJavaWorldSynchronousRequestMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessRequest"/>
</message>
<message name="HelloJavaWorldSynchronousResponseMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessResponse"/>
</message>
<portType name="HelloJavaWorldSynchronous">
<operation name="process">
<input message="client:HelloJavaWorldSynchronousRequestMessage"/>
<output message="client:HelloJavaWorldSynchronousResponseMessage"/>
<fault name="myFault" message="ns1:RuntimeFaultMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="HelloJavaWorldSynchronous">
<plnk:role name="HelloJavaWorldSynchronousProvider">
<plnk:portType name="client:HelloJavaWorldSynchronous"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
The standard RuntimeFault.wsdl file (RuntimeFaultMessage message is defined in here, so I don't need a message in HelloJavaWorldSynchronous.wsdl. Do I?)
<?xml version="1.0"; encoding="UTF-8"?>
<definitions name="RuntimeFault"
targetNamespace="http://schemas.oracle.com/bpel/extension"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<message name="RuntimeFaultMessage">
<part name="code" type="xsd:string"/>
<part name="summary" type="xsd:string"/>
<part name="detail" type="xsd:string"/>
</message>
</definitions>
But when we invoke the process, after the standard 45 seconds timeout, we still get...
<Faulthttp://schemas.xmlsoap.org/soap/envelope/>
<faultcode>env:Server</faultcode>
<faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is f290d62d2ad31aa6:-49eb76f4:124eb51622a:-7c91. Please check the process instance for detail.</faultstring>
</Fault>
The console audit below might hold a clue. I noticed the mesage BPELFault" has not been caught by a catch block at the end.
<catchAll>
<sequence>
Assign_3
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</FaultVar>
Throw_2 (faulted)
[2009/11/13 11:18:32] "{http://xmlns.oracle.com/HelloJavaWorldSynchronous}myFault" has been thrown. More...
-<myFault xmlns="http://xmlns.oracle.com/HelloJavaWorldSynchronous">
-<part name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</myFault>
</sequence>
</catchAll>
[2009/11/13 11:18:32] "BPELFault" has not been caught by a catch block.
[2009/11/13 11:18:32] BPEL process instance "570162" cancelled

Answer 1

Thanks very much for this answer. It was right on.
You wanted to know "how (I) get on". Funny you should ask. Believe it or not, I had figured out the problem on my own just about the time you were posting your reply (of course, this is a bit too convenient. No one will ever believe me).
But the answer leads to another question. What is the Throw activity for, if not to throw an error to the calling process? Is it only used to throw within scope of the process its self?
I am probably biased by the Java world I am coming from, but Throw feels like it should terminate the process (without side effects like a big red mark in the console) bubble up the fault to the calling process who can catch it (if so desired). Using the reply we must explicitly Terminate (which includes that unsightly red mark).
Is there any way to get this behavior from the Throw, or should we just reprogram the "wetware" and learn a new paradigm?
Is there any way to end a process without marking it with a red flag that suggests something went wrong?