Hi CoP,
Requesting for assistance with this issue. Upgraded to 2.39.0.1 and facing this issue with the maintenance app when trying to edit datasets in the maintenance app. I am able to open dataset menu, however when I click on a dataset in the dataset list, it brings a blank page and keeps loading, throws off this error message.
Regards,
Cynthia.
Hi @ckambobe
Thank you for the post! After clearing the appplication cache using the Data Administration app → Maintenance, please try to use Guest mode in your browser to be 100% sure it’s not a cache issue. If you are still facing this issue, could you try to access: [YourInstanceURL]/2.39.0.1/api/29/dataSets/dataSetID.json (you can find this URL from the dataset details before opening it.
Is this happening for all users? It could be a database issue because if you check the instance on DHIS 2 Demo - Sierra Leone the datasets load and open without any errors, so would it be possible to share the Catalina.out log (without sensitive info)?
Thank you!
I have used guest mode- and cleared the cache, still getting the same error. So it;s not a cache issue.
I have tried accessing [YourInstanceURL]/2.39.0.1/api/29/dataSets/dataSetID.json, I am able to get the dataset details in json format.
I have tried accessing the datasets with a different user, still getting the same error.
The catalina.out file does not have any output relating to the error.
Blockquote 13-Jan-2023 13:57:06.921 INFO [Catalina-utility-2] org.apache.catalina.core.StandardContext.reload Reloading Context with name [/manager] has started
13-Jan-2023 13:57:06.968 INFO [Catalina-utility-2] org.apache.catalina.core.StandardContext.reload Reloading Context with name [/manager] is completed
13-Jan-2023 13:57:06.968 INFO [Catalina-utility-2] org.apache.catalina.startup.HostConfig.reload Reloading context [/docs]
13-Jan-2023 13:57:06.968 INFO [Catalina-utility-2] org.apache.catalina.core.StandardContext.reload Reloading Context with name [/docs] has started
13-Jan-2023 13:57:07.014 INFO [Catalina-utility-2] org.apache.catalina.core.StandardContext.reload Reloading Context with name [/docs] is completed
13-Jan-2023 14:27:21.265 INFO [http-nio-80-exec-19] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name [0x050x010x00…]. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:419)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:271)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1789)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:834)
Thanks Cynthia! I asked the dev but we still need more info – any log or indication that could lead us to the cause!
If you are testing using the superuser account, would you please open the Network tab in the DevTools in your browser (F12 → Network) and then click on the dataset? After that see what are the errors, click on them, and take screenshots please. (You can blur the domain name from the screenshot)
Also, it might be related (and might not) but I remember once it helped with finding out the issue, after the above, could you try change the database language in the user account settings?
Thanks!
Hi @Gassim
This is what’s in the network tab
The only error I can see in the catalina logs is this one. Not sure if it relates to the maintenance dataset management. I have checked the DHIS2 logs, nothing that relates to the problem.
Blockquote 16-Jan-2023 08:59:40.481 INFO [https-jsse-nio-443-exec-9] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name [{“id”:1,“jsonrpc”:“2.0”,“method”:“login”,“params”:{“login”:“459UZRybRrtZTcgcfDy8hCH2vWiurwdatVyZTtFhLPUrV7bHYSaWFL4EbzGRSjYh3z9roD8FWVyDvBtuc1TVWF187zvxQQy”,“pass”:“x”,“agent”:"XMRig/6.15.3 ]. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:419)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:271)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1789)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:834)
Regards,
Cynthia
It would be great if you could report this issue in Jira @cynthia. We suspect the Tomcat log error might not be related. Would be great if you could look for other error-related content in your Tomcat log, nginx log and Javascript browser console.
best regards,
Lars
