Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NX: RMI and java.net.ConnectException

 
Morgan Bath
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Testing my threading/locking solution and I get great rersults now for 100 threads over 100 iterations each (10,000 updates). But when I go to the remote version I get a "java.net.ConnectException: connection refused" thrown every now and again. The more threads I run the more exceptions I get. Plus the longer ive been running the server the more I get.
From a fresh reboot I can get 80 or 90 threads running 100updates, after 10 or 15 mins I get less than 40 able to run without exceptions.
As long as I dont get this exception I get perfect results. If I run 50 threads at 100 updates each I get the perfect 5,000 updates all on the same record.
This feels like a problem with the system, not my solution. Or could there be an issue with my network solution. Am I overloading the remote server or should I panic and strip my code down?
 
Morgan Bath
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Oh, server and client threads running on the same machine in different VMs.
 
Ken Krebs
Ranch Hand
Posts: 451
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Take a look at this thread: Topic: More than 17 clients CRASH?!
 
Morgan Bath
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks, nice to see that its not just me. In fact it seems im actually managing quite a load for winxp. IG relief.
morgan
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic