I think there is a very simple solution to this which is much safer. Instead of triggering threads off in your class, move the thread body into a MDB and then simply send several messages from your session bean.
The MDB will enable your code to run asynchronously which is probably the effect you are trying to achieve. On Tue, 2002-10-15 at 13:46, rahul ganjoo wrote: > Guys any help with this would be much appreciated. > I am repeating the scenario here: > Environment: Jboss 3.0.3 ,Red hat Linux 7.2 > > A session bean invokes a java class and then another class > which triggers off threads to do some db updations etc. > However we find we can get the results just one time > but the second time it hangs giving the trace below > (Saroj's mail). > However it runs fine on Win2k with same JB config. > Even if we change those db updations to just SOPs, > it still hangs the second time around. -- Peter Beck BEng (hons) - Managing Director, Electrostrata Ltd. http://www.electrostrata.com --+-+-- Experts in e-business and e-commerce ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
