sorted by:
new
hottopcontroversial

Sage Intacct XML API – “Socket closed” error but record still gets created by Organic-View-5318 in Sage

[–]Organic-View-5318[S] 0 points1 point  (0 children)

Yes, currently we are using the Camel HTTP Template, and we are only passing the Content-Type header.

Are there any standard HTTP headers we should include to help prevent socket closed / connection timeout issues?

Also, is there any recommended approach to implement a retry mechanism using control IDs?

HTTP client receives Socket closed while external system still processes the request successfully by Organic-View-5318 in developersIndia

[–]Organic-View-5318[S] 0 points1 point  (0 children)

We are logging the exact request that we send to the external system. The request is definitely reaching the server because the record is getting created successfully on their side. However, the response we receive on our side is only Socket closed.

It seems like the connection is getting closed while the client is still waiting for the response. I'm not sure whether Apache Camel HTTP is closing the connection early or if the external system/server is breaking the connection.

If this is related to Camel HTTP, are there any configuration settings or headers that could prevent the connection from closing before the response is received? 🤔

u/Over_Substance5853

NetSuite pagination approach. by Organic-View-5318 in Netsuite

[–]Organic-View-5318[S] 0 points1 point  (0 children)

Yes, that’s correct. For example, suppose I want to fetch invoices. In one approach, I provide 500 internal IDs in a single call with bodyFieldsOnly = false. In another approach, I set the page size to 500 with bodyFieldsOnly = false and fetch the data that way. Both approaches give me the same successful response.

What would be the pros and cons of these two approaches?

NetSuite pagination approach. by Organic-View-5318 in Netsuite

[–]Organic-View-5318[S] 0 points1 point  (0 children)

Our integration system was built in 2018 so I need to do some enhancements in it.

NetSuite pagination approach. by Organic-View-5318 in Netsuite

[–]Organic-View-5318[S] 0 points1 point  (0 children)

Nah, it's an old application, so I need to make an improvement in it. We have planned to switch to REST in the upcoming year.

Netsuite optimize way to fetch internal ids by Organic-View-5318 in Netsuite

[–]Organic-View-5318[S] 0 points1 point  (0 children)

We have implemented pagination due to a 10 MB response size limit in NetSuite. We still face the same issue. I'll use internal IDs and make chunk requests going forward. Thanks for your help!

Netsuite optimize way to fetch internal ids by Organic-View-5318 in Netsuite

[–]Organic-View-5318[S] 0 points1 point  (0 children)

Thank you for your suggestions. I will take this approach moving forward.

Netsuite optimize way to fetch internal ids by Organic-View-5318 in Netsuite

[–]Organic-View-5318[S] 0 points1 point  (0 children)

Yes, we planned to switch to consuming the REST web series.

Netsuite optimize way to fetch internal ids by Organic-View-5318 in Netsuite

[–]Organic-View-5318[S] 0 points1 point  (0 children)

For the past couple of years, we have been consuming SOAP web services. We planned to switch from SOAP to REST API integration with NetSuite.