Variable initialized with wrong message type

Question

Hi,
I have a BPEL process variableA of Message type A as defined in the partnerlink WSDL file. This variable get initialized during operation A from the partnerlink. The WSDL has another message type B defined for another operation B.
During runtime when operation A is called variable A gets initialized with message type A, however when operation B is invoked with mesage type B variableA gets initialized again with the content of message type B even though it's defined to be of message type A. Below are the snippets from the WSDL and BPEL process file
WSDL file ..
<message name="MessageTypeA">
<part name="payload" element="mpx:MessageARequest"/>
</message>
<message name="MessageTypeB">
<part name="payload" element="mpx:MessageBRequest"/>
</message>
<portType name="MutilPort">
<operation name="A">
<input message="tns:MessageTypeA"/>
</operation>
<operation name="BA">
<input message="tns:MessageTypeB"/>
</operation>
</portType>
Process BPEL file
<variable name="VariableA"
messageType="tns1:MessageTypeA"/>
<variable name="VariableB"
messageType="tns1:MessageTypeB"/>
<pick name="Pick_2" createInstance="yes">
<onMessage portType="tns1:MutilPort" operation="square"
variable="VariableA" partnerLink="Multiplex">
<sequence name="Sequence_1">
<assign name="Assign_2">
<copy>
<from variable="VariableA" part="payload"
query="/ns1:MessageARequest/ns1:Operand1"/>
<to variable="ResponseVariable" part="payload"
query="/ns1:AllOpProcessResponse/ns1:Result1"/>
</copy>
</assign>
</sequence>
</onMessage>
<onMessage portType="tns1:MutilPort" operation="addition"
variable="VariableB" partnerLink="Multiplex">
<sequence name="Sequence_2">
<assign name="Assign_1">
<copy>
<from variable="VariableB" part="payload"
query="/ns1:MessageBRequest/ns1:Operand5"/>
<to variable="ResponseVariable" part="payload"
query="/ns1:AllOpProcessResponse/ns1:Result1"/>
</copy>
</assign>
</sequence>
</onMessage>
</pick>
Please can anyone shed some light on why and how this can happen and where is it going wrong.
Thanks,
Shishir

Answer 1

Looks like the destination which is used by your EG has default settings,
particulary the RedeliveryLimit param. If it is set to -1 (default setting)
WL will try to redeliver the message forever in case of any error. Just set
it to something else. You can also specify an ErrorDestination and hadle
error messages specifically in it.
Denis.
<Gunjan Shukla> wrote in message news:[email protected]..
Hi,
We are using WLI 8.1, in one of our applications I have a message broker
channel configured to listen to rawdata type messages. A jms event
generator is configured to publish messages, which are sent to a jms
topic, on this channel.
We have no control over type of messages sent by client applications, when
some client application sends an ObjectMessage instead of BytesMessage,
following error is thrown
####<Jun 1, 2006 10:47:14 AM GMT-07:00> <Error> <WLW> <P931467> <cgServer>
<ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<anonymous>>
<BEA1-004324CB0C4F26C12C0A> <000000> <Cannot publish non-BytesMessage to
channel of type RAWDATA>
####<Jun 1, 2006 10:47:14 AM GMT-07:00> <Error> <WLI-Core> <P931467>
<cgServer> <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'>
<<anonymous>> <BEA1-004324CB0C4F26C12C0A> <BEA-489048> <Not a
BytesMessage>
server keeps throwing this exception and fills the logs and ultimately
server needs to be re-started.
Can somebody point me to whether its possible to catch these exceptions in
a process?
Or alternatively is it possible to somehow ignore the messages with
mismatched message type?
Any ideas are greatly appreciated.
Thanks and regards,
Gunjan