Skip to main content

Listener when building Squawk with PLATFORM_TYPE=SOCKET

Please note these forums are being decommissioned and use the new and improved forums at
2 replies [Last post]
Joined: 2011-07-26


I build squawk with PLATFORM_TYPE=SOCKET in a Ubuntu linux with:
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode)

It build without problems.
When is try to start the Tests/SocketTests test with:

./squawk -Xioport:4567 -suite:tests/TestSockets/TestSockets

I get:
[DIAG] In main - squawk.c 0
[DIAG] in Squawk_main_wrapper 0
[DIAG] in Squawk_main 0
[DIAG] in Squawk_setup 0
[DIAG] in processArgs 0
*************** Tracing version ***************
[DIAG] setupMemory: ram size 0x800000
[DIAG] setupMemory: nvmSize size 0x800000
connect: Connection refused

I could not find any documentation on how to set up a proper listener for the socket connection on the corresponding port (4567 in my case)
should this happen "automagicaly", or what kind of steps are necessary?

kind regards

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2006-09-08

Wow, this wasn't documented well internally either, so thanks for asking.

The server half of the system can be started by running:

java -cp squawk.jar -port:4567 com.sun.squawk.vm.ChannelIO

We haven't had a reason to run in this configuration in a long time, and have been tempted to eliminate it. Are you using it as a way to get around the socket problems in the NATIVE configuration on linux, or is there a deeper reason to use it?


- Derek

Joined: 2011-07-26

thank you for looking that up,

the reason to try it was as a work around for the socket problems in the NATIVE configuration on linux,
in the end it was faster to work out the socket constant problem to the point where sockets are useable again.

thanks again