--- Begin Message ---
On 8/7/07, Keith Hodges <[EMAIL PROTECTED]> wrote:
> We in the gjallar camp have been trying to get a remote server
> connection without success. I am using beta2.
The Magma test cases run all tests across via the remote connection;
hundreds of them with multiple connects, disconnects and even quitting
the server image (twice!) in the middle of a huge commit and the
clients reconnect succesfully after the server recovery..
So can you tell me what code you are using to start the server and
then what code to connect the clients?
> It appears that it is sending 'connect' and it is being recieved as an
> MAMalformed etc due to the class id not being recognized. It is #207
> when the largest id in the ClassIdManager is 206.
This 'connect' request is sent only by the lower-level framework, Ma
client server, on behalf of Magma, to establish the #protocol (merely
a list of classes). You should check what class the client thinks is
207. 207 seems awfully high too, something is almost certainly not
configured correctly.
You should try two vanilla Magma images (without Gjaller), establish a
server on one:
MagmaServerConsole new
open: '/path/to/the/repository' ;
processOn: 1010 ;
inspect
and connect from another image:
(MagmaSession host: 'serverName' port: 1010)
connectAs: 'test' ;
inspect
Note you can connect to a Gjaller repository even without the Gjaller
code in the client; the missing classes will be created on the fly in
order to instantiate the domain instances (but with no methods).
> I also notice that the error occurs when it tries to send
> repositoryController to this MaMalformed error instance and this occurs
> outside of the MaError handler.
Yes. The Malformed check is actually in
MaTcpRequestServer>>#materializeRequest:.
> Is there some initialization that I need to do to get the class id's set
> up correctly?
No, not for Magma.
> Secondly sig tried opening a telnet to the magma port and sending random
> characters in. he got a rather drastic Out of Memory error and a
> corrupted image.
On the server or telnet client? I assume on the client right?
That'll learn him. :)
So he told Magma to listen on the port reserved for telnet?
Actually the server should have signaled a MalformedRequest error
which would have been serialized and shipped back to the telnet
client. Is that what happened?
I'm curious about this story, but this version of Magma is not
designed to be strong against misuse or attack, so I don't know how
concerned I'll be about it (again, for this version).
> It is late and I am not feeling very coherent. If you need more to go on
> I can give you an image tomorrow
Send me more information about what is being done, what steps
including the code snippets.
Regards,
Chris
--- End Message ---
_______________________________________________
Setools mailing list
[email protected]
http://lists.squeakfoundation.org/mailman/listinfo/setools
