Please report new issues athttps://github.com/DOCGroup
The problem occurs with AMI invocations to a server with a persistent IOR. After one invocation failed because the server went down, all following invocations after a server restart fail silently. But when I use SMI instead, all invocations after a server restart return successfully. Reproducy by: I've written a simple example to reproduce the problem - sourcecode available under the URL above. Just adapt the ACE_ROOT in the Makefile, then: execute ./runtest_ami.sh to build and run the AMI version execute ./runtest_smi.sh to build and run the SMI version The testscript starts the server and the client. After 5 seconds, it kills the server. The client gets an exception and prints "failed" with both versions. After another 5 seconds, the server is restarted. With the SMI version, all following invocations succeed again. With the AMI version, all following invocations fail silently (neither exception nor successfull return). Btw, I discovered similary behaviour with oneway invocations in the past. Workaround: None, except to use many threads and SMI to achieve "non-blocking" behaviour, but i wanted to get around this by using AMI...
Created attachment 275 [details] Test case that shows failure of AMI while SMI works
Assigning the bug to me. Should be able to take a look. If this misses this beta, we will surely get it in for the next
corbaloc url is used by the client. Obviously AMI can't yet deal with location forward reply.
I verified that this problem is related to corbaloc URLs. I modified the testcase to use a stringified IOR, and this works.
Fri Jan 13 13:24:12 UTC 2006 Johnny Willemsen <jwillemsen@remedy.nl> * tests/Bug_1869_Regression/*: Added this regression to cvs, no fix yet and regression could be improved more to give more output to the user
Changed component to AMI
to pool