* The parameter sended via Post is a XML that represents an entity
The JBoss server is listen the port 8009 but mi App2 have a service that is listen the port 8900, this service is configured with Mule-ESB.
I try this configurations:
1.- Worker port: 8900
In this case App2 receive an unexpected message (see result.png)
2.- Worker port: 8009
The message is sended to App2 by balancer (I know that because the message in "access.log" is: "127.0.0.1 - - [23/Aug/2011:15:00:47 -0500] "POST /orderReceiver HTTP/1.1" 404 988") but this is not attended by App2
3.- Worker port: 8009 and App2 listen the same port 8009
The same result as scenario #1
In case #1, when I set "JkLogLevel debug" in mod-jk.conf I see that the XML is sendend but preceded by some meta-information, I suspect that this information is nos recognized by my service and for this reason I obtain the result shown in result.png
I've made a trivial app that recive and print a GET request and print it in console, this app works fine. I deploy this app in a default Tomcat (with default ports).. I can't test this app with POST request.
So, my questions are:
1.- mod_jk allow the POST request? It's necessary to do any change in my configuration to receive POST request?
2.- Exist any difference between the original POST and the POST received by Mule-ESB?
3.- It's necessary to do any other configuration in my JBoss instance?
I've atached my configuration files.
Any help is welcome,
Alexis Gamarra Cano
posted 8 years ago
These are the settings I used:
Configuration in Apache:
In file <APACHE_HOME>/conf/httpd.conf I add this row:
# Include mod_jk configuration file
# Mount your applications
JkMount /application/* loadbalancer
# You can use external file for mount points.
# It will be checked for updates each 60 seconds.
# The format of the file is: /url=worker
# Add shared memory.
# This directive is present with 1.2.10 and
# later versions of mod_jk, and is needed for
# for load balancing to work properly
# Add jkstatus for managing runtime data
Deny from all
Allow from 127.0.0.1
# Definimos el nodo Nodo1
# Puerto del conector ajp de nuestro tomcat (JBoss)
# Ip del nodo 1.
# Peso de nuestro nodo. A más peso, mas peticiones recibe.
# Definimos el nodo Nodo2
# Status worker for managing load balancer
# Simple worker configuration file
# Mount the Servlet context to the ajp13 worker