[esb-issues] [JBoss JIRA] Commented: (JBESB-1434) Caching service invokers in EsbNotifier/EsbActionHandler can require restart of server
[ http://jira.jboss.com/jira/browse/JBESB-1434?page=comments#action_12395811 ]
Mark Little commented on JBESB-1434:
------------------------------------
Can you confirm that when you "change the transport of a service" you undeploy
the old one? If so, I can see why this causes problems. In fact, this is the only case
that makes sense and the fix is straightforward in that situation.
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: Kurt Stam
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