Spring remoting retry and recovery
We will be using the spring remoting approach to access the Appistry resident modules.
I'm wondering what options we have for configuring the communications between the client and Appistry.
There are two reasons for this question.
1) Sometimes in development we may need to remotely debug an application in appistry. I've figured out how to do this,but one issue is that when I'm sitting at a break point the client times out (com.appistry.fabric.RecoverableTransactionException). So a strategy to extend that time out would be good. (I haven't tried tcp-connect-timeout yet).
2) I would like to ensure that in production that we are recovering from recoverable issues. So for instance if the fabric stops responding, does the client to retry for a while. Is there a best practice approach to this? Should we be catching certain exceptions and manually retrying?
Thank you,
-Vito








Here are some options for your bean factory:
processingTimeout: int
recoverTimeout: int
setupRetries: int
setupTimeout: int
autoRecover: boolean
resubmitFailedAutoRecover: boolean
For example:
<bean id="MapGenerator" class="com.appistry.spring.FabricProxyFactoryBean"> <property name="serviceInterface" value="IMappingService "/> <property name="fabric"><ref local="fabric"/></property> <property name="applicationName" value="..."/> <property name="componentName" value="MappingServices"/> <property name="processingTimeout" value="30"/> <property name="autoRecover" value="true"/> </bean>1.) If you want to extend the time the client waits for a response before it returns a message stating that it is recoverable, you will want increase the processingTimeout.
In the example above, I added:
2.) The auto retry option will allow tell your client to automatically try to recover until your recover timeout occurs.
In the example above, I added:
I can ask around to find out if anyone has a best practice solution or someone on the forums can chime in as well.
Excellent. Thank you.