Web service requests cannot be blocked even after mod_cluster stopped the application context
Issue
- We are running mod_cluster on an Apache web server fronting two JBoss EAP 6 application servers
server_aandserver_b. Both application servers have the same deployment of application"/myapp". - When we disabled the application context
"/myapp"onserver_b, we still saw the web request from mod_cluster toserver_b. We even tested undeployed the EAR file fromserver_b, but the web server still occasionally forward the web request"/myapp"to the undeployedserver_band got an error message back to user. -
This issue seems to only occur when we invoke a web service call to the mod_cluster URL from the other application server
server_a. Below is the code extract for the section on how we create the webservice proxy and invoke it from a controller in AS:String serviceURL = "http://loadbalancer:8080/myapp/ExampleService"; QName serviceName = new QName("http://myapp.example.com/", "ExampleService"); URL wsdlURL = new URL(serviceURL + "?wsdl"); Service service = Service.create(wsdlURL, serviceName); ... ExampleService proxy = (ExampleService) service.getPort(ExampleService.class); proxy.doSomething(request); -
When the
"/myapp"context is stopped onserver_b, the above web service invocation fromserver_ashould never reachserver_b. -
I noticed in the server log:
19:28:56,820 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://server_b:8080/myapp/ExampleService -
So
http://server_b:8080/myapp/ExampleServicewould point straight to JBoss EAP, not httpd.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.x
- mod_cluster
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
