Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
"Your connection has timed out"
What changed in version 11 or WSDL 1.3.2 that would cause a login to think it's timed out? I have worked with Web Services in version 10 and now ran my code in version 11 (using WSDL version 1.3.2). I am able to log in but the first time that I try to run a search I get an InvalidSessionFault: "Your connection has timed out". This SAME CODE worked in version 10 and WSDL 1.3.1. I am setting the header cookie before login as follows:
NetSuitePortType port = service.getNetSuitePort();
NetSuiteBindingStub stub = (NetSuiteBindingStub)port;
stub._setProperty(HTTPConstants.HEADER_COOKIE, new String[] {"ACCOUNT=" + myAccount});
0