Author: mamwl1 Message: Hi,
If it is a problem with a thread pool it isn't the one used by WMQ. The bottom of that stack trace would be the same for any thread doing WMQ activation spec work. The important point is that the MDB is taking more than 120 seconds to do its processing. This is either because something has gone wrong at the other end of the socket OR it could be that your app runs slow enough that the transaction timeout occurred during the read. Do you get a timeout for every request or just when under load? If it is under load you need to find out where your app is spending its time and go from there. Regards, Matt. To respond to this post, please click the following link: <http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674276> ____________________________________ Unsubscribe via the "binocular" icon on the web
