What happens if requests exceeds specified maxThreads on JBoss Web HTTP Connector

Solution Verified - Updated -

Issue

  • What happens if 200 requests go to the JBoss Web HTTP Connector on port 8080 at the same time? The maxThreads is 100 and the acceptCount is 30.
  • The acceptCount does not seem to be used within JBoss Enterprise Application Platform (EAP). The actual value when the requests are rejected are much higher than the set value.

  • When the requests are rejected, there is no error returned. The client will actually timeout. I would expect some error returned when the server starts rejecting messages.

  • JBoss 5 EAP doesn't use acceptCount (in server.xml) as expected. When the threads get all busy, the queue seems not to exist. All subsequent requests are rejected. This is not the expected behaviour. This problem only occurs in JBoss EAP 5.1, not in JBOSS 5.1 AS - based on my tests.
  • What caused the following message:

    INFO  [JIoEndpoint] Maximum number of threads (###) created for connector with address /127.0.0.1 and port 8080
    

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 4
    • 5
  • Linux
  • Solaris

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In