I could make this work by using the following code:
public override void PostConfigureServices(ServiceConfigurationContext context) { var configuration = context.Services.GetConfiguration(); var serverName = configuration.GetValue<string>("Schedule:ServerName"); var workerCount = configuration.GetValue<int>("Schedule:WorkerCount"); if (!string.IsNullOrEmpty(serverName) && workerCount > 0) { Configure<AbpHangfireOptions>(options => { options.ServerOptions = new BackgroundJobServerOptions { WorkerCount = workerCount, ServerName = serverName, Queues = new string[] { "default" , "logs"}, }; }); } base.PostConfigureServices(context); }
Still cannot limit the execution time for job instance, so any job does not work more than 5 minutes for example
Thank you for your response, Can you provide me more details about the first point:
Typically there is only one hangfire server per application instance, you can use AbpHangfireOptions to create hangfire server instance if you want.
Currently I add hangfire using the following code:
GlobalConfiguration.Configuration.UseSqlServerStorage(configuration.GetConnectionString("Default-hangfire"));
context.Services.AddHangfire(config =>
{
config.UseSqlServerStorage(configuration.GetConnectionString("Default-hangfire"), options: ops);
});
Thank you
Dear Support team, any update on the original issue?
Hello,
What is your angular version?
Is the defaultProject property exists in your
angular.json
?We know defaultProject deprecated with angular 14. And we fixed proxy generation. The fix will be available in 6.0.2
Same error here, abp version 6.0.1, prompt enter target Angular project to place the generated code. when execute
generate-proxy -t ng
for the Application Module project type. So what's the time for releasing 6.0.2?
That does not solve the problem!
Dear Support team, any update on the original issue?
Any update Please :) ?
Thank you!
It worked!, I will do some tests and confirm if there is no issues
The defaultProject in angular.json is already set to my project correctly, I did not change it and it was working.
Angular CLI: 12.0.5 Node: 14.18.0 Package Manager: yarn 1.22.5 OS: win32 x64 Angular: 12.0.5
and this is a subset of my packages: "@abp/ng.components": "~4.2.1", "@abp/ng.core": "~4.2.1", "@abp/ng.setting-management": "~4.2.1", "@abp/ng.theme.shared": "~4.2.1", "@angular-devkit/build-ng-packagr": "^0.1002.0", "@angular/animations": "~12.0.2", "@angular/common": "~12.0.2", "@angular/compiler": "~12.0.2", "@angular/core": "~12.0.2", "@angular/fire": "^6.1.5", "@angular/forms": "~12.0.2", "@angular/platform-browser": "~12.0.2", "@angular/platform-browser-dynamic": "~12.0.2", "@angular/router": "~12.0.2", "@volo/abp.commercial.ng.ui": "~4.2.1", "@volo/abp.ng.account": "~4.2.1", "@volo/abp.ng.audit-logging": "~4.2.1", "@volo/abp.ng.identity": "~4.2.1", "@volo/abp.ng.identity-server": "~4.2.1", "@volo/abp.ng.language-management": "~4.2.1", "@volo/abp.ng.saas": "~4.2.1", "@volo/abp.ng.text-template-management": "~4.2.1", "@volo/abp.ng.theme.lepton": "~4.2.1", on devDependencies:
I tried: "devDependencies": { "@abp/ng.schematics": "^4.2.1" and tried "@abp/ng.schematics": "^4.3.3", "@angular-devkit/build-angular": "^12.0.5", "@angular/cli": "^12.0.5", "@angular/compiler-cli": "~12.0.2", "@angular/language-service": "~12.0.2", "@types/jasmine": "~3.5.0", "@types/jasminewd2": "~2.0.3", "@types/node": "^12.11.1",
I did not understand your last post line, do you want me to upgrade abp cli to 6.0.2? what about other tools?
The issue was resolved not because the previous solution, There was an issue in (Cross Origin Resource) therefor there was an issue in loading the expiry dates