Thanks, but why is Muse creating a session for every publish(_TOPIC_NAME, element); call or who is creating the session? I'm completely confused by this. I only deploy a publisher and a consumer so why would many sessions be created on the Consumer end to receive the publishes?
-----Original Message----- From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 11, 2007 10:36 AM To: [email protected] Subject: Re: Too many sessions If you're running Muse as a J2EE app, the answer lies in the configuration of your HTTP/J2EE container. If that's Tomcat, I think the maxActiveSessions parameter can be used to limit the number of sessions created: http://ontoweb.med.yale.edu/tomcat-docs/monitoring.html I'm not entirely sure about this - shutting off sessions is well-documented for JSPs, but for servlets (SOAP engines) it was a little harder to find. Dan "Callner, David A." <[EMAIL PROTECTED]> wrote on 04/11/2007 09:54:57 AM: > I'm using the WSN-Notification and every time do a publish a session is > created in the Consumer. I'm sending thousands of messages. How can I > create just one Consumer session to handle all the publishes? > > Thanks, > > David Callner > Senior Software Systems Engineer > The MITRE Corporation > Center for Advanced Aviation System Development > 7515 Colshire Dr. > McLean, VA. 22102 > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > 703.983.6431 (work) > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
