• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WAS 7.0 ND: addNode timeout

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm trying to federate a node on one machine to an ND instance on another machine, but it keeps timing out on trying to transfer a small (150 KB) .car file to the ND machine. The ND machine is listening on port 5000 for SOAP, and the messages indicate that the base machine is successfully connecting to port 5000 on the ND machine. The exception is simply "java.net.ConnectException: Connection timed out". I have increased the timeout on both machines in soap.client.props, but it doesn't seem to have any impact on how long the addNode process tries to transfer.

So, 3 questions...
1) Is the file being transferred over port 5000 or could another port be used? There is a firewall between machines, so it could be that something's being blocked, but the addNode docs don't mention any other ports, other than the one specified on the command line.

2) Why are my timeout changes not working? Is there another file to modify besides soap.client.props? I'm specifying SOAP as a parameter to addNode, so it shouldn't be using something else.

3) Any other ideas?

Thanks for any help,
Dan
 
Dan Werner
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Never mind. The problem was that the filetransfer app was trying to communicate with the ND box's admin port, which wasn't open in the firewall. Thanks for not including that in the documentation, IBM! What a fun adventure!
 
Well THAT's new! Comfort me, reliable tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic