In mod_cluster the context length is limited to a max of 40

Solution Unverified - Updated -

Environment

  • JBoss Enterprise Application Platform (EAP) 5.1
  • mod_cluster 1.0.4

Issue

  • The mod_cluster documentation contains the following on the limitations chapter: "Max context length 40 (for example myapp.war deploys in /myapp /myapp is the context)."
  • When we call WS through the LoadBalancer (EWS JBoss 1.0.2 configured mod_cluster-manager), the system returns an http error 404 . But while calling JBoss directly, our calls are working perfectly.
    Here's what we can see in the logs of LoadBalancer:
10.20.30.40 - - [21/Mar/2012:16:30:50 +0100] "POST /one-two-three-4-ear-1.0.0-SNAPSHOT-one-two-three-4-implementation-1.0.0-SNAPSHOT/GettingMoreInformationOnAccountsWS HTTP/1.1" 404 410 "-" "Apache-HttpClient/4.1.1 (java 1.5)"

Resolution

  • The feature request JIRA browse/MODCLUSTER-236 has been opened to increase the max context length:   Note that there is no plan currently to include this feature request in mod_cluster 1.0.x at this time. It is available in EAP 6.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.