I follow and implement the Kafka integration base on document you've send but still rollback is not working. even I manually throw exception to consumer.
still the behavior is the same once consumer fail my transaction in publisher success.
Hi
I have some doubt regarding Kafka integration how the publisher notify if one consumer fail? and how the unitofwork works
ex. **Publisher: ** I want to keep copy of country to all microservice.
if consumer fail I want to rollback the transaction in publisher?
Is this possible using the build in distributed events using kafka?
Thanks
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
If you're creating a bug/problem report, please include followings:
This issue is happen intermittent.
docker image build using gitlab agent.
can you advice the stable solution for this issue and what is the possible issue why sometimes this happen.
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
If you're creating a bug/problem report, please include followings:
I have requirements to implement entity synchronizer in my project using abp version 6.0 but this functionality is exists in version 7.0+., how can I implement this manually without upgrading to latest version is this possible?
reason why we don't want to upgrade to latest version is we still using identity server if we upgrade to latest version we are forcing to change many things in current project.
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
If you're creating a bug/problem report, please include followings:
perfect! this is what i need thank you.
we are not using multitenant the requirement is to allow merchant to (modified or create) their own email template and those template is accessible only for them base on their username and password. they have their own dashboard , menu and access right one of their rights is to create their own email template.
I have requirement to use the current Text Template Management Module but each customer are allowed to modified the existing temple.
ex. Default Template: Email Sending
Merchant1 -> Template: EmailSending -> Content: {{code}} {{link}} "with their own logo and designed" Merchant2 -> Template: EmailSending -> Content: {{code}} {{link}} {{name}} "with their own logo and designed"
If merchant1 login to the admin portal he/she will allowed to view/edit their own email template.
Please let me know if this kind of requirement is possible?.
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
If you're creating a bug/problem report, please include followings
No "access control allow origin" header is present on requested encounter error when implementing nginx-ingress cache for both authserver and admin page.
to replicate the issue Step 1 - (Fail) ingress configmap file.
admin portal ingress configuration
authserver ingress configuration
Step 2 - (Success) This is completely improve the application loading performance into 70%
ingress configmap file.
admin portal ingress configuration
or maybe its not good idea to cache the authserver because of issuance of token and cookie. please advice.
Regards Moises B. Bas If you're creating a bug/problem report, please include followings: