clorb-devel Mailing List for Common Lisp ORB

[..snip...server traces from cmu cl...]
 
> This is from make-string. It must be LEN that is -1. And it must be
> the operation name it is trying to unmarshal. I can't figure out why
> the length is -1.
> 
> What kind of machine and OS are you running on? 

I'm running this on FreeBSD 3.3 and with CMU CL 18b and clisp 
2000-03-06.

> Could you try and load the "test-marshal.lisp" and see if it 
produces any 
> errors?

test-marshal.lisp loads fine and tests with zero errors. This inspired 
me to try out the other tests, and the only one which fails is 
test-intern.lisp (this is the cmu cl output, but it also fails on 
clisp with similar output):

* (load "test-intern.lisp")

; Loading #p"/usr/home/chapmanb/clorb-0.2/test-intern.lisp".

Warning: This variable is undefined:
  *R

Warning: This function is undefined:
  INTERNALIZE
;;; In test case Test hello
;;;! Exception 
Error in function PCL::FIND-CLASS-FROM-CELL:  No class named: 
IREPOSITORY.
;;; ------------- Test Internalize finished -----------------
;;; 1 tests executed with 1 errors

Could the problem be due to sockets? (since that seems to be a 
sticking point with the clisp server). The error didn't really seem 
like it, but I am also still working on getting Dan Barlow's socket 
code working on FreeBSD, so I am using whatever socket capabilities 
cmu cl has. Just a random idea because I'm not positive where to go. 
To talk myself out of that, if Eric has this problem as well, this may 
not be the case.

Onward to clisp:

> Eric Marsden:
> 
>>   bc> [7]> (run-hello :file "hw.ior")
>>   bc> 
>>   bc> *** - UNIX error 49 (EADDRNOTAVAIL): Can't assign requested 
address
>> 
>> it looks like you already have something running on the port 
specified
>> in clorb-options.lisp (maybe simply CLORB in another lisp 
instance?).

Lennart:
> I think that that would usually give another error code.

> I wonder what that error code means. It is probably not the same as
> "address already in use". Could you try to find a description of this
> error. The man-pages socket(2), bind(2) and listen(2) might contain
> something. The Linux man-pages doesn't (they say "SVr4 documents
> additional EADDRNOTAVAIL, EADDRINUSE, and ENOSR general error
> conditions").

Okay, I double checked that port and nothing is running on it. For 
fun, I modified the port to ones that I've used previously (for 
python programming, tho), and added Eric's fixes for defining the 
*host* without relieving the errors :-<.
    The FreeBSD bind man page has the following to say about 
EADDNOTAVAIL:

[EADDRNOTAVAIL]
            The specified address is not available from the local 
machine.

and I guess if it was the problem Eric mentioned, I would see an error 
like:

    [EADDRINUSE]
                  The specified address is already in use.

Of course, now I don't have any idea what kind of problems cause an 
address not to be available :-<.

Eric:
>> The hello example works fine for me with CLISP (the
>> InterfaceRepository has to know about the IDL:Hello/World interface
>> first).

Lennart: 
> An alternative is to load the hello-idl.lisp file before running
> run-hello. That allows the hello servant to provide the client with 
an
> InterfaceDef object for the Hello:World interface.
> 
> With (clorb::load-ir) and the above file, it should be possible to 
run
> the example without an InterfaceRepository.

The (clorb::load-ir) method is what I've been using to try and get 
this working (I'm following almost exactly the information in the 
README). So if this way works fine for both of you on Solaris and 
Linux, then there must be a problem with clisp and FreeBSD sockets? Is 
the best route now to go to the clisp list and see what I can find out 
there?
    I really appreciate both of you helping me with these problems. If 
there is anything else at all I can try, I would be happy to do so. 
Thanks again!

Brad

Eric Marsden <ema...@ma...> writes:

