I'm using Axis 1.0's AdminClientTask to deploy a Web service on Tomcat
4.1.3. My operating system is Suse Linux Enterprise Server 9.0 (SLES 9.0).
I got the "Remote administrator access is not allowed" error. I was able to
get rid of the error by opening up axis.jar and modifying
server-config.wsdd to have the enableRemoteAdmin parameter on AdminService
to be true. That said, I still don't understand why this is perceived as
remote administration since I'm deploying locally (Tomcat is running on
localhost). I put some print statements in org.apache.axis.utils.Admin's
process(..) method to see what was happening and discovered that the
remoteIP in the MessageContext is 0:0:0:0:0:0:0:1 instead of what I
expected (127.0.0.1). When I run on Windows 2000 and Red Hat Enterprise
Linux 3.0, the remoteIP in the MessageContext is 127.0.0.1 which looks
right.

Any ideas on what the reason could be for this strange remoteIP address in
SLES 9.0?
More generally, why might local deploys perceived as remote on SLES 9.0?

Thanks,
Rupam

Reply via email to