Details
-
Fix
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
- YADE makes use of the CIFS interface library jcifs-ng version 2.0.6.
- When used with high performance storage systems an error occurs:
[stdout] 24 16:00:59.746 [WARN ] (SmbTransportImpl.java:1107) - Failure decoding message, disconnecting transport [stdout] java.io.IOException: WHAT? ( read 124 decoded 128 ): command=SMB2_CLOSE,status=0,flags=0x000D,mid=6,wordCount=0,byteCount=0 [stdout] at jcifs.smb.SmbTransportImpl.doRecvSMB2(SmbTransportImpl.java:1187) [stdout] at jcifs.smb.SmbTransportImpl.doRecv(SmbTransportImpl.java:1100) [stdout] at jcifs.util.transport.Transport.loop(Transport.java:459) [stdout] at jcifs.util.transport.Transport.run(Transport.java:762) [stdout] at java.lang.Thread.run(Thread.java:744) [stdout] 24 16:00:59.747 [WARN ] (SmbTransportImpl.java:719) - Disconnecting transport while still in use Transport6[filer-p/10.4.16.170:445,state=5,signingEnforced=false,usage=3]: [SmbSession[credentials=in-kon.ch\filexfer-k_svc-p,targetHost=filer-p,targetDomain=null,uid=0,connectionState=2,usage=2]]
- This is a packet level problem with the TCPS packet SMB2_CLOSE. This level is out of control of YADE, therefore the resolution has to be found with an updated jcfis-ng library.
- Existing Issues in jcifs-ng
Desired Behavior
- YADE makes use of an updated version 2.0.8 of the jcifs-ng library
Workaround
- Find attached the updated library jcifs-ng-2.0.8.jar.zip
- Store the library in the ./lib/patches directory of JobScheduler Master or Agent that run the YADE job.
Test instructions
- Configure YADE using a SMB fragment
- Check execution result
- Check the ./lib/3d-party directory (JobScheduler Master and Agent) to find a jcifs-ng-2.0.8.jar file
Attachments
Issue Links
- relates to
-
YADE-563 Upgrade jcifs-ng from 2.0.6 to 2.1.5
- Released