Sorry, I did misunderstand you... (I was a little tired, on friday...) If thought it was already fixed in the 2.4.0.CR2 and thought this was only a problem with jboss remoting.
I made all of this work by patching Jboss-remote (to fix this) Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java and I did patch jboss-messaging too, in order to fix this point: Exception in thread "Thread-13" java.security.AccessControlException: access denied (java.lang.RuntimePermission setContextClassLoa | der) | at java.security.AccessControlContext.checkPermission(Unknown Source) | at java.security.AccessController.checkPermission(Unknown Source) | at java.lang.SecurityManager.checkPermission(Unknown Source) | at java.lang.Thread.setContextClassLoader(Unknown Source) | at org.jboss.messaging.util.JBMExecutor$TCLExecutor.run(JBMExecutor.java:75) In both cases, my patch was a quick and dirty one, adding some AccessController.doPrivileged(PrivilegedAction) blocks. Thanks for the quick answers, LK View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149910#4149910 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149910 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
