I think we'll need more information than that. If a J2EE webapp is using HTTP to send SMS to an external gateway webapp, there's no way Apache fronting the J2EE app should make any difference at all. Most likely you have some sort of firewall changes that were made when Apache was brought in, but it would help if you could provide us with the exact text of the error message.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Mar 07, 2011
WOW! I hadn't expected such a fast reply!
First of all, just to clarify, I'm not using HTTP to send SMS. All I'm sending is a standard HTTP post request to the BulkSms website, and they send an sms to my cell phone to trigger the mobile client application.
When I first ran the system with Apache running, I got a 401 (authorisation/authentication) error:
As the error specified the BulkSms url, I initially thought that this was where the error was occurring, but when I inquired about this, BulkSms replied that they had no record of a 401 error having occurred.
After further trials, I removed the password file from Apache and ran the system again. This time I got a different error:
The error message changed as a result of changing Apache, and this led me to think that I had a configuration problem. This is the first time I've configured a server, so I'd better show you what I did.
Tomcat's server.xml file already had this line:
In Apache's httpd.conf file, I made sure that the proxy modules were un-commented:
I then added the following lines to configure the proxy:
Finally, I configured the Windows firewall to allow tcp and udp exceptions for httpd.exe on ports 80 and 443, all scoped for any computer.
As I said before, most of this is new territory for me. I'm still struggling with some of the basic concepts, so any advice you can offer will be very much appreciated.