[ http://jira.jboss.com/jira/browse/JBESB-1590?page=all ] Tom Fennelly updated JBESB-1590: -------------------------------- Description: Task JBESB-1568 identified an issue thrown up by the scheduler code, but in doing so also highlighted a secondary issue in the way that the gateway itself manages the lifecycles of the files it is processing. Specifically... when a file "disappears" while that instance of the gateway is processing it (or about to process it). This could happen through a single FileGateway config before JBESB-1582 was fixed, but can still happen when multiple gateways are configured to process the same fileset in the same directory. The gateway should handle such contention issue more cleanly. Should it support multiple gateway instances processing a single fileset in a single directory? This could be a head wrecker to get right *and prove right* on all platforms! We could just document this as something that's not supported. It should def be able to handle different filesets in the same dir using multiple gateway instances! was: Task JBESB-1568 identified an issue thrown up by the scheduler code, but in doing so also highlighted a secondary issue in the way that the gateway itself manages the lifecycles of the files it is processing. Specifically... when a file "disappears" while that instance of the gateway is processing it (or about to process it). This could happen through a single FileGateway config before JBESB-1568 was fixed, but can still happen when multiple gateways are configured to process the same fileset in the same directory. The gateway should handle such contention issue more cleanly. Should it support multiple gateway instances processing a single fileset in a single directory? This could be a head wrecker to get right *and prove right* on all platforms! We could just document this as something that's not supported. It should def be able to handle different filesets in the same dir using multiple gateway instances! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1590?page=all ] Tom Fennelly reassigned JBESB-1590: ----------------------------------- Assignee: Tom Fennelly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1590?page=com.atlassian.jira.plu... ] Douglas Zanatta Ulian commented on JBESB-1590: ---------------------------------------------- Hi, I'm facing the exact same issue. Im using JBossESB-4.4.GA, using a single thread. Is this really solved? Is there any special configuration that I should use to avoid it, like setting some attribute or property? Thanks for the attention, Regards, Douglas -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira