Hi Maarten, Thank you for the information. I thought the servlet spec stated that the ability to spawn threads in a J2EE container could not be relied upon. I'm not sure how WebSphere would behave in this situation. Our communication spec guarantees a synchronous request/response protocol, so we may just go with java sockets on this one to avoid any threading issues. We used Mina for a server implementation of a similar, but asynchronous, protocol, and did this outside of the web container, and it works perfectly. We were hoping to use it again for the client side, though no big deal if not possible.
Thanks for your help, Matt On 5/21/07, Maarten Bosteels <[EMAIL PROTECTED]> wrote:
Hi Matt, I am not sure I understand/problem your question eniterly. We are running a MINA server within tomcat. The application is a regular web app (with spring controllers etc for admin functions) that happens to also start a MINA SocketAccepor (on another port obviously) Our application is not single-threaded though, the servlet spec does not forbid you to start new threads. IIRC, entreprise beans (Entity beans and session beans) are not allowed to start new threads. Maarten On 5/21/07, Matt Mehalso <[EMAIL PROTECTED]> wrote: > > Has anyone had any success using Mina within a WebContainer, such as > WebSphere? Is there any way to configure Mina to run in a single thread, > or > to integrate the framework with a WorkManager (container-managed thread > pool)? > > The reason that I ask is that we have a requirement to answer some web > requests with information from a remote system. We must conform to > existing > specifications regarding the connection with this system, and thus are > confined to tcp/ip socket request/response messaging. > > Thanks, > > Matt >
