New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not run java azure function locally, created using maven archetype:generate given on microsoft site using mvn azure-functions:run, not showing error. Its simply freezing. #167
Comments
I had the issue, too.
If I try to "cd" to the staging directory and call "func start" [2021-03-26T08:26:37.096Z] Job host started Functions:
(...Maybe this is a workaround) I tried to inspect the running process with the jconsole. The main thread is blocked at: Name: main Stack trace: .... maybe this helps somehow |
Maybe this is related to the maven plugin and not to the archetype |
Thanks a lot luzuz! I am extremely thankful to you.it worked the way you mentioned. I was struggling since 2 days as I am new to azure functions. |
@Luzuz Thanks a lot for your comment. @sarojbala123 Thanks for your report and really sorry for the trouble. We meet some compatibility issues with the latest function core tools. The issue has been addressed in microsoft/azure-maven-plugins#1367, will be shipped in functions maven plugin 1.10.0. Before the release, you may use core tools 3.0.3331 or previous version or invoke func host start in staging folder as a workaround. |
I also tried running Spring boot azure function using TimeTrigger by following below steps: instead of HttpTrigger I used TimeTrigger Its showing a new error now as shown below: I have used local.setting.json properties as shown |
Followed every step and verified many times mentioned in below link:
https://docs.microsoft.com/en-us/azure/azure-functions/create-first-function-cli-java?tabs=bash%2Cazure-cli%2Cbrowser
Below is screenshot of cmd running mvn azure-functions:run command
I tried to run mvn azure-functions:run -X and its showing below and freezing:
The text was updated successfully, but these errors were encountered: