Hello everyone, I'm new to the digest and after going through the messages, I still have'nt figured out the answer to my application design. Basically, how does anybody connect to another machine from code within Weblogic app and process raw socket messages from it ? Our Management (Weblogic 4.5.1) application needs to connect to different machines on demand and maintain a constant message interaction on their TCP sockets (each machine spits out messages on 2 TCP sockets). Currently, we fork user threads that maintain this interaction for each managed machine - one for each socket, and maintained in a "machine-thread-pool". But from what I understood of EJB and the various messages on this group, forking off user threads within EJB container is disallowed - is my understanding correct ? Even though these threads do not reference any EJB, they just reside inside the Weblogic JVM. The forked off threads maintain a conversation as follows - the client thread i.e. from the servlet/EJB invoked thread of control sending the message and a permanant listener thread reading the response, and thread synchronization between to correlate the request & response, timeout handling etc. The response from WL customer support was to have a stateless session bean maintain the conversation instead of the forked off user threads. However, these session beans need to live on forever (cannot create a socket on each conversation request). And my concern was with the SB timeout/passivation issues - are'nt all SessionBeans passivated at a certain stage ? Also a concern is the thread synchronization issues between sending/receiving SB (if we use the same model). Weblogic customer support could not answer this satisfactoriy, and suggested we look into Weblogic consulting services - anyone have any good experiences from them ? Thanks in Advance Any and all responses greatly appreciated ! Arun =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
