[jacorb-bugs] [Bug 972] New: Method _repository_id() not found when invoked from C++ (TAO)

bugzilla-daemon at jacorb.org bugzilla-daemon at jacorb.org
Tue Dec 10 17:24:21 CET 2013


http://www.jacorb.org/bugzilla/show_bug.cgi?id=972

            Bug ID: 972
           Summary: Method _repository_id() not found when invoked from
                    C++ (TAO)
           Product: JacORB
           Version: 3.3
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: ORB
          Assignee: jacorb-bugs at lists.spline.inf.fu-berlin.de
          Reporter: joseph.h.schwarz at gmail.com

The org.omg.Object._repository_id() method, when invoked by a Java client on a
Java object in another JVM (on a single PC) works correctly. However, when
invoked from from a C++ process via TAO, it fails with:

2013-12-09T15:45:29.009 WARNING [jacorb at monColTestCont] rid: 11 opname:
_repository_id starts with request processing
2013-12-09T15:45:29.009 WARNING [jacorb at monColTestCont] rid: 11 opname:
_repository_id invokeOperation on servant (stream based)
2013-12-09T15:45:29.010 INFO [jacorb at monColTestCont] rid: 11 opname:
_repository_id invocation: system exception was thrown.
org.omg.CORBA.BAD_OPERATION: _repository_id not found
    at alma.ACS.ROdoublePOA._invoke(<MyImpl>)
    at
org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:362)
    at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:684)
    at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:846)

>From the implementation provided by the Jacorb Delegate class (where the method
is called "repository_id()," it appears that only a local invocation is
foreseen. (We see the same implementation in Jacorb 3.4-beta.)

 Since our system makes liberal use of interacting C++, Java and Python
objects, interoperability of this kind is essential for us. We have been using
Jacorb 2.2.4 with TAO successfully for many years, but we needed the
functionality of the newer org.omg APIs (already in TAO and now in Jacorb 3.x
as well) in order to be able to take advantage of functionality such as
_repository_id(); the above problem is a major hitch in our upgrade.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spline.inf.fu-berlin.de/pipermail/jacorb-bugs/attachments/20131210/48a7a4df/attachment.html>


More information about the jacorb-bugs mailing list