Hi All, I am a newbe to Tomcat & Axis but learned a lot over the past couple of evenings. I did solve the problem! I learned the following:
1. Do not trust the error messages coming back to the Axis Client. They are filtered such that the root cause may not be displayed. 2. Launch Tomcat in a separate console window instead of as a service under Win/NT so you can see the entire trace of exceptions. This is what helped me A LOT. 3. If using rmi from inside a Axis service be very careful since the demarshaling of objects at the client will fail with malformed URL because of the space in the folder name "Tomcat 4.1". 4. RMI failures inside a Axis service will cause Tomcat to crash and you will not know it because you get the same socket disconnect error regardless of the true problem. 5. Always make sure the RMI classes for both client and server are the same package structure otherwise the registry will not send the classes to the client or server. In Tomcat the Axis service will throw the exception in the cmd window. Hopefully I will not lose more time now that I have a working methodology for troubleshooting these interesting problems. Hope this message helps others. -Tony Hi All, Has anyone tried using rmi calls inside of a Axis service on Tomcat? Using Tomcat 4.1.12 on Windows NT. I get errors about access permissions at 127.0.0.1:1099 showing up in the stdout log file in the common/logs directory. I have set permissions on my dev machine for tomcat in catalina.policy to allow for all permissions. Am I the first to try rmi calls (client-side) inside a Axis service?? Many Thanks
