So, it looks like this has to be combined with the relevant Thread model. Stopping the thread should be controlled from there.
On Tue, Mar 1, 2011 at 8:57 PM, Paul Fremantle <[email protected]> wrote: > Azeez > > Thread.stop() will kill a thread, but its highly dangerous because of the > way the JVM handles this. > > See http://download.oracle.com/javase/1.4.2/docs/api/java/lang/Thread.html > > We probably have to find some way of hooking into the thread and getting > the thread to commit suicide to be safe in a long running runtime. > > Paul > > On 1 March 2011 14:23, Afkham Azeez <[email protected]> wrote: > >> Thanks Danushka. It seems that we can use >> the java.lang.management.ThreadMXBean to get Thred information. However, >> that API does not allow killing the Threads. Perhaps, the our programming >> API should provide a method for tenant apps to get hold of a Thread, and >> then we can control those threads. However, this will not work for all >> cases. For example, if a tenant DS request is taking a long time to process, >> we should have a way to kill it. >> >> Azeez >> >> >> On Tue, Mar 1, 2011 at 6:03 PM, Danushka Menikkumbura >> <[email protected]>wrote: >> >>> I think we can do something based on JMX. >>>> >>> >>> I guess so. Maybe you have seen this but I hope "Monitoring the JVM" in[1] >>> would be useful. >>> >>> BTW, this is something that RRD was looking for :-). >>> >>> [1] - >>> http://www.ibm.com/developerworks/library/j-rtm1/index.html?ca=dgr-jw22javaruntime1&S_TACT=105AGX59&S_CMP=GR >>> >>> Thanks, >>> Danushka >>> >> >> >> >> -- >> *Afkham Azeez* >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> * >> * >> *Member; Apache Software Foundation; >> **http://www.apache.org/*<http://www.apache.org/> >> * >> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > Office: +44 844 484 8143 > Cell: +44 798 447 4618 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > [email protected] > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other confidential > information and is intended exclusively for the addressee/s. If you are not > the intended recipient/s, or believe that you may have received this > communication in error, please reply to the sender indicating that fact and > delete the copy you received and in addition, you should not print, copy, > retransmit, disseminate, or otherwise use the information contained in this > communication. Internet communications cannot be guaranteed to be timely, > secure, error or virus-free. The sender does not accept liability for any > errors or omissions. > -- *Afkham Azeez* Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, * * *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/> * email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
