I posted last week about a dieing mx server. After installing seefusion it appears at some point all the available threads stick. They just sit there for 15 minutes unable to complete. It appears that mx never completes the threads.
Here is what vex's me beyond the fact I cannot figure why the heck they all stick all of a sudden. 1. I have mx set to kill anything over 15 seconds. 2. using seeFusion it has a kill thread command (Java's Thread.stop()) These threads won't respond to either of these, mx cannot time them out, and thread.stop() seems to have no effect. Anyone encounter this? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225902 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
