Hi all... We have our application deployed in weblogic 8.1 cluster environment with 2 managed servers and 1 admin. We have configured ExecuteQueue in both the managed as well as admin server, which will be constantly listening for JMS Topics. Application uses applet to communicate with the server making an URL connection. We have configured Execute Queue to listen to JMS Messages which inturn writes it to another Thread.
When a connection is made by the applet wht happenes is that it opens a socket connection with the admin server, then admin server forwards the request to the managed server(Here again another socket is opened) and the response comes back in same manner. When ever a message listening applet is loaded then execute queue becomes active rather than being idle. our application works fine till this. The problem we are facing is when applet exits or it connection gets closed, the admin server still retains the socket connection,because of this Execute Queue still listens to the request where as the client has closed the connection. Because of this scenario weblogic server gets stuck or hangs.... How can i overcome this problem??? just b4 exiting is there a way to close the connection... waiting for the response.. thanks r sasi =========================================================================== 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".
