[jira] Updated: (SM-1441) Add support for asynchronous messaging in File poller

["Lars Heinemann (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/SM-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Heinemann updated SM-1441:
-------------------------------

         Assignee:     (was: Lars Heinemann)
    Fix Version/s: 3.2.2
                   3.3
       Attachment: patch.diff
       Patch Info: [Patch Available]

I created a patch for the endpoint against the trunk.
The locking mechanism is still not working and it will throw a java.lang.IllegalMonitorStateException
when trying to unlock a file.

The SimpleLockManager should be reworked using a simplified Lock object that isn't aware of thread ownership.

IRC Log:
11:28	gnodet	without having to modify the code at all
11:29	gnodet	so either we get rid of that LockManager, or we implement a simplistic lock that does not rely on threads ownership
11:29	gnodet	which should be quite easy as we only use tryLock() and unlock()
11:30	lhein	yeah, so I will change the SimpleLockManager then
11:30	gnodet	well, if we do that, we need to implement the full Lock interface
11:30	lhein	yes, a lot of methods
11:30	gnodet	but that would be the best option imho
11:31	lhein	just need to spy on another Lock implementation...never did such things ;)
11:31	gnodet	i guess we could discard the lockInterruptibly and tryLock(long time, TimeUnit unit) for now
11:32	gnodet	actually, it may be done with a countdown latch
11:32	gnodet	not sure yet
11:32	gnodet	they all use the AbstractQueuedSynchronizer internally it seems
11:33	gnodet	so it may be the best option



> Add support for asynchronous messaging in File poller
> -----------------------------------------------------
>
>                 Key: SM-1441
>                 URL: https://issues.apache.org/activemq/browse/SM-1441
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-file
>    Affects Versions: 3.2.1
>            Reporter: Ron Gavlin
>             Fix For: 3.2.2, 3.3
>
>         Attachments: patch.diff
>
>
> Allow the endpoint to be configured to use asynchronous messaging instead of handling everything using sendSync(). 
> Also, support specifying a maximum concurrency level to avoid sending tons of messages to the bus and causing an OutOfMemory exception. 
> The solution here should also be applicable for the servicemix-ftp component (SEE SM-1282).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.