Got 500 when creating new message format #53
Comments
|
Hmm. So this happens just when you click on 'create new message format' link from /configuration/messageFormat ? |
|
Hi @Crim , Thanks for your reply. |
|
Hmm are you able to share your jar and see if i can reproduce it? Are your dependencies included in the jar? |
|
The jar contains lots of company code which I may not able to share, but will sharing the deserializer class help too? |
|
Yea I had a feeling that might be the case. I'm betting it has to do with how the dependencies are or aren't packaged in the jar. Are you able to paste the entire stack trace? |
|
I think you are right. |
|
The first stack trace I had attached is misleading because I actually have two issues here: I have the webview tool running on two places: my localhost and my AWS instance. I have one test jar file which I am able to create message format succesfully using my AWS instance but got 500 when create it when the tool is running on local machine. In this case, the error I got in the log is like this: org.thymeleaf.exceptions.TemplateInputException: Error resolving template "/configuration/messageFormat/create", template might not exist or might not be accessible by any of the configured Template Resolvers Please note that for this one I am using exactly the same configuration - same jar, same class. Don't understand why it worked when the client is running on AWS and doesn't work when running from my local... |
|
yea the 2nd one seems odd...I'll dig into that one more closely locally here and make sure I haven't screwed something up. The first stack trace to me reads like it can't find the dependency. Do you package an uber jar? In the examples project this is how it builds the uber jar using maven, tho there are many different ways to accomplish the same thing. |
|
I guess that's the root cause as you said for the first issue, I will make sure my jar contains all the dependencies and try it on AWS again. Meanwhile will see if you can reproduce my issue in your local. |
|
Will do |
|
Hi @Crim , I had the new jar ready with dependencies, but then I got another exception: This time my jar file size is big, to resolve this issue, is it something you can help from your end like increase the maximum size? |
|
Yep, give me a few minutes, there may be a setting you can drop in your config file to adjust it. |
|
Are you using the docker image? If so might require some work to make changes to the config file persist. If you're using the .zip distribution, should be pretty simple tho: Open up your config.yml file and add the following lines: spring:
http:
multipart:
max-file-size: 15MB
max-request-size: 15MBobviously adjusting 15MB to whatever you need. Then try restarting the service. |
|
Yes, I am using docker image. I can wait for the update, no worry. |
|
Yea I can publish an updated image to docker hub real quick with higher limits. Longer term I need to make it so you can easily adjust the config. |
|
Ok, I believe I published a new dockerhub image with the limit raised to 64MB. |
|
Thanks for the quick response, I can confirm this issue( jar file size) is being addressed now. |
|
All working then? |
|
I have other issue which I believe it's on my end so far. I am still got stuck with creating message format when the client is running on my local which is using windows 10 |
|
Are you running it under Docker in windows? Or natively? |
|
I am running it natively in my windows machine |
|
Cool, I'll fire up a windows VM and see if I can replicate it. |
|
Yep, replicated it under windows. I'll see if I can work out whats going on here. |
|
So I was able to fix the 500 error.... but I'm still unable to successfully upload a jar under windows. I'm guessing something must be handled in a way that's not currently compatible with windows. I'll have to spend some more time playing around with it and figure out exactly whats preventing it from working. |
|
cool, you are able to reproduce it. Thanks for the investigation, for now I will set up my linux environment to run the client. |
|
I believe this should be fixed via #164 |
Hi @Crim ,
Thanks for this awesome project!
I am trying to play around with this tool and had two custom deserializer ready for test purpose.
I am able to add one of them successfully, but for the other one always got 500.
The two custom deserializer both implement the kafka deserilize interface but with different logic inside.
Exceptions in the log is as below:
2018-01-25 15:10:01.375 ERROR 18792 --- [nio-8080-exec-9] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.thymeleaf.exceptions.TemplateInputException: Error resolving template "/configuration/messageFormat/create", template might not exist or might not be accessible by any of the configured Template Resolvers] with root cause
org.thymeleaf.exceptions.TemplateInputException: Error resolving template "/configuration/messageFormat/create", template might not exist or might not be accessible by any of the configured Template Resolvers
at org.thymeleaf.engine.TemplateManager.resolveTemplate(TemplateManager.java:870) ~[thymeleaf-3.0.7.RELEASE.jar!/:3.0.7.RELEASE]
at org.thymeleaf.engine.TemplateManager.parseAndProcess(TemplateManager.java:607) ~[thymeleaf-3.0.7.RELEASE.jar!/:3.0.7.RELEASE]
at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1098) ~[thymeleaf-3.0.7.RELEASE.jar!/:3.0.7.RELEASE]
at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1072) ~[thymeleaf-3.0.7.RELEASE.jar!/:3.0.7.RELEASE]
......
Any clue about this issue?
The text was updated successfully, but these errors were encountered: