It's possible that for security reasons, this particular system only allows opening listener connections on selected ports.
One thing you might try, however, is to code the URL as "localhost:4444" instead of an implied host. Just in case it's not smart enough to figure that out.
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
I found the problem. It appears that the JBed JVM has a problem with listening on a port. Be it ServerSocketConnection or DatagramConnection. the error is the same.
I found a way around this problem. I installed a Creme JVM (which is free for evaluation) and this is a CDC JVM which does not have support for stream sockets but does have support for datagram sockets. The datagram socket seems to be working well, even though I have to take care of the reliability aspect.
You can't have everything. Where would you put it?
SKIP - a book about connecting industrious people with elderly land owners