Sandesha sequence auto termination
Hello, I found the following property: org.apache.sandesha2.storage.beans.RMSBean.avoidAutoTermination but I don't understand how it works AFAIS, the setter for this property is only called on the client side, so the client can ask Sandesha not to terminate the sequence? The problem seems to be that on the server side, the value of the property isn't set anywhere... so it remains false and the Sandesha server keeps sending TerminateSequence messages back to the client, as a response to the client's own TerminateSequence message(which probably is another bug)
Sandesha sequence auto termination
Hello, I found the following property: org.apache.sandesha2.storage.beans.RMSBean.avoidAutoTermination but I don't understand how it works AFAIS, the setter for this property is only called on the client side, so the client can ask Sandesha not to terminate the sequence? The problem seems to be that on the server side, the value of the property isn't set anywhere... so it remains false and the Sandesha server keeps sending TerminateSequence messages back to the client, as a response to the client's own TerminateSequence message(which probably is another bug)
Sandesha sequence auto termination
Hello, I found the following property: org.apache.sandesha2.storage.beans.RMSBean.avoidAutoTermination but I don't understand how it works AFAIS, the setter for this property is only called on the client side, so the client can ask Sandesha not to terminate the sequence? The problem seems to be that on the server side, the value of the property isn't set anywhere... so it remains false and the Sandesha server keeps sending TerminateSequence messages back to the client, as a response to the client's own TerminateSequence message(which probably is another bug)
Sandesha sequence auto termination
Hello, I found the following property: org.apache.sandesha2.storage.beans.RMSBean.avoidAutoTermination but I don't understand how it works AFAIS, the setter for this property is only called on the client side, so the client can ask Sandesha not to terminate the sequence? The problem seems to be that on the server side, the value of the property isn't set anywhere... so it remains false and the Sandesha server keeps sending TerminateSequence messages back to the client, as a response to the client's own TerminateSequence message(which probably is another bug)