[ODE-659] Incorrect status for InOnly JBI MessageExchange (patch included)

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0
• Fix Version/s: 2.0-beta3
• Component/s: JBI Integration
• Labels: patch
• Environment: ServiceMix 3.3.1
• Assignee: Unassigned
• Reporter: Lasse Engler
• Created: 02/Sep/09 13:41
• Updated: 11/Feb/11 18:39

Description

The OdeService (JBI Integration) regards ONEWAY as an "unexpected Acktype". Thus the status for an in-only message exchange is always set to "Error" - even if it is processed correctly.

The attached patch should fix this problem. (At least it works as expected - and as it does with ODE 1.2.)

The related log entries (for the sake of completeness):
17:19:55,184 | FATAL | pool-5-thread-3 | OdeService | org.apache.ode.jbi.OdeService 224 | Unexpected AckType:ONEWAY
17:19:55,215 | ERROR | pool-5-thread-3 | Receiver | org.apache.ode.jbi.Receiver$1 181 | Error processing JBI message.
java.lang.IllegalStateException: component is not owner
at org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setProperty(MessageExchangeImpl.java:403)
at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:429)
at org.apache.ode.jbi.OdeService.onJbiMessageExchange(OdeService.java:136)
at org.apache.ode.jbi.JbiMessageExchangeEventRouter.onJbiMessageExchange(JbiMessageExchangeEventRouter.java:67)
at org.apache.ode.jbi.Receiver$1.run(Receiver.java:179)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)