[jacorb-developer] Unexpected exception on local calls interceptions

[Hugo Roenick]

Hi, Phil.

Just checked in older mail from Nick that attachments are stripped from list.
Should I place a Bug report in Bugzilla?

Best regards,
-- Hugo

On Apr 15, 2014, at 1:31 PM, Hugo Roenick <hroenick at gmail.com> wrote:

> Trying again as tar.gz ...
> 
> Not sure why its not making to the list.
> 
> 
> 2014-04-15 13:23 GMT-03:00 Hugo Roenick <hroenick at gmail.com>:
> Hi, Phil.
> 
> I used the 3.4 version. Also tested the with branch BZ976.
> 
> Not sure why the attachment did not make to the list... anyway attaching it again.
> 
> 
> 
> 
> Regards,
> -- Hugo
> 
> On Apr 15, 2014, at 11:22 AM, Phil Mesnier <mesnier_p at ociweb.com> wrote:
> 
> > Hi Hugo,
> >
> > Can you confirm the JacORB version you are using?
> > Also, your attachment did not make it to the list.
> >
> > Best regards,
> > Phil
> >
> > On Apr 15, 2014, at 7:54 AM, Hugo Roenick wrote:
> >
> >> Hi, all.
> >>
> >> I've experienced an unexpected behaviour while implementing a handshake protocol using CORBA interceptors and forward request.
> >>
> >> I built a small example to illustrate the problem that I'm experiencing. In this example my protocol defines that the server side will only accepts calls from who attaches a correct secret to requests. If a wrong secret is attached, then the server throws a NO_PERMISSION exception. On the client side, the interceptor knows that if it gets a NO_PERMISSION then he can retry the request attaching the correct secret. Forward Request is used by the client interceptor to retry the request.
> >>
> >> In this example the client will call "sayHello" to server, which print the hello message but he will also try to say goodbye, calling "sayGoodbye" to himself (emulating the local call) through a CORBA reference of him self.
> >>
> >> Running this demo we can see that the client reaches de server, the server prints the Hello message, but an exception occurs while checking if the CORBA reference to him self does exists.
> >>
> >> Here is the output from the server side:
> >>
> >> SLF4J: Class path contains multiple SLF4J bindings.
> >> SLF4J: Found binding in [jar:file:/Users/hroenick/Development/jacorb/3.4/lib/slf4j-jdk14-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> >> SLF4J: Found binding in [jar:file:/Users/hroenick/.m2/repository/org/slf4j/slf4j-jdk14/1.6.4/slf4j-jdk14-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> >> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> >> INFO Initialising ORB with ID:
> >> INFO InterceptorManager started with 1 Server Interceptors, 1 Client Interceptors and 0 IOR Interceptors
> >> INFO oid: 00 01 0F 2D 0B 1F 04 02 0F 2C 1E 28 10 06 30 46 38 14 14 1B ...-.....,.(..0F8...48 4C 1B                                                    HL.object is activated
> >> INFO Using server ID (5631190032) for transient POA
> >> INFO ORB run
> >> INFO Opened new server-side TCP/IP transport to 192.168.0.103:56885
> >> INFO Closed server-side transport to 192.168.0.103:56885
> >> INFO Opened new server-side TCP/IP transport to 192.168.0.103:56886
> >> INFO Closed server-side transport to 192.168.0.103:56886
> >> INFO Opened new server-side TCP/IP transport to 192.168.0.103:56887
> >> INFO Closed server-side transport to 192.168.0.103:56887
> >> INFO Opened new server-side TCP/IP transport to 192.168.0.103:56888
> >> Hello, World!
> >> INFO ClientConnectionManager: created new ClientGIOPConnection to 192.168.0.103:56882 (39b8d6f7)
> >> SEVERE rid: 0 opname: sayHello invocation: throwable was thrown.
> >> java.lang.NullPointerException
> >>      at org.jacorb.orb.Delegate.servant_postinvoke(Delegate.java:2561)
> >>      at org.jacorb.orb.Delegate.non_existent(Delegate.java:2205)
> >>      at org.omg.CORBA.portable.ObjectImpl._non_existent(ObjectImpl.java:61)
> >>      at demo.HelloImpl.sayHello(HelloImpl.java:15)
> >>      at demo.HelloPOA._invoke(HelloPOA.java:54)
> >>      at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:350)
> >>      at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:672)
> >>      at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:830)
> >> INFO Closed server-side transport to 192.168.0.103:56888
> >>
> >> Is this a bug of JacORB when dealing with local calls?
> >>
> >> PS: demo's source is attached to the mail.
> >>
> >> Regards,
> >> -- Hugo
> >>
> >> _______________________________________________
> >> jacorb-developer maillist  -  jacorb-developer at lists.spline.inf.fu-berlin.de
> >> https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer
> >
> > --
> > Phil Mesnier
> > Principal Software Engineer and Partner,   http://www.ociweb.com
> > Object Computing, Inc.                     +01.314.579.0066 x225
> >
> >
> >
> >
> > _______________________________________________
> > jacorb-developer maillist  -  jacorb-developer at lists.spline.inf.fu-berlin.de
> > https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer
> 
> 
> 
> 
> 
> -- 
> -- Hugo Roenick
> <localcall.tar.gz>