Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 68616 invoked by uid 500); 17 Dec 2002 23:10:47 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 68572 invoked from network); 17 Dec 2002 23:10:46 -0000 Message-ID: <000501c2a621$a45969d0$1219570f@ranier> From: "Steve Loughran" To: "axis-dev" Subject: AdminService Wierdness Date: Tue, 17 Dec 2002 15:11:30 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-MailScanner: Found to be clean X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Anyone seen this 'new' behaviour? I'm trying to deploy to the code I've just uploaded, using a build file that used to work perfectly, and now I'm seeing a 301 redirect coming back when the admin client talks to it. Do a GET to it, and I get back the 'hi there' answer; change the localhost to be the machine name and I get the 'no remote admin' error message instead. [axis-admin] AxisFault [axis-admin] faultCode: {http://xml.apache.org/axis/}HTTP [axis-admin] faultSubcode: [axis-admin] faultString: (301)Moved Permanently [axis-admin] faultActor: null [axis-admin] faultNode: null [axis-admin] faultDetail: [axis-admin] null: return code: 301 [axis-admin] <HTML> [axis-admin] <HEAD><TITLE>Redirection</TITLE></HEAD> [axis-admin] <BODY><H1>Redirect</H1></BODY> [axis-admin] [axis-admin] Running axis-admin with parameters: [axis-admin] action: [axis-admin] url:http://127.0.0.1:8080/stelvio/services/AdminService [axis-admin] hostname:null [axis-admin] port:0 [axis-admin] servletPath:null [axis-admin] fileProtocol:null [axis-admin] username:null [axis-admin] password:null [axis-admin] transportChain:null [axis-admin] debug:true FYI I'm now running tomcat4.17, but this was happening on tomcat4.12 this morning; I upgraded tomcat to see if it would make a difference. And of course, when I try a fully qualified hostname, 'ranier', the admin service rejects me as an external caller. which is not the case.