[esb-issues] [JBoss JIRA] Commented: (JBESB-1434) Caching service invokers in EsbNotifier/EsbActionHandler can require restart of server

[Jiri Pechanec (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-1434?page=comments#action_12395905 ] 
            
Jiri Pechanec commented on JBESB-1434:
--------------------------------------

I was swapping File transport with JMS when I was testing jBPM integration. The problem is that there was no exception but the messages were not processed. After restart the message processing worked OK again.
My guess was that after the change the EPR still operated over the dir as  File EPR as was cached in service invoker in static variable. Moreover when you change the transport this way and the dir is still there then there is no reason for File invoker to fail.



> Caching service invokers in EsbNotifier/EsbActionHandler can require restart of server
> --------------------------------------------------------------------------------------
>
>                 Key: JBESB-1434
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1434
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Process flow
>    Affects Versions: 4.2.1 CP1
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Little
>            Priority: Critical
>             Fix For: 4.2.1 CP1
>
>
> If you change the trnsport definition of service and redeploy application the cached service invoker can malfunction and server restart is required.

-- 
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