You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jamie McCrindle (JIRA)" <ji...@apache.org> on 2006/04/11 15:55:50 UTC
[jira] Created: (SM-395) InOut doesn't failover to another node if
source node is unavailable
InOut doesn't failover to another node if source node is unavailable
--------------------------------------------------------------------
Key: SM-395
URL: https://issues.apache.org/activemq/browse/SM-395
Project: ServiceMix
Type: Improvement
Components: servicemix-core
Versions: incubation
Reporter: Jamie McCrindle
Fix For: incubation
Currently, an InOut exchange will fail if its source component is unavailable.
Ideally, if there a a cluster of the same component on different nodes and the source component is unavailable, servicemix should failover and pass the InOut exchange to one of the live components.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (SM-395) InOut doesn't failover to another node if
source node is unavailable
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-395?page=all ]
Guillaume Nodet resolved SM-395:
--------------------------------
Fix Version: 3.0-M2
(was: incubation)
Resolution: Fixed
Assign To: Guillaume Nodet
ServiceMix now recognize and use 2 properties on the JBI exchange (defined in JBIConstants class):
* org.apache.servicemix.consumer.stateless
* org.apache.servicemix.provider.stateless
These properties tell the clustered flows (jms and jca) that the provider or consumer is stateless (or clustered statefull).
In these cases, the JBI exchange may not return back to the same component on the same node, but rather to the same
component on another node.
Author: gnodet
Date: Wed Apr 12 17:25:32 2006
New Revision: 393668
URL: http://svn.apache.org/viewcvs?rev=393668&view=rev
Log:
SM-395: InOut doesn't failover to another node if source node is unavailable
Added:
incubator/servicemix/trunk/servicemix-core/src/test/java/org/apache/servicemix/jbi/nmr/flow/jms/StatelessJcaFlowTest.java
incubator/servicemix/trunk/servicemix-core/src/test/java/org/apache/servicemix/jbi/nmr/flow/jms/StatelessJmsFlowTest.java
Modified:
incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/JbiConstants.java
incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/nmr/flow/jca/JCAFlow.java
incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/nmr/flow/jms/JMSFlow.java
incubator/servicemix/trunk/servicemix-core/src/test/java/org/apache/servicemix/jbi/nmr/flow/jms/PingService.java
> InOut doesn't failover to another node if source node is unavailable
> --------------------------------------------------------------------
>
> Key: SM-395
> URL: https://issues.apache.org/activemq/browse/SM-395
> Project: ServiceMix
> Type: Improvement
> Components: servicemix-core
> Versions: incubation
> Reporter: Jamie McCrindle
> Assignee: Guillaume Nodet
> Fix For: 3.0-M2
>
>
> Currently, an InOut exchange will fail if its source component is unavailable.
> Ideally, if there a a cluster of the same component on different nodes and the source component is unavailable, servicemix should failover and pass the InOut exchange to one of the live components.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira