Databases
StackOverflow2013
Postsdbo
PODeploying axis2.war to container broke client calls to external axis2 webservices
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODeploying axis2.war to container broke client calls to external axis2 webservices
    primarykey
    data
    text
    <p>I have several existing web-apps deployed as standalone war files in the app container (resin). Some use axis2 jar files and axis2-generated Stub files to make calls to external SOAP based web services. They were all working fine prior to this.</p> <p>I recently deployed axis2.war to the same container in order to create web services (unrelated to the client code mentioned above). </p> <p>As soon as I restart the app container, client calls to the external webservices seem to be "intercepted" by my newly deployed axis2.war. Services appear temporarily in the "Available Services" page of the axis2 web-app, with what appears to be randomly generated name based on the original external webservice name. </p> <p>These services disappear shortly after, but the result is that my client code fails with a 500 error, as the local Axis2.war doesnt know how to handle those requests.</p> <p>I have been searching for 2 days and haven't found mention of anyone experiencing anything similar. I am not even sure how to explain what is going on, as my client code never references localhost to make those web service calls. I am assuming this has to do with some configuration in axis2.war?</p> <p>If anyone has any idea or insight into what might be happening, I would really appreciate any information.</p> <p>Thanks for your help</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBruno
    1. USBruno
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CODo you mean that axis2.war interferes with the calls in clients for external WebServices (not in the same container)?
      singulars
      1. PODeploying axis2.war to container broke client calls to external axis2 webservices
      1. USPaul Vargas
    2. COThat's correct. The client apps make calls to WebServices that are on remote containers not hosted by us, but somehow those calls are being intercepted by the axis2.war running on our container where the client apps are hosted.
      singulars
      1. PODeploying axis2.war to container broke client calls to external axis2 webservices
      1. USBruno
    3. CODoes anybody have any idea what is going on ?
      singulars
      1. PODeploying axis2.war to container broke client calls to external axis2 webservices
      1. USBruno
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload