Contact Us 1-800-596-4880

NetSuite Connector 13.0 Troubleshooting

Connectivity Test Failure During Application Startup

If a connectivity test fails during application startup and you see the following statement in the stack trace, configure a reconnection strategy for the connector:

Caused by: java.lang.InterruptedException
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:998) ~[?:1.8.0_221]

To configure a reconnection strategy for the connector in Anypoint Studio (Studio), add these lines to the Configure XML tab in the connector properties window:

<reconnection failsDeployment="true">
	<reconnect count="2" frequency="5" />
</reconnection>

For example, the configuration XML for the connector might look like this after you add the reconnection strategy:

<netsuite:config name="NetSuite_Config" doc:name="NetSuite Config" doc:id="8a4f73c2-e5e1-4f5d-8978-980069828ff0" >
    <netsuite:token-based-authentication-connection consumerKey="${netsuite.consumerKey}" consumerSecret="${netsuite.consumerSecret}" tokenId="${netsuite.tokenId}" tokenSecret="${netsuite.tokenSecret}" account="${netsuite.account}">
		<reconnection failsDeployment="true">
			<reconnect count="2" frequency="5" />
		</reconnection>
	</netsuite:token-based-authentication-connection>

In Studio, you can also use the Advanced tab in the connector properties window to configure a reconnection strategy. To do so, complete the following fields:

Field Value

Reconnection strategy

Standard

Frequency (ms)

5

Reconnection Attempts

2

No Logging of Log Requests and Responses

To log requests and responses when using the connector, add this XML statement to the Log4j configuration file:

<AsyncLogger
  name="org.mule.module.netsuite.extension.internal.connection.HttpWithCookieMessageDispatcher"
  level="DEBUG"/>
<Root level="debug">
    <AppenderRef ref="Console" />
</Root>

Permissions Error When Fetching Metadata

To avoid receiving a permissions error when fetching metadata, enable the Control SuiteScript and Workflow Triggers in Web Services Request option in NetSuite for the role used in the connector configuration.

Inability to Search for Certain Types of Objects

There is a limitation in NetSuite’s SuiteTalk API, that prevents you from searching for certain types of objects, such as Sales Order objects. Because of this limitation, you can’t use the NetSuite Connector Search operation to locate these objects.

To perform a search for Sales Order objects and other unsupported objects, you can create a saved search and call it from the connector.

On Modified Object Triggers New Objects

The On Modified Object source also triggers new objects. NetSuite populates the lastModifiedDate field when an object is created. When the On Modified Objects source polls objects based on lastModifiedDate, the On Modified Object source retrieves all new objects too, because all new objects have the lastModifiedDate field populated.

Custom cxf.xml Settings Aren’t Applied

NetSuite Connector 13.0 uses mule-soap-engine 3.0.3. That library reads a classpath cxf.xml file only when it starts the Spring bus. It starts the Spring bus only when Spring is already visible to the application. Otherwise it starts the non-Spring CXF bus, which does not read cxf.xml.

The connector does not ship Spring, and its code does not call Spring or CXF. Token-Based Authentication and the connector HTTP client do not use cxf.xml.

If HTTP settings, timeouts, interceptors, or WS-Security from cxf.xml no longer apply, re-test the integration. Adding Spring to the application is not a documented way to make an application cxf.xml apply to this connector.