Possible bug? (was Re: [omniORB] Fatal exception during event sending)

vonWedel@lfpt.rwth-aachen.de vonWedel@lfpt.rwth-aachen.de
Wed, 17 Jan 2001 14:13:40 +0100


Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 0049E3BBC12569D7_=
Content-Type: text/plain; charset="us-ascii"

Hi again,

Okay, I'm getting closer now. The statement from the trace that
omniDynamic is not being linked is just misleading, it is the same
for the type test stuff in omniORBpy/examples (which do work).

Instead it seems, as it is not possible to send some object
reference using an Any with typecode = CORBA._tc_Object:

I have meanwhile identified that the problem obviously depends
on the filterable data part of the structured event instance that is
going to be sent. One of the items in the property list is used to
transfer an object reference with the event. As a 'toy' item for
testing I use the root naming context of omniNames.

The transmission of the structured event is only possible if the
typecode for the Any value is either CosNaming._tc_NamingContext
or CosNaming._tc_NamingContextExt. Formerly, I used
CORBA._tc_Object which has led to a fatal exception as described
previously.

I can hardly believe that the behavior experienced is intended like this?

Lars








vonWedel@lfpt.RWTH-Aachen.DE
Sent by: owner-omniorb-list@uk.research.att.com
17/01/01 12:01

 
        To:     omniorb-list@uk.research.att.com
        cc: 
        Subject:        [omniORB] Fatal exception during event sending


Hi, 

using Python 2.0 on Solaris 2.7 together with omniORB and omniORBpy 
I get a fatal exception when working with omniNotify. I can create a new 
event channel, connect a push consumer and a push supplier to it 
(in separate Python processes). When I try to push the event to the 
channel like this: 

        evt = CosNotification.StructuredEvent(evt_header, fd_body, 
txn_val) 
        self.str_px.push_structured_event(evt) 

I get: 

        Run-time exception error; current exception: fatalException 
                No handler for exception. 

I know that this is of little help... What could I do to give you (and me) 
some 
hints about what is happening here? 

Lars 


--=_alternative 0049E3BBC12569D7_=
Content-Type: text/html; charset="us-ascii"




<br><font size=2 face="sans-serif">Hi again,</font>
<br>
<br><font size=2 face="sans-serif">Okay, I'm getting closer now. The statement from the trace that</font>
<br><font size=2 face="sans-serif">omniDynamic is not being linked is just misleading, it is the same</font>
<br><font size=2 face="sans-serif">for the type test stuff in omniORBpy/examples (which do work).</font>
<br>
<br><font size=2 face="sans-serif">Instead it seems, as it is not possible to send some object</font>
<br><font size=2 face="sans-serif">reference using an Any with typecode = CORBA._tc_Object:</font>
<br>
<br><font size=2 face="sans-serif">I have meanwhile identified that the problem obviously depends</font>
<br><font size=2 face="sans-serif">on the filterable data part of the structured event instance that is</font>
<br><font size=2 face="sans-serif">going to be sent. One of the items in the property list is used to</font>
<br><font size=2 face="sans-serif">transfer an object reference with the event. As a 'toy' item for</font>
<br><font size=2 face="sans-serif">testing I use the root naming context of omniNames.</font>
<br>
<br><font size=2 face="sans-serif">The transmission of the structured event is only possible if the</font>
<br><font size=2 face="sans-serif">typecode for the Any value is either CosNaming._tc_NamingContext</font>
<br><font size=2 face="sans-serif">or CosNaming._tc_NamingContextExt. Formerly, I used</font>
<br><font size=2 face="sans-serif">CORBA._tc_Object which has led to a fatal exception as described</font>
<br><font size=2 face="sans-serif">previously.</font>
<br>
<br><font size=2 face="sans-serif">I can hardly believe that the behavior experienced is intended like this?</font>
<br>
<br><font size=2 face="sans-serif">Lars</font>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=2 face="sans-serif"><b>vonWedel@lfpt.RWTH-Aachen.DE</b></font>
<br><font size=2 face="sans-serif">Sent by: owner-omniorb-list@uk.research.att.com</font>
<p><font size=2 face="sans-serif">17/01/01 12:01</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;omniorb-list@uk.research.att.com</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;[omniORB] Fatal exception during event sending</font></table>
<br>
<br><font size=2 face="sans-serif"><br>
Hi,</font><font face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
using Python 2.0 on Solaris 2.7 together with omniORB and omniORBpy</font><font face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
I get a fatal exception when working with omniNotify. I can create a new</font><font face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
event channel, connect a push consumer and a push supplier to it</font><font face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
(in separate Python processes). When I try to push the event to the</font><font face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
channel like this:</font><font face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;evt = CosNotification.StructuredEvent(evt_header, fd_body, txn_val)</font><font face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;self.str_px.push_structured_event(evt)</font><font face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
I get:</font><font face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;Run-time exception error; current exception: fatalException</font><font face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;No handler for exception.</font><font face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
I know that this is of little help... What could I do to give you (and me) some</font><font face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
hints about what is happening here?</font><font face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
Lars</font><font face="Times New Roman"> </font>
<br>
<br>
--=_alternative 0049E3BBC12569D7_=--