Hi Roedy.

I saw another thread in the 'talk about programming' network that you
answered  to FB.

He was saying that he has a couple of threads that are spawned and the code
that checks permissions is on the threads. These fail.

This got me thinking. I the two calls to create sockets that are failing in
my applet's main class, under the start() method. Guess what? They worked.

Now, I have a couple of threads that are started and make connections to a
server. These are failing. Even though the applet is signed correctly.

I have also read that classes must be assigned to a CodeBase that a policy
will cover. With a signed app I just assumed all code was covered for all
things.

So, my question is, The threading issue, is that a red herring? Or must I
handle the policies for each one?

I am getting a bit stuck here!

Steve

PS: The calls I make are:

1)
Socket o_Sock = new Socket(o_URL.getHost(), o_URL.getPort());

2)
SecurityManager o_SecurityManager = System.getSecurityManager();
    if (o_SecurityManager!=null){
     o_SecurityManager.checkConnect("127.0.0.1",0); //Works in main
class!!!
    }

OK, Found the problem.
Our applet is compiled using J++, which of course is a bad bad thing.
It is riddled with conditional compile options for SUN_JVM versions..

Then I realised that I am running a fiarly new verion of the JRE/JVM from
sun which of course changed the way they manage security.

Rolled back to 1.4.1nnn of the JRE and it all works!

My next task is to rip out all the conditional stuff and build a version
that works with both SUN and MS JVMs - probably on separate instances I
guess.

Hey ho..

Steve