You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Cihad Guzel (JIRA)" <ji...@apache.org> on 2019/02/25 22:10:00 UTC

[jira] [Updated] (CONNECTORS-1588) Custom Jcifs Properties

     [ https://issues.apache.org/jira/browse/CONNECTORS-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cihad Guzel updated CONNECTORS-1588:
------------------------------------
    Description: 
In some cases, "jcifs" is running slowly. In order to solve this problem, we need to set custom some properties. 
  
 For example; my problem was in my test environment: I have a windows server and an ubuntu server in same network in AWS EC2 Service. The windows server has Active Directory service, DNS Server and shared folder while the ubuntu server has some instance such as manifoldcf, an db instance and solr. 
  
 If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means^~[1]~^; firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it checks the DNS server. In my opinion, the linux server doesn't recognize the DNS server and threads are waiting for every file for access to read.
  
 I suppose, WINS is used when accessing hosts on different subnets. So, I have set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
  
 Another suggestion for similar problem from [another example|https://stackoverflow.com/a/18837754] : "-Djcifs.resolveOrder = DNS"
  
 We need to set custom resolveOrder variable.

^[1]^ [https://www.jcifs.org/src/docs/resolver.html] 

  was:
In some cases, "jcifs" is running slowly. In order to solve this problem, we need to set custom some properties. 
 
For example; my problem was in my test environment: I have a windows server and an ubuntu server in same network in AWS EC2 Service. The windows server has Active Directory service, DNS Server and shared folder while the ubuntu server has some instance such as manifoldcf, an db instance and solr. 
 
If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means[1]; firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it checks the DNS server. In my opinion, the linux server doesn't recognize the DNS server and threads are waiting for every file for access to read.
 
I suppose, WINS is used when accessing hosts on different subnets. So, I have set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
 
Another suggestion for similar problem from [another example|[https://stackoverflow.com/a/18837754]]: "-Djcifs.resolveOrder = DNS"
 
We need to set custom resolveOrder variable.


[1] [https://www.jcifs.org/src/docs/resolver.html] 


> Custom Jcifs Properties
> -----------------------
>
>                 Key: CONNECTORS-1588
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1588
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: JCIFS connector
>    Affects Versions: ManifoldCF 2.12
>            Reporter: Cihad Guzel
>            Priority: Major
>             Fix For: ManifoldCF 2.13
>
>
> In some cases, "jcifs" is running slowly. In order to solve this problem, we need to set custom some properties. 
>   
>  For example; my problem was in my test environment: I have a windows server and an ubuntu server in same network in AWS EC2 Service. The windows server has Active Directory service, DNS Server and shared folder while the ubuntu server has some instance such as manifoldcf, an db instance and solr. 
>   
>  If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means^~[1]~^; firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it checks the DNS server. In my opinion, the linux server doesn't recognize the DNS server and threads are waiting for every file for access to read.
>   
>  I suppose, WINS is used when accessing hosts on different subnets. So, I have set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
>   
>  Another suggestion for similar problem from [another example|https://stackoverflow.com/a/18837754] : "-Djcifs.resolveOrder = DNS"
>   
>  We need to set custom resolveOrder variable.
> ^[1]^ [https://www.jcifs.org/src/docs/resolver.html] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)