Page 1 of 1
java.lang.NullPointerException when bulk uploading documents
PostPosted:Thu Feb 28, 2019 6:12 pm
by kefren69
Hello Forum,
I am on tomcat 8.5.24
OKM 6.3.6
I want to upload a document bulk via the administrative utility.
The utility seems to fail immediately and I think found why.
When navigating in the folders if I try to enter a folder with a special character french (which by chance is the first folder in list) the exception in subject is raised.
No error is raised if I navigate into any other folder which does not contain any special character.
On the other side if I tried to used the single document loading I can enter in the directory with special characters and correctly load the document.
Anything I forgot to configure?
thanks in advance
Giancarlo
Re: java.lang.NullPointerException when bulk uploading documents
PostPosted:Fri Mar 01, 2019 2:09 pm
by kefren69
Actually an error is raised in the consolle…
Code: Select all2019-03-01 08:59:01,932 [http-nio-0.0.0.0-8080-exec-2] ERROR c.o.e.servlet.DataBrowserServlet - null
java.lang.NullPointerException: null
I removed the OPENKM directory in the webapps to rebuild the packge but no luck.
I browsed the forum a little more in depth and the issue was reported in the past but no solutions have been provided
Regards
Giancarlo
Re: java.lang.NullPointerException when bulk uploading documents
PostPosted:Fri Mar 01, 2019 7:28 pm
by jllort
Rebuild OpenKM.war has not sense.
We need more detailed description of the error:
1- catalina.log file ( when the error happened, does not share 2 days of catalina.log file )
2- some screenshot for better understanding of the error
Re: java.lang.NullPointerException when bulk uploading documents
PostPosted:Mon Mar 04, 2019 5:18 pm
by kefren69
Thanks for the follow up.
Here the sequence...:
I navigate to the "administration" tab and click on the "import" tab - so far so good
Files are all local on C:/IKM
I click on File system path abd navigate where I need :
https://drive.google.com/open?id=1CT6ee ... D4WOv5fG8K
I click on directory (note the special french characters) path and I get the error :
https://drive.google.com/open?id=1-6dLJ ... jKJloo0Rag
Finally the Log on the Java consolle (I guess it is catalina response)
https://drive.google.com/open?id=1C7lvM ... C0rf30GRn5
Let me know if you have everything...
note : if I access the folder from the normal document load it works welll. Clearly I cannot load the documents one by one.
Thanks in advance
GIancarlo
Re: java.lang.NullPointerException when bulk uploading documents
PostPosted:Mon Mar 04, 2019 5:27 pm
by kefren69
I did a test and created 2 directories :
~test
¡test
The first special character belongs to the first UTF8 section and I can navigate into it (~test) .
The second (¡test) has a special character which belongs to the extended UTF8 character sets.
Both are ok when I navigate in the W10 files explorer
When I navigate with the databrowser of OPKM I can navigate in the first directory but not in the second raising the same error
https://drive.google.com/open?id=1-6dLJ ... jKJloo0Rag
It may help....
Giancarlo
Re: java.lang.NullPointerException when bulk uploading documents
PostPosted:Mon Mar 04, 2019 7:32 pm
by jllort
The error happens in the administration but from desktop view, it works right. Please confirm me this point.
Re: java.lang.NullPointerException when bulk uploading documents
PostPosted:Mon Mar 04, 2019 7:38 pm
by kefren69
confirmed!
Re: java.lang.NullPointerException when bulk uploading documents
PostPosted:Wed Mar 06, 2019 10:09 pm
by jllort
Please add a ticket at
https://github.com/openkm/document-mana ... tem/issues and in the description add the URL of this post.
Re: java.lang.NullPointerException when bulk uploading documents
PostPosted:Thu Mar 07, 2019 6:24 pm
by kefren69
Done...
so now I need to follow up on the other system?
Where you able to recreate the issue on your system?
thanks for the support.
Giancarlo
Re: java.lang.NullPointerException when bulk uploading documents
PostPosted:Sun Mar 10, 2019 6:51 pm
by jllort
As soon as possible we will attend the issue, but now we are involved in some releases and until be finished with it we will not be able to work on it.