Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Policy problem?

 
Andreas Bystrom
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When I try to use RMI from a servlet I get this exception:
java.net.SocketException: Software caused connection abort: socket write error

I think that it can have somethign to do with policys. I have 2 jar files that my application uses that in turn uses two jar files that does stuff over RMI. These jar-files are located in {catalina.home}/common/lib/. This jar files also has a properties file that it uses. This file is located in myapp/WEB-INF/classes/file.conf

Do I need to set any policys for this application? I use tomcat 5.0.25 on an XP machine.

I use a network sniffer "ethereal" to look at what is really sent. What I can see is a exception that looks something like this:
"access denied to classloader ... java.security.AccessControlException ... access denied java.io.FilePermission /C:/java/jakarta-tomcat-5.0.25/webapps/myapp//WEB-INF/classes/- read". This exception is sent from the RMI server to the application computer.

Anyone have an ide of what I have missed?

// Andreas
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13055
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sure looks to me like you have to set a policy for that application.
Be aware that at least one version of Tomcat 5 had a really strange bug related to application of a policy to an application using RMI - I finally dropped back to Tomcat 4.
Bill
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic