Bug #1722
RPC call to a Windows RSB RPC server causes exception on the Server when executing server.deactivate() on the cient
| Status: | Rejected | Start date: | 01/22/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | C++ | |||
| Target version: | rsb-0.9 |
Description
I have a C++ programm running as a RPC RSB Server and a java application running as a RPC calling client.
Using the example code on http://docs.cor-lab.de//rsb-manual/0.9/html/examples-basic.html#tutorial-rpc-server
The RPC Server throws an exception when I call the server.deactivate() on the calling java client.
The RPC server started the called procedure correctly. In the case of the example it properly returned the echo.
I can do this several times without problem.
But when I call the server.deactivate() on the java client, the C++ Programm throws an exception.
I can repeat this even after the exception was thrown. If I restart the client, call the remote procedure, the server will still execute the procedure, and again when the client calls server.deactivate(), the RPC server throws the exception.
Eine Ausnahme (erste Chance) bei 0x75d4c41f in ModuleSupervisor.exe: Microsoft C++-Ausnahme: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_weak_ptr> > an Speicherposition 0x046af8d0..
History
#1 Updated by J. Wienke over 10 years ago
Can you please add the full backtrace?
#2 Updated by J. Moringen about 10 years ago
- Status changed from New to Feedback
Did you manage to produce a backtrace?
#3 Updated by J. Moringen about 10 years ago
- Status changed from Feedback to Rejected
We cannot work on this without additional information.