[#MULE-834] Sporadic concurrency issue in VOIP example

Mule

Sporadic concurrency issue in VOIP example

Created: 13/May/06 08:33 AM Updated: 18/Oct/06 12:18 PM

Component/s:

Core: Concurrency / Threading, Transport: Axis

Affects Version/s:

1.3-rc3

Fix Version/s:

1.3

Time Tracking:

Not Specified

File Attachments:

mule.log (40 kB)

Issue Links:

Block

This issue blocks:

~~MULE-1075~~ Sporadic concurrency issues in LoanBroker examples

Related

This issue relates to:

~~MULE-893~~ Clarify/reachitect MuleMessage property mutability & handling

~~MULE-892~~ Clarify Endpoint/EndpointURI mutability

This issue relates to:

~~MULE-1031~~ Apply the workaround filter which patched LoanBroker-ESB to LoanBroker as well

Labels:

Description

« Hide

Running the VOIP example out of the box fails with an exception "most of the time" - while testing I didn't get it once or twice so it seems to be yet another multithreading bug, probably in endpoint or component initialization.

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Holger Hoffstaette added a comment - 13/May/06 08:34 AM

logfile as reported by jhuo<at>nortel.com

[ Permlink | « Hide ]

Holger Hoffstaette added a comment - 27/Jun/06 02:41 PM

Actually I think the following LoanBroker exception might be caused by the same root cause:

[06-27 13:50:47] WARN DefaultMessageAdapter _vmConnector#4171180._vmConnector#4171180.dispatchers.dispatcher.4: setProperty(key, value) called with null value; removing key: method; please report the following stack trace to dev@mule.codehaus.org.
java.lang.Throwable
at org.mule.providers.AbstractMessageAdapter.setProperty(AbstractMessageAdapter.java:144)
at org.mule.providers.DefaultMessageAdapter.<init>(DefaultMessageAdapter.java:96)
at org.mule.impl.MuleMessage.<init>(MuleMessage.java:65)
at org.mule.providers.vm.VMMessageReceiver.onEvent(VMMessageReceiver.java:88)
at org.mule.providers.vm.VMMessageDispatcher.doDispatch(VMMessageDispatcher.java:159)
at org.mule.providers.AbstractMessageDispatcher$Worker.run(AbstractMessageDispatcher.java:485)
at org.mule.impl.work.WorkerContext.run(WorkerContext.java:290)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:534)

..namely some concurrency problem with mutable endpoints/message props as used by the Axis provider. The above is also very rare and happens mostly after the first or second requests, not after that.

[ Permlink | « Hide ]

Travis Carlson added a comment - 12/Sep/06 12:47 PM

This thread discusses yet another sporadic problem in the LoanBroker-ESB example, apparently due to concurrency issues:
http://www.nabble.com/Re%3A-LoanBroker-ESB-test-failing...-tf2223856.html

[ Permlink | « Hide ]

Travis Carlson added a comment - 28/Sep/06 10:31 AM

Assigning over to Ross as per his comment.

[ Permlink | « Hide ]

Ross Mason added a comment - 03/Oct/06 03:51 AM

The issue with the VoIP example was with the Static Recipient list because it wasn't creating a clean copy of the message for each endpoint it was sending one. This issue was fixed for 1.3. But the LoanBroker bug is still outstanding, though we do have a work around.

[ Permlink | « Hide ]

Travis Carlson added a comment - 18/Oct/06 12:18 PM

Closing this since the VOIP issue was fixed for 1.3

The related (outstanding) issue with the LoanBroker examples should be followed up on ~~MULE-1075~~