Thanx Charles!  Yes, I meant sevlet-api.jar, sorry.  The webapp is
written in Adobe Flex calling custom java apis.  Looking at the web.xml
file used, could it have something to do with this listener as you said
earlier?

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";>
<web-app>

    <display-name>BlazeDS</display-name>
    <description>BlazeDS Application</description>

    <!-- Http Flex Session attribute and binding listener support -->
    <listener>
        <listener-class>flex.messaging.HttpFlexSession</listener-class>
    </listener>

    <!-- MessageBroker Servlet -->
    <servlet>
        <servlet-name>MessageBrokerServlet</servlet-name>
        <display-name>MessageBrokerServlet</display-name>
 
<servlet-class>flex.messaging.MessageBrokerServlet</servlet-class>
        <init-param>
            <param-name>services.configuration.file</param-name>
            <param-value>/WEB-INF/flex/services-config.xml</param-value>
       </init-param>
        <load-on-startup>1</load-on-startup>
    </servlet>

    <servlet-mapping>
        <servlet-name>MessageBrokerServlet</servlet-name>
        <url-pattern>/messagebroker/*</url-pattern>
    </servlet-mapping>

    <welcome-file-list>
        <welcome-file>index.html</welcome-file>
        <welcome-file>index.htm</welcome-file>
    </welcome-file-list>

    <!-- for WebSphere deployment, please uncomment -->
    <!--
    <resource-ref>
        <description>Flex Messaging WorkManager</description>
        <res-ref-name>wm/MessagingWorkManager</res-ref-name>
        <res-type>com.ibm.websphere.asynchbeans.WorkManager</res-type>
        <res-auth>Container</res-auth>
        <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    -->
    
    <error-page>
       <error-code>404</error-code>
       <location>/main.html</location>
    </error-page> 

</web-app>


-----Original Message-----
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] 
Sent: Saturday, November 27, 2010 10:08 AM
To: Tomcat Users List
Subject: RE: Please help ... [MultiThreadedHttpConnectionManager
cleanup]

> From: Emerson, Christopher [mailto:cemer...@orangelake.com] 
> Subject: RE: Please help ... [MultiThreadedHttpConnectionManager
cleanup]

> If I have 100+ concurrent users, won't that effect the other users?

Each webapp should have its own copy of the HTTP client, so no.

> Is it possible that I have something as simple as an incorrect 
> web.xml configuration?

Can't tell without seeing it, can we?  As suggested earlier, you may
well have an incorrect configuration for the libraries you're using, and
their configuration may not be in WEB-INF/web.xml.

> Another thing I noticed is that the servlet api is in Tomcat's lib
> directory.  Should that be in the individual webapp directories?

Absolutely not.  It's correctly placed where it is.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




DISCLAIMER:
Orange Lake Resorts does not accept legal responsibility for the contents of 
this message. Orange Lake Resorts reserves the right to monitor the 
transmission of this message and to take corrective action against any misuse 
or abuse of its e-mail system or other components of its network. The 
information contained in this e-mail is confidential and may be legally 
privileged.  It is intended solely for the addressee. If you are not the 
intended recipient, any disclosure, copying, distribution, or any action or act 
of forbearance taken in reliance on it, is prohibited and may be unlawful. Any 
views expressed in this e-mail are those of the individual sender, except where 
the sender has been duly authorized to specifically state the content of the 
e-mail on behalf of Orange Lake Resorts.  The recipient should check this 
e-mail and any attachments for the presence of viruses. Orange Lake Resorts 
accepts no liability for any damage caused by any viruses transmitted by this 
e-mail.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to