Discussions
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Don’t miss your chance to meet our SuiteGurus—NetSuite Support professionals and subject matter experts with extensive experience in select product areas, including OneWorld, Advanced & Basic Accounting, Supply Chain Management, Receivables & Payables, CRM, Account Administration, and the SuiteCloud Platform. Full Conference attendees can prebook exclusive 30-minute one-on-one sessions for your product questions.
Spots are limited! Register through your Agenda Builder and find SuiteGuru under Agenda Enhancements.
Connection timeout with Ruby script
When running a Ruby script using classes generated through wsdl2ruby (part of SOAP4r), the login is successful, but a subsequent search generates a SOAP fault complaining that the connection has timed out. The query is submitted immediately following the successful login. If the same steps are executed manually from within the Ruby interactive interpreter (irb), the login and the search are both successful.
Removing all of the flow control and error checking, the script boils down to this:
service = NetSuiteService.new
service.login(uid, pwd)
service.getFutureEvents
service.logout
NetSuiteService is a slim wrapper around NetSuitePortType generated by wsdl2ruby. Even if I replace it with direct calls to NetSuitePortType (as per the code below) from the script, the result is the same.