>   bc> [7]> (run-hello :file "hw.ior")
>   bc> 
>   bc> *** - UNIX error 49 (EADDRNOTAVAIL): Can't assign requested address
> 
> it looks like you already have something running on the port specified
> in clorb-options.lisp (maybe simply CLORB in another lisp instance?).

I think that that would usually give another error code.

> The hello example works fine for me with CLISP (the
> InterfaceRepository has to know about the IDL:Hello/World interface
> first).

An alternative is to load the hello-idl.lisp file before running
run-hello. That allows the hello servant to provide the client with an
InterfaceDef object for the Hello:World interface.

With (clorb::load-ir) and the above file, it should be possible to run
the example without an InterfaceRepository.
-- 
Lennart Staflin  <le...@ly...>

Brad Chapman <cha...@ar...> writes:

> * (hello-client :file "hw.ior")
> Error in function CLORB::UNMARSHAL-GIOP-HEADER:  Not a GIOP message
> 
> Restarts:
>   0: [ABORT] Return to Top-Level.
> 
> Debug  (type H for help)
> 
> (CLORB::UNMARSHAL-GIOP-HEADER
>  #S(CLORB::BUFFER
>       :OCTETS #(0 0 0 0 0...)

The client seems to have read in a lot of zeros from the stream. That
is strange. Could be some error handling that is wrong.

Any way, this is probably a consequence on the error on the server
side.


> The server also crashes when this occurs, with the following backtrace:
> 
> * (run-hello :file "hw.ior")
> Compiling LAMBDA (#:G1518 #:G1519 #:G1520 #:G1521 #:G1524 #:G1525):
> Compiling Top-Level Form:
> ;;; Acception tcp connection: 6
> ;;  - to stream: #<Stream for descriptor 6>
> ;; Receive (60)
> 
> Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
>    -1 is not of type (MOD 536870911)
> 
> Restarts:
>   0: [ABORT] Return to Top-Level.
> 
> Debug  (type H for help)
> 
> (CLORB::UNMARSHAL-STRING
>  #S(CLORB::BUFFER
>       :OCTETS #(71 73 79 80 1...)
>       :POSITION 32
>       :BYTE-ORDER 1
>       :START-POS 0))
> Source:
> ; File: /usr/home/chapmanb/clorb-0.2/clorb-unmarshal.lisp
> (MAKE-STRING LEN)

This is from make-string. It must be LEN that is -1. And it must be
the operation name it is trying to unmarshal. I can't figure out why
the length is -1.

What kind of machine and OS are you running on? Could you try and load
the "test-marshal.lisp" and see if it produces any errors?



> clisp
> -----
> On clisp, I get an error immediately upon trying to start up the server,
> and it gives the following trace.
> 
> [7]> (run-hello :file "hw.ior")
> 
> *** - UNIX error 49 (EADDRNOTAVAIL): Can't assign requested address

I wonder what that error code means. It is probably not the same as
"address already in use". Could you try to find a description of this
error. The man-pages socket(2), bind(2) and listen(2) might contain
something. The Linux man-pages doesn't (they say "SVr4 documents
additional EADDRNOTAVAIL, EADDRINUSE, and ENOSR general error
conditions").

-- 
Lennart Staflin  <le...@ly...>

I think the following definition of *host* is more useful than
"localhost" as currently defined in clorb-options.lisp (otherwise IORs
are useless on other machines).

   (defparameter *host*
     #+(or cmu sbcl)
     (unix:unix-gethostname)
     #+clisp
     (let ((mi (machine-instance)))
       (subseq mi 0 (position #\Space mi))))

-- 
Eric Marsden                          <URL:" rel="nofollow">http://www.laas.fr/~emarsden>

>>>>> "bc" == Brad Chapman <cha...@ar...> writes:

  bc> * (hello-client :file "hw.ior")
  bc> Error in function CLORB::UNMARSHAL-GIOP-HEADER:  Not a GIOP message

I get the same error (CMUCL on Solaris using db-sockets) when invoking
_list on the InterfaceRepository; I haven't tracked down where it
comes from.


  bc> * (run-hello :file "hw.ior")
  bc> Compiling LAMBDA (#:G1518 #:G1519 #:G1520 #:G1521 #:G1524 #:G1525):
  bc> Compiling Top-Level Form:
  bc> ;;; Acception tcp connection: 6
  bc> ;;  - to stream: #<Stream for descriptor 6>
  bc> ;; Receive (60)
  bc> 
  bc> Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
  bc>    -1 is not of type (MOD 536870911)

same.

  
  bc> On clisp, I get an error immediately upon trying to start up the
  bc> server, and it gives the following trace.
  bc> 
  bc> [7]> (run-hello :file "hw.ior")
  bc> 
  bc> *** - UNIX error 49 (EADDRNOTAVAIL): Can't assign requested address

it looks like you already have something running on the port specified
in clorb-options.lisp (maybe simply CLORB in another lisp instance?).
The hello example works fine for me with CLISP (the
InterfaceRepository has to know about the IDL:Hello/World interface
first).
  
-- 
Eric Marsden                          <URL:" rel="nofollow">http://www.laas.fr/~emarsden>

Hello;
	I've been working on trying to get the hello-world example client
and server (thanks incredibly much for the simple example to work with!)
running on CMUCL and CLISP, but have not been having much luck :-<. I
finally got myself stuck where I can't move any further, so I thought I
would ask here. I apologize in advance if the problems are due to my
inexperience with lisp.

CMUCL
-----
I thought I would start with this since I have had the most luck here so far.
I have been successful at starting up a server without any errors, but when
I open up a new interpreter and try to run a client against the server, I
get the following error in the client:

* (hello-client :file "hw.ior")
Error in function CLORB::UNMARSHAL-GIOP-HEADER:  Not a GIOP message

Restarts:
  0: [ABORT] Return to Top-Level.

Debug  (type H for help)

(CLORB::UNMARSHAL-GIOP-HEADER
 #S(CLORB::BUFFER
      :OCTETS #(0 0 0 0 0...)
      :POSITION 1
      :BYTE-ORDER 1
      :START-POS 0))
Source:
; File: /usr/home/chapmanb/clorb-0.2/clorb-unmarshal.lisp
(ERROR "Not a GIOP message")
0] bac

0: (CLORB::UNMARSHAL-GIOP-HEADER
    #S(CLORB::BUFFER
         :OCTETS #(0 0 0 0 0...)
         :POSITION 1
         :BYTE-ORDER 1
         :START-POS 0))
1: (CLORB::CORBA-GET-NEXT-RESPONS-1 #<Stream for descriptor 5> :WAIT T)
2: (CLORB::REQUEST-GET-RESPONSE #<OMG.ORG/CORBA:REQUEST {922C9C5}> NIL)
3: (CLORB::REQUEST-INVOKE #<OMG.ORG/CORBA:REQUEST {922C9C5}> #<unused-arg>)
4: (CLORB::OBJECT-INTERFACE
    #<OMG.ORG/CORBA:PROXY "IDL:Hello/World:1.0" @ localhost:4711>)
5: (CLORB::OBJECT-OPDEF
    #<OMG.ORG/CORBA:PROXY "IDL:Hello/World:1.0" @ localhost:4711>
    "greet")
6: (CLORB::OBJECT-CREATE-REQUEST
    #<OMG.ORG/CORBA:PROXY "IDL:Hello/World:1.0" @ localhost:4711>
    "greet"
    NIL)
7: (CLORB:INVOKE #<OMG.ORG/CORBA:PROXY "IDL:Hello/World:1.0" @ localhost:4711>
                 "greet")
8: (INTERACTIVE-EVAL (HELLO-CLIENT :FILE "hw.ior"))
9: (COMMON-LISP::%TOP-LEVEL)
10: (COMMON-LISP::RESTART-LISP)

The server also crashes when this occurs, with the following backtrace:

* (run-hello :file "hw.ior")
Compiling LAMBDA (#:G1518 #:G1519 #:G1520 #:G1521 #:G1524 #:G1525):
Compiling Top-Level Form:
;;; Acception tcp connection: 6
;;  - to stream: #<Stream for descriptor 6>
;; Receive (60)

Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
   -1 is not of type (MOD 536870911)

Restarts:
  0: [ABORT] Return to Top-Level.

Debug  (type H for help)

(CLORB::UNMARSHAL-STRING
 #S(CLORB::BUFFER
      :OCTETS #(71 73 79 80 1...)
      :POSITION 32
      :BYTE-ORDER 1
      :START-POS 0))
Source:
; File: /usr/home/chapmanb/clorb-0.2/clorb-unmarshal.lisp
(MAKE-STRING LEN)
0] bac

0: (CLORB::UNMARSHAL-STRING
    #S(CLORB::BUFFER
         :OCTETS #(71 73 79 80 1...)
         :POSITION 32
         :BYTE-ORDER 1
         :START-POS 0))
1: (CLORB::DECODE-REQUEST
    #S(CLORB::SERVER-REQUEST
         :STREAM #<Stream for descriptor 6>
         :BUFFER #S(CLORB::BUFFER
                      :OCTETS #
                      :POSITION 32
                      :BYTE-ORDER 1
                      :START-POS 0)
         :MSGTYPE 0
         :IIOP-VERSION NIL
         :SERVICE-CONTEXT #()
         ...))
2: (CLORB::GET-MESSAGE #<Stream for descriptor 6>)
3: (CLORB::|(PCL::FAST-METHOD HANDLE-STREAM (CLORB-ADAPTOR T))| #<unused-arg>
                                                                #<unused-arg>
                                                                #<unused-arg>
                                                                #<Stream for de
scriptor 6>)
4: (CLORB::|(PCL::FAST-METHOD SERVER-FALLBACK (CLORB-ADAPTOR))| #<unused-arg>
                                                                #<unused-arg>
                                                                #<CLORB::CLORB-
ADAPTOR {922FEAD}>)
5: (CLORB::ORB-WAIT #<OMG.ORG/CORBA:ORB {922F65D}> NIL)
6: (CLORB::|(PCL::FAST-METHOD OMG.ORG/FEATURES:RUN (ORB))| #<unused-arg>
                                                           #<unused-arg>
                                                           #<OMG.ORG/CORBA:ORB
{922F65D}>
                                                           NIL)
7: (INTERACTIVE-EVAL (RUN-HELLO :FILE "hw.ior"))
8: (COMMON-LISP::%TOP-LEVEL)
9: (COMMON-LISP::RESTART-LISP)

clisp
-----
On clisp, I get an error immediately upon trying to start up the server,
and it gives the following trace.

[7]> (run-hello :file "hw.ior")

*** - UNIX error 49 (EADDRNOTAVAIL): Can't assign requested address
1. Break [8]> Backtrace-1

- NIL
- #<SYSTEM::SIMPLE-OS-ERROR #x203950D1>
frame binding variables (~ = dynamically):
  | ~ SYSTEM::*PRIN-STREAM* <--> #<UNBOUND>
- #<SYSTEM::SIMPLE-OS-ERROR #x203950D1>
- 4711
- #<COMPILED-CLOSURE CLORB::OPEN-PASSIVE-SOCKET>
- 4711
- #<COMPILED-CLOSURE CLORB::SETUP-SERVER>
- #<OMG.ORG/CORBA:ORB #x203799A5>
- #<COMPILED-CLOSURE CLORB::ROOT-POA>
- #<OMG.ORG/CORBA:ORB #x203799A5>
- #<COMPILED-CLOSURE CLORB::ROOT-POA>
- ("RootPOA" . #<COMPILED-CLOSURE CLORB::ROOT-POA>)
- "RootPOA"
- #<COMPILED-CLOSURE #:TOP-LEVEL-FORM-21-2-1-1>
- ("RootPOA")
- #<OMG.ORG/CORBA:ORB #x203799A5>
- #<OMG.ORG/CORBA:ORB #x203799A5>
- #<COMPILED-CLOSURE SETUP-HELLO>
- NIL
- "hw.ior"
- SETUP-HELLO
- #<OMG.ORG/CORBA:ORB #x203799A5>
- #<COMPILED-CLOSURE RUN-HELLO>
- (:FILE "hw.ior")
- #<COMPILED-CLOSURE RUN-HELLO>
EVAL frame for form (RUN-HELLO :FILE "hw.ior")
- #<SYNONYM-STREAM *TERMINAL-IO*>
- #<SYNONYM-STREAM *TERMINAL-IO*>

Could anyone offer any advice about what exactly is going on in either
case, or suggest further paths that I could try? Thanks in advance for any
help!

Brad

I have made a new release of CLORB. It can be downloaded from

	<URL:" rel="nofollow">https://sourceforge.net/projects/clorb/>

There has been a lot of interface chagnes to make this release close
to the IDL/Lisp mapping.

I also included an Hello World example using mostly standard
interfaces.

-- 
Lennart Staflin  <le...@ly...>

Brad Chapman <cha...@ar...> writes:

> Hi Lennart;
>     Thanks for getting back with me! I thought I would send this to 
> your official development list...

> [...] I was just curious--what mapping 
> standard are you following. I had been looking around a bit and found 
> what appears to be the standard mapping on the omg page 
> (http://www.omg.org/cgi-bin/doc?orbos/99-05-18). Is this what you are 
> following? I know that ILU also has a LISP mapping, and I'm not 
> exactly positive if they differ. I just wanted to make sure I was 
> reading the right information :-)

The intent is to make it follow the OMG standard, currently
orbos/99-05-18. 

>     I was just curious, would you interested in assistance with any of 
> the coding on CLORB? As I mentioned, I'm really new to LISP and not 
> very proficient, but I am very interested in coding more in it to help 
> me learn. It is completely up to you, of course, but if you had a 
> small part of CLORB for me to work on, I would be very interested 
> (and appreciative for letting me help).

Yes I thinks so. First I need to get the interfaces sorted out. Then
code should be a bit more stable.

-- 
Lennart Staflin <le...@ly...>        /*/         (:ABSOLUTE :WILD)

Hi Lennart;
    Thanks for getting back with me! I thought I would send this to 
your official development list...

> I started writing an example, but the current interface to the
> portable object adapter (POA) is highly non-standard. And I want the
> example to be close to standard. I then started to try figuring out
> how the interface is supposed to be... 

Okay, this is no problem at all. I was just curious--what mapping 
standard are you following. I had been looking around a bit and found 
what appears to be the standard mapping on the omg page 
(http://www.omg.org/cgi-bin/doc?orbos/99-05-18). Is this what you are 
following? I know that ILU also has a LISP mapping, and I'm not 
exactly positive if they differ. I just wanted to make sure I was 
reading the right information :-)

> In effect, if you don't want to wait for the next release, you will
> have to do with the server in ns-server.lisp and client code in
> clorb-util.lisp (resolve and rebind).

That sounds great. I've been looking at things more, and I am in no 
rush, so waiting for the POA interface changes in the next release is 
no problem at all.
    I was just curious, would you interested in assistance with any of 
the coding on CLORB? As I mentioned, I'm really new to LISP and not 
very proficient, but I am very interested in coding more in it to help 
me learn. It is completely up to you, of course, but if you had a 
small part of CLORB for me to work on, I would be very interested 
(and appreciative for letting me help).
    Again, thanks for responding and for CLORB.

Brad

Testing new list.

-- 
Lennart Staflin  <len...@in...>  /*/  STEP Infotek AS,
http://www.infotek.no/  Gjerdrums vei 12, N-0486 Oslo, Norway