Monitor socket with thread in WebLogic

Question

I've recently joined a company where a solution was put in place within web apps to monitor a socket. The socket communication comes from a C-based app sending in messages to a socket monitored by a thread.
This was done in a web app that used WebLogic Express, with only JSP's and servlets. My question is...how appropriate is this architecture in a WebLogic server that will now call EJB's from this thread? How can I spawn this thread outside of a servlet, maybe a startup class? My services layer may receive RMI-based client calls, thus the servlet would not come into play.
My thoughts are that this should become a JMS-based communication, but for the initial versions, we may not have time rehaul the messaging infrastructure.
I'd appreciate any opinions on this....
Chuck

Answer 1

<p>cheinle,</p>
<p>It's not clear from your post what it is you need to achieve. What protocol is your service layer using? Is your service layer <b>only</b> going to deal with synchronous RMI requests?</p>
<p>Answering your first question the implementation you describe using WebLogic Express is also applicable to WebLogic.</p>
<p>With respect to Servlets and EJBs a typical architecture would have HTTPServlets listen on a ServerSocect and dispatch requests to a service layer implemented in EJBs (in their own threads). You could implement your own Servlets to deal to with protocols other than HTTP.</p>
<p>You can also provide an HTTP wrapper for your RMI service layer using servlets see here for an introduction to using HTTPServlets with RMI</p>
<p>cheers</br>
Hussein Badakhchani</br>
www.orbism.com
</p>