Hi,
How we can configure seperate endpoints for Read (Multiple) and write operations
regards, Harshit
Any Update on it??
when i m using RedisCache , i m getting an issue in WidgetDefinitionCacheManager class on GetAll function but it is working fine with inMemory cache , General details about the product - 1] asp.net zero version - 13.0.0 2] "Abp.AspNetCore" Version="9.2.2" 3] Abp.RedisCache" Version="9.2.2"
For reference please find below images - in this image i m getting inMemory cach and it is working fine but
in this i m getting RedisCache and this is giving me error
NotSupportedException: Deserialization of interface types is not supported. Type 'Abp.Authorization.IPermissionDependency'
Hi @kansoftware
Could you test with a tool or redis-cli to see if you are able to connect to your redis instance ?
Yes, we can connect to the Redis server using telnet, but we are unable to establish a connection in our application
Thanks
But Redis not getting connect.
Currently we have hosted application on linux server which is behind load balancer and in case enable scaling and multiple instances are running. Chat module is not working.
I believe we need to configure backplane looking at documentation
Do you have steps configuration we are using latest version of aspnetzero.
Focus is lost in abp.confirm.message dialog when its show on modal pop.
We are facing this issue after upgrading project from Version(9.1.0) to Version(12.0.0).
abp.notify.warn(data.message) and abp.notify.error(data.message) gives a blank badge at the bottom of the screen while abp.notify.success(data.message) and abp.notify.info(data.message) works on the same page. path of js is : \src\CDP.Web.Mvc\wwwroot\view-resources\Views\FolderName\File.js
We are facing this issue after upgrading project from Version(9.1.0) to Version(13.0.0).
related ticket
https://support.aspnetzero.com/QA/Questions/2356/Elastic-Redis-Cache-AWS
We are facing similar issue
We are getting following error
RedisConnectionException: It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code.
Telnet is also working
Regards,
We are facing similar issue
We are getting following error
RedisConnectionException: It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code.
Telnet is also working
Regards,
Actually we are running both versions on the server but we only see these waits for the new application
Can you please check why the newer version introduce the waits.
its happening on production so request you for a quick response
Regards