[ https://issues.jboss.org/browse/AS7-6088?page=com.atlassian.jira.plugin.s... ] Chao Wang commented on AS7-6088: -------------------------------- I accidentally found one similar thread when I tried to reproduce exception : https://community.jboss.org/thread/205228 and the EJB3.1 specification restrict: {quote} The enterprise bean must not attempt to manage threads. The enterprise bean must not attempt to start, stop, suspend, or resume a thread, or to change a thread’s priority or name. The enter- prise bean must not attempt to manage thread groups. These functions are reserved for the EJB container. Allowing the enterprise bean to manage threads would decrease the container’s ability to properly manage the runtime environment. {quote} [~dlmiles] Could you follow this article : http://www.adam-bien.com/roller/abien/entry/conveniently_transactionally_... try with java.util.concurrent.Executor approach ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-6088?page=com.atlassian.jira.plugin.s... ] Darryl Miles edited comment on AS7-6088 at 12/6/12 6:16 AM: ------------------------------------------------------------ Thanks for the link to spec. Did this restriction exist before EJB3.1 ? Even with this advice there is still a bug in that if you define 2 interfaces and one is Runnable it does not cause the SecurityException the bug would be the lack of consistency (and also the message not being very clear about the problem, i.e. it would be useful to contain the full class name trying to be accessed with an indication that access to the package is the cause of the security restriction). Such as: SecurityException: Prohibitied package name: java.lang (when trying to access java.lang.Runnable) Since it took a long time trying to work out which java.lang thing was the cause of the problem. Having digested the comment I do not think Executor pattern fits well for a long running thread. Is there a container managed service for managing real threads ? i.e. with priority and name and possibly thread groups. The code originally was an MBean or some service interface but JBoss took it away so it was converted for AS7 into something that worked. was (Author: dlmiles): Thanks for the link to spec. Did this restriction exist before EJB3.1 ? Even with this advice there is still a bug in that if you define 2 interfaces and one is Runnable it does not cause the SecurityException the bug would be the lack of consistency (and also the message not being very clear about the problem, i.e. it would be useful to contain the full class name trying to be accessed with an indication that access to the package is the cause of the security restriction). Having digested the comment I do not think Executor pattern fits well for a long running thread. Is there a container managed service for managing real threads ? i.e. with priority and name and possibly thread groups. The code originally was an MBean or some service interface but JBoss took it away so it was converted for AS7 into something that worked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira