ABP CLI 7.4.2 ABP Suite 7.4.2 Node.js v18.19.0 Angular CLI: 17.0.6 Node: 18.19.0 Package Manager: npm 10.2.3 OS: darwin arm64
Create new project Microservice
abp new Abc.Project -t microservice-pro -u angular --version 7.4.2
follow the rest based on the official document (https://docs.abp.io/en/commercial/latest/startup-templates/microservice/create-new-microservice)
Create a new Microservice module to the existing project solution
abp new SaleService -t microservice-service-pro --version 7.4.2
follow the rest based on the official document (https://docs.abp.io/en/commercial/latest/startup-templates/microservice/add-microservice#authserver-configuration)
Suite-log 2023-12-14 11:00:45.935 +08:00 [INF] 10/11 - AngularUiGenerateWithSchematicsCommand started... 2023-12-14 11:00:45.938 +08:00 [INF] Running the Angular Schematics command: node run-schematics.mjs '/Users/ij/Documents/Development/Abp_Io/Project/apps/angular/.suite/schematics/node_modules/.bin/ng' g '.suite/schematics/collection.json:entity' microservice-pro Bkrm.Crm.SaleService '/Users/ij/Documents/Development/Abp_Io/Project/services/sale/.suite/entities/DemoEntity.json' '/Users/ij/Documents/Development/Abp_Io/Project/apps/angular' 2023-12-14 11:00:46.839 +08:00 [INF] Angular Schematics command failed. /Users/ij/Documents/Development/Abp_Io/Project/apps/angular/.suite/schematics/node_modules/execa/lib/error.js:60 error = new Error(message); ^
Error: Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Bkrm.Crm.SaleService --source /Users/ij/Documents/Development/Abp_Io/Project/services/sale/.suite/entities/DemoEntity.json [Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace. at makeError (/Users/ij/Documents/Development/Abp_Io/Project/apps/angular/.suite/schematics/node_modules/execa/lib/error.js:60:11) at handlePromise (/Users/ij/Documents/Development/Abp_Io/Project/apps/angular/.suite/schematics/node_modules/execa/index.js:118:26) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async file:///Users/ij/Documents/Development/Abp_Io/Project/apps/angular/.suite/schematics/run-schematics.mjs:6:20 { shortMessage: 'Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Bkrm.Crm.SaleService --source /Users/ij/Documents/Development/Abp_Io/Project/services/sale/.suite/entities/DemoEntity.json', command: '.suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Bkrm.Crm.SaleService --source /Users/ij/Documents/Development/Abp_Io/Project/services/sale/.suite/entities/DemoEntity.json', escapedCommand: '".suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" --template microservice-pro --target Bkrm.Crm.SaleService --source "/Users/ij/Documents/Development/Abp_Io/Project/services/sale/.suite/entities/DemoEntity.json"', exitCode: 1, signal: undefined, signalDescription: undefined, stdout: '', stderr: '[Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.', failed: true, timedOut: false, isCanceled: false, killed: false }
Node.js v18.19.0
2023-12-14 11:00:46.843 +08:00 [INF] 10/11 - AngularUiGenerateWithSchematicsCommand completed. | Duration: 907 ms.
Hi,
Sorry my bad, we've created an issue i'm working on it
hi, any fixing on this? or any workaround?
Suite fails when generating angular front-end in microservice solution
Steps to produce:
- Create new microservice solution with
abp new Test -t microservice-pro -u angular -csf- Migrate databases and launch project
- Use suite to generate a new entity in the ProductService
- Observe suite produces a success message:
- Re-load the angular UI
- Observe the permission for the new entity is created, but no UI has been added.
I've reverted Cli and Suite to 7.3.3 and confirmed that this sequence works correctly in the previous version.
This is the suite log output showing the error:
2023-10-21 18:18:10.157 +01:00 [INF] 1/14 - EntityGenerateCommand started... 2023-10-21 18:18:12.449 +01:00 [INF] 1/14 - EntityGenerateCommand completed. | Duration: 2287 ms. 2023-10-21 18:18:12.449 +01:00 [INF] 2/14 - RepositoryCommand started... 2023-10-21 18:18:12.583 +01:00 [INF] 2/14 - RepositoryCommand completed. | Duration: 134 ms. 2023-10-21 18:18:12.583 +01:00 [INF] 3/14 - ManagerCommand started... 2023-10-21 18:18:12.625 +01:00 [INF] 3/14 - ManagerCommand completed. | Duration: 41 ms. 2023-10-21 18:18:12.625 +01:00 [INF] 4/14 - AppServiceCommand started... 2023-10-21 18:18:18.596 +01:00 [INF] 4/14 - AppServiceCommand completed. | Duration: 5970 ms. 2023-10-21 18:18:18.596 +01:00 [INF] 5/14 - ProxyControllerCommand started... 2023-10-21 18:18:18.627 +01:00 [INF] 5/14 - ProxyControllerCommand completed. | Duration: 31 ms. 2023-10-21 18:18:18.627 +01:00 [INF] 6/14 - PermissionCommand started... 2023-10-21 18:18:18.677 +01:00 [INF] 6/14 - PermissionCommand completed. | Duration: 49 ms. 2023-10-21 18:18:18.677 +01:00 [INF] 7/14 - ApplicationObjectMappingCommand started... 2023-10-21 18:18:18.692 +01:00 [INF] 7/14 - ApplicationObjectMappingCommand completed. | Duration: 14 ms. 2023-10-21 18:18:18.692 +01:00 [INF] 8/14 - UnitTestCommandCommand started... 2023-10-21 18:18:18.762 +01:00 [INF] 8/14 - UnitTestCommandCommand completed. | Duration: 70 ms. 2023-10-21 18:18:18.762 +01:00 [INF] 9/14 - GenerateProxyCommand started... 2023-10-21 18:18:18.814 +01:00 [INF] 9/14 - GenerateProxyCommand completed. | Duration: 52 ms. 2023-10-21 18:18:18.815 +01:00 [INF] 10/14 - MvcUiGenerateCommand started... 2023-10-21 18:18:19.016 +01:00 [INF] 10/14 - MvcUiGenerateCommand completed. | Duration: 201 ms. 2023-10-21 18:18:19.016 +01:00 [INF] 11/14 - MvcObjectMappingCommand started... 2023-10-21 18:18:19.035 +01:00 [INF] 11/14 - MvcObjectMappingCommand completed. | Duration: 19 ms. 2023-10-21 18:18:19.035 +01:00 [INF] 12/14 - MvcMenuContributorCommand started... 2023-10-21 18:18:19.101 +01:00 [INF] 12/14 - MvcMenuContributorCommand completed. | Duration: 65 ms. 2023-10-21 18:18:19.101 +01:00 [INF] 13/14 - AngularUiGenerateWithSchematicsCommand started... 2023-10-21 18:18:51.525 +01:00 [INF] Running the Angular Schematics command: node run-schematics.mjs '/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/.bin/ng' g '.suite/schematics/collection.json:entity' microservice-pro Test.ProductService '/Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json' '/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular' 2023-10-21 18:18:56.009 +01:00 [INF] Angular Schematics command failed. /Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/execa/lib/error.js:60 error = new Error(message); ^ Error: Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Test.ProductService --source /Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json [Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace. at makeError (/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/execa/lib/error.js:60:11) at handlePromise (/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/execa/index.js:118:26) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async file:///Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/run-schematics.mjs:6:20 { shortMessage: 'Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Test.ProductService --source /Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json', command: '.suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Test.ProductService --source /Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json', escapedCommand: '".suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" --template microservice-pro --target Test.ProductService --source "/Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json"', exitCode: 1, signal: undefined, signalDescription: undefined, stdout: '', stderr: '[Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.', failed: true, timedOut: false, isCanceled: false, killed: false } Node.js v18.17.1 2023-10-21 18:18:56.025 +01:00 [INF] 13/14 - AngularUiGenerateWithSchematicsCommand completed. | Duration: 36923 ms.
any fixing on this?
Hi Anjali,
Noted.
We have gone through the discussion as mention, unfortunately it was a different problem.
Yes, we do have cache server for Redis.
Thanks.
Hi Anjali,
Any findings on this matter.
Thanks.
Hi Anjali,
Thanks.
However could you check why micro-service gateway has issue with http/2 and TLS/SSL in Chrome.
We notice that Chrome works with http/2 and TLS/SSL with Angular and Auth Server but not the gateway.
Chrome also works with our previous application that using ASP.NET Zero (http/2 and TLS/SSL).
Thanks.
Hi Anjali,
We found a same issue https://stackoverflow.com/questions/74889221/chrome-edge-safari-http2-requests-getting-stalled-for-every-6th-request-for-up and manage to resolve it by disable http2.
However we are not clearly understand how does http2 works.
Understand that http2 reduce overhead by just having a single tcp connection. However, could it be a bottleneck since http2 just using a single tcp connection.
Thank you for your support and commitment.
Thanks!
Hi Anjali,
We have tested the above link and notice that the response time for preflight have some improvement but in angular chrome the issue still persist.
The pre-flight is fine. Refer below.
The xhr request is the issue. Refer below.
Fyi, we will try to promote the micro service to use public network instead of private.
Also we have tried below approach to understand further:
https://support.google.com/chrome/thread/49442697/xhr-requests-pending-for-a-long-time-in-recent-chrome-updates-when-not-recording-in-performance-tab?hl=en. Not working
Using a lower version chrome v90. Not working
Appreciate your support for the issues.
Do let us know if you required any additional information.
Thanks.
Dear Anjali,
We have tested the mentioned steps, however the issue still persist. Please advise.
Do let us know if you required any additional information.
Thanks.
Hi Anjali,
Just to add in.
We notice that if we use non SSL protocol (http throughout the entire back end solution), there is no performance issue.
When we use https only we face the issue.
Refer below screenshot. Preflight and polyfill take 1.6 min to response.
When we continue to click other menu. its fine. but after few click again the issue come back.
We suspect the solution having a handshake issues. However for Auth and Gateway are using a valid certificate.
Also there is no performance issue in Firefox and Safari browser.
Auth
Gateway
We also notice if we directly call the APIs via Postman, there are no performance issue.
Only we use Angular in Chrome and Edge browser we face the performance issue.
Do let us know if you required any additional information.
