Now I'm a little bit closer. Now I get the following exception when running an applet on the html page:
at java.lang.Class.forName0(Native Method)
Caused by: java.security.AccessControlException: access denied (java.util.PropertyPermission org.jboss.util.NestedThrowable.parentTraceEnabled read)
I guess that's still problem of configuration.... Please help!
hmmm, and I guess important is that this exception is raising in this line:
topicConnection = topicConnectionFactory.createTopicConnection();
The first one was a security issue. You are not allowed to open TCP/IP sockets on any host but the one where the applet was downloaded.
I assume you solved the issue
The other one is a Class.forName which failed. Are you sure your applet have all the classes needed (check client jars)
Does your applet work fine with the AppletViewer?
Yes, I was very surprised that it works fine in Appletviewer, is it something with misiing jars?
You shouldn't be surprised. Doing what you are trying to achieve in an applet is not that easy. My first guess is a corrupted/missing jar.
In any case, it's related to your configuration/deployment. It has nothing to do with JBoss nor JMS in general.
Is your JBoss running on 22.214.171.124 ?
Yes, I have two network adapters, but my main IP is 126.96.36.199. My JBoss is running on that IP.
DAMNIT! please provide the full stracktrace when you have a problem...
If you check the cause, it's a security exception being thrown by the applet (meaning the applet has not the right to read some JBoss property or something)
You will have to sign your applet and give it the needed rights.
Thanks, and don't be agry, the full stacktrace is in my firsty post. I thought you've seen it... :)
I am not angry :o
Anyway, thanks for your help...
Could you solve this problem at all! I am having the same problem and it looks like not a problem of missing jar or some thing.
Thanks in advance,
People, this is basic applet behaviour. It is restricted by the sandbox security.
Look at the root cause of your exception. It is trying to do a getProperty() which it doesn't have permission to. It has nothing to do with missing jars!
To make it work, either:
1) Modify the java.policy file on your client to grand permission, or
2) Sign the damn JAR file :P