Problem

-- getting this error on several messages when processing a high load on Windows 2012 R2

* Integrator trace :

ERROR :20170619:12.35.15.57:B2Bi PE TA B2BXGI IB Task(procengine(transadaptenv)):error received from filer server:file rename error
WARNING:20170619:12.35.15.57:B2Bi PE TA B2BXGI IB Task(procengine(ta_b2bxgi)):HandleClientEvents: 'Unexpected exception FILER during event handling: error received from filer server:file rename error'

* Interchange te logs

2017-06-19 12:35:15,610 - ERROR [Worker37-134] (B2BiMessageTask.execute:168) - Error sending message to integrator.
com.cyclonecommerce.tradingengine.transport.UnableToProduceException: B2Bi client: Unable to produce: com.axway.b2bi.transport.TransportException: unexpected end of input stream when reading header. socket=59947
at com.cyclonecommerce.tradingengine.transport.b2bi.B2BiClientImpl.send(B2BiClientImpl.java:149)
at com.cyclonecommerce.tradingengine.transport.b2bi.B2BiClientImpl.send(B2BiClientImpl.java:103)
at com.cyclonecommerce.tradingengine.transport.b2bi.transfers.B2BiMessageTask.sendAsynchronousToB2BiConnector(B2BiMessageTask.java:280)
at com.cyclonecommerce.tradingengine.transport.b2bi.transfers.B2BiMessageTask.execute(B2BiMessageTask.java:144)
at com.cyclonecommerce.util.task.TaskScheduler$WorkerThread.primRun(TaskScheduler.java:394)
at com.axway.cluster.extensions.thread.EventedThread.run(EventedThread.java:80)
Caused by: com.axway.b2bi.transport.TransportException: unexpected end of input stream when reading header. socket=59947
at com.axway.b2bi.transport.B2BiClient.readOpReply(B2BiClient.java:425)
at com.axway.b2bi.transport.B2BiClient.readOpReply(B2BiClient.java:381)
at com.axway.b2bi.transport.B2BiClient.send(B2BiClient.java:138)
at com.cyclonecommerce.tradingengine.transport.b2bi.B2BiClientImpl.send(B2BiClientImpl.java:139)
... 5 more

Resolution

- the problem is caused by the file system

- make sure SMB3 only is used

- follow the recommendations from the installation guide

Windows SMB2 / SMB3 client configuration requirement for clustered environments
To avoid file locking errors on SMB2 (Windows 2008 R2) and SMB3 (Windows 2012 R1 and R2) platforms, set the following registry values:

On the client machine, set the SessTimeout parameter to the recommended value of 240 seconds.
Registry path: HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

On the server machine, set the SessionKeepAlive registry parameter to the recommended value of 30000 milliseconds (30 seconds).
Registry path: HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters
Note on Windows upgrades to Windows 2012 R1/R2 SMB3: When upgrading from an earlier Windows OS to Windows 2012 (which uplifts SMB2 to SMB3), double-check these registry settings (even if they were correctly set before the upgrade). The platform upgrade may have reset platform defaults, which can lead to B2Bi restart issues.