The PolicyError exception will go away if you comment out just the SASInitializer, which is the one that installs a request interceptor and thus affects performance. The CSIv2Initializer must remain enabled, as it defines a POA policy that is used at EJB deployment time. This initializer does not install a request interceptor, so it should not cause a decrease on performance.
There is another problem, though. Due to a coding oversight in releases 4.0.0 and 4.0.1 of JBoss, commenting out the just the SASInitializer will result in another exception. No exception will be thrown at EJB deployment time, but you will get an exception whenever the EJB receives a remote call. This problem has been fixed in CVS and won't be present in JBoss 4.0.2. Right now what you can do is get Branch_4_0 from CVS and build JBoss 4.0.2beta, which works properly with no request interceptors at all (with SASInitializer and Tx interceptor initializers commented out). Regards, Francisco View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862250#3862250 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862250 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